[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 672
  • Last Modified:

Decommission Existing NT Server-based WINS Server and Add New 2003-based WINS Server With Same IP Address

We are currently running a Windows NT Server with WINS, IP address of 172.17.33.3. It is the only machine left in our company in our old domain, we'll call it "domain_old." We want to decommission this server since WINS is its only function and we no longer need the domain_old domain.

We also have a Windows 2000 Server running WINS, IP address of 172.17.33.36, in "domain_new." Both WINS servers are using push/pull replication with each other.

All of our client PCs (virtually all are Windows XP Professional - approximately 250) are hard-coded to point to IP address 172.17.33.3 for the WINS server (in each PC's Local Area Connection properties). Since we don't use group policy yet, we don't want to go to each client PC and change the WINS server IP address to 172.17.33.36.

So what I'd like to do is take our 172.17.33.3 NT server offline, install WINS on another member server of "domain_new" and change its IP address to 172.17.33.3. This member server is running Microsoft Server 2003 Standard R2 SP1. I would think I could set up a new replication with the .36 WINS server and everything would run as normal.

Does anyone think this is a good idea? Is there a better way to go about doing this? I read about removing WINS altogether from our domain but according to Microsoft, it's still needed for certain tasks. If it's of any relevance, we're running Microsoft Exchange Server EE 2003 and 2000 Active Directory on the domain_new domain.
0
mschmidt14
Asked:
mschmidt14
  • 6
  • 4
1 Solution
 
LauraEHunterMVPCommented:
Sounds like a reasonable proposal to me, I've swapped out many a server using steps similar to what you've outlined.  You'll likely need to delete the WINS replication connections and re-create them, but aside from that it should be swimming.
0
 
mschmidt14Author Commented:
Laura-

Do you think I should stop the replications first? If so, can you walk me through the steps in WINS, preferably on the 2000 box (172.17.33.36)?
0
 
LauraEHunterMVPCommented:
Just delete the replication partners under the Replication Partners folder, and then re-create them once you're done.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
mschmidt14Author Commented:
Thanks, Laura. There's no "primary" WINS server I need to worry about when I delete the replication partners and set them back up?

Lastly, I would assume I don't have to move the WINS database from the server I'm decommissioning, but instead it will replicate to the new WINS serer once I set up the replication partners. Correct?

Thanks,
Jeff
0
 
LauraEHunterMVPCommented:
> "There's no "primary" WINS server I need to worry about when I delete the replication partners and set them back up?"

Correct.  Unlike primary/secondary DNS zones, WINS is multi-master and doesn't have any notion of a single authoritative data source when multiple servers are involved.

> "I don't have to move the WINS database from the server I'm decommissioning"

As long as the WINS data is present and correct on the remote replication partner, your assumption is correct.
0
 
mschmidt14Author Commented:
Awesome. Thanks for the help. I plan on making this switch later this week. I'll close the question at that point barring any unforeseen questions.

0
 
mschmidt14Author Commented:
Laura-

I'm thinking about doing a manual replication before I take the server to be decommissioned offline. Do you have an idea how long the replication will take? Again, we have approximately 250 PCs. Will it take a matter of a couple minutes, an hour, longer?

Thanks!
Jeff
0
 
LauraEHunterMVPCommented:
If you are referring to WINS replication, this will be dependent on the speed of your network link between the servers and the size of the database.  Really impossible to guess-ti-mate since I'm unfamiliar with your environment.  Assuming good LAN speeds and a normal-sized database given the network size that you indicate, I'd kick off replication, leave it for an hour, and check the event logs for any errors.
0
 
mschmidt14Author Commented:
OK, thanks.
0
 
mschmidt14Author Commented:
Although I haven't done the conversion yet, you answered my questions and it sounds like it should go smooth. Thanks for the help.

Jeff
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now