Server 2012 R2 Essentials Deployment
I currently have a Dell server running SBS 2003 in a domain environment.
I have a new Dell server running Windows Server 2012 R2 Essentials that I am going to replace the SBS 2003 with.
I have decided not to do a migration, but a clean install/setup (2012 Essentials is already installed on the new Dell server). I only have 12 clients and PC's.
My question is this. When I set up the new server name and domain name should I keep the same names as the old server and domain names?
I pretty much know that I need to keep the same server name because I have users that are using hyperlinks to link to files on the existing server. If when I moved the files/folders to the new server with a different name the hyperlinks would no longer work.
The domain name I am not sure about.
My thought is to keep both server name and domain name the same.
Any thoughts or suggestions.
I have a new Dell server running Windows Server 2012 R2 Essentials that I am going to replace the SBS 2003 with.
I have decided not to do a migration, but a clean install/setup (2012 Essentials is already installed on the new Dell server). I only have 12 clients and PC's.
My question is this. When I set up the new server name and domain name should I keep the same names as the old server and domain names?
I pretty much know that I need to keep the same server name because I have users that are using hyperlinks to link to files on the existing server. If when I moved the files/folders to the new server with a different name the hyperlinks would no longer work.
The domain name I am not sure about.
My thought is to keep both server name and domain name the same.
Any thoughts or suggestions.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I understand what you are saying.
I plan to on each client PC remove them from the old domain and rejoin them to the new domain. Then give them rights to their resources on the new server. In essence building a brand new network.
I have a test network to use. I am going to test creating a new domain name and keeping the same server name. Then see if the existing hyperlinks still work.
I plan to on each client PC remove them from the old domain and rejoin them to the new domain. Then give them rights to their resources on the new server. In essence building a brand new network.
I have a test network to use. I am going to test creating a new domain name and keeping the same server name. Then see if the existing hyperlinks still work.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wouldn't that prevent any conflict in naming and connectivity?