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.
This process interferes with the SCCM accounts created at setup.
This behavior is usually seen at a central site, but could potentially occur anywhere.
Work from any errors reported in the component log files on the site server: sinvproc.log, dataldr.log, sinvproc.log, dataldr.log, One potential cause for this type of error is an inventory resynchronization.
Once the package is created, it is automatically deployed to deployment point and servers perform updates on their maintenance period.
This update method should not be used on complex environment as Hyper-V cluster or Exchange infrastructure.
To create Automatic Deployment Rule open SCCM console, go to Software Library and right click on Automatic Deployment Rule and click on New: So I create an Automatic Deployment Rule called « Baseline – W2012R2 » with the Patch Tuesday template.
The scheduler for creating update package can be fine-grained configured.
It is possible for example to create update package automatically every second Tuesday of each month.
– The second scenario is that the cache will be cleared any time the collection evaluator becomes idle for any period of time.
The Coll Eval logs the server shows that it is extremely busy, with some collections starting to evaluate 20 minutes after they were scheduled. An example CSV filtered on Update Schedule of Every 59 Minutes looks something like this: 5.