You should see no real issues from the rename of a file server...
*ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market...* On Mon, Nov 24, 2014 at 3:49 PM, Reimer, Mark <[email protected]> wrote: > Server is running 2012, virtualized, with 2008 DC's. > > > > It's a fairly new install, and I'm migrating from an old 2003 server. > However, the powers asked that I rename the new server. > > > > Can I do this (without messing up a bunch of AD stuff)? Rename > a.mycompany.com to b.mycompany.com. I realize that any clients using > a.mycompany.com would have to be switched to look at b.mycompany.com > > Can/Should I add a DNS entry (AD DNS internal only) with new name pointing > to server IP? B.mycompany.com pointing to 101.101.101.101 (fictitious IP > address of a.mycompany.com) > > Should I just make a new fileserver with the name chosen (b.mycompany.com), > migrate what I have (from a.mycompany.com to b.mycompany.com), then > continue my original migration? > > > > I don't see much help on Google (it shows up articles on how to rename > files and directories). > > > > Thanks > > > > *Mark Reimer* > > Servers & Network Administrator > > Prairie Bible Institute > > Tel: 403-443-5511, Ext. 3476 > > Email: [email protected] > > > > *Need Computer Support?* Email [email protected] > > > > >
