"TAB" <tab405[ at ]comcast.net> wrote in message
news:1182442352.564367.17800[ at ]k79g2000hse.googlegroups.com...
[Quoted Text] > While setting up for WSUS 3.0...
>
> I had a WSUS 2.0 build that I wanted to keep in play (production) so I
> built a second 2.0 box and synchronized it with my original 2.0 build.
> I built it as a replica.
>
> I then took the new 2.0 (replica) and upgraded it to 3.0.
> This seems to have gone well and I now see all the updates and groups
> from my original build in my upgraded build, but I do not see any
> computers.
>
> Is this normal behavior?
Yes.
> Should the computers also have been transfered to the replica?
No. Building a replica server does *not* transfer across =computer=
information. The only way a WSUS server gets computer information is when a
computer specifically reports to it (or a WSUS 3.0 replica server utilizes
reporting rollup to sync that data to an upstream server).
> If I change it from a replica server and just point it upsteam to
> synchronize, will that get the objects on to my newly upgraded 3.0?
Nope. You'll have to wait for the computers assigned to that server (at
whatever point they become assigned) to execute a detection/reporting event.
> Is there a way to get the computers over to this new box and have them
> in the same groups they were in on my original build?
If your intent was to simply migrate from WSUS 2.0 on box 'a' to WSUS 3.0 on
box 'b', =and= preserve all data from the original WSUS 2 system, you have
two options:
[a] Backup/Restore the WSUS 2.0 server onto the new system. (Replica is
certainly a way to get the server configs, update metadata, and update
content onto a new server, but the one thing it will not bring across is
data for computers not assigned to update from that server.) Upgrade
in-place on the new server.
[b] Upgrade in-place the existing WSUS 2.0 server. Backup/Restore the WSUS
3.0 server onto the new system. (Again, building a replica is an option, but
will not replicate the computer information.)
Now, having said all that, I'll reiterate -- the computer information will
re-populate within 24 hours after the client systems are reassigned to the
new server. In fact, it'll actually happen exponentially faster than that.
As soon as you update the policy with the URL of the new server, clients
will begin obtaining that URL through normal policy refresh cycles. That
will take up to two hours. The policy refresh, because the URL has changed,
will trigger an immediate detection event on every client, which will be
followed by a reporting event within the next 10-20 minutes.
Net effect, within 3-4 hours (worst case scenario, and allowing for
overloads on the WSUS server from servicing all the clients simultaneously),
you'll have a fully populated computer status dataset.
--
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
.....
|