We help IT Professionals succeed at work.

Windows Server 2012 R2 Essentials - Domain setup - Clean Install - create custom domain suffix (domain.office vs. domain.local)

3,266 Views
Last Modified: 2014-05-20
I’m setting up a Win2K12 R2 Essentials server (Clean Install).   I need to setup the domain suffix to be “domain.office” instead of the default “domain.local”.  What is the easiest method to modify the domain setup so that I may specify a custom domain suffix? Or can the suffix be changed after the fact? (Note: changing the suffix after the fact is not the preferred method... unless the solution also includes a comprehensive/verifiable explanation of why doing so is the correct method.)
Comment
Watch Question

Brent ArnoldTechnician

Commented:
As a clean install I'm going to answer your question with YES: the EASIEST method is just changing the suffix after the fact. I have changed entire domain names <domain.suffix> ON NEW INSTALLATIONS and never missed a beat.
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
The above comment is incorrect in this instance. Essentials installs as a DC and thus cannot be renamed. Demoting essentials will break things and puts you in an unrecoverable state. Don't go that route.

You cannot get around the dot-local suffix via the GUI. You'll have to grab the deployment tools that OEMs use to customize and create a custom answer file. That is the only supported way to get a custom suffix in essentials during a clean (non migration) install.

Author

Commented:
To all - I'm in agreement with Cliff... as Essentials is the new "Wizards" based SBS type solution (where both are products of the same beast).  I have in the past, successfully circumvented the SBS wizards on custom configurations, but from experience, I know these wizards reach far and deep... so to successfully modify outside of the gui/wizard requires a lot of "dotting of i's and crossing of t's.  (which is why my request had such a disclaimer... requesting a quantifiable explanation of which "i's" and "t's" to cross.)

To Cliff - Installing the OEM tools, is this done on the target server? and is it the cfg.ini that needs to be modified?  A little direction would be helpful.

Thanks to both for responding.
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Here is a link to the deployment kit. The kit includes both tools and documentation. The documentation has the details in customizing the deployment. I honestly can't recall if the custom domain name js done in the PE stage or the later stage, so it may be u attend.xml or cfg.ini, but the documentation will answer that question.

http://www.microsoft.com/en-us/download/details.aspx?id=34866
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Anyone who reads the entire thread... will see that I, "the initiator", did the research and found the easiest/correct method for accomplishing this task.  The final solution provides the methodology, as well as the linked sources about the solution.

Example cfg.ini - written in notepad.exe and saved to root of USB drive. (obviously, the example cfg variables are hypothetical)
[InitialConfiguration]
Keyboard=0409:00000409
AcceptEula=true
CompanyName=domain
ServerName=domainSVR
NetbiosName=domain
DNSName=domain.office
UserName=AdminUsrNm
PlainTextPassword=4Admnpw!
StdUserName=Path
StdUserPlainTextPassword=4Pathpw!
Settings=None
IPv4DNSForwarder=168.168.44.2
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.