Hello everyone

I have a 2007 r2 SCCM and 3.0 WSUS environment.  I am trying to troubleshoot why my deployment packages are empty.

Looking at WSUS content folder, I have nearly 15 GB of data in there that appears to be all of the update information required.  However when I attempt to Download the updates through SCCM from the internet, SCCM attempts to download, appears to show that it is finished but each update says "Unable to contact server - timeout".   Now I know this server can access the internet since WSUS has no problems connecting to Microsoft Updates.  

Is the server being contacted the WSUS server?  I downloaded the superflows on this but it really wasnt clear to me.  if the server being contacted is Microsoft Update, then there really should be no reason why there is a communication issue since the Proxy is set up through SCCM and WSUS uses that info to contact Microsoft Update.

What ends up is that in the directory where the updates deployments are stored, is a whole lot of empty GUID.1 directories, and no updates are deployed.

if you folks have an idea, please fire em off... 

Matthew 

Hi,

it is actually the computer where you run the sccm admin console that does the downloading of updates so you can use another computer with the console installed instead of the sccm site server.

The WSUS server content is never used when you use WSUS together with SCCM, it is only used to download information about available updates that the then shown in the admin console and by the clients when the clients scan for updates, then they use the wsus server as well to download information about which updates it sould scan for.

Regards,
Jrgen

Ok thank you... that clears that up...

now... as for the unable to download the updates... SCCM downloads them directly from Microsoft Updates? 

Correct. If you open the properties of any update and go to the content location tab, you can actually see the URL it is using for that update.

*sigh*

Make sure that not only does your SCCM point to the proxy, but also make sure that your Internet Options in the control panel also points there as well... 

*grumble*

Thanks for your input guys.. it was helpful.

Matthew

• Marked as answer by Matthew Ornawka 11 hours 48 minutes ago

*sigh*

Make sure that not only does your SCCM point to the proxy, but also make sure that your Internet Options in the control panel also points there as well... 

*grumble*

Thanks for your input guys.. it was helpful.

Matthew

• Marked as answer by Matthew Ornawka Friday, April 17, 2015 7:50 PM

*sigh*

Make sure that not only does your SCCM point to the proxy, but also make sure that your Internet Options in the control panel also points there as well... 

*grumble*

Thanks for your input guys.. it was helpful.

Matthew

• Marked as answer by Matthew Ornawka Friday, April 17, 2015 7:50 PM

*sigh*

Make sure that not only does your SCCM point to the proxy, but also make sure that your Internet Options in the control panel also points there as well... 

*grumble*

Thanks for your input guys.. it was helpful.

Matthew

• Marked as answer by Matthew Ornawka Friday, April 17, 2015 7:50 PM

*sigh*

Make sure that not only does your SCCM point to the proxy, but also make sure that your Internet Options in the control panel also points there as well... 

*grumble*

Thanks for your input guys.. it was helpful.

Matthew

• Marked as answer by Matthew Ornawka Friday, April 17, 2015 7:50 PM