|
|
|
|
"packav" <packav[ at ]discussions.microsoft.com> wrote in message
news:051B2482-A573-41C7-8BB6-9129457C1901[ at ]microsoft.com...
[Quoted Text] > Greetings,
>
> I'm on a recently upgraded WSUS 3.0 with 1 main server and 3 replica
> downstream servers. My replica servers are showing updates with an
> Unapproved
> status, but my upstream server doesn't have any Unapproved updates.
When is the last time the replica(s) successfully synchronized?
Also..since we're primarily talking about legacy updates here (all but one
of the updates in the list is superceded), any chance you DECLINED them on
the upstream server, which is preventing their display as an Unapproved
update?
--
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
.....
|
|
First off, thanks for the reply Lawrence.
I'm basically trying to resolve Not Approved updates showing as needed on
downstream server reports although those same updates are not present / have
a decline status on the main server.
[Quoted Text] >When is the last time the replica(s) successfully synchronized?
I've configured the replicas to synch every night. Also I can do a synch on
demand. No errors reported.
I usually decline any updates that I do not plan on approving at some point.
For example, this image shows that on my main server I have 0 failed or
needed Not Approved updates:
http://i198.photobucket.com/albums/aa166/packav/WSUSex5.jpg
On the replica server, it shows I have 10 failed or needed not approved
updates:
http://i198.photobucket.com/albums/aa166/packav/WSUSex4.jpg
I think I realized the problem just now however. I ran the WSUS clean up
tool on the main server, but not on the replica servers. Seeing as these
updates showing Not Approved are all very old, perhaps they were deleted off
the main server but not the replica servers.
Anyway, I'm going to run that same cleanup tool on the replica servers to
see if that helps.
"Lawrence Garvin (MVP)" wrote:
> "packav" <packav[ at ]discussions.microsoft.com> wrote in message
> news:051B2482-A573-41C7-8BB6-9129457C1901[ at ]microsoft.com...
> > Greetings,
> >
> > I'm on a recently upgraded WSUS 3.0 with 1 main server and 3 replica
> > downstream servers. My replica servers are showing updates with an
> > Unapproved
> > status, but my upstream server doesn't have any Unapproved updates.
>
>
>
> Also..since we're primarily talking about legacy updates here (all but one
> of the updates in the list is superceded), any chance you DECLINED them on
> the upstream server, which is preventing their display as an Unapproved
> update?
>
>
> --
> 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
> .....
>
>
>
|
|
Oddly enough, running the cleanup tool on the replica servers cleaned up
those old Unapproved updates on the updates screen and the reports. It still
bothers me though that they didn't pull the declined status from the main
server though.
"packav" wrote:
[Quoted Text] > First off, thanks for the reply Lawrence. > > I'm basically trying to resolve Not Approved updates showing as needed on > downstream server reports although those same updates are not present / have > a decline status on the main server. > > >When is the last time the replica(s) successfully synchronized? > > I've configured the replicas to synch every night. Also I can do a synch on > demand. No errors reported. > > I usually decline any updates that I do not plan on approving at some point. > For example, this image shows that on my main server I have 0 failed or > needed Not Approved updates: > http://i198.photobucket.com/albums/aa166/packav/WSUSex5.jpg> > On the replica server, it shows I have 10 failed or needed not approved > updates: > http://i198.photobucket.com/albums/aa166/packav/WSUSex4.jpg> > I think I realized the problem just now however. I ran the WSUS clean up > tool on the main server, but not on the replica servers. Seeing as these > updates showing Not Approved are all very old, perhaps they were deleted off > the main server but not the replica servers. > > Anyway, I'm going to run that same cleanup tool on the replica servers to > see if that helps. > > > "Lawrence Garvin (MVP)" wrote: > > > "packav" <packav[ at ]discussions.microsoft.com> wrote in message > > news:051B2482-A573-41C7-8BB6-9129457C1901[ at ]microsoft.com... > > > Greetings, > > > > > > I'm on a recently upgraded WSUS 3.0 with 1 main server and 3 replica > > > downstream servers. My replica servers are showing updates with an > > > Unapproved > > > status, but my upstream server doesn't have any Unapproved updates. > > > > > > > > Also..since we're primarily talking about legacy updates here (all but one > > of the updates in the list is superceded), any chance you DECLINED them on > > the upstream server, which is preventing their display as an Unapproved > > update? > > > > > > -- > > 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> > ..... > > > > > > |
|
"packav" <packav[ at ]discussions.microsoft.com> wrote in message
news:FC733F70-CE81-41B5-8EE3-A76F13404E80[ at ]microsoft.com...
[Quoted Text] > First off, thanks for the reply Lawrence. > > I'm basically trying to resolve Not Approved updates showing as needed on > downstream server reports although those same updates are not present / > have > a decline status on the main server. > >>When is the last time the replica(s) successfully synchronized? > > I've configured the replicas to synch every night. Also I can do a synch > on > demand. No errors reported. > > I usually decline any updates that I do not plan on approving at some > point. > For example, this image shows that on my main server I have 0 failed or > needed Not Approved updates: > http://i198.photobucket.com/albums/aa166/packav/WSUSex5.jpg> > On the replica server, it shows I have 10 failed or needed not approved > updates: > http://i198.photobucket.com/albums/aa166/packav/WSUSex4.jpg> > I think I realized the problem just now however. I ran the WSUS clean up > tool on the main server, but not on the replica servers. Seeing as these > updates showing Not Approved are all very old, perhaps they were deleted > off > the main server but not the replica servers. > > Anyway, I'm going to run that same cleanup tool on the replica servers to > see if that helps. > > > "Lawrence Garvin (MVP)" wrote: > >> "packav" <packav[ at ]discussions.microsoft.com> wrote in message >> news:051B2482-A573-41C7-8BB6-9129457C1901[ at ]microsoft.com... >> > Greetings, >> > >> > I'm on a recently upgraded WSUS 3.0 with 1 main server and 3 replica >> > downstream servers. My replica servers are showing updates with an >> > Unapproved >> > status, but my upstream server doesn't have any Unapproved updates. >> >> >> >> Also..since we're primarily talking about legacy updates here (all but >> one >> of the updates in the list is superceded), any chance you DECLINED them >> on >> the upstream server, which is preventing their display as an Unapproved >> update? >> >> >> -- >> 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>> ..... >> >> >>
|
|
|
|
I have also created this problem for myself by doing a cleanup and not
following up with the replication servers. The only soulution I have
found to correct the problem is Uninstall Wsus 3.0 on the replication
server using the following steps:
Run Windows Server Update Services 3.0 SP1 Setup Wizard
(WSUSSetup_30SP1_x86.exe)
Put a check in the boxes labeled Windows Server Update Serves 3.0 SP1
database and Log files
Leave the box un-checked labled Downloaded update files
Next
Next
When finished reboot server.
As the server reboots go to the Upstream server and delete it from the
Downstream servers list. Answer YES to the delete all rollup information
question.
Re-install WSUS 3.0 SP1 using the same settings as the previous
installation. Making sure you specify the correct location of the saved
updates.
Synchronize with the upstream server and it should have the correct
Unapproved,Approved and Declined Updates when complete.
All computers that report to the server will have to report status
again. Give it a day or so and your computers will be updated and
reported.
This is the only way I have found to correct this problem. It seems to
stem from a corruption in the database on the replication server. I have
tried running the command line fixes to no avail.
If anyone has a eaiser way to fix this problem I would like to get the
proceedure in case it happens again.
Terry K Mixon
--
mixont70706
------------------------------------------------------------------------
mixont70706's Profile: http://forums.techarena.in/members/mixont70706.htm
View this thread: http://forums.techarena.in/server-update-service/774523.htm
http://forums.techarena.in
|
|
"mixont70706" <mixont70706.3ibg7c[ at ]DoNotSpam.com> wrote in message
news:mixont70706.3ibg7c[ at ]DoNotSpam.com...
[Quoted Text] >
> I have also created this problem for myself by doing a cleanup and not
> following up with the replication servers. The only soulution I have
> found to correct the problem is Uninstall Wsus 3.0 on the replication
> server using the following steps:
While this procedure you describe is certainly the most thorough, and thus
the most reliable, there is a simpler procedure that should work, and avoids
the need to re-transport the entire file archive across the network:
1. Delete all of the subfolders and files of the ~\WSUSContent folder. (Do
not delete the ~\WSUSContent folder, as it has ACLS that need to be
inherited to the 00-FF subfolders when recreated.)
2. Make a removable media (DVD, Tape) copy of the ~\WSUSContent folder from
the master server and restore it to the replica server. (Note: If the
archive is too big for media, or if you're not concerned with the bandwidth
consumption, you can XCopy or RoboCopy the master server to the replica
server.)
3. While this restore/re-copy is running, do your think with deleting the
replica server and rollup reporting data from the master.
> This is the only way I have found to correct this problem. It seems to
> stem from a corruption in the database on the replication server. I have
> tried running the command line fixes to no avail.
Actually, if there were an issue with corruption on the =database= on the
replication server, the reinstallation of WSUS on the replica server would
not have resolved the corruption, since you checked the box to KEEP the
database when uninstalling WSUS. Therefore, the net effect of your entire
replica-side procedure is really nothing more than deleting and rebuilding
the ~\WSUSContent folder tree by re-downloading the master's file store.
More likely, in the scenario where you've run the SCW on the master server,
and not coordinated it's execution with replica synchronizations and
downloads, what's happened is that you've deleted metadata and/or update
files from the master server that the replica server needs, but once gone,
cannot obtain.
It may also be that another 'fix' for your situation is simply to run the
SCW on the replica servers (removing the stale metadata and/or files), and
then resynchronize with the master.
One final note, it's a new risk with WSUS 3.0 replica systems -- because
servers can be flip-flopped between replica mode and autonomous mode with
the check/uncheck of an options box, it's not unlikely that a server can be
removed from replica mode, synchronized with microsoft.com, placed back in
replica mode, and end up with a totally mucked up database/filestore.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|