Hi,
In may we had to do a restore of our lab environment because of a server crash.
Primary site was restored via a SCCM backup. Wsus was reinstalled on the server. Most of the things seemed fine after the restore but working for a few months, some skeletons are falling out of the closet...
eg:
Custom Hardware monitoring was not working anymore for new machines, seems that configuration.mof file was not restored in the inboxes folder... but we have one bigger issue;
We can't install updates via SCCM that were released and downloaded before the server crash. Whenever we create an UG that contains updates from before may (server crashed in may), the UG does not work, the UpdatesDeployment.log keeps saying: "Assignment already in progress state (AssignmentStateDetecting). No need to evaluate". Updates installation is also failing during OSD. The same UG is working if it is deployed to a server that does not need updates from before the crash.
Actions taken:
- checked out all possible loggings, but no errors thisfar, I missing the correct logging I'm sure
- I removed all the downloaded updates from the environment and removed all the UG and deployment packages
- downloaded all the updates again in a new package and created new list
- lists containing updates release after crash are deploying fine. Lists including updates released before crash, don't install
- did NOT reinstall WSUS yet because this was done during the restore
- I had a look into the databases (sccm and Wsus) but could not find any difference between updates from before crash or after, in wsus database all updates had creationdate after crashdate.
Can there be a mismatch between tables in SCCM database and WSUS database?
Is there a logging that shows what "AssignmentStateDetecting" is actually doing?
(environment is now SCCM 2012 R2 SP1 CU1 on 2008 machine WSUS 3.0 SP2)
Thanks
Other recent topics
