Hi,

We are planning an Exchange Server upgrade from 2003 -> 2013.  The directory servers are all on 2003.  I see that Exchange 2010 and 2013 will run on 2003 directory services.

Are there benefits to upgrading the domain controllers to 2008 or 2012 before we upgrade Exchange?

Thanks!

--Kent

I am installing the first exchange 2013 MBX server in an existing 2007 org, and during the services start up portion of setup I am getting the error :Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server. 

I've attempted to manually start the service, but it just stops immediately.  Here is a snippet from the install log:

Service Control Manager reports no process ID for service MSExchangeMailboxAssistants.
[11/25/2013 23:13:32.0448] [2] Unable to get the process ID for service MSExchangeMailboxAssistants because another similar process 0 was found
[11/25/2013 23:13:32.0448] [2] [ERROR] Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
[11/25/2013 23:13:32.0542] [2] [ERROR] Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
[11/25/2013 23:13:32.0620] [2] Ending processing start-SetupService
[11/25/2013 23:13:32.0667] [1] The following 1 error(s) occurred during task execution:
[11/25/2013 23:13:32.0792] [1] 0.  ErrorRecord: Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
[11/25/2013 23:13:32.0792] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
   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.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/25/2013 23:13:32.0855] [1] [ERROR] The following error was generated when "$error.Clear(); 
	start-SetupService -ServiceName MSExchangeMailboxAssistants" was run: "Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.".
[11/25/2013 23:13:32.0855] [1] [ERROR] Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
[11/25/2013 23:13:32.0855] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___6dafc355332b4424880090d93b6a67df Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/25/2013 23:13:32.0933] [1] Setup is stopping now because of one or more critical errors.
[11/25/2013 23:13:32.0933] [1] Finished executing component tasks.
[11/25/2013 23:13:33.0261] [1] Ending processing Install-MailboxRole
[11/25/2013 23:18:04.0888] [0] End of Setup

Google is yielding no results, they all point to the transport service, which is running on my VM. 

Hello,

I have a possibly broken installation of Exchange 2013 I am tasked with removing. I am learning that all my cdmlet knowledge of 2010 is only partially useful in this adventure. Long story short is that I initially tried to run the uninstaller and got the typical failure citing the various mailboxes that would need to be audited & deleted or at the least disabled. After slogging through get-mailbox commands, identifying User, Archive, Arbitration, etc. mailboxes & deleting/disabling them, I am still getting an error stating that the database cannot be disconnected/unmounted

I am wondering what it is I am missing here...

We are migating from exchange 2010 sp3 to exchange 2012 cu2

when we create a move request for a mailbox it shows that is queued with 0% complete,

can someone advise please

Hello,

can I ask for advice or help ?

I have Exchange 2010 SP3, and succesfuly installed new Exchange 2013.

Problems:  Can't move mailboxes to new Exchange (ecp or shell)

Can't install ru2 for sp3 for Exchange 2010. It start but rollback.. (I turn off check for cert revocation)

My Exchange servers don't have conectors between them. Is this normal ? I tought that this will be created automaticaly.

Thanks, for any advice how to procede...

Single Server Install - Coexistence with Ex2010 SP3

Currently on CU1 with Ex2013

Error Recieved during setup:

11/26/2013 20:11:05.0256] [1] [ERROR] The following error was generated when "$error.Clear();
          $configFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "GenericAppPoolConfigWithGCServerEnabledFalse.config");
          $rpcProxyCLRConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeRpcProxyAppPool_Cafe_CLRConfig.config");
          $windir = $env:windir;
          [System.Array] $appPoolsExcludedFromWorkstationGC = "msexchangerpcproxyapppool","internalexchangesharedapppool";
          $appPools = &"$windir\system32\inetsrv\appcmd.exe" "list" "apppool";
          foreach($appPool in $appPools)
          {
              $startIndex =  $appPool.IndexOf('"') + 1;
              $numChars = $appPool.SubString($startIndex).IndexOf('"');
              $appPoolName = $appPool.SubString($startIndex, $numChars);

              # Do not enable Workstation GC for AppPools that Allocate greater than 50MB/s at their peak e.g. MSExchangeRpcProxyAppPool
              if ($appPoolName.ToLower() -eq "msexchangerpcproxyapppool")
              {
                  $c= &"$windir\system32\inetsrv\appcmd.exe" "set" "apppool" "$appPoolName" /CLRConfigFile:"$rpcProxyCLRConfigFilePath";
                  Write-ExchangeSetupLog -Info ($c)
              }
              elseif ($appPoolsExcludedFromWorkstationGC.Contains($appPoolName.ToLower()) -ne $true)
              {
                  # We'll set this whether or not the app pool exists.  Failures are ignored.
                  $a= &"$windir\system32\inetsrv\appcmd.exe" "set" "apppool" "$appPoolName" /managedRuntimeLoader:"";
                  $b= &"$windir\system32\inetsrv\appcmd.exe" "set" "apppool" "$appPoolName" /CLRConfigFile:"$configFilePath";
                  Write-ExchangeSetupLog -Info ($a + " " + $b)
              }
              else
              {
                  Write-ExchangeSetupLog -Info "Skipping $appPoolName since it should remain as Server GC";
              }
          }
        " was run: "Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported.".
[11/26/2013 20:11:05.0256] [1] [ERROR] Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported.
[11/26/2013 20:11:05.0256] [1] [ERROR] Specified method is not supported.
[11/26/2013 20:11:05.0256] [1] [ERROR-REFERENCE] Id=CafePostSetupComponent___SelectedAppPoolsToGCServerFalseCafe Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/26/2013 20:11:05.0256] [1] Setup is stopping now because of one or more critical errors.
[11/26/2013 20:11:05.0256] [1] Finished executing component tasks.
[11/26/2013 20:11:05.0506] [1] Ending processing Start-PostSetup
[11/26/2013 20:22:02.0489] [0] End of Setup

Brian A Bohanna

Hi, I was planning my Exchange 2010 (sp1) HA architecture, but I stumble in something unexpected (due to my ignorance) and I'm looking for advice.

Here is the situation now:

I have a virtual exchange server with HUB and CAS roles and another phisical exchange server with mailbox role installed. They are both in my primary site.

Now we have a remote site and a remote vmware hosts to use for HA and disaster recovery purposes. The internal network of the DR site is different from mine and it's natted too. More precisely my primary network is 192.168.100.0/24 and the DR network is 192.168.60.0/24 natted with 192.168.113.0/24.

The DR domain controller and the DR AD site are already in place.

My idea was:

- to use veeam replication to create a replica of the first exchange server, the virtual one of course, with CAS and HUB roles. I thought to use the veeam network remapping tool to change che server IP address in case of failover.

- to install a new exchange server in the DR site with mailbox role only and configure a DAG

I thought it was brilliant.

It was not..

Since i cannot create the veeam replica right now (long story) I tried to install the DAG and here we are with my problems.

Error:

Setup encountered a problem while validating the state of Active Directory. Could not find Active Directory site to which this server belongs.

This is weird, because I have no problems with site replications etc.

Warning:

Setup did not detect an existing Huh Transport Server role installed in Active Directory site 'DR'...
Setup did not detect an existing Client Access Server role installed in Active Directory site 'DR'...

And that's my real problem. I didn't remember that Exchange is site based.

What are my options now?
Could I install CAS and HUB just to complete the install and then ignore them or they will cause problems with my primary site?

In the end, what do you think should I do?

At this point I could re-think the all thing.

Thank you and sorry for the grammar

Hi all,

When I try to connect to to Exchange powershell, this is what I get. Redirection disabled, binding seems correct (80 and 443 only with correct SSL) and ECP and other directories are working fine. Thanks

VERBOSE: Connecting to exchange.company.uni.edu.au.
New-PSSession : [exchange.company.uni.edu.au] The WinRM service cannot process the request because the request needs
to be sent to a different machine. Use the redirect information to send the request to a new machine.  Redirect
location reported: https://exchange.company.uni.edu.au/powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;c
lientApplication=ManagementShell;TargetServer=;PSVersion=4.0&sessionID=Version_15.0_(Build_515.32)=rJqNiZqNgbqnvLe+sbi6
0Z6b0YqOipGWkJHRio7RmpuK0Z6Kgc7Gy87GxsnPzMmBzc3Qzs7Qzc/OzN/LxczIxc/L376y . To automatically connect to the redirected
URI, verify the "MaximumConnectionRedirectionCount" property of the session preference variable "PSSessionOption", and
use the "AllowRedirection" parameter on the cmdlet.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportRedirectException
    + FullyQualifiedErrorId : RedirectInformationRequired,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: exchange.company.com.au
VERBOSE: Connecting to exchange.company.com.au.
New-PSSession : [exchange.company.com.au] Connecting to remote server exchange.company.com.au failed with the following error
message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot
find the computer exchange.company.com.au. Verify that the computer exists on the network and that the name provided is
spelled correctly. 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 : NetworkPathNotFound,PSSessionOpenFailed

Hi,

I am performing a migration to a hybrid exchange deployment.

I have looked on the deployment assistant for autodiscover dns information but it just says I need autodiscover.domain.com externally pointing to my on premise CAS which I already have from my current deployment.

My question is... If a user mailbox gets moved to office 365 how does autodiscover work to redirect them to the cloud service for their URL's?

Can someone give me a high level description for internal and external outlook users?

i.e. external user: connect to cas using public autodiscover.domain.com A record, on premise CAS provides alternative autodiscover URL??

***Don't forget to mark helpful or answer***

Hi Guys & Girls,

I've a painful issue with my environment which is made up of 1 x 2010 CAS server with 1x 2010 Mailbox server and 1x 2013 CAS server with 1 x 2013 mailbox server.

The users who've yet to be migrated to 2013 and are still on the 2010 server are unable to open shared mailboxes which have already been migrated to 2013.

When trying to access shared mailboxes on the 2013 servers they received the following error:

The configuration of OutlookAnywhere on my two CAS servers is as follows:

RunspaceId                         : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName                         : THCAS1
SSLOffloading                      : True
ExternalHostname                   : mail.resourcegroup.co.uk
InternalHostname                   : mail.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://THCAS1.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path                               : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 14.3 (Build 123.4)
Server                             : THCAS1
AdminDisplayName                   :
ExchangeVersion                    : 0.10 (14.0.100.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS1,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=ResourceGroup,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity                           : THCAS1\Rpc (Default Web Site)
Guid                               : 71f76f2a-4ee1-4a9a-b2da-06d79e975403
ObjectCategory                     : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 26/11/2013 16:23:13
WhenCreated                        : 25/11/2013 16:33:45
WhenChangedUTC                     : 26/11/2013 16:23:13
WhenCreatedUTC                     : 25/11/2013 16:33:45
OrganizationId                     :
OriginatingServer                  : thdc1.ResourceGroup.co.uk
IsValid                            : True
ObjectState                        : Changed

RunspaceId                         : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName                         : THCAS2
SSLOffloading                      : True
ExternalHostname                   : thcas2.resourcegroup.co.uk
InternalHostname                   : thcas2.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://THCAS2.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 712.24)
Server                             : THCAS2
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS2,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=ResourceGroup,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity                           : THCAS2\Rpc (Default Web Site)
Guid                               : 39c5133f-14cb-4d44-ae9c-69f7fb0fc432
ObjectCategory                     : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 26/11/2013 16:23:05
WhenCreated                        : 26/11/2013 12:49:17
WhenChangedUTC                     : 26/11/2013 16:23:05
WhenCreatedUTC                     : 26/11/2013 12:49:17
OrganizationId                     :
OriginatingServer                  : thdc1.ResourceGroup.co.uk
IsValid                            : True
ObjectState                        : Changed

If anyone could offer any help it'd be much appreciated, it's going to take several days to migrate my remaining 2010 users to 2013 which is causing a lot of use complaints.

Hello

I have installed exchange server

But do problems wih domain controller I had to reinstalled my domain. So I get new domain name but my exchange server is not working. How can I fix this easy or reinstall my exchange server. Ther is no mailbox active yet so no loss of data 

Hi,

I am trying to create a new mailbox from remote Exchange management shell. I get the error

"An exchange 2007 server on which an address list service is active cannot be found."

Please advise on this.

Please also let me know which ports need to be open in the firewall between the server having Exchange management shell and the Exchange Server.

Thanks,

<v:shapetype coordsize="21600,21600" filled="f" id="_x0000_t75" o:preferrelative="t" o:spt="75" path="m@4@5l@4@11@9@11@9@5xe" stroked="f"><v:stroke joinstyle="miter"><v:formulas></v:formulas></v:stroke></v:shapetype><v:shape alt="" id="Picture_x0020_1" o:spid="_x0000_i1025" style="width:484.5pt;height:23.25pt;" type="#_x0000_t75"></v:shape>

Hello,

I am trying to configure and enable Exchange Server 2013 for Task Synchronization with SharePoint 2013 and following the directions on: http://technet.microsoft.com/en-us/library/jj554516.aspx and I am trying to run the following script:

.\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMetadataUrl https://<SP_FQDN>/_layouts/15/metadata/json/1

The script should be located in: C:\Program Files\Microsoft\Exchange Server\V15\Scripts, but when I navigate there, the folder is empty and when I try to run the script in Windows PowerShell, I get the following error message:

.\Configure-EnterprisePartnerApplication.ps1 : The term '.\Configure-EnterprisePartnerApplication.ps1' is notrecognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or ifa path was included, verify that the path is correct and try again.At line:1 char:1+ .\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMe ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : ObjectNotFound: (.\Configure-Ent...Application.ps1:String) [], CommandNotFoundException    + FullyQualifiedErrorId : CommandNotFoundException

Where is the script file?  Do I need to install something?  

Please help.

Thanks in advance for any suggestions and help.

I am looking to upgrade all my domain controllers to 2012 R2. Does Exchange 2013 support them at this time?

Thanks!

Shawn

Hi, 

I installed Microsoft Exchange 2013 hoping I could sync my MS Outlook calendar to my phone. --Nothing else seemed to work. I set up a free Outlook.com account to test it, rather than using my hosted email accounts. 

Since I wasn't able to find the correct "server" information I cannot complete the process. Nor can I uninstall it. 

Now my MS Outlook isn't responding at all, and I cannot access any email or my calendar. 

This is a critical time in my new company. Please either help me complete the installation or uninstall the server. It seems neither is a typical user-friendly process. Thank you. 

Basic info

Exchange 2010 SP1 on Server 2008 R2.  An Upgrade from Exchange 2007.  Auto Reply returns an error from Outlook "Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later."  When attempting to access auto reply from OWA, the user is brought back to an OWA login screen.  (which does not allow the user to log back in)  This is a different URL than the normal OWA log in URL.

I have attempted to remove and recreate the EWS directory without success. In current troubleshooting, if I attempt to remove the virtual directory, I receive an error it does not exist on the domain controller, if I try to recreate it, it tells me it already exists.  If I try to set it, it tells me it cannot be found.

PowerShell information included below...

I have tried many different methods to resolve this so far without success.  (hence posting here) I HAVE NOT yet attempted removing/reinstall the CAS role, or anything involving adsi edit.

[PS] C:\>Remove-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)"
The operation couldn't be performed because object 'Server.Domain.net\EWS (Default Web Site)' couldn't be f
ound on 'DomainController.Domain.net'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Remove-WebServicesVirtualDirectory], ManagementObjectNotFoundEx
   ception
    + FullyQualifiedErrorId : AE5EDDA2,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveWebServicesVirtual
   Directory

[PS] C:\>get-webservicesvirtualdirectory | fl identity,internalurl,externalurl
[PS] C:\>

[PS] C:\>New-WebServicesVirtualDirectory -Identity 'server\EWS (Default Web Sit
e)' -InternalUrl  https://webmail.domain.net/EWS/Exchange.asmx -basicauthentication 1 -windowsauthentication 1
The virtual directory 'EWS' already exists under 'server.domain.net/Default Web Site'.
Parameter name: VirtualDirectoryName
    + CategoryInfo          : InvalidArgument: (server\EWS (Default Web Site):ADObjectId) [New-WebServicesVirtual
   Directory], ArgumentException
    + FullyQualifiedErrorId : 775B2C6B,Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDir
   ectory

[PS] C:\>Set-WebServicesVirtualDirectory -Identity "server\EWS (Default Web Site)" -InternalUrl  https://webmail.domain.net/EWS/Exchange.asmx
The operation couldn't be performed because object 'server\EWS (Default Web Site)' couldn't be found on 'DomainController.Domain.net'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-WebServicesVirtualDirectory], ManagementObjectNotFoundExcep
   tion
    + FullyQualifiedErrorId : D6F18491,Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebServicesVirtualDir
   ectory

[PS] C:\>get-webservicesvirtualdirectory | fl identity,internalurl,externalurl
[PS] C:\>

i'm looking at different solutions for hub transport server replacements. i see that the mailbox servers include transport roles. Can i have a 3rd party SMTP server send directly to the mailbox servers? (without CAS role installed). and go directly from mailbox servers to the 3rd party SMTP server for outbound mail?

thanks

GD