It does however get your deployment solution up and running again.Message ID 576, 578, & 579: Possible reasons for this message: The Windows Server that SCCM was installed on was promoted to a Domain Controller after the installation or installation occurred on a Domain Controller that was demoted to a Member server.
For this ,created collection to get computers with MS office 2010 ,created application for MS office 2013 upgrade and deploy to collection .Looking at the server side, everything looked fine, so it had to be something on the client side. There was no Client Certificate for the client I’ve seen this before with SCCM 2007, and then the problem was the client was still in Provisioning Mode.Provisioning Mode is a mode that the client is in during OSD, which blocks policies from being applied during the installation.The other day I had an issue at a customer, where the installations of new computers ran without any errors, but once logging in, it was obvious that everything was not right.The reason why we noticed that something was wrong, was that all new computers that had been installed, were missing the SCEP client. Fewer Actions than usually for the Configuration Manager client 3.