Search the Community

I realize that this is the 2012 section and my title refers to the 2007 client, but let me explain. A couple years ago there was a failed attempt to utilize Configuration Manager 2007 at the place I am currently working - for some reason it was decided to ditch the project and the server sat unloved for about a year. New management came along and decided to go with Configuration Manager 2012 and we have that set up and are in the process of rolling out Windows 7 and using SCCM 2012 to manage the environment. It's good. I like it. And Windows-Noob has been invaluable in helping is get it operational. The problem lies with the old SCCM 2007 and its client. The server was retired earlier this year but somewhere in our environment is a process that is attempting to install an update to the 2007 agent via WSUS (I should have mentioned that we have an old WSUS server that will be retired once we've migrated everyone over to W7, another instance of WSUS is running on SCCM and W7 machines will be pointed to that via group policy). The update downloads to newly migrated machines even though they are using the latest 2012 agent (which works fine) - the machine then hangs at reboot "Installing update 1 of 1". After an hour or so the update, all 253 KB of it, fails and the reboot continues but I really can't continue the upgrades to W7 while this is happening. I can't find anything in group policy that might be applying the 2007 client to machines and so causing the WSUS update, nor is there anything in logon scripts. Please, does anyone have any suggestions on how to resolve this?