Setup SCCM 2007 on server Windows 2003 sp2. (sccmserv) WSUS on server Server 2008 sp2. (wsusserv) - Port 80 Clients running Windows 7 Professional SP1 All management roles other than update server are on sccmserv. The console shows the site system status for all points running and normal software deployment is running properly. Before I connected the WSusserv to the SCCM console I created a group and sent updates to two computers. These worked perfectly. I've since deleted the group. Problem When I create an update package the clients continue to see no updates. The updatesdeployment log on the client shows no issues.# I'd be grateful for any suggestions. 

Are the updates showing as "required" BTW... There's no reason that I can think of to split WSUS on to it's own server. It does hardly anything and splitting it off just creates unnecessary complexity. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Not on the client - the client reports no updates found. I separated the Wsus server because I found a number of sites recommending this. Also the WSUS server was less busy in network terms than the elderly SCCM one. The client UpdatesDeployment.log shows "No Pending Updates" Thanks Jay    

Hi, What is in the windowsupdate.log file? is the client using thenew SUP? no old Group Policies which are causing the problem? Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

I don't know who would have reccoemnded that but I'd disagree with them. Anyway, that's not helping you so... I'm wondering if the updates are showing as required on the server side in the SCCM console. That would tell me whether or not the clients are reporting that they need the updates. If they are not then we need to figure out why. If they are that's going to most likely be a different issue. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

 I'm unable to paste the contents of the log but it does show the correct address and it shows that it is successfully checking the system. However it finds no updates.

I think you may be right, now I look at the updates in the updates list it shows either 0 or 1 as required for each of them (mostly 0). I'm surprised by this because I'm sure I set them to deploy. I'm very grateful, how would I set this right? Thanks jay

You should see a number of machines "required" before you even deploy the updates. You'd see that in the updates repository. Better yet, are you seeing the correct number of systems in any status? If so what are the majority of them in? I'm guessing unknown? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

You're absolutely right - 595 machines with status unknown.

Do you have an old GPO in-place pointing them to the wrong server for WSUS? You should remove any GPO's such as that. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I've double checked (just now) and the domain gp and the workstation gp both point to the new Wsus server http://wsusserv.domain.local:80. I've checked that connecting to this point works and can download iuident.cab from there. Since you pointed me in that direction I've tried running the script you've posted elsewhere for this issue without any immediate response. I don't know whether one would expect some response straight away. Thanks again for your continued help - its much appreciated!   

I'm not sure what script you are talking about. Sorry. Can you post the client and server logs somewhere or email them to me? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I'd be very glad to send you the logs, are there particular ones which would be useful or should I just dig out all the ones which look relevant. As for the script I got it from http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/94d36993-2aa1-4805-b3f9-f1670ad1a0a6/. It looked as though it might be relevant. thanks again jay

Hi John I happened to look at my config manager setup on my own machine this morning, the screen shot is below. I don't know if this is correct or not. The spssrv01 is the wsusserver. However I wouldn't have thought this was right for the overall management point. Our GP gives the spssrv01 as the update point in Computer Configuration/Admin Templates/Windows Components/Windows Update. I note that there are special ADMs in the Config manager CD - should I be using those - they seem to relate to installation rather than Management point, or should I be pointing my computers to the main Config Manager point. If so is there a way to check which port is correct? Sorry to be so much of a nuisance. Best wishes jay

Actually you should remove all GP's having to do with WSUS. The SCCM client will create local GPO's to do what it needs. That may be your problem. You do need to make sure to set the correct ports when installing the SUP. Normally it's best to install WSUS to use 8530 and 8531 but you also need to specify that in the SUP. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Thanks John I've reset the gps to take all references to automatic updates out. I've forced a gp update on one of the workstations. However the following remains the case: The config manager client still lists spssrv01 as its Management point The Registry setting HKLM/software/microsoft/policies/windowsupdate now point to the SCCM server with the port 8530 - which isn't on offer and the attempt to check for updates errors because it can't find any update service there. I wonder whether I should be removing WSUS back to the original server and taking the SCCM element out?

jay, What time zone are you located in? If I could see this I could probably fix it in less than 30 min. Maybe we could jump on a Live meeting. The fastest way to fix this is to: uninstall the SUP, uninstall WSUS and remove the WSUS database. Install WSUS on the same server that is running SCCM, during the install select to use a custom website and keep the default ports which are 8530 and 8531. Next reinstall the SUP and make sure to also select 8530 and 8531. That should clear up anything that's preventing this from working. It will take you less than 1 hour to complete but it will cause a rather large download to the WSUS server from the internet. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

John that's an incredibly kind offer and I'm really grateful. As it happens I've just been running that exact procedure. I got as far as the synchronisation. I then saw a message in the system status to the effect that "sms wsus configuration manager failed to configure upstream server settings on wsus server". To clear the issues and to reset the proxy settings (although we'd seen no problems in this area before) I tried restarting the server, unfortunately it's stuck going down and I won't be able to get to it physically until tomorrow morning. I'm in the UK. I'm going to try to reset the server tomorrow, double check the config and restart the synchronisation. If I do see issues and you're still willing to tackle this tomorrow I'd be really grateful for your help. Thanks again. Jay

Thanks very much for all your help - it's working now! Best wishes Jay

awesome. I'm glad you got it working.John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|