This week I enabled the Software Updates feature. I used a separate IIS web site instance for these updates, which configures the server ports 8530/31 to be the ports that the clients will connect to, versus 80/443. WSUS installations went smoother than silk, and the Software Updates role enabled with no errors on first go-round. First time I've added a role that didn't result in errors immediately after installation. I'm getting better. ;) I even synced to Microsoft Update, pulled updates of my selected products down, and downloaded them to the network share where the distribution point will grab them from. However, once I deployed the updates, the clients did not receive the updates. I was confused as to why, until I checked the logs in C:\Windows\CCM\Logs on the clients.
I started out with UpdatesDeployment.log and saw this message repeated:
Obviously this error does not tell me much, but did confirm that the client is receiving the deployment but cannot continue due to this error and the updates will be made available for install on this machine.
After further checking, I looked at the WUAHandler.log and noticed this gem:
Group policy. Of course. I bet my GPO's were still pointing the clients to the old WSUS server. Sure enough changed the policy to the FQDN (make sure you do this - ex: http://myserver.company.com:8530) and the updates started flowing through the SCCM client on the machines. Huge achievement. Hope this can help someone! Endpoint integration coming up next! Hoping for a smooth transition from FCS.....(^_^')
