Welcome to The Daily Reviewer

The Daily Reviewer selects only the world's top blogs (and RSS feeds). We sift through thousands of blogs daily to present you the world's best writers. The blogs that we include are authoritative on their respective niche topics and are widely read. To be included in The Daily Reviewer is a mark of excellence.

How Will Changing Office Ip Range Impact On Active Directory???? My company needs to change from the 192.168.x.x range to a 10.10.x.x range. We are currently on Win2K and XP clients and are using active directory. We've got 4 smaller (50 or so people) remote offices where we have DC's, and are using MS DNS. Since we've never done something like this we are afraid to simply change IP's on the servers etc. This might screw up things for Active Directory we fear, and of course we want as little downtime as possible for the company. I've tried to find info on what kind of procedures to follow on the web but have unfortunately not been able to find it. What approach would be best? what Best Practices and procedures should we follow? Who has done this & might have pointers? Any advise, tips or recommended reading? thanks! Paul	Share on Facebook Share on Twitter Share on Del.icio.us Share on StumbleUpon Share on Digg Share on Reddit Share on Technorati Share on Newsvine
< 6 Answers >
Answer Number 1 >> Re: How Will Changing Office Ip Range Impact On Active Directory???? <inline> "Paul" <Paul2@syncpuls.com> wrote in message news:10ne119adlgoke2@corp.supernews.com... My company needs to change from the 192.168.x.x range to a 10.10.x.x range. We are currently on Win2K and XP clients and are using active directory. The obvious question I have to ask is *why*? Why go through all that in order to change IPs from one private addressing scheme to another? We've got 4 smaller (50 or so people) remote offices where we have DC's, and are using MS DNS. Are you using DHCP? Since we've never done something like this we are afraid to simply change IP's on the servers etc. This might screw up things for Active Directory we fear, and of course we want as little downtime as possible for the company. If you plan this correctly, you will have little downtime - but you will have some downtime. It's a long weekend job. It's not just the servers. All the clients (of course) must be changed. In addition, you have the routers and VLANs. Then, you need to change scopes on all the DHCP Servers, clear the WINS database, etc. Then there is troubleshooting. Before you start this, save some time and search for unknown Hosts and LMHOSTS files - and get rid of them. I've tried to find info on what kind of procedures to follow on the web but have unfortunately not been able to find it. Create a script for everyone to follow. Do a dry run with the team, test it in the lab, do another dry run ... IOW - get the proceedure down pat. Ensure you have a backout plan. Establish a command center and man it. Get radios or phones for everyone. Know what everyone's job is during the project, ensure each step is done and dHow Will Changing fi Ipange Impact On Active Directory?? | TheDailyReviewer Ambassador Cutelittleslut Szh Mississippi Cute Slut Little Suti Cute hHow Will Changing fi Ipange Impact On Active Directory?? | TheDailyReviewer Ambassador Cutelittleslut Szh Mississippi Cute Slut Little Suti Cute w w Slut Little