Changing Domain Controller for Exchange 2013

Folks
I have an Exchange 2013 running on Server 2012.
Old DC on Server 2008.
I want to decommission the 2008 server. I have build a 2012 DC and for the life of can not work out how to change the DC that my exchange box uses????
Using Set-ADServerSettings cmdlet only seems to change the server for that current session?? reboot and back to the old DC...
When I use the Se-ExchangeServer cmdlet, I get domain controller cant be found. I have set the execution policy on the dc to unrestricted and still Domain controlleer cant be found..
New dc is a GC..
Any ideas would be good.
-graham

First, the behavior observed for the cmdlet Set-ADServerSettings is normal. The values for the domain controllers
designated are " per session". For example:
The PreferredServer parameter
specifies the FQDN of the domain controller to be used for this session.
http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
+++
What parameters, exactly, did you use for Set-ExchangeServer? What was the entire command?
If the domain controller(s) were found for "Set-ADServerSettings"
and... if Exchange is functioning OK in general, the domain controllers should be accessible.
+++
Are you in a position where you could shut down the older server (during off hours for example) and see if Exchange can
find - and use - the newer DC?
Will you only have one DC after decommission of the old one?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

Changing domain name on Exchange 2013

Hi All,
Having changed the domain our 2012 AD Server is running on from domainv2.local to domain.com, in order to ensure valid wildcard SSL certificate can be used rather than a self signed with unmatched domain causing invalid SSL popups all the time, the Exchange
2013 server no longer works. I should have looked at the implications to Exchange prior and from what I am reading there is no way to change the domain name used by Exchange as of 2003.
I currently cannot connect on EMS/ECP/OWA/Clients, and am slowly coming to terms with the fact that I will have to do a reinstall of the 2012 and exchange server on the new domain.
The current error I get on ECP is:
Server Error in '/ecp' Application.Cannot find information about the local server host.domain.com in Active Directory. This may be related to a change in the server name.
Can anyone please advise on the best procedure to follow to recover from this? I want to keep as many settings as possible so that I can review them while installing the new server as it took some time to get it where I wanted it.
I assume that the main thing is to back up the database and the logs and then install using the same file paths. But imagine there is a lot more that I will be able to retain if done properly.
Kind Regards,
Anthony

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Addon Domain Name for Exchange 2013.

Dear All,
I have one exchange Server 2013 ([email protected]) but my organization have more 5 domain name. Now we need add in the exchange server more 5 domain name for mail ID. It's possible in exchange server to add addon domain name for mail ID.
Md. Ramin Hossain

Yes Absolutely. You can add as many as you want, they are added under Accepted Domains.
Make sure you have already pointed the MX Records to your exchange server and after adding the domain to accepted domain you will start receiving the emails.
Where Technology Meets Talent

Preparing Domain for Exchange 2013 in an Exchange 2010 Organization

When preparing the domain for Exchange 2013, can we use the same Organizational Name as was used for Exchange 2010 or should we select a new variation?

When preparing the domain for Exchange 2013, can we use the same Organizational Name as was used for Exchange 2010 or should we select a new variation?
You dont have define the org name since it already exists.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Recovering Domain Controller in Exchange 2010 environment.

Hi Friends,
We have one windows 2008 Domain controller & one Exchange 2010 server with all role installed, My problem is if My domain controller failed , how i can recover it?
Is there ant step for domain controller recovery in Exchange 2010 Environment.?
Thanks & regards,
Pradeep

Hi Pradeep,
Sorry to hear that... The only option you have is to do non-authoritative restore of Active Directory...
From Exchange prospective, once you do restore from an old backup whatever changes you made in Exchange since then won't be there as Exchange keeps all the settings in active directory, for example if you have created users then you would need to recreate
them and attach their mailbox to back to users...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Configuring Lync Server 2013 to be a partner Application for Exchange 2013

Hello Guys,
I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever.
As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013.
But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain.
So I started to review the script to find the issue and I found that the script was configured as below
$acceptedDomains = Get-AcceptedDomain ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains[0].Name;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
which is totally wrong as below:
firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain.
Not all customers configure the name of the Accepted Domain to be the Domain Name.
Secondly it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
The first domain may be not the default Accepted Domain.
So I have configured the script as below
$acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"} ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains.DomainName;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
I hope This help.
Thanks
Ahmed Fouad

Hi,
This is helpful, thanks for sharing.
Best regards,
Belinda Ma
TechNet Community Support

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Change layout controller for permissions in details command

How can we change layout controller for permissions shown when you select any repository > details > settings > permissions. here only 5 users are shown in the table i wanted to change the layout to see if i can display more than 5 rows but i can not seem to find the iView corresponding to this pop up screen. Any ideas?

Hi Firasath,
In the end, this is a modification of the standard, and there are several ways to do such things (and to avoid problems with it, for example when upgrading your installation).
As this is a complex task, I won't say this and that is the right direction. That's really an individual decision for each customer. I know customers who really have a lot of modifications (and they enjoy their extended functionality), others I know who never ever would touch the SAP code. And many ways are in between...
Just for a very fast shot (but not advised as a "clean" way), you could decompile the class itself, make it compilable as a Java project consisting of one class (extending the compile classpath to fit the classes needs), do the change, exchange the original class within the JAR by your modified version and restart the portal (for exchanging WinRAR for example can be used very easily).
A more clean approach would be to import the original PAR as a portal project, decompile the class in question, remove it from the compiled JARs (which have to be added manually into the PAR structure), recompile and redeploy (within the same original namespace).
A more complicated approach is to try to create a new PAR within a new namespace, so that in the end you are not modifying the original component but just "steal" code from the original component and deploy it independently. But this needs most experience.
Not understood everything in detail?! In this case, sorry, but: It's really an absolute non-trivial task which only should be done by people having the experience to understand these lines more or less in a second...
Hope it helps
Detlev

Unable to find domain controller for the specified domain. Please explicitly specify the domain controller.

Im getting error "Unable to find domain controller for the specified domain. Please explicitly specify the domain controller." when I try to create an AD connection for my User Profile Service. The entire sharepoint environment is installed
on one server. That server has everyting on it, AD, SQL, Sharepoint, and its the domain controller. I cant figure out why this will not identify?Trevor Fielder

Hi,
Did you get this error when clicking on the Populate Containers button?
If yes, please make sure that you have provide the domain credentials in the account name and password
boxes below when entering the domain information. The account must be granted the replicating directory changes permission on the domain.
You can refer to this blog:
http://www.harbar.net/articles/sp2010ups.aspx
Xue-Mei Chang

Transport agent for Exchange 2013

Hello!
I write transport agent for Exchange 2013 and I have two questions:
1. How I can determine is AD OU of recipient different from OU of sender?
2. How I can change routing of message from internal to external for such recipient.
Thanks in advance

1. You can't get that information from within a Transport Agent directly so you need to either use LDAP to lookup the sender (which from a performance point of view isn't a wonderful idea) or some form of cache etc.
2. You can use a routing override to do this see
http://blogs.technet.com/b/appssrv/archive/2009/08/26/how-to-control-routing-from-your-own-routing-agent.aspx for an example
Cheers
Glen

Enable legacy public folders for Exchange 2013 prior to migration?

We're about ready to migrate to Exchange 2013 from 2010. We have a public folder database on 2010 that users can't see once migrated to 2013. If I run through the commands according to the technet article "Configure legacy public folders where user
mailboxes are on Exchange 2013 servers" (https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx), will users who's mailboxes are still on Exchange 2010 be able to see these public folders?

I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Running setup.exe for Exchange 2013 does nothing

Hi All,
Unable to find this issue anywhere else, please excuse if it's a duplicate of another issue.
Basically, I have a new 2008 R2 server setup, added it to a domain, and want to install Exchange 2013 on this new server. There are no Exchange servers anywhere on the domain.
The server is fully up to date, including .Net 4, and looking for updates results in zero new updates found.
When I run setup.exe for Exchange 2013, a command prompt appears for less than a second, then closes, then nothing else happens.
Did a fresh reboot before trying to install, and after waiting about 20 minutes to see if anything happened after the vanishing command prompt, rebooted again, tried again, same result.
There is nothing called Exchange anywhere on the server that I can find, no setup logs or anything, and I am totally stumped.
Thanks in advance for any advice.
Michael

Hello,
Exchange 2013 need to be installed on windows server 2008 R2 SP1. If you use windows server 2008 R2 SP1, I sugegst you check if there is any exchange server via ADSIEDIT.
CN=Configuration,DC=Domain ->CN=services ->CN=Micorosft Exchange ->CN=Organization ->=Administrative Groups ->CN=Exchange Administrative Group ->CN=Servers
Here is the article for your reference.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx#WS2008R2SP1
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

ACL migration Error : 1210 could not find a domain controller for domain "Test Domain" (Old Domain)

Hi
We are migrating from old domain to new domain. Before live migration, we are trying to check the ACE/ACL migration through SubInACL. We are running the SubInACL on a cluster, which is a member of the Old Domain (Test Domain). We are able to resolve and
ping both Old Domain and the New domain from this cluster machine. We have created a network share on this cluster, which is accessible to all Domain Users of the Old Domain. Both Domains have two way forest level trust. we are trying to migrate
the ACL of this share (\\ClusterMachine\testshare$) to the new domain using SubInACL. We are trying to run the below command to get it done.
subinacl /outputlog=C:\Users\Administrator\Desktop\Migrationlog.txt /subdirectories
\\ClusterMachine\testshare$\*.* /migratetodomain=OldDomain=NewDomain=mappingfile.txt
Mapping file contains : Domain Users=NewDomain_Users
But we are geeting the Error that "1210 could not find a domain controller for domain "Test Domain". Error finding domain name : 1210 the format of the specified computer name is invalid. Current Object "\\ClusterMachine\testshare$"
will not be processed."

Hello,
how in detail is DNS set up in each domain?
Any problems when using nslookup to verify?
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Is smb 3.0 already supported for exchange 2013

Hello,
We are looking to deploy exchange 2013. We have a netapp storage and vmware environment.
I was wondering if smb 3.0 is already supported for exchange 2013. I read in a blog of 2012 that it wasn't supported at the time. We would like to use it instead of a iscsi lun.

Hi,
Based on my knowledge, it is still not supported for Exchange 2013 up to now.
Here is an article for your reference, please refer to the "Exchange storage requirements" section.
Exchange 2013 Virtualization
http://technet.microsoft.com/en-us/library/jj619301.aspx#BKMK_Prereq
Another related article for your reference.
Exchange 2013 Storage Configuration Options
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

Hello
The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
Are there any alternatives to this for Exchange 2013?
Thanks!

Haven't really played with it too much, but check out Get-ServerHealth
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Looks to have replaced Test-SystemHealth.

Changing Domain Controller for Exchange 2013

Similar Messages

Maybe you are looking for