27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 1 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

MSExchangeGuru.comLearn Exchange the Guru way !!!

HOME THE TEAM CONTACT US -MS EXCHANGE GURU DISCLAIMER MSEXCHANGEGURU ON YOUTUBE

« Exchange Server 2013Service Pack 1 and lotsmore

My 1st Blog atblogs.msdn.com »

Exchange 2013 SP1: Installation and UpgradeMicrosoft released SP1 on Feb 25 2014 with many changes and the organization (has a policy to wait forSP1 before considering into production) will be looking to deploy Exchange 2013.

Warning: Please test in your lab with all the agents and configurations before trying to installand upgrade in Production.

You can’t upgrade Windows when Exchange is installed on the server. http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

Warning: If you are running a 3rd party transport agent then you need to run the fixit scriptto run the transport Agent. The script can be download from here.

Many Organizations are expecting an increase in the migration projects. At this time we would like to guidethe steps of the Exchange 2013 Service Pack 1 installation.

Exchange 2013 SP1 is the Cumulative Update 4 which is also full exchange 2013 means you can directlydeploy Exchange 2013 SP 1 in your environment without previous versions.

Exchange 2013 SP1 will do the schema update so make sure we have healthy AD and Organization isaware about the change in schema with change approvals.

There has been a practice to stop replication on the schema master server and do the schema update. Andonce schema master tested a success, start the replication with other DCs throughout the Forest.

We can install Exchange 2013 SP1 in a windows 2012 R2 Active Directory. Check the exchange matrixhere.

Operatingsystemenvironment

Exchange2013 SP1

Exchange2013 CU2and CU3

Exchange2010 SP3RU5 orlater

Exchange2010 SP2

Exchange2007 SP3RU13 orlater

Exchange2003 SP2

WindowsServer 2003SP1 ActiveDirectoryservers

X X

WindowsServer 2003SP2 ActiveDirectoryservers

X X X X X X

WindowsServer 2008SP2 ActiveDirectoryservers

X X X X X X

CategoriesADLDSADRMSAutodiscoverBest PracticesBlackberryCASClusteringConferenceDAGDatabase ManagementDemotionDisaster RecoveryDomain ControllerECPEdgeEdge TransportExchange 2003Exchange 2007Exchange 2010Exchange 2013Exchange ActiveSyncExchange OnlineProtectionExchange ToolsExMergeExport Mailbox usingShellGFIHyper-VIISInstallationIOPSLegacyExchangeDNLyncMailFlowMigrationMiscellaneous blabberingsmsExch AttributesOAB/OALOCSOffice 365Online and Offline DefragOutlookOWAPOP/IMAPPowershellPublic FoldersRBACRecoveryRecovery Storage GroupSchema UpdateScriptingSIP FederationSite UpdatesTech BuzzTipsTransportUncategorized

MSExchangeGuru953LikeLike

MVP Exchange

Subcribe toMSExchangeGuruSign up for our NewsLetterand article updates Subscribeto MSExchangeGuru

Follow Us!

Recent CommentsPrabhat Nigam on PublicFolders Migration fromExchange 2007/2010 toExchange 2013Prabhat Nigam on Exchange2010/2007 to 2013 Migrationand Co-existence GuidePrabhat Nigam on Exchange2013 SP1: Edge TransportServer Installation andConfigurationPravin on Exchange 2013SP1: Edge Transport ServerInstallation and ConfigurationPravin on Exchange 2013:Recover a DAG and DAGNode from crash Part 3

EventMarch 31: MEC 2014

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 2 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

WindowsServer 2008R2 SP1 ActiveDirectoryservers

X X X X X X

WindowsServer 2012ActiveDirectoryservers

X X X X X

WindowsServer 2012R2 ActiveDirectoryservers

X X X X

Domainandforestfunctionallevel

Exchange2013 SP1

Exchange2013 CU2and CU3

Exchange2010 SP3RU5 orlater

Exchange2010 SP2

Exchange2007 SP3RU13 orlater

Exchange2003 SP2

WindowsServer2003interimdomainfunctionallevel

X

WindowsServer2003domainfunctionallevel

X X X X X X

WindowsServer2008 R2SP1domainfunctionallevel

X X X X X X

WindowsServer2012domainfunctionallevel

X X X X X

WindowsServer2012 R2domainfunctionallevel

X X

WindowsServer2003interimforestfunctionallevel

X

WindowsServer2003 forest

X X X X X X

UpgradeVirtualizationWindows 2012 R2

ArchivesMarch 2014February 2014January 2014December 2013November 2013October 2013September 2013August 2013July 2013June 2013May 2013April 2013March 2013February 2013January 2013December 2012November 2012October 2012September 2012August 2012July 2012June 2012May 2012April 2012March 2012February 2012January 2012December 2011November 2011October 2011September 2011August 2011July 2011June 2011May 2011April 2011March 2011February 2011January 2011December 2010November 2010October 2010September 2010July 2010June 2010May 2010April 2010February 2010January 2010November 2009October 2009September 2009July 2009June 2009

Conference

Other cool placesFlipping BitsLets ExchangeMSExchangeTeamPowerWindows

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 3 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

functionallevel

WindowsServer2008 R2SP1 forestfunctionallevel

X X X X X X

WindowsServer2012 forestfunctionallevel

X X X X X

WindowsServer2012 R2forestfunctionallevel

X X

Prerequisite:

1. Exchange 2003 should be removed from the Active Directory.2. Every Active Directory site should have a Global catalog server.3. Every Active Directory site should have one Windows 2003 SP2 or higher domain controller with GC.4. Domain and Forest functionality should be Window 2003 or higher5. All outlook Clients should be minimum or higher then mentioned below.

Outlook 2013 (15.0.4420.1017)Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update(14.0.6126.5000).Outlook 2007 Service Pack 3 with the Outlook 2007 November 2012 update(12.0.6665.5000).Outlook for Mac 2011

6. Current Active Directory and Exchange org is healthy.

Permissions required:

Your login id must have following group membership:

Domain Admins

Schema Admins

Enterprise Admins

Organization management if any (2010/2007) exchange org exist.

Preparing Exchange 2010/2007: If this is a coexistence then these steps will be required.

1. Install the hotfix 2550886 for DAG failover improvements on Exchange 2010/2007 DAG servers.

http://support.microsoft.com/?kbid=2550886

2. Login to the Exchange 2010/2007 server with Schema Admins, enterprise admins, domain adminsand organization management group member id as SP 3 will extend the schema.

3. Install Exchange 2010/2007 SP3 on all the exchange 2010/2007 servers in CAS then HT thenmailbox role order if they are not on the same server

SP3 can be downloaded from the below link:

http://www.microsoft.com/en-us/download/details.aspx?id=36768

4. Check the below link for SP3 installation steps

http://msexchangeguru.com/2013/04/03/exchange-2010/2007-sp3/

Pre-Exchange Installation preparation steps:

1. Server Build Steps:

Install the following prerequisites

For Windows 2012:

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 4 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

1. Open Windows PowerShell.2. Run the following command to install the required Windows components.

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console,Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

3. Restart the server.4. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

http://www.microsoft.com/en-us/download/details.aspx?id=34992

5. Microsoft Office 2010 Filter Pack 64 bit

http://www.microsoft.com/en-us/download/details.aspx?id=17062

6. Microsoft Office 2010 Filter Pack SP1 64 bit

http://www.microsoft.com/en-us/download/details.aspx?id=26604

For Windows 2008:

1. Open Windows PowerShell.

2. Run the following command to load the Server Manager module.

Import-Module ServerManager

3. Run the following command to install the required Windows components.

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net,Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing,Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

4. Restart the server

5. Microsoft .NET Framework 4.5

http://msdn.microsoft.com/en-us/library/5a4x27ek(VS.110).aspx

6. Windows Management Framework 3.0

http://www.microsoft.com/en-us/download/details.aspx?id=34595

7. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

http://www.microsoft.com/en-us/download/details.aspx?id=34992

8. Microsoft Office 2010 Filter Pack 64 bit

http://www.microsoft.com/en-us/download/details.aspx?id=17062

9. Microsoft Office 2010 Filter Pack SP1 64 bit

http://www.microsoft.com/en-us/download/details.aspx?id=26604

10. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)

http://support.microsoft.com/?kbid=974405&wa=wsignin1.0

11. Enable the Association Cookie/GUID that is used by RPC over HTTP to also be usedat the RPC layer in Windows 7 and in Windows Server 2008 R2

http://support.microsoft.com/?kbid=2619234

12. Knowledge Base article KB2533623 (Insecure library loading could allow remotecode execution)

http://support.microsoft.com/?kbid=2533623

2. Restart the servers before next step.

3. Download the Exchange 2013 Service Pack 1 from here. 4. Active Directory Preparation Steps: a. Disable the replication on the schema master server by running the following commands

repadmin /options serverhostname +DISABLE_OUTBOUND_REPLrepadmin /options serverhostname +DISABLE_INBOUND_REPL

b. Do the schema and domain update with the following steps

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 5 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

c. We need to install AD management tool to update schema so that it can read ldf files. Openpowershell with run as administrator and run the below command.

On 2012: Install-WindowsFeature RSAT-ADDS

On 2008: Add-WindowsFeature RSAT-ADDS

d. There is no setup.com and it is only setup.exe so run the below command to update schema.

”Setup.exe /prepareschema /IAcceptExchangeServerLicenseTerms”

e. Run the below command to update Active Directory

Important: We will not be able install exchange 2010 after this step. See the warning.

“setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms/OrganizationName:”GiveTheORGName”"

f. Run the below command in every Exchange user domain

-If we have only one domain then this command is not required.

-If we have to multiple domain and some of the domain will not use exchange then run the belowcommand in all the exchange domains.

“setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms”

Else run the below command to prepare all domains.

“setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms”

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 6 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

g. Post schema update checks

Run dcdiag and check for errors. Replication error will come as replication isdisabled.Open Active Directory Schema mmc and check it is working properly.Open Active Directory users and computers then check working.

h. Enable the replication traffic by running the following commands

repadmin /options serverhostname -DISABLE_INBOUND_REPLrepadmin /options serverhostname -DISABLE_OUTBOUND_REPL

i. Go to cmd and run the command “repadmin /replsum” and check for error. Try doing manualreplication from Active Directory Site and services.

j. We are done if the replication is working fine.

Installation Steps:

Run the setup.exe and you will see the below screen

On check for updates select “Don’t check for updates right now” and click next

Now we will see the below screen

After some time we will see the below screen, click next here.

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 7 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

At the license page select I accept and click next

Select “Don’t use recommended settings” and click next

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 8 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

Select the Exchange server role you wanted to install and click next. You can install Mailbox and ClientAccess together but Edge Transport will be installed separately and can’t be merged with any other role.Edge transport role will be fully managed by powershell until we install an Edge Subscription.

Select the installation path and click next.

If this is a first exchange server installation and you have not run the schema update then you will see the

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 9 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

below screen to add the Exchange ORG Name.

Give the Exchange ORG name and click next.

Go with default setting on Malware Protection setting and click next.

Now setup will run the Readiness Checks. If readiness comes clean then click Install. Else fix the missingupdate.

In my case this was the 1st exchange server in my lab on a domain controller so I got the warning. It is

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 10 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

not recommended to install Exchange on a domain controller. This is just my lab. Click next here.

Now we will see the setup progress screen which is a 15 steps setup because I am installing mailbox andclient access together. Number of steps will change as per your selection on role.

Take a break, it will take sometime depends on the hardware configuration. After some time you will seethe below screen.

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 11 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

Read the highlighted text and make sure we restart the exchange server.

After restart create a send connector or add this server in the send connecter in a coexistence.

If you are running a 3rd party transport agent then you need to run the fixit script to run the transportAgent. The script can be download from here.

Prabhat Nigam

Microsoft MVP | Exchange Server

Team@MSExchangeGuru

Posted March 2nd, 2014 under Exchange 2013, Installation, Schema Update, Tech Buzz, Tips,Upgrade, Windows 2012 R2. RSS 2.0 feed. Leave a response, or trackback.

28 Responses to “Exchange 2013 SP1: Installation and Upgrade”1. Exchange 2010/2007 to 2013 Migration and Co-existence Guide « MSExchangeGuru.com Says:

March 2nd, 2014 at 4:35 pm

[…] 7. Exchange 2013 Installation – Please follow the below link for the Exchange 2013installation: http://msexchangeguru.com/2013/04/29/install-e2013/or Exchange 2013SP1installation: http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/ […]

2. Art Alexion Says: March 3rd, 2014 at 3:04 pm

We have a 6 server cluster where we installed Exchange CU3 on Win Server 2012. When Iupgraded Server 6 to Win Server 2012 R2, I lost access to the Exchange Management Console.When I upgraded Exchange to 2013 SP1, the EMC returned. On Server 5, I upgraded Exchange,and then upgraded Windows and no EMC. So, I reinstalled the Exchange upgrade after upgradingWindows, and still no EMC. I installed Exchange every time with “setup.exe /m:upgrade/IAcceptExchangeServerLicenseTerms”.

Any ideas on how I get the EMC back?

3. Prabhat Nigam Says: March 3rd, 2014 at 3:27 pm

@ArtI am sorry but you are following an unsupported way.You can upgrade from Exchange 2013 to Exchange 2013 SP1 but windows 2012 to windows 2012R2 in-place upgrade is not recommended and supported.

You can probably check the ECP directory in IIS. There is no EMC in 2013 you need to use ECP.Because of the these issue it is not supported way of upgrade. You may expect some other issue ifyou try on another server but I will not recommend to do so.

4. Art Alexion Says: March 3rd, 2014 at 3:43 pm

Thank you, Prabhat. I followed this article for upgrading Windows

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 12 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

(http://www.techrepublic.com/blog/data-center/tips-for-an-easy-upgrade-from-windows-server-2012-to-windows-server-2012-r2/#ftag=RSS56d97e7) and the process seems to have gone well.Sorry for the confusion. I used EMC by mistake. I meant to use EMS as an abbreviation forExchange Management Shell. My question should have read:

“We have a 6 server cluster where we installed Exchange CU3 on Win Server 2012. When Iupgraded Server 6 to Win Server 2012 R2, I lost access to the Exchange Management *Shell*.When I upgraded Exchange to 2013 SP1, the EMS returned. On Server 5, I upgraded Exchange,and then upgraded Windows and no EMS. So, I reinstalled the Exchange upgrade after upgradingWindows, and still no EMS. I installed Exchange every time with “setup.exe /m:upgrade/IAcceptExchangeServerLicenseTerms”.

Any ideas on how I get the EMS back?”

5. Exchange 2013 SP1 -- Way to go Windows 2012 R2 - The Microsoft MVP Award Program Blog - SiteHome - MSDN Blogs Says: March 3rd, 2014 at 4:55 pm

[…] Exchange 2013 SP 1 installation steps are described here. […]

6. Prabhat Nigam Says: March 3rd, 2014 at 6:17 pm

It is not supported to upgrade a windows 2012 server to windows 2012 R2 Server which hasExchange 2013. I am searching a technet for this.Then techrepublic blog does not speak about the exchange server. So this is just for a windows2012 upgrade.

So don’t upgrade this way to remaining 4 servers.————

7. Prabhat Nigam Says: March 3rd, 2014 at 6:19 pm

For the current situation

Check the Exchange services are running.Then check if URL has changed.Check the powershell directory in IIS.

8. Prabhat Nigam Says: March 4th, 2014 at 7:05 pm

@Art

Check this text “You can’t upgrade Windows when Exchange is installed on the server.” in theTechnet article below:http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx

9. Art Alexion Says: March 5th, 2014 at 10:10 am

Thanks Prabhat. As I have learned, you are 100% correct. Here is how I solved the problem.

Uninstalled Exchange on that server (all the mailboxes had been moved from the database on thathost for the original upgrade, but it turns out that the uninstall does not delete the databases, incase someone who does this forgets to move the data first.)

Reboot. You will not be prompted, but it is necessary.

Reinstall (I used setup.exe /m:install /role:ClientAccess,Mailbox/IAcceptExchangeServerLicenseTerms

Thanks for your help, and I hope the above information is useful for anyone else with the problem.

10. Prabhat Nigam Says: March 5th, 2014 at 11:07 am

@ArtGreat to hear back a solution…

11. Art Alexion Says: March 5th, 2014 at 11:43 am

After you move the mailboxes off of any databases on the subject server, the uninstall command isas simple as setup.exe /m:uninstall.

The process of uninstalling and re-installing is unattended, but takes several hours to complete.

12. NeWay Technologies – Weekly Newsletter #85 – March 6, 2014 | NeWay Says: March 10th, 2014 at 12:08 am

[…] Exchange 2013 SP1: Installation and Upgrade – 2-Mar-2014 […]

13. NeWay Technologies – Weekly Newsletter #85 – March 7, 2014 | NeWay Says: March 10th, 2014 at 12:12 am

[…] Exchange 2013 SP1: Installation and Upgrade – 2-Mar-2014 […]

14. Senthil G Says: March 10th, 2014 at 2:48 pm

I’m little bit confused regarding the statement

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 13 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

Every Active Directory site should have one Windows 2003 SP1 or higher domain controller with GC.

Every site should have Win 2003 SP2 or higher GC right as per the matrix

15. Prabhat Nigam Says: March 10th, 2014 at 3:02 pm

@SenthilThank you. Corrected the typo.Hope rest of the blog was helpful and you installed Exchange 2013 SP1.

16. Senthil G Says: March 10th, 2014 at 4:25 pm

Thank you for the reply.Yes it was really helpfull.

17. Philips Says: March 12th, 2014 at 5:58 am

In a Virtual environment how Databases and log files should be placed? On the same disk ordifferent disk?

Ex. If we will create 10 database how many Virtual disk should add to the server?

Thanks

philps

18. Prabhat Nigam Says: March 12th, 2014 at 7:04 am

@Philips

you have asked 2 question.

-In a Virtual environment how Databases and log files should be placed? On the same disk ordifferent disk?Databases and log files should be placed on different physical disk to get best performance. Todaymost of the disk has higher disk IOPS so we are keeping database and log files on the samedatabase.

-Ex. If we will create 10 database how many Virtual disk should add to the server?10 Databases can be on same disk or in the a big partition of multiple physical disks so it alwaysdepends on IOPS you get and how you have configure the environment.

If you wish to use reseed feature, then you need to plan 1 disk per database and log to get fasterreseeding.

Conclusion: It depends on IOPS and features you are planning. Database and logs can be on samedisk.

19. Art Alexion Says: March 13th, 2014 at 5:14 pm

I was upgrading 6 pre-production servers (not yet clustered) There are 6 servers, MB01-MB06. Iwas upgrading per the procedure in my last comment, starting with MB06. All good through MB02.Setup.exe is not letting me uninstall because there are still mailboxes in its associated database, thearbitration mailbox, FederatedEmail, and DiscoverySearchMailbox. Neither of these are visible in theECP and have to be moved via PowerShell. While the other system mailboxes moved these keepfailing.

I am afraid to delete them and recreate them as there are some production mailboxes in theenvironment and I don’t know the effect.

Any suggestions?

20. Prabhat Nigam Says: March 13th, 2014 at 5:25 pm

You can move them to a different Database on different server.Check out then commands herehttp://msexchangeguru.com/2013/05/10/exchange2013-migration/

21. Art Alexion Says: March 14th, 2014 at 3:43 pm

Thanks, Those are the very commands I used and the moves keep failing. I can’t do this throughthe ECP, and can’t find the reason for failure in the logs. Perhaps I am looking in the wrong place orthe wrong log.

How much damage would it do to remove the mailboxes and re-create them per these instructions?They apply to 2010, so I don’t know if there are material differences.http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx

22. Prabhat Nigam Says: March 14th, 2014 at 4:13 pm

These commands work. Did you try these commands?Get‐Mailbox –Arbitration | New‐MoveRequest –TargetDatabase TargetDBNameGet-Mailbox “*Discovery*” | New‐MoveRequest –TargetDatabase TargetDBName

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 14 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

If yes then try the following.Open Exchange management shell with run as administratorGet‐Mailbox SourceDBName –Arbitration | New‐MoveRequest –TargetDatabase TargetDBNameGet-Mailbox SourceDBName “*Discovery*” | New‐MoveRequest –TargetDatabase TargetDBName

Could you share the error?

In ECP you can go to Migration tab and create a move. There you will be able to search thesemailboxes.

Damage will not be much. Many functions will not work.

If you delete the database without moving these mailboxes then you will have to disable themailbox and Enable them back. I will not recommend deleting the database without moving themailboxes.All the steps mentioned on your link will not work because you still have users but mailboxes hasbeen removed.

23. Art Alexion Says: March 17th, 2014 at 11:09 am

Thanks, Prabhat. I was using the commands,Get‐Mailbox –Arbitration | New‐MoveRequest –TargetDatabase TargetDBNameGet-Mailbox “*Discovery*” | New‐MoveRequest –TargetDatabase TargetDBNameandGet‐Mailbox SourceDBName –Arbitration | New‐MoveRequest –TargetDatabase TargetDBNameGet-Mailbox SourceDBName “*Discovery*” | New‐MoveRequest –TargetDatabase TargetDBNamebut was getting undefined failures.

So, I used the ECP from the migration tab, and though the failures persist, I was able to determinethat the cause was corrupted x.400 address on these two mailboxes. Some background, a whileback, while on a support call with Microsoft we were instructed to run a command that removed allof our 2007 mailboxes. While we were able to recover our mailboxes, the x.400 addresses werecorrupted. This, generally, does not cause a problem in our environment. When making changes toa mailbox via the 2007 console or the 2013 ECP, we get an error when trying to save. I delete thebad x.400, and everything is OK.

The problem I have now is that I can’t use ECP to access the properties of these system mailboxesand am having trouble using the set-mailbox -EmailAddress command-let because I don’t have thefull addresses to use in Powershell.

Your help has been fantastic, and I hope you can suggest a solution.

24. Art Alexion Says: March 17th, 2014 at 11:51 am

Here is an error I am getting

[PS] C:\Windows\system32>Set-Mailbox -Identity “discoverysearchmailbox{d919ba05-46a6-415f-80ad-7e09334bb852}” -EmailAddresses @{remove=’x400:C=US\;A= \;P=RHD\;O=RHD.ORG\;S=MsExchDiscoveryMailboxD919BA05-46A6-415\;?’}The address ‘x400:C=US\;A= \;P=RHD\;O=RHD.ORG\;S=MsExchDiscoveryMailbox D919BA05-46A6-415\;’ is invalid: Specifiedargument was out of the range of valid values.Parameter name: “C=US\;A= \;P=RHD\;O=RHD.ORG\;S=MsExchDiscoveryMailbox D919BA05-46A6-415\;” isn’t a valid X.400address space.+ CategoryInfo : NotSpecified: (:) [Set-Mailbox], DataValidationException+ FullyQualifiedErrorId : [Server=MB01,RequestId=9c18b0e3-68e6-444a-91e0-cfad460be2ac,TimeStamp=3/17/2014 3:49:08PM] 391243F1,Microsoft.Exchange.Management.RecipientTasks.SetMailbox+ PSComputerName : mb01.rhd.org

Of course the x400 address is invalid. That is why I am trying to remove it!

25. Prabhat Nigam Says: March 17th, 2014 at 12:36 pm

@Art

Please use ADSIEDIT and active directory user and computers to access these user objects. Theyare in the default USERS OU.

26. Art Alexion Says: March 17th, 2014 at 1:29 pm

Wow! Thank you. ADSI Edit worked and the move completed.

27. Prabhat Nigam Says: March 17th, 2014 at 8:31 pm

Glad to hear I was helpful.

28. Exchange 2013 SP1: Edge Transport Server Installation and Configuration « MSExchangeGuru.comSays: March 24th, 2014 at 6:51 pm

[…] Install the Exchange Prerequisite from the help of my blog here. […]

27.03.14 23:51Exchange 2013 SP1: Installation and Upgrade « MSExchangeGuru.com

Seite 15 von 15http://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website

Submit Comment

Notify me of followup comments via e-mail. You can also subscribe without commenting.

© 2012MSExchangeGuru.com All Rights Reserved | Privacy Policy Entries (RSS) and Comments (RSS).