I need help uninstalling Exchange 2013. The uninstaller fails with these 2 errors:

This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue.
This computer is responsible for expanding the membership of 1 dynamic distribution groups. These groups must be reassigned to another server before Setup can continue.

I've gone so far as to disabling all distribution groups which removes its email properties and the uninstaller still fails.
This is what happens in the eventlog:

System.Management.Automation.ParseException: At line:1 char:67
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+                                                                   ~~~~~~~~~~~~~
Unexpected token 's-Hertogenbosch/ou=Exchange' in expression or statement.
At line:1 char:175
+ ... s/cn=CADEXCDB13'}
+                    ~~
The string is missing the terminator: '.

At line:1 char:38
+ Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
+                                      ~
Missing closing '}' in statement block.
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
] [ParentValue:"<NULL>"] [Thread:11] [Duration:00:00:00.0156248]

I'm sure what happens here is the powershell commands looking at the distribution groups fail, because of our city name ('s-Hertogenbosch). Because of the apostrophe, the parameter is not passed successfully of this legacyExchangeDN. As this check fails, I believe the readiness check fails on these steps.

This legacy administrative group name is still left from a 2003 -> 2010 -> 2013 migration.

I've opened a Microsoft support request for this last week, but I thought someone might have dealt with this? I want to do a clean uninstall if possible.

I have a new install of Exchange 2013, with the DC on a separate machine with Server 2012. I'm trying to setup users on it. Machines that have Windows 7 connect completely fine. No interaction is needed to get Outlook up and running. 

Machines with Windows XP SP3 cannot connect at all. Using Internet Explorer and going to https://mail.domain.com/owa shows a "Internet Explorer cannot display this webpage". Trying to connect with Outlook 2007 shows a "Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." error box. 

Both the DC and Exchange machines are using Centralized Certificates. I have SSL certs for both the mail.domain.com and autodiscover.domain.com installed. 

I can connect to https://mail.domain.com/owa from Firefox and Chrome on the XP machines and all shows OK. Just not IE. 

This is the log from Outlook when trying to connect:

All tests from TestEchangeConnectivity pass.

I have migrated most of my mailboxes from our Exchange 2010 server to our Exchange 2013 server.   (single Exchange 2010 server (all roles) and a single Exchange 2013 server (all roles) within the same domain.

Two of my users have started seeing their x500 address show up as their return address and show up as the creator of Calendar meetings on their  computers (Outlook 2010, Outlook 2013).   From OWA, they see their user name, and the recipients of their emails or calendar invites see their username and or email address (SMTP).  But from their own outlook they see their x500 address.   The strangest part, is that even after deleting the x500 address from their user mailbox in Exchange 2013 ECP  they still see this address.   Also, If the user is not in cached mode, the x500 does not appear.  

So, I guessed that it was a profile issue and creating a new profile for the user would fix the problem.  I created a new profile and it did fix the problem, for 1 day, then the issue returned.   Where is Outlook getting the address from?  It is no longer an address for the user.  And if the user is not in cached mode, the issue does not occur.

So far it is not causing any mail flow issues, just annoyance with end users.   

Note:  Exchange 2013 is in hybrid configuration with Exchange Online and the x500 address /0=ExchangeLabs/... is still present, but it is not the x500 address that is showing up for the users.

Fred Zilz

I have installed Exchange 2013 in Exchange 2010 environment everything working fine except outlook autodiscovery for exchange 2013 users. If I change EXPR frommsstd:e2k10ht.abc.com   tomsstd:e2013ht.abc.com Exchange 2013 outlook Auto discover working  and Exchange 2010 user outlook prompt for password .

[PS] C:\Windows\system32>Get-OutlookProvider

Name                         Server                       CertPrincipalName            TTL

----                         ------                       -----------------            ---

EXCH                                                       msstd:e2013ht.abc.com       1

EXPR                                                       msstd:e2k10ht.abc.com...   1

WEB                                                                                      1  

Regards

Bhupen

Hi all

I encountered a weird issue when migrating Public Folders from Exchange 2010 to 2013. I follow part 2 of the tutorial from msexchange.org, and came as far as the command

[PS] C:\PB-Migration>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -server EXCH.domain.com) -CSVData (Get-Content .\PB-Folder-Mailbox-Map-Final.csv -Encoding Byte)

When then running Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics, I got the following error:

Cannot process argument transformation on parameter 'Identity'. Object reference not set to an instance of an object.
    + CategoryInfo          : InvalidData: (\:PSObject) [Get-PublicFolde...questStatistics], ParameterBindin...mationE
   xception
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-PublicFolderMigrationRequestStatistics
    + PSComputerName        : exch2013.domain.com

Having a closer look at the migration request, it struck me that the name column was empty:

[PS] C:\PB-Migration>Get-PublicFolderMigrationRequest

Name                                           SourceDatabase                                 Status
----                                           --------------                                 ------
                                               CompanyPublicFolders                         InProgress

The identity of the migration request is reported as 00000000-0000-0000-0000-000000000000, but also here something seems to go bad:

[PS] C:\PB-Migration>Get-PublicFolderMigrationRequestStatistics -Identity "00000000-0000-0000-0000-00000000000"

After a while, the status of the migration request changed from "In Progress" to "Failed".

How can I get a "handle" on this migration request, for either canceling/removing it or finding the reason for failure?

Thanks for reading and regards
/Maurice

My system is Win server 2012 running on premises, with MS Exchange 2013.  Can't connect to EAC or EMS.  Nothing is working.  The upgrade instal was performed via the power-shell:  The upgrade finished successful.  I rebooted the machine, all services started except Internet Connect Sharing (ICS).  I went to open the EMS and received the following error:

         Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Tip of the day #27:

Want to work with data contained in a CSV file? Use Import-CSV to assign the data to an object. For example, type:

 $MyCSV = Import-CSV TestFile.CSV

You can then manipulate the data easily in the Exchange Management Shell. For example, if there is a column called Mailb
oxes in the CSV data, you can use the following commands to sort or group the data by the Mailboxes column:

To sort: $MyCSV | Sort Mailboxes
To group: $MyCSV | Group Mailboxes

VERBOSE: Connecting to mail1.dorothy.local.
New-PSSession : [mail1.dorothy.local] Connecting to remote server mail1.dorothy.local failed with the following error
message : [Server=MAIL1,RequestId=00000000-0000-0000-0000-000000000000,TimeStamp=8/13/2013 1:41:27 PM]  For more
information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed
VERBOSE: Connecting to MAIL1.dorothy.local.

Please assist.

Randy Cheek

Randy Cheek

I am setting up a new 2013 Exchange server with 3.5TB of usable data space on a Raid 10 array.

We have Exchange Standard, so only 5 databases allowed.  We currently have about 700 users using 300 GB of space, but trying to make room for growth.

Should I carve the array up into separate volumes for databases and logs?  Is it best to start large or small with volume size?  2TB is the database size limit, right?  Can't see us needing that much space for a long, long, time.   And how much log space do I need in proportion to mailbox database size?

Hello All,

I currently have a small Exchange Hosted environment that exists of one Exchange 2007 Server.  I want to start the process of migrating my hosted solution to Exchange 2013 and was hoping someone could guide me in the right direction.  TIA

Larry

Larry D.

We currently have following structure:

Empty Root - OURCORP.LOCAL

Child domain - XYZCORP.COM  (both, internal/external dns names)

Exchange Org/2010 DAG currently exists in XYZCORP.COM. The company is planning to add new child domain - NEWCORP.COM and also introduce Exchange 2013 into an existing Org. The company wishes to create new Exchange infrastructure in NEWCORP.COM child domain and then get all the mailboxes out of XYZCORP.COM to NEWCORP.COM Exchange infra.

1. Is it possible to introduce an entirely new set of exchange servers within same Exchange Organization but in a different domain? 

2. What are the caveats/constraints we need to be aware of in general? What about for co-existence / migration scenarios, considering it's in the same forest? 

3. Any links specifically dealing with the Active Directory design and planning for Exchange in multiple child domains would be most appreciated.

Thanks in advance!

Currently working on installing 2x 2013 servers in coxistance with 2007.

I have the MBX role installed as defined, and was going to install the CAS role on the 2nd server next.  I tried looking at the local admin consle and it wont work.  

I have a feeling it wont work until I install the CAS role on the other 2013 server. Am I correct on this?  Just want to make sure before I add another server.

Front end is CAS, back end is MBX roles.

Thanks, Grady Vogt

We have an Exchange SP2/hosting setup running and want to upgrade to Exchange 2013CU1 

Is it possible to upgrade SP2hosting to sp3/hosting and install a new Exchange 2013cu1 setup and migrate the organizations and mailboxes without building a new forest ?

Or must i make a new forest with exchange 2013 and migrate then using the migration tools ?

Wouter

Hi, 

I am running Exchange 2013 in Coexist and Frankly hate it, nothing but problems I have been having.  I haven't been able to migrate any mailboxes over to the 2013 environment because I cant get it working.  

Here is my setup:

ExchangeFE1 - Exchange 2010 CAS

ExchangeMail - Exchange 2010 Mailbox Server

ExchangeUM - 2010 UM Role

Mail 13 - 2013 Mailbox, UM

MailExchange2 - SEcondary 2013 Mailbox Server

Exchangecas13 - 2013 CAS Server

Using OWA on the 2013 CAS server I can send/receive email perfectly fine both internal and external.  I am unable to get Outlook to work at all.  Even when I manually try typing in the server it doesn't work.  What does work for no apparent reason is if I type exchangefe1 as the server and type the user on the 2013 mailbox and click checkname it then, fills in Mail13 as the server.  However, if I manually type Mail13 it doesnt work.  Even when I get done with that it wont let me open the mailbox says I have to already open it.  

Alright so I Figure its a certificate issue.  I add the local Exchange2013 cert to my PC's trusted root certificate, doesnt work.  So then I create an SSL cert with Godaddy.  It complains because the command name is company.domain.com.  

The other issue is that Webmail Redirection doesnt work I looked at the logs it tries but never gets there.  Right now I am running two seperate SSL certs one for production through Godaddy and 1 for our 2013 environment with Godaddy.  There still might be a cert issue but this coexist is confusing me because I dont want to impact anything running.  

I run autodiscover on the 2010 environment but its not configured on the 2013 environment.  I can only have 1 SRV record so I dont want to take down the 2010 environment which is were all the mailboxes are.  

Any assistance is greatly appreciated. 

Hello,

I have a three node Exchange 2013 DAG.  Currently when I look at the DAG Cluster Resources in Failover Cluster Manager I see that one of the cluster IP addresses is offline.  I am curious if that is normal behavior?

This DAG is a cross-site DAG with two of the servers at one location and the third at another physical location.  We are rebuilding one DAG member or there would be two at each location with a FSW at a third.

When I ping the DAG name my DNS server is returning the DAG IP that is currently offline.  Should DNS have an entry for both of the IP's or should the DAG be updating DNS whenever the databases move to the other site?

Thank you,

Matt

I deployed updated todays to some servers in a DAG that I am deploying and the first two of the servers I installed the updated on removed the Microsoft Exchange Search Host Controller service from services. There is a new service called Host Controller Service for Exchange, but does not start. All indexing on all 48 Database copies is in a failed state.

In the servicestate.15.00.0620.032.xml file I see this new service

-<Obj RefId="855"><TNRef RefId="0"/><ToString>HostControllerService</ToString>-<Props><B N="CanPauseAndContinue">false</B><B N="CanShutdown">false</B><B N="CanStop">false</B><S N="DisplayName">Host Controller service for Exchange </S>-<Obj RefId="856" N="DependentServices"><TNRef RefId="1"/><LST/></Obj><S N="MachineName">.</S><S N="ServiceName">HostControllerService</S>-<Obj RefId="857" N="ServicesDependedOn"><TNRef RefId="1"/><LST/></Obj>-<Obj RefId="858" N="ServiceHandle"><TNRef RefId="2"/><ToString>SafeServiceHandle</ToString>-<Props><B N="IsInvalid">false</B><B N="IsClosed">false</B></Props></Obj>-<Obj RefId="859" N="Status"><TNRef RefId="3"/><ToString>Stopped</ToString><I32>1</I32></Obj>-<Obj RefId="860" N="ServiceType"><TNRef RefId="4"/><ToString>Win32OwnProcess</ToString><I32>16</I32></Obj><Nil N="Site"/><Nil N="Container"/></Props>-<MS><S N="Name">HostControllerService</S><Ref RefId="857" N="RequiredServices"/></MS>

Now, I uninstalled this update and still did not regain my service.

I am still trying to validate if this update is causing the issue, but it was the only Exchange aware update that I applied at this time.

Can anyone confirm this behavior??

I have built a 2010 SP3 server to move mailboxes from 2003. Ultimately, we are going to have a 2 node 2013 DAG and 2 front end servers. What I haven't been able to identify is if I can start building the 2013 with the 2003 still in production. I know 2013 does not coexist with 2003 but didn't know if I could at least install the servers.

Thanks

I am moving mailboxes from a 2007 server to our new 2013 server and they are taking days to move, and I have no idea why. I have tried everything on this forum (and googled it for days while I'm waiting) regarding settings on the DB (DataMoveReplicationConstraint setting), making sure I am not replicating to another DB while migrating ect. For example we have some <100MB mailboxes that take 4 hours to complete. Other than the speed everything else seems fine, once moved everything works. I have even tried moving a few mailboxes to a new DB on the 2007 think perhaps the original DB has some corruption, but then moving those mailboxes was no faster either. both servers are on the same gigabit network sitting right next to each other. Any ideas would be much appreciated.

Thanks

I am running two, two node DAG's with Exchange 2013.

One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.

No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".

I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers.  I also receive errors when trying to failover the databases because the content index state is failed.

In my test environment I have a very similar setup working fine with no issues.

Please let me know what I can try to get this resolved.

The error I receive when running the following set of commands is:

suspend-MailboxDatabaseCopy dag2db1\mbox1

update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles

[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles

Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Hi - I have an existing 2010 environment of 2 CAS servers and 2 mailbox servers.  All external URLs are set to mail.contoso.com and all internal URLs are set to mail.contoso.com.  The CASArray is mail.contoso.internal.

I want to keep all my URLs the same for 2013.  So I will install Exchange 2013 and set all the external and internal URLs on my 2013 environment to mail.contoso.com

That sounds simple enough and so now I re-point my external and internal DNS records for mail.contoso.com to the new 2013 environment. Is this going to work? 

I have looked at how 2013 proxies or redirects to the 2010 environment it seems to suggest that everything is proxied which sounds good.  However, I saw this article http://michaelvh.wordpress.com/2012/10/09/exchange-2013-interoperability-with-legacy-exchange-versions/ which suggests that 2013 will only proxy is there is no external URL set on the 2010 servers. In this case there still will be - it will be mail.contoso.com.  Do I need to remove the external URLs on my 2010 servers?

And one last thing regarding the article above, it says that Exchange 2013 does some clever stuff when proxying, it doesn't use the internal URL and instead builds a URL from the CAS server name.  Is that correct? the problem I'm anticipating if that is the case is that I do not have the 2010 cas server address on my certificates - I only have mail.contoso.com.

If anybody could clarify this process that would be great - I would have thought that the majority of people would want to migrate keeping their URLs the same - but the documentation doesn't seem to confirm whether anything needs to be changed on the 2010 environment.  Thanks

Hello all,

I am planning an Migration from EX2010 to EX2013 by installing the EX2013 parallel to EX2010. During that planning i have red a lot of public folder migration (e.g. http://technet.microsoft.com/en-us/library/jj150486.aspx) - but after all I am a bit confused.

When reading above mentiones technet article I understand the following:

- When using the method describes it is a kind of an one way copy. Is this right?

- When using this method users on EX2010 as well as users on Ex2013 can access andcreate public folders. Is this right?

- But there is no kind of syncronisation between Public Folders hosted on EX2010 and EX2013. Is this right? So there will be an inconsitence between PF hosted on EX2010 and EX2013?

I have the issue that the user migration will take about a month or more. How can I solve the issue of getting inconsitences?

Please execuse my bad English.

Thanks in advance

Lars

Hello,

I have a program that uses public folders.  I am in a process of moving users from Exchange 2010 to Exchange 2013, but it will take time.

There is nothing in public folders that should be migrated or copied. So, my question is:

Can I create public folders in Exchange 2013 and assign it only to users that I migrated to Exchange 2013.  I do not need them to be able to use public folders on Exchange 2010.

At the same time, I want users on Exchange 2010 only to be able to use Exchange 2010 public folders and not public folders on Exchange 2013.

Can I do it?

Thank you. Eric.