Brian presented a great plan.
I fully agree with building the new infrastructure and hooking up the
replication between them and make sure it is all working properly. Drop in a
few records and make sure they make it around properly. You can do that by
either pointing a machine at one of the new WINS Servers or by creating a
dynamic record in the new structure with netsh like so... This will
eventually expire and be cleaned up.
[Wed 05/19/2004 8:58:58.26]
C:\WINDOWS>netsh wins server \\w2kasdc1 add name name=winsrocks rectype=1
IP={192.168.69.69}
***You have Read and Write access to the server w2kasdc1***
Command completed successfully.
[Wed 05/19/2004 8:59:18.18]
C:\WINDOWS>netsh wins server \\w2kasdc1 show name winsrocks
***You have Read and Write access to the server w2kasdc1***
Name : WINSROCKS [20h]
NodeType : 1
State : ACTIVE
Expiration Date : Tuesday, May 25, 2004 8:58:21 AM
Type of Rec : UNIQUE
Version No : 0 1623
RecordType : DYNAMIC
IP Address : 192.168.69.69
Name : WINSROCKS [00h]
NodeType : 1
State : ACTIVE
Expiration Date : Tuesday, May 25, 2004 8:58:21 AM
Type of Rec : UNIQUE
Version No : 0 1624
RecordType : DYNAMIC
IP Address : 192.168.69.69
Name : WINSROCKS [03h]
NodeType : 1
State : ACTIVE
Expiration Date : Tuesday, May 25, 2004 8:58:21 AM
Type of Rec : UNIQUE
Version No : 0 1622
RecordType : DYNAMIC
IP Address : 192.168.69.69
Command completed successfully.
[Wed 05/19/2004 8:59:22.83]
C:\WINDOWS>
Once you know that the replication is all cool around that new
infrastructure, you will probably want to tie into the old for a bit. If
there is some reason you DON'T want to pull entries from the old into the
new like say you don't want to drag in Static entries or something what you
can do is ascertain all machines you want to be found via WINS name
resolution (most likely your servers mainly), and then register them in the
new system as specified above and set up a connection to send entries down
to the old WINS Servers. Then repoint the servers to the new structure.
As for the clients, depending on your DHCP leases and how fast you want them
cut over, you may consider reducing your lease times up front. The
migrations I have been involved in we usually chopped the lease times down
to a day or two. It created more traffic but not like killer amounts more.
When you did the DHCP config change then most everything got the change
within a day.
I also agree with Brian's idea of watching to see if the old equipment is
still being used. However I would reset the stats on the service (restart
the service or do a netsh wins server \\servername reset stat) and then let
them sit for a couple of hours or days and then do a
Netsh wins server \\servername show stat
And see if anything has hit them. If so, then pull out the netmon or
ethereal and start capturing port 137 traffic. Either way will work, I
mention this way so you don't have to go into a net sniffer unless you
really have to. Not that going into one is bad and in fact any chance to use
a sniffer is a good. :o) Just offering alternatives. Another alternative is
that I believe I have a little simple sniff program I wrote laying around
that can watch specific ports and will dump to screen traffic to specific
ports. I was/am working towards a tool to pull off LDAP binds/Queries to
watch them and stuff them into a text file without having to pull out a full
blown network monitor tool. Nice thing about it is that it is self
contained, nothing to install. You say hacker tool, I say tool that I don't
have to worry about an install futzing with the registry or file system...
joe
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Tuesday, May 18, 2004 10:54 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT: WINS configuration question
Well, what I'd do is get your 2003 infrastructure fully inplace first. Then
I'd setup replication amongst the new infrastructure. However it floats your
boat is fine. Then, get a new server in each site pulling form the old hub
to the new ring. This should get you initially setup with data, and you can
see if there's replication problems and what have you. You'll also need to
push out from the new infrastructure into the old until things are working.
Next, I'd get as many of the clients transitioned over to the new hardware
as possible. This means a DHCP change and waiting a minimum of the length of
a lease. You'll need to update all your servers and statically addressed
machines if they're not using reservations in DHCP. Then, get out your
trusty copy of netmon, and figure out how much traffic is hitting the old
boxes. When that gets down to almost nothing, you can cut replication with
the out-of-service WINS box, power it down, and do the robot wars thing like
in the Dell commercial with it.
--Brian Desmond
[EMAIL PROTECTED]
Payton on the Web! Http://www.wpcp.org
v: 773.534.0034 x135
f: 773.534.0035
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 9:35 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] OT: WINS configuration question
We're combining 7 business units together into a new Server 2003 forest.
We'll have an empty root and the 7 BUs will be combined into an AMER domain.
Some BUs already have AD with Server 2000 and others still have NT4.0. All
BUs are running WINS and we believe that we'll still need WINS. However, 7
WINS environments are not the way we want to continue and there are way too
many WINS servers around right now. Setting up push/pull replication
between them doesn't seem to make sense either. We wish to reduce the
number of WINS servers to just our 8 major datacenters (each are hubs in our
current WAN -- we hope to get that fixed but not soon enough).
Question is this...
Do we build one WINS server using Server 2003 in each of the datacenters and
either specify automatic partner configuration or replication partners based
on the WAN, shut down the old WINS servers on a Friday night, reconfigure
all servers and workstations to new WINS addresses (scripted), and pray that
all's well by Monday? Or do we work to reduce the number of WINS servers in
each of the BUs, upgrade them to 2003, and set up replication, thus
preserving our current entries?
I know that I may not be giving you much information. Can and will provide
more if you need.
Thanks,
Mike
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
