Microsoft Exchange Migration

Hi.
Is there any way to migrate the user password from exchange mail server to a messaging mail server (LDAP)??? crypt or sha or ssha???
Thanx Ram

Hi.
Is there any way to migrate the user password from
exchange mail server to a messaging mail server
(LDAP)??? crypt or sha or ssha???
Thanx RamYou can insert the password using ldapmodify. Place the ecryption method within barces.
Example:
#ldapmodify -D "cn=Directory Manager" -w password
dn: uid=user,ou=people,o=example.com,o=isp
changetype: modify
change: userPassword
userPassword: {SSHA}jddh#$fje99jkdj=e090jd
Note that you enter the between braceltes. You can specify SSHA, crypt, or SHA.

Similar Messages

Exchange Migration Workflow down

Using Exchange 2013 CU6 Standard with 2 Server in a DAG. Both Servers with the same Patchlevel. Last night the "Microsoft Exchange Migration Workflow" goes down. When I try to restart the Service goes imidetly down again.
Application Event says every time: Event ID 4999 from Source "MXExchange Common":
Watson report about to be sent for process id: 10984, with parameters: E12IIS, c-buddy-RTL-AMD64, 15.00.0995.029, M.E.Diagnostics.Service, M.E.Diagnostics.PerformanceLogger, M.E.D.P.PerformanceLogSet.StartLog, System.ArgumentException, 95c6, 15.00.0995.012.
ErrorReportingEnabled: False
Mailbox-Migration only works on the second node where no problems with Migration Workflow Service detected.
Any ideas?

Hi
In my case the event 4999 shows:
Watson report about to be sent for process id: 12992, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, MSExchangeMigrationWorkflow, unknown, M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10, System.NullReferenceException, 49af,
unknown.
ErrorReportingEnabled: True
Does that solution apply too? or it has another problem?, because began to raise another events like 1001 from Windows Reporting:
Fault bucket , type 0
Event Name: E12IIS
Response: Not available
Cab Id: 0
Problem signature:
P1: c-RTL-AMD64
P2: 15.00.0995.029
P3: MSExchangeMigrationWorkflow
P4: unknown
P5: M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10
P6: System.NullReferenceException
P7: 49af
P8: unknown
P9:
P10:
Attached files:
C:\Windows\Temp\1e07ce7f-6e1c-49ce-a995-6152985231ac\report.txt
C:\Windows\Temp\1e07ce7f-6e1c-49ce-a995-6152985231ac\report.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: c3dece0a-76c6-11e4-80d0-6cae8b1d2a4b
Report Status: 262144
Hashed bucket:
But I cannot find the file report.txt and .XML even if I select to show hidden ítems.
In the active node of the dag, that service is running without problems, but in the other node stops....
or raise Eventid 7031 Service Control Manager:
The Microsoft Exchange Migration Workflow service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
This raise every 10 seconds... even if I set that service in Manual startup type.
I noticed this when I tried to add a database copy with no success...
Exchange 2013 CU6 and all patch applied until this week.

Double prompts for Exchange 2013 migrated users: "The microsoft exchange administrator has made a change that requires you to restart outlook"

I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
A couple of pieces of information that may be relevant:
1. On exchange 2013, the authentication method for the internal host name is NTLM
2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
Thanks in advance for your help.

Hi,
From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
For your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
https://support.microsoft.com/kb/2934750?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Problem e-mailing reports after migrating to new Microsoft Exchange server

Hi,
I am now unable to e-mail (SMTP) reports to anyone in my company because we just migrated to a new Microsoft Exchange server. Anyone know how to get rid of this message?
Status: Failed
Printer: The instance is not printed.
External Destination: Mail the instance to "____________" with a subject of " %SI_NAME% %SI_STARTTIME% ".
Data Refresh Settings: Use the server defaults.
Start Time: 8/4/09 1:00:18 PM
End Time: 8/4/09 1:01:07 PM
Server Used: gmmc-crs.reportjobserver
Error Message: server error. SMTP_E_TCPSOCKET_OPEN(2): CrystalEnterprise.Smtp
We tried changing the gmmc-crs.reportjobserver with no luck.
Thanks,

Hi,
You need to start with your exchange logs and possibly enable tracing on your BO webi/crystal/destination job servers (depending on the type of report and whether or not it is scheduled) to get an idea of how far down the line the SMTP connection is getting.
You could also confirm a few key things:
Have the SMTP destinations on your BO servers been updated with the new SMTP server info
Can you telnet to the mail server on port 25 from the BO server - if not, then check the firewall between the two servers and change the existing ruleset to allow connectivity to the new server
Possibly the old mail server didn't require authentication and the new server does, you could test this through telnet?

Migration issue - X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.StoragePermanentException

Im in the middle of a rather large migration and a few users are see the below error when trying to log in to OWA:
X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.StoragePermanentExceptionI cant find much on this error other than the enable inheritance permissions fix which all these accounts already have.Has anyone else come across this before?

Hi
This problem occurs because the discretionary access control list (DACL) inheritance is disabled on the user account in Active Directory. The Exchange Servers group must have permissions
to write the msExchUserCulture attribute on the user when the language has been specified in OWA.
To resolve this problem, follow these steps:
1. Open Active Directory Users and Computers.
2. Click View, and then click Advanced Features.
Note To make the Security tab available at both the user level and the organizational unit level, you must enable the Advanced Features option in Active Directory Users and Computers. This option is available under the View menu.
3. Open the properties for both the user level and the organizational unit level that the users are located in, and then locate the Security tab.
4. Click Advanced.
5. Make sure that the following check box is selected:
Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here.
6. Force Active Directory replication.
Remember to 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

Migrate or Redirect Client Mail Server to Microsoft Exchange Server

Hi, i am new in Microsoft Exchange Server and Email Administrator. At present, my company planed to have a Microsoft Exchange Server 2013 and my scope will be redirect or migrate the webmail database to the Exchange. Would you guys give me any solution and
advice for this? Thanks a ton
Sorry for my bad English.

Hello,
The steps can be like this. There are various approached available and this can be a general approach
1. Install and configure the Exchange 2013
2. Export the current mailboxes to pst
3. Create the current domains as accepted domain in Exchange
4. Change DNS and direct email traffic to Exchange server
5. Import the psts to new outlook
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

Microsoft Exchange server and Mailbox box prompt after migration

We are getting prompted to click OK when we open Outlook on the Microsoft Exchange server and Mailbox dialog box.
We just migrated from 2007 exchange to 2013 exchange and the people with windows 7 seem to be able to access exchange through outlook 2010 without getting prompted. Also people who are getting prompted are not able to access public folders and our
XP. Those using windows 7 can access public folders.

Hi,
From your description, I would like to clarify the following thing:
Windows XP does not like msstd:*.domain and must use msstd:server.domain instead.
So I recommend you set this by updating the CertificateName via EMS.
1. If you use a wildcard certificate, please run the following cmdlet:
Set-OutlookProvider EXPR –CertPrincipalName msstd:*.contoso.com
2. If not please run the Set-OutlookProvider EXPR –CertPrincipalName msstd:$null cmdlet. Once done, repair Outlook profiles and check results.
Besides, when there is a Windows XP user, we recommend SAN certificate not wildcard certificate.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Migration of Microsoft Exchange to iMS

Hello,
I need to migrate Microsoft Exchange users and mailboxes to iMS 5.2. Anyone knows were I can find information, procedures or tools to do this ?
Thanks in advance.
Regards.

For the end user this should be transarant as they should use their favourite client (eg MS Outlook, Thunderbird, etc). It is easy to manage when you have sufficient Oracle skills (db and AS).
Of course you have other components (calendar, RTC, Portal, News, Discussion, etc) in the OCS.
cu
Andreas

Migration from exchange SBS 2008 to Microsoft exchange 20013

i have started an upgrade of an SBS 2008 to an exchange 2013
i installed the 2 server in coexistence and moved all mailboxes as well as all public folders
what should i do next to be able to decommission the SBS and turn it off completely
PS: our company does use third party certificate as all the users are local users on TS server
much appreciate it

Please follow the Microsoft Exchange Server Deployment Assistant
which is web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios.
http://technet.microsoft.com/en-in/exchange/jj657516.aspx
Exchange Queries

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
Symptom
=======================================
Consider the following scenario:
Exchange 2013 was installed for a migration from Exchange 2007/2010.
The legacy Exchange server is removed after successful migration.
Exchange 2013 may be updated to Exchange 2013 SP1.
Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Cause
=======================================
The issue may be caused due to Public Folders.
The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
Solution
=======================================
Removed the Public Folder from all the Exchange
2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
1. Open ADSIEdit.
2. Connect to the Configuration container.3.
Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
please clear the value.8. Click OK.9. Check the rest of the databases to make sure
that they are not populated in the same way.
References:
https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This one? http://support.microsoft.com/kb/2934750

Microsoft Exchange Categories in iCal, Address Book and Mail

I work in a Microsoft environment with my MacBook Pro and would like to use iCal, Address Book and Mail as my default applications rather than Microsoft Oulook 2011, however, there is not support for the Microsoft Exchange Categories to be replicated into the various Apple applications. This results in my address book not to differentiate any longer from my contact categories stored on the Exchange server, nor my calendar. Categories can be created in iCal and other Apple applications but it then requires for the event or contact to be duplication "On my Mac" which makes me loose my synchronization with other systems. Any idea about to fix that?

Same issue here. I would love to migrate to iCal but the lack of support for categories is a limiting factor. Same applies to Contacts.

The Microsoft Exchange Address Book was unable to log on to Exchange

I am currently migrating a exchange 2007 to exchange 2013.
Exchange 2013 is installed on a seperate Windows Server 2012 server.
Exhange 2007 is installed on a seperate Windows Server 2003 R2 server.
I have moved some mailboxes from exchange 2007 to exchange 2013 and also created some new mailboxes on the exchange 2013 server itself.
OWA, ActiveSync , IMAP are all working correctly for those mailboxes , but I am not able to connect to outlook with the exchange option (local connection).
Outlook 2013:
When I use autodiscover to connect to the exchange server step 1 & 2 are working correctly (establishing network connection & searching for mailbox settings) but on the 3th step (logging on to the mail server) I receive the following error
The name cannot be resolved. The Microsoft Exchange Address Book was unable to log on to Exchange. Contact you system administrator if the problem persists.
When I filll in the exchange server manually (using the normal servername server.hq.corp.domain.local not the guid version) the check name resolves correctly and the profile creation is finishing ok. But when I try to open outlook with that profile it gives
me the following errors :
with cached exchange mode selected:
Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened.
You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)
with cached exchange mode deselected:
Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened.
Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance
When I use the Microsoft Connectivity Analyzer it fails on the following step:
Testing the address book "Check Name" operation for user [email protected] against server [email protected]
An error occured while attempting to resolve the name. Elapsed Milliseconds: 91 Additional Details: The address book bind operation failed with status -2147221231. NSPI Status 2147746065

Hi,
Please run the following command in Exchange server to get Exchange GUID:
Get-Mailbox UserA | FL Identity,ExchangeGuid
Then open Outlook, click File > Account Settings > Account Settings > Change (If you can’t open Outlook, go to Control Pane > Mail to change it). In Server Settings, import the [email protected] into the Server box and click Check Name
to have a try.
If the name is checked successfully but also can’t open the profile, please close Outlook. In the Start menu, Run command (Windows key + R), type or paste
outlook.exe /resetnavpane (Note: Make sure there is a space between the words.)
Then press Enter (or OK button) to restart Outlook
Regards,
Winnie Liang
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

Hello all,
We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40'
Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
I also ran these commands in shell to attempt to cancel the stuck request.
Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

Hello,
Please try to restart iis services to check the result.
If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
Set-AdServerSettings
http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
Besides, please install the lasted rollup to check the result.
Cara Chen
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs. I had a similar problem which I solved by removing some old migration batches, now I have a problem
with the Microsoft Exchange Mailbox Replication service.
The event logged is:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
configured incorrectly DNS server.
The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring. When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
How can I stop these events occurring and is it likely to be causing something else not to work correctly.
We are running Exchange 2013 CU1

No, that didn't work. Here are more details:
Source: MSExchange ADAccess (EventID: 2130)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
incorrectly DNS server.
Source: MSExchange ADAccess (EventID: 2119)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
Common causes of this error include the following:
- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
at set intervals. This computer is configured to use DNS servers with following IP addresses:
10.59.100.7
10.59.100.8
fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
- One or more of the following zones do not include delegation to its child zone:
admin.riddlesdown.local
riddlesdown.local
local
. (the root zone)
Source: MSExchange Mailbox Replication Service (EventID: 1121)
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
--> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Something is cause the Exchange server to go looking for our old domain, but what and why?

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Microsoft Exchange Migration

Similar Messages

Maybe you are looking for