Link to home
Start Free TrialLog in
Avatar of sglee

asked on

Migrating SBS2011 while using same computer name in new File Server

 I have SBS2011 and I need to:
 1. Move all of the user files and folders to a new member server with same computer name as current SBS2011.
 2. Transfer FSMO role to DC1 domain controller and run DHCP from DC1.
 3. Demote SBS2011 and completely remove its name "FileServer1" from the network.
 4. Rename FS1 to FileServer1.
Having said that, here are some information about involved servers.

Computer Name    IP address         Note
*******************    **************      ****************************************************
FileServer1         SBS2011 server and currently has FSMO role
FS1                 File Server and will be renamed to FileServer1
                                                        IP address  will be changed to
DC1                    W2016 domain controller. It will assume FSMO role
                                                         and run DHCP.

Below are the steps that I am going to take:

1. Since user files and folders were on a separate vhdx file in SBS2011 VM, I have already detached it from SBS2011 VM and attached it to FS1 VM.
2. Exported Network Shares out of SBS2011 and import it into FS1 using RegEdit.
3. Exported Printers from SBS2011 Printer Management and Import it into FS1.
4. I will Transfer FSMO role from SBS2011 to DC1.
5. I will remove SBS2011/FileServer1 from the network completely thru demotion process.
6. I will rename FS1 member server  to FileServer1.
7. I will assign to FS1.

The reason I need to keep the name "FileServer1" is because there are some programs out there that refers the name of "FileServer1" and I don't know which programs do that. So if I keep the same name on the new file server, I don't have to worry.

Do you have any additional suggestions or see potential issues with my plan?

Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
We had something put together by an SBS MVP (Jeff Middleton) called the SwingIT Migration.

Unfortunately the site is offline now.

Process was SBS --> TempDC --> AD Clean-up --> New DC with old SBS name.

EDIT: We ran _lots_ of them. Excellent process.
Avatar of sglee


  I agree with you that not using new server name would make things simpler from domain management standpoint.
  I just have to spend time identifying which programs are referring to current SBS server name.
  I personally have done both. In one SBS migration, I pursued "keeping the name" scenario and it worked fine. In another SBS migration, I could not rename new file server to SBS server name for some reason. It kept saying that the name still exist. So I have to use new name. It was not a big deal because it was small network.
 This time it is fairly large and I can't afford surprises.
  So I think I will send time finding out where the SBS name is used and go with new name.

Avatar of sglee


I heard that if you transfer FSMO role from SBS2011 to another server, SBS will turn itself off at some point.
So I am going to keep it there for a while while moving user files and folders and printers into the new file server.
Meanwhile is it safe to move DHCP server function as well out of SBS2011?
There is a hack to disable the auto-reboot of SBS 2011 after the FSMO Roles get moved.

Yes, you can move DHCP over.

Just keep in mind that your new DC may refuse to start ADDS if your FSMO Role holder is offline.
Avatar of sglee


@ Philip,
”There is a hack to disable the auto-reboot of SBS 2011 after the FSMO Roles get moved.” —> Interesting idea. Where can I find the information

“new DC may refuse to start ADDS if your FSMO Role holder is offline.” —> I may keep SBD2011 as FSMO holder indefinitely because it still plays Remote Gateway role which is useful. There are two additional domain controllers on the network, so I am not in a hurry to abandon SBS.
Hacks like that violate licensing so we can't tell you where / what to do with a hack.

Keeping the server online, ESPECIALLY for purposes that involve it being exposed to the internet is a REALLY BAD IDEA.  SBS 2011 is based on Server 2008 R2; Server 2008R2 has been out of support for over a year.  That means it does NOT get important security updates that prevent potential threats like ransomware.  The longer you leave that on the greater your exposure and the threat of compromise.  You should be getting that off the network ASAP!

All versions of Windows Server Standard include Remote Desktop Gateway - you just need to enable it, get RDS CALs for all users, and set it up.  It's not difficult.
Avatar of sglee


Based on the advise of the expert, I went with new name for the new file server and was able to make necessary changes that came because of server name change.
After transferring FMSO & DHCP roles to one of two domain controllers, I uninstalled DNS and AD from SBS2011, disjoined it from the domain and now removed from Hyper-V server completely.
Thank you for your advise!