SCCM Issue Tracker

Today I face one issue with the AD discovery that after run the AD discovery it always takes 1 or 2 OU to search out of 4 OU. I check from adsysdis.log valid container always shows 2. After searching over the net I found one solution from MS that “ Microsoft has confirmed that this is a problem in the Microsoft products ” and kb article for this is KB978757. Environment: SCCM 2007 R3 Problem: I have set 4 OU in AD system discovery .2 is for XP And 2003 and rest for win7 and 2008 . But after running the discovery method in adsysdis.log shows 2 OU is valid. Where Workstation and server is for XP/win 2003 and WorkstationWP and ServerEP for Win 7 /2008 Solution:   Check this hotfix from MS . After applied the Hotfix run the discovery by force and wait for a few minutes . And a few minutes later you got a big smile :)))))

I have written this post on behalf of my one best friend Christian, Who suggest me to do some work with obsolete jobs  in SCCM inboxes whenever a site is removed and preinst / deljob is not helping to stop ongoing jobs.         How to Identify obsolete jobs You're Seeing this error because SMS is trying to contact to site S3F and is unable To. There are several possible reasons for this, the most likely being that the Target site is offline or unreachable for some reason. Your first course of Action should be to check that the target Site is up and running and Functioning correctly, including network connectivity. But in most cases, the The error is being generated in the log because although the Site had been removed From the SMS hierarchy, there were still outstanding jobs in SMS waiting to be Sent to the target Site.       Workaround to solve this issue       Note: It's A good idea once you'v...