I started work at my current company a year and a half ago, I was hired in to run the Desktop Engineering department and perform application automation packaging and work with the current SMS 2003 administrator there to fill the spot of Jr. SMS 2003 Administrator. I have a long experience history in SMS and was set for the position for sure. When the Sr. SMS 2003 administrator left and I moved into his position I knew I was taking on a system that I had no hand in designing. Little did I know how out of tune the system was and what I was in for.
I had started working on cleaning up the SMS 2003 server prior to going to the MMS 2008 in Las Vegas this year, cleaning up collections and groups, correcting reports and queries. Providing better tools and access to our Support Center via reporting, as well as cleaning up and performing weekly maintenance on the server that had been obviously long neglected. When I returned from MMS 2008 the SMS 2003 server had suffered a serious failure while I was gone due to SQL Maintenance not being performed and the drive had filled up due to the .log file not truncating. This in turn caused the SQL DB to come crashing down and SMS 2003 services to halt in a not so happy fashion.
I looked at the road ahead and I could either restore and rebuild SMS 2003 or I could move forward with SCCM 2007, I chose the path of SCCM 2007 and thus far have been completely happy with this choice. Lately I have seen some issues regarding a few of our locations with smaller bandwidth pipe lines and while I have been configuring QOS and Throttling on the SCCM server for clients and site to site communication. When roll outs in mass would occure (Updates, Software Packages) those locations were peaking the bandwidth to almost 100%. After further discovery with WhatsUp Gold I saw they were all reporting back to the Primary Site SCCM Server instead of their Secondary Site (local) Server they should have been.
I started looking at the boundaries in SCCM and found that there may be an issue with the Sites and Services here at my company, the bounadries were imported from the pre-existing SMS 2003 server. The clients were all pointing to the Primary Site instead of the closer sites and while I could find nothing wrong in the SCCM bounadries my attempts to reassign them automatically were failing, they would just go back to the Primary SCCM site.
So I am here working, looking at our AD Sites and Services definitions and working to a way to get my client agents pointing to where they belong....
I will let you know how it goes and document the details on how to correct this if you come across it in your life time, if you have and you have any advice please feel free to contact me.
Thanks