Dear Sir,

Please help me to allocate space for exchange server 2010, or increase it.

Regards, Ravi Kumar

Hi,

I have the client tools (CU6) installed on one of my servers. I am trying to run the CU7 installation in order to update the server. As soon as setup finishes the Copying Files step I receive the following error message:

The Type Initializer for Microsoft.Exchange.Management.Powershell.CmdletConfigurationEntr (line is cut off)

threw an exception. Could not load file or assembly 'Microsoft.Exchange.MailboxLoadBalanceClient Version=15.0.0.0 (message is cut off).

Any ideas how to troubleshoot this?

Thanks,

I. Kinal

Hi,

We are in process of migrating from Exchange 2007 to Exchange 2013 Servers.

To meet the migration requirements we have changed the standard single name SSL certificate with UCC Certificate having multiple SAN values using the exchange 2013 EAC wizard. Later on we applied the same certificate to both Exchange 2013 and 2007 CAS servers.

Outlook Anywhere was enabled since long on exchange 2007 servers and was working fine till we made the certificate change. After we make the change of certificate given were the error message we started encountering:

Another change which we noticed were of Domain Controllers names in the same AD site as exchange getting added to VALID PORTS key under given HASH:

HKLM\Software\Microsoft\RPC\RPCProxy

As per my understanding Valid ports entry is populated with all the mailbox servers in organization only until unless we define DC there, which we never did until now. I can also see values for Exchange 2013 mailbox server there.

And now since Valid ports entry contains reference for domain controller i have to made following registry entry on my domain controllers to make it work :

On the Global Catalog servers: a REG_MULTI_SZ  entry needs to be created on each GC named NSPI interface protocol sequences at HKLM\System\CCS\Services\NTDS\Parameters\ and the value set to ncacn_http:6004

I have tried modifying the Valid Ports entry manually and removing the domain controllers reference from there but then my Outlook Anywhere doesn't work anymore. Yes i know that RPCConfigurator again populate the entry every 15 minutes and i can turn it off,i have tried that but no luck.

Result of the above change now my CAS is directly speaking for my domain controllers which earlier mailbox server was doing through DSPROXY.

Can anyone suggest me what is happening wrong here...given are the environment details:

2 CAS +HUB Exchange 2007 SP3 RU13 server on windows 2003 R2

Exchange 2007 Mailbox Server SP3 RU13 SCC on Windows 2003 R2

Exchange 2013  CU5  CAS + Mailbox Server on Windows 2012 R2

Windows 2003 AD with mix of 2008R2 DC.

Regards,

Vishal Malhan

Hello,

We started to notice that when we move a user from our legacy exchange 2007 to exchange 2013, the contact list appears twice for users.  I heard CU6 was suppose to fix this issue but we went ahead and downloaded the latest version and we are still seeing this.  Can anyone provide guidance on how to stop this for the remaining migrations?

Thanks

Hi Everyone,

I'm hoping others on this forum have some thoughts on whether it is worthwhile deploying only the Exchange 2013 CAS role for the purposes of SMTP relay.

When using Exchange Online, most guides suggest installing the IIS virtual SMTP component in an environment if SMTP relay is required. This is simple enough, however Microsofts future plans for IIS vSMTP look uncertain.

So my question is, has anyone deployed only the Exchange 2013 CAS role in an environment solely for the purposes of SMTP relay?
One pitfall I'm thinking about is the autodiscover service. Once the CAS role is installed an AD SCP is created, so this could cause potential problems.

I'm not concerned about having to extend the AD schema, or the cost. It's the other technical bits :)

cheers!

Trying to update a new CU6 installation to CU7 and I can't get past this error.  Please help.

Exchange Server component Mailbox role: Transport service failed.

Error: Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Exchange Back End'.

Parameter name: VirtualDirectoryName

   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.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Default Web Site'.

Parameter name: VirtualDirectoryName

   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.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

David

I have just installed my first Exchange 2013 deployment.  Small single server install, no Edge Server.  Things seem to have gone pretty well.  I haven't enabled external mail yet but just wanted to do a bit of testing.  I can send test messages and log in via OWA just fine.

However, when I try to connect an Outlook client I get the message: "Outlook cannot log on.  Verify you are connected to the network.  The connection to Microsoft Exchange is unavailable."  I have an internal DNS record for autodiscover and the internal urls in Exchange.

Before I go much further, I will also add that I have not yet installed the cert.  So I do get the certificate error when setting up Outlook.  I think I read that without a valid cert install, Outlook will not connect to Exchange 2013.  Is that true?  I will be finishing things up and installing the cert soon.  Once I do that, do you suspect the above error message will go away?

Also, after the error above, the dialog box appears that lists the server name.  Instead of what I would consider a valid server name, the name shows up as 505ef3b4-5d84-458e-b084-53d45c532bf0@domain.com.  Is that normal?

Thanks for any clarification

I am trying to reinstall exchange 2013 and I have been getting the errors below in the exchange setup log. I have been going through a lot of knowledge bases and the suggestions hasn't been helpful.

[02-09-2015 08:42:24.0144] [2] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0144] [2] Ending processing set-mailbox
[02-09-2015 08:42:24.0144] [1] The following 2 error(s) occurred during task execution:
[02-09-2015 08:42:24.0144] [1] 0.  ErrorRecord: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0144] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] [ERROR] The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".
[02-09-2015 08:42:24.0159] [1] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] 1.  ErrorRecord: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] 1.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   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, Boolean reThrow)
   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[02-09-2015 08:42:24.0159] [1] [ERROR] The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".
[02-09-2015 08:42:24.0159] [1] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___1DEE95834DBA48F2BB211C2FB6765A5A Component=EXCHANGE14:\Current\Release\Client Access\Unified Messaging
[02-09-2015 08:42:24.0159] [1] Setup is stopping now because of one or more critical errors.
[02-09-2015 08:42:24.0159] [1] Finished executing component tasks.
[02-09-2015 08:42:24.0206] [1] Ending processing Install-MailboxRole

The basic symptom is this: The PF migration appears to work perfectly but when trying to assign a user to test the new folders it still attempts to connect to the old folders even though the users's DefaultPublicFolderMailbox is set to the new server. Connection status in Outlook still shows a connection to the 2007 server.

I'm using the TechNet PF migration article: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

This is a single server migration from 2007 SP3 UR10 to 2013 CU5 Standard. The migration of mailboxes is complete with no errors and I'm trying to move the 100mb in public folders over to the 2013 server. Using several guides but once I've had problems I've switched to using the "standard" TechNet article as follows. I am creating only one PF mailbox since there are 10 folders and 100mb in data roughly. My Mailboxmap.csv file shows only the following:

"TargetMailbox","FolderPath"
"PFRoot","\"

The entire PF migration steps work flawlessly with no errors that I can see at all. I've rolled back and ran this process a half dozen times now to see if I've missed something.

I'm stuck on Step 8: Item #2 testing the migration from the test user in Outlook.

I've assigned the DefaultPublicFolderMailbox properties as that Item #2 shows me to do and if I use Get-Mailbox (test user) | Select DefaultPublicFolderMailbox command I see the new PFRoot mailbox listed as the default. However, the test user can't access the public folders at all. If I look in EAC I still see no public folders listed at all. If I use this guide:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part2.html

It shows after setting "Set-Mailbox PFRoot -PublicFolder -IsExcludedFromServingHierarchy $False" I should be able to see the public folders in EAC. However, I can see the PF mailbox (PFRoot) but no public folders at all in EAC.

Where do I go from here? Even though I have no errors I don't want to complete the migration because the test isn't working.

Jeremy Regehr

Hello!

We are on an hybrid deployment with some users on Exchange 2013 on-premises and others on Exchange Online (Office 365 E3 plan). We have enabled photo sync (PhotosEnabled attribute) in the organization relationship, both on-premises and online, but while Exchange Online users can see all profile pictures, Exchange on-premises can see only on-premises pictures.

It also looks like that online users can see only a low resolution version of on-premises users' pictures.

Do you have any idea how to troubleshoot or fix this, please?

Dear all,

for some reasons we are in Exchange Server Coexistance mode that is 1 Exchange 2003 Server and 2. Exchange 2010 servers.

We have CAS array(node-1 And Node-2) and DAG in place , but the problem is whenever my Node-1 is down emails are getting stuck routing group connector on legacy server and Exchange 2010 to Exchange 2010 emails are working.

oppositly

when my Node-2 is down everything works.

how do I FIX this ?

TheAtulA

I'm consolidating users from companyA to companyB.  CompanyA will keep it's domain name and be added as an Accepted Domain in companyB's exchange environment.
CompanyA has autodiscover and webmail DNS pointing to there exchange server.  I'm not sure if I'm correct or not and would like a little guidance but what I think I want to do is modify the
certicate and remove webmail and just have autodiscover and import the certificate into the companyB's exchange? Also, point CompanyA's DNS record for autodiscover to CompanyB's exchange server?
Does this sound accurate?

The final goal is to have CompanyA be able to have Outlook Anywhere working as it did before and webmail through CompanyB

All users from CompanyA are created in AD, SMTP addresses modified to the accepted domain and they can send and receive email however they can't do the above and I believe that is because of the
autodiscover?

The exchange environment is 2013.

We are planning to upgrade Exchange 2010 to SP3 with latest rollup updates. We have 3 HUB/CAS servers and 3 mailbox servers in a DAG. We are not quite confident if we can install Rollup updates right after applying SP3 to all servers. We think we probably wait a few days after applying SP3 to identify any potential issues before move on to the rollup updates . However SP3 is quite buggy and it requires patching as soon as possible. What's your best practices and experience? Thanks in advance !

This posting is provided AS-IS with no warranties/guarantees and confers no rights.

This weekend we moved our mail server. After many troubles with copying we managed to get it running on the new host (ESXi5.5).

For the mail server we opened ports 80, 443, 135 and 25. All dns records point to the new IP. I also recreated the recursive lookup zone for the new internal ip.

Yet, mail flow is not working while I can connect and login on owa and connect with Outlook from both inside and outside the network. Internal mail, even from and to the same address is not working.

This is the first time we moved a mail server and we might have missed something. Any ideas where to look?

This has been the recovery from hell. First, the databases did not want to be deleted from the failed server and then the server itself did not want to be removed from the DAG. Finally, after solving all of these issues, I was ready to do a recovery install. Wouldn't you know it. It fails at the point where mailbox transport service is attempting to start. An attempt to start the service manually fails with the message, the service started and then stopped. Have tried redoing the connectors, making sure both DC's are global catalog servers. There are no third party software installed. In fact, I have not installed the antivirus. I started by formatting and reinstalling Server 2008 enterprise clean. Any help would be appreciated.

Thanks

Ron

I'm having autodiscover issues with the new Exchange 2013 server. I rechecked the authentication and its fine. I rechecked my certificate with SAL and it has autodiscover.mydomain.com in it. Services are assigned to the certificate.

However, when I run the remote test for outlook connectivity it states its having trouble with autodiscover.

My main domain used for all services is m1.mydomain.com and I have an A record out there on DNS servers on the internet. Do I need one also for the the autodiscover.domain.com?  The test states it cannot The Microsoft Connectivity Analyzer is attempting to test Autodiscover for mymailbox@domain.com  testing autodiscover failed.   The Autodiscover service couldn't be contacted successfully by any method.  Also all other tests failed. What am I missing? Do I need to configure the autodiscover area in virtual directories? Currently when I click on the wrench there is no information in there. None in the external address. is something suppose to be there?

Had to rebuild a server from scratch after it failed in a DAG and was unable to recover it. Added it back to the DAG after using cluster manager to evict it. I was surprised because it was not showing in the DAG manager. Now, I am attempting to add a database copy to the rebuild server and the error is "log file on a removable disk" The server that holds it had two hard drives, and the database is no drive letter "E". Not sure what to do with it now.

thanks

Ron

Dear All,

Last year, we migrated Exchange 2010 to Zimbra and found it was difficult to handle.

So we want to move back to Exchange 2013. Exchange 2013 and Zimbra may co-exist in our organization.

We will deploy two Exchange Server,CAS+Mailbox.

We are considering if put Exchange as the smarthost.

Anyone has idea?

Besides, is there any wonderful migration tool?

Xiu

Hey, I am back

Hi Everyone,

I'm hoping others on this forum have some thoughts on whether it is worthwhile deploying only the Exchange 2013 CAS role for the purposes of SMTP relay.

When using Exchange Online, most guides suggest installing the IIS virtual SMTP component in an environment if SMTP relay is required. This is simple enough, however Microsofts future plans for IIS vSMTP look uncertain.

So my question is, has anyone deployed only the Exchange 2013 CAS role in an environment solely for the purposes of SMTP relay?
One pitfall I'm thinking about is the autodiscover service. Once the CAS role is installed an AD SCP is created, so this could cause potential problems.

I'm not concerned about having to extend the AD schema, or the cost. It's the other technical bits :)

cheers!