| Author |
 Topic  |
|
|
CallMeAl
Seasoned But Casual Onlooker
USA
42 Posts
Status: offline |
 Posted - 08/05/2012 : 10:59:39 AM
|
So long story short, our department is moving to the university’s virtual firewall, and according to the powers that be, in order for this to happen, we must be assigned new IP space.
In theory, I plan to do the following:
1. Create a new DHCP scope for the client machines.
2. Bring up a second NIC on each server and assign that NIC to its Ip in the new server range.
3. Insure that clients and servers can talk to each other on the new IPs and if so, turn off the old NICs.
4. Request the appropriate external DNS changes be made for our Mail server, MX record, Web server, VPN server, etc.
5. Manually change the IP addresses of all printers, cameras and other devices which are statically assigned.
Questions I have:
1. If I change the IPs of shared printers on the server, how do I insure that clients are pointing to the correct IP? I’m thinking I could create or modify an existing GPO and update the preference? If I point to the same shared printer again, will this update the IP accordingly?
2. What other gotchas am I missing? I’m sure there are probably a thousand things likely to break that I haven’t even considered.
Thanks!
Al
|
|
|
anthony
Moderator
USA
2373 Posts
Status: offline |
Posted - 08/05/2012 : 9:22:34 PM
|
You don't need a second NIC in the servers. You could just ADD a 2nd IP to the existing NIC. The only caveat to that is though... if you don't remove the old address - you really don't fully know that things are working because they are now right, or because they are using the "old way". Also, it could make things like routing, and troubleshooting all the more complicated since you are dealing with two schemes now instead of one. Just my opinion, but I would just pull the band-aid off and commit to the new scheme and go with it.
On the questions:
1. If the printers are shared and the clients connect to the printers VIA a Shared Printer from a Windows Server, then as long as you change the IP Port on the printer on the server, you clients wont need to be changed at all, they will still connect to the share as before. Since they print VIA the server, the SERVER is the only thing that needs to point to the new printer IP.
2. I did this less than a year ago. Planning is key. We started by creating a spreadsheet with every devices CURRENT IP Address. We then planned out the new scheme, and on the same sheet, assigned everything's IP well before it is GO time. You don't want to be doing this as you're changing things. Finally, keep track of all the things that have/have not been changed in the spreadsheet, or on a printed version of it. Go down the list, and run through it. If all was planned well, the switch is not so bad. The more effort you take in the planning, the less gotchas on GO day.
Either way, unless you have a super simple setup, or you are a god. SOMETHING will get forgotten - you just put those fires out as they happen on that first day back.
Godspeed. 
|
anthony
There should be only one World's Greatest Dad shirt. And you should have to kill the previous owner to wear it.
|
 |
|
|
chamezzzz
Honorable But Hopeless Addict
United Kingdom
2298 Posts
Status: offline |
Posted - 08/06/2012 : 03:59:06 AM
|
In my experience, the real pain is
(1) Printers - already discussed
(2) Domain Controllers - discussed here - http://goo.gl/HVQRZ
(3) IIS - if you have set any of your websites to manually use an IP - they stick with that IP - this can cause frustration as to why everything else is working but not your IIS - it is likely you just have them set to listen on all - which is the default setting..but worth being aware of in case you have changed this setting on any iis servers.
As Anthony has already mentioned, planning is key and be prepared to go back if anything goes wrong. Its a big project and it just takes one misconfigured subnet mask, fat fingered under tiredness or stress to get things wrong.
Plan it well...and you will be fine. |
James |
Edited by - chamezzzz on 08/06/2012 04:01:54 AM |
|
|
| |
Topic |
|
|
|
Need to RE-IP Everything in my Domain, yay ...
