Yes the sync is still scheduled. Got it fixed. Turns out that the update service didn't start. I had no idea why because there were no error in the event log (checked application and system). No evidence that it even tried to start since May 28. But once I manually started the service, everything is fine now.
I could figure out why it didn't start, though. The server was rebooted on May28 due to a unscheduled power outage....
"Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:#CpPl6WrHHA.4548[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > "mlai" <mlai[ at ]community.nospam> wrote in message > news:%23BSwDTWrHHA.1380[ at ]TK2MSFTNGP04.phx.gbl... >> Had WSUS3.0 installed and it worked initially without a hitch. However, >> since May28, it has stopped synchronizing. I checked the event logs and >> there were no errors. In fact, the synchronization does not even start. >> The client machines are still updating their status with the WSUS3.0 >> server and the admin interface shows the last synch on May28 and no >> failure and no success since. >> >> Anything I can do to rectify? If I reinstall the WSUS3.0, will it kill >> the existing database and will I have to start all over again? > > No... but if it's not starting, did you check the Options | > Synchronization Options screen and make sure the sync is still > *scheduled*? > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> .... > > > >> > >
|