• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 235
  • Last Modified:

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.
0
jet0654
Asked:
jet0654
  • 2
  • 2
3 Solutions
 
YorickosCommented:
I would suggest to change the server and domain name.
You will experience connectivity problems when keeping the same names.
0
 
jet0654Author Commented:
I am going to take the existing SBS off the network before I connect the new 2012 server. The new server will never see the old server on the network.  I was planning to have all the client PC's shutdown before connecting the new server. Then after connecting and configuring the new server add the users and client PC's to the new server and network.

Wouldn't that prevent any conflict in naming and connectivity?
0
 
MaheshArchitectCommented:
No matter if you created domain with same name \ new name, still you have to create new users and disjoin computers from old domain and rejoin it again to new domain
Obviously you will not be able to access resources on new domain even if you have same domain name \ DC name as user SID in old domain and new domain are different and you must grant explicit permissions to all users on new domain resources
0
 
jet0654Author Commented:
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.
0
 
MaheshArchitectCommented:
Hyperlink will resolve if you have same server name as old, but it will be able to access unless you explicitly provide access
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now