|
|
Trying to bounce a question off you guys in something Im trying to plan out.
With the release of WSUS 3.0, we are looking to deploy that to a new server
that we will be putting into place here in a month or two.
Is there a way to migrate approvals from one database (WSUS 2.0) to a new
server database (WSUS 3.0)
Also, a detail to add, I believe we were a bit foolish in planning, but our
clients are all set for http://hostname instead of using IPs. So the new
server will have a different hostname, so this could be quite a big task to
change over all of our clients to point to a new name or IP.
Anyone have any suggestions in this migration?
|
|
"Mike_STLCC" wrote:
[Quoted Text] > Also, a detail to add, I believe we were a bit foolish in planning, but our > clients are all set for http://hostname instead of using IPs. So the new > server will have a different hostname, so this could be quite a big task to > change over all of our clients to point to a new name or IP. > > Anyone have any suggestions in this migration?
Are you using Active Directory? If so, it shouldn't be a big deal to change
your GPO to point to the new server. Otherwise, I suppose you could create a
..REG file and deploy that to each machine to modify the local policy to point
to the new hostname.
|
|
Mike_STLCC wrote:
[Quoted Text] > Also, a detail to add, I believe we were a bit foolish in planning, but our > clients are all set for http://hostname instead of using IPs. So the new > server will have a different hostname, so this could be quite a big task to > change over all of our clients to point to a new name or IP.
Hostnames are almost always better than IPs. I don't think this case is an
exception.
Is the old server going to be decommissioned? Because if so you could always
create a DNS alias for the old hostname pointing to the new one. The WSUS
clients should be able to follow the alias.
Harry.
|
|
"Mike_STLCC" <MikeSTLCC[ at ]discussions.microsoft.com> wrote in message
news:35273EB2-FD7A-4500-9181-5A039F777AB2[ at ]microsoft.com...
[Quoted Text] > Trying to bounce a question off you guys in something Im trying to plan
> out.
>
> With the release of WSUS 3.0, we are looking to deploy that to a new
> server
> that we will be putting into place here in a month or two.
>
> Is there a way to migrate approvals from one database (WSUS 2.0) to a new
> server database (WSUS 3.0)
Yes, but it essentially involves either duplicating the WSUS2.0 environment
on the new box and then doing an in-place upgrade, or upgrading the existing
box, and then duplicating that upgraded WSUS3.0 environment onto the new
box.
> Also, a detail to add, I believe we were a bit foolish in planning, but
> our
> clients are all set for http://hostname instead of using IPs.
Why would you consider that foolish. That's the way it *should* be done!
> So the new
> server will have a different hostname, so this could be quite a big task
> to
> change over all of our clients to point to a new name or IP.
Not if you're using policy to deploy the settings. :-)
You can also alias the old hostname to the new server's IP Address. As long
as the new server is configured to respond to "All Unassigned" IP Addresses
in IIS, and is not using host headers, it'll work seamlessly.
--
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
.....
|
|
On May 28, 12:02 am, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text] > "Mike_STLCC" <MikeST...[ at ]discussions.microsoft.com> wrote in message
>
> news:35273EB2-FD7A-4500-9181-5A039F777AB2[ at ]microsoft.com...
>
> > Is there a way to migrate approvals from one database (WSUS 2.0) to a new
> > server database (WSUS 3.0)
>
> Yes, but it essentially involves either duplicating the WSUS2.0 environment
> on the new box and then doing an in-place upgrade, or upgrading the existing
> box, and then duplicating that upgraded WSUS3.0 environment onto the new
> box.
>
Lawrence, could you please point me in the direction of how I would do
either of the two options you described here? I've found a few blogs
that give some hints but nothing that lays it out in detail.
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...
>
> Everything you need for WSUS is athttp://technet2.microsoft.com/windowsserver/en/technologies/featured/...
>
> And, almost everything else is athttp://wsusinfo.onsitechsolutions.com
> ....
|
|
<mortalone[ at ]gmail.com> wrote in message
news:1180982121.499435.258050[ at ]p77g2000hsh.googlegroups.com...
[Quoted Text] >> > Is there a way to migrate approvals from one database (WSUS 2.0) to a
>> > new
>> > server database (WSUS 3.0)
>> Yes, but it essentially involves either duplicating the WSUS2.0
>> environment
>> on the new box and then doing an in-place upgrade, or upgrading the
>> existing
>> box, and then duplicating that upgraded WSUS3.0 environment onto the new
>> box.
> Lawrence, could you please point me in the direction of how I would do
> either of the two options you described here? I've found a few blogs
> that give some hints but nothing that lays it out in detail.
To be honest, I don't believe anything formal has been written to that level
of detail or scenario as of yet.
Option #1: Duplicating the WSUS 2.0 environment on the new box.
[a] Use NTBACKUP to backup the \WSUS folder (and the database files if
located elsewhere).
[b] Install WSUS 2.0 on the new system.
[c] Use NTBACKUP to restore the \WSUS folder from the backup of the
original server.
[d] Execute in-place upgrade of WSUS 3.0.
Option #2: Upgrade existing box and duplicate.
[a] Execute in-place upgrade of WSUS 3.0
[b] Use NTBACKUP to backup the \WSUS folder (and the database files if
located elsewhere).
[c] Install WSUS 3.0 on the new system.
[d] Use NTBACKUP to restore the \WSUS folder from the backup of the
original server.
--
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
.....
|
|
On Jun 4, 10:26 pm, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text] > <mortal...[ at ]gmail.com> wrote in message > > news:1180982121.499435.258050[ at ]p77g2000hsh.googlegroups.com... > > >> > Is there a way to migrateapprovalsfrom one database (WSUS2.0) to a > >> > new > >> >serverdatabase (WSUS3.0) > >> Yes, but it essentially involves either duplicating the WSUS2.0 > >> environment > >> on the new box and then doing an in-place upgrade, or upgrading the > >> existing > >> box, and then duplicating that upgraded WSUS3.0 environment onto the new > >> box. > > Lawrence, could you please point me in the direction of how I would do > > either of the two options you described here? I've found a few blogs > > that give some hints but nothing that lays it out in detail. > > To be honest, I don't believe anything formal has been written to that level > of detail or scenario as of yet. > > Option #1: Duplicating theWSUS2.0 environment on the new box. > [a] Use NTBACKUP to backup the \WSUSfolder (and the database files if > located elsewhere). > [b] InstallWSUS2.0 on the new system. > [c] Use NTBACKUP to restore the \WSUSfolder from the backup of the > originalserver. > [d] Execute in-place upgrade ofWSUS3.0. > > Option #2: Upgrade existing box and duplicate. > [a] Execute in-place upgrade ofWSUS3.0 > [b] Use NTBACKUP to backup the \WSUSfolder (and the database files if > located elsewhere). > [c] InstallWSUS3.0on the new system. > [d] Use NTBACKUP to restore the \WSUSfolder from the backup of the > originalserver. > > -- > Lawrence Garvin, M.S., MCTS, MCP > IndependentWSUSEvangelist > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > Everything you need forWSUSis at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> ....
I'm in a similar situation here, the only difference is that I'd like
to place a WSUS 3.0 server first that would be the upstream server for
all currently WSUS 2.0 servers. No other clients will be connecting to
this WSUS 3.0 server except for the dowstream server (I'll call it
WSUS1 which will converted to be a replica of this new WSUS 3.0) and
its replica servers ( about 5 of them). The idea was to approve the
updates on the new WSUS 3.0 server and resolve some of the
difficulites when approving updates on WSUS1 which is serving over
25000 clients. I would then upgrade the rest to 3.0 when everything
works well.
My question is, do I need to migrate the approvals from the downstream
server (WSUS1) including of course the Target groups, products and
languages? or just duplicate everything as mentioned by Lawrence would
be a more better way?
|
|
"VocalEyes" <cdeguia[ at ]gmail.com> wrote in message
news:1181833268.128370.5050[ at ]n15g2000prd.googlegroups.com...
[Quoted Text] > I'm in a similar situation here, the only difference is that I'd like
> to place a WSUS 3.0 server first that would be the upstream server for
> all currently WSUS 2.0 servers. No other clients will be connecting to
> this WSUS 3.0 server except for the dowstream server (I'll call it
> WSUS1 which will converted to be a replica of this new WSUS 3.0) and
> its replica servers ( about 5 of them).
Assuming you're talking about making your current master server (which has 5
replicas) a replica of a new WSUS 3.0 server, the fundamental flaw is that
you have to uninstall/reinstall the WSUS server to convert it to a replica.
In the process of doing so, you'll need to discard your existing database,
so that a fresh database can be populated with the configs and approvals
'replicated' from the new WSUS 3.0 server.
> The idea was to approve the
> updates on the new WSUS 3.0 server and resolve some of the
> difficulites when approving updates on WSUS1 which is serving over
> 25000 clients.
Ouch. Talk about exceeding the documented capabilitites of a product!
The supported/documented ceiling on a WSUS 2.0 server is 15,000 clients, and
that presumes a super-powerful front-end/back-end configuration. I'm
surprised it's even remained functional with 25,000 clients!
Furthermore, it also exceeds the supported/documented ceiling for a WSUS 3.0
server!
You're going to need to add a couple more servers to support 25k clients
successfully. And, since you didn't explicitly mention it, doing so on a
single-server installation is also contributing to the problem. If you do
have a back-end server, leaving out that *critical* detail in this request
for evaluation of a migration plan would not be a good thing. In your
environment, a back-end database server is *mandatory* to support 25,000
clients.
> I would then upgrade the rest to 3.0 when everything works well.
> My question is, do I need to migrate the approvals from the downstream
> server (WSUS1) including of course the Target groups, products and
> languages? or just duplicate everything as mentioned by Lawrence would
> be a more better way?
Here's what I'd suggest doing (aside from getting those clients spread out
to additional servers so you at least get under the supported/documented
limit for client loads):
[1] Convert your WSUS 2.0 SP1 server to a back-end database server running
SQL Server 2005 Standard Edition SP1.
[2] Upgrade the WSUS 2.0 SP1 server to WSUS 3.0
[3] Install a new WSUS 3.0 server using the Windows Internal Database,
ultimately to be the new master server, serving *only* the replica servers
(and possibly a small test environment). Configure it as a /replica/ of the
server you just upgraded to WSUS 3.0. Synchronize. After synchronizing,
change it's replica status to autonomous and configure it to update from
microsoft.com. Synchronize.
[4] Convert your upgraded WSUS server to be a replica of the new WSUS 3.0
master server. Synchronize.
[5] Upgrade your downstream replicas as time permits.
--
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
.....
|
|
|