replica server have more updates than master one Malte 6/21/2007 7:07:02 AM Hi, if have a WSUS 3 Server and a WSUS 3 in replica mode. Issue is that the replica server have more updates than the master one. Every sync (replica from master) will cause that ,several updates that was already declined on replia, are set back to unapproved. But these updates are not existing on master server !! So no way to decline them there. The Updates that are found again and again by replica are revoked updates. I already did a reset with wsusutil on both systems. Any idea ? Thanks. BR, Malte

Re: replica server have more updates than master one "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/22/2007 3:46:14 AM "Malte" <Malte[ at ]discussions.microsoft.com> wrote in message news:F1FC5C4E-549C-48A6-B830-8C6EC9A7F111[ at ]microsoft.com... [Quoted Text] > Issue is that the replica server have more updates than the master one. > > Every sync (replica from master) will cause that ,several updates that was > already declined on replia, are set back to unapproved. They *will* be set back to the status as it exists on the master server at every sync. You cannot configure approvals at the replica server, only at the master. If the updates are not declined on the master, they will not be declined at the replica(s). > But these updates are not existing on master server !! This can also be an issue if the master server has had a "Server Cleanup" performed without consideration as to the status of the replica servers. If the updates have been purged from the master server, the replica has no way to get status information on the approval status for those updates, contained with its own database, ergo the updates are reverted to the *default* status, which is "Not Approved" for lack of any other guidance. > Any idea ? Yes. Uninstall the replica server and trash the database. Keep the content. Reinstall the replica server and resync with the master server. Run the server cleanup wizard on the replica server to purge the uneeded content from the filesystem. Wait 24 hours for the replica's assigned clients to report back in (or force the reporting by running 'wuauclt /detectnow' at each client). -- 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 .....

Re: replica server have more updates than master one Malte 6/22/2007 6:52:00 AM Hi works ! Thanks "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Malte" <Malte[ at ]discussions.microsoft.com> wrote in message > news:F1FC5C4E-549C-48A6-B830-8C6EC9A7F111[ at ]microsoft.com... > > > > Issue is that the replica server have more updates than the master one. > > > > Every sync (replica from master) will cause that ,several updates that was > > already declined on replia, are set back to unapproved. > > They *will* be set back to the status as it exists on the master server at > every sync. You cannot configure approvals at the replica server, only at > the master. > > If the updates are not declined on the master, they will not be declined at > the replica(s). > > > > But these updates are not existing on master server !! > > This can also be an issue if the master server has had a "Server Cleanup" > performed without consideration as to the status of the replica servers. If > the updates have been purged from the master server, the replica has no way > to get status information on the approval status for those updates, > contained with its own database, ergo the updates are reverted to the > *default* status, which is "Not Approved" for lack of any other guidance. > > > > Any idea ? > > Yes. > > Uninstall the replica server and trash the database. Keep the content. > > Reinstall the replica server and resync with the master server. > > Run the server cleanup wizard on the replica server to purge the uneeded > content from the filesystem. > > Wait 24 hours for the replica's assigned clients to report back in (or force > the reporting by running 'wuauclt /detectnow' at each client). > > > > -- > 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 > ..... > > >