Solved

Rename domain from domain.local to ad.domain.no

Posted on 2013-06-28
8
958 Views
Last Modified: 2013-06-28
Hello!
I need to rename my domain.local to ad.domain.no. This is because I have a Citrix setup that needs SSL cert. But from 1.november 2015 .local is not a valid fqdn.

Anyone know how I can easily rename my domain to ad.domain.no ? What will happen with my Exchange server? And all other servers/client connected to my domain.local ?

I hope someone can help clarify things :)

Thanks
0
Comment
Question by:Oeyhope
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 25

Expert Comment

by:Tony Johncock
ID: 39284088
You absolutely cannot rename an AD with Exchange 2007+ installed. Sorry

I seem to recall you could use a fixup tool for Exchange 2003.
0
 
LVL 24

Accepted Solution

by:
Sandeshdubey earned 250 total points
ID: 39284091
Domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010. DNS domain rename is supported in Exchange Server 2003.However, renaming of the NetBIOS domain name is not supported in any version of Exchange Server.
 
More here: http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx
 
You need to understand nuances of Domain rename and its working before you actually taken on migration production env.Also, its much better if you can simulate in a lab environment for successful result.
 
Domain rename with or without exchange.
 http://msmvps.com/blogs/acefekay/archive/2009/08/19/domain-rename-with-or-without-exchange.aspx
 
Windows Server 2008 R2 ADDS Domain Rename Operation Document
 http://blogs.technet.com/b/justin_gao/archive/2011/06/30/windows-server-2008-r2-adds-domain-rename-operation-document.aspx
 
I would not recommend to rename domain unless and until there is strong business requirement.Alternately you can install new domain and migrate users/computers,etc from old domain to new domain with ADMT tool but this also needs testing.ADMT doesn’t have an Exchange/mailbox migration option more refer below links
 
ADMT Guide: Migrating and Restructuring Active Directory Domains
 http://technet.microsoft.com/en-us/library/cc974332(WS.10).aspx
 
MIGRATING STUFF WITH ADMTV3
 http://blogs.dirteam.com/blogs/jorge/archive/2006/12/27/Migrating-stuff-with-ADMTv3.aspx
 
Sample User/Computer migration steps.
 http://www.arconi.com/solutions-articles/solutions/120-admtmigrationsteps.html
 
ADMT doesn’t have an Exchange/mailbox migration option
http://social.technet.microsoft.com/Forums/pl/winserverDS/thread/faea9e46-e6b8-401a-b4c1-f6a72af9d03e
 
Hope this helps
0
 
LVL 15

Expert Comment

by:Rob Stone
ID: 39284092
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 25

Expert Comment

by:Tony Johncock
ID: 39284109
Stoner:

From: http://technet.microsoft.com/en-us/library/cc781575%28v=ws.10%29.aspx

The domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010. DNS domain rename is supported in Exchange Server 2003. However, renaming of the NetBIOS domain name is not supported in any version of Exchange Server.

From: http://technet.microsoft.com/en-us/library/cc738208%28v=ws.10%29.aspx

It is imperative that you not attempt a domain rename operation until you read and understand the contents of this technical reference. The domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010.


 And finally the document you provided - http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a2a2e2/Domain-Rename-Procedure.doc  - predates Exchange 2007.

It is not supported and anyone attempting this would be opening a world of potential pain not to mention handing MS a get of jail free card should you try open a support call now or down the line.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39284116
Why do you need an internal SSL certificate for Citrix? You should be able to switch to a public name and just change the references in Exchange and Citrix to your public name.

Simon.
0
 
LVL 25

Assisted Solution

by:Tony Johncock
Tony Johncock earned 250 total points
ID: 39284157
Simon raises a very good point and I'm a tad annoyed, as a Citrix specialist, I missed that.

Even if connecting to an internal web interface, there's no reason you couldn't point internal DNS to an alias if you don't want them coming out and back into the network.
0
 

Author Comment

by:Oeyhope
ID: 39284174
Thank you so much for all the information!! Very helpfull, and I guess rename the domain is not for me to do just yet! :)

I am running storefront 1.2 and my storefront has url: storefront.domain.local.

How can I change fqdn to: storefront.domain.no? :)
0
 
LVL 25

Assisted Solution

by:Tony Johncock
Tony Johncock earned 250 total points
ID: 39284214
Hi

This I can help with :-)

From http://support.citrix.com/article/CTX135050:
(Which I realise talks about changing from http to https but still valid)

SetHostBaseUrl.ps1 "http://storefront.example.com"
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In-place Upgrading Dirsync to Azure AD Connect
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question