Installing Exchange 2013 management tools

I am unable to install Exchange Management Tools on other server in network. I am getting error when trying to run unattended setup "exchange server.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI
package is 'Error reading from file: C:\Users\backup-admin\Downloads\Exchange2013\RemoteScripts\ConsoleInitialize.ps1. Verify that the file exists and that you can access it". Also tried to run the setup.exe, but this option not highlighting
"Management Tools" option to select.
Mohammed Qamaruddin

Hi,
Please try the following cmdlet to solve this issue.
set-executionpolicy unrestricted
If this doesn’t work, please try to copy the
ConsoleInitialize.ps1 from a working server to this server then reinstall Exchange management Tool.
If this still doesn’t work, we should consider to re-download Exchange Server 2013 Management Pack from this
site, then try to install.
Related document:
https://technet.microsoft.com/en-us/library/bb232090%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Best Regards.

Similar Messages

Exchange 2013 Management Tools Install Error on Win8

Hello,
I'm having some trouble installing the management tools for Exchange 2013 on Windows 8. While going through the install if I leave "Automatically install Windows Server roles and features that are required to install Exchange Server" check I get
this error...
Error:
The target of the specified cmdlet cannot be a Windows client-based operating system.
If I uncheck that option and just check the Management Tools option, the error message changes to...
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Any help on resolving this so I can move on with the installation would be appreciated.
Thanks.

Hi,
To install the Exchange 2013 Management Tools, there are many prerequisites we need to understand before installation. And even
we must manually install some required software.
Here are some references that may be helpful to you:
Install the Exchange 2013 Management Tools
http://technet.microsoft.com/en-us/library/bb232090(v=exchg.150).aspx
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 management tools installation on windows 2012 standard edition gives error.

Exchange 2013 management tools installation on windows 2012 standard edition gives following error.
Does anyone observed this issue ?
Error:
The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx
My Test lab is having
Exchange 2013 installed (xyz.local) domain and working fine.
Now i am installing Exchange Management tools on server which is member of (xyz.local) Domain (base OS : Windows 2012 standard edition : Windows updated)
Best Regards
sameer Prabhune

Hi Sprabhune,
It should work.
Did you install the tool by GUI or cmd?
Please select "Automatically install Windows Server roles and features that are required to install Exchange Server" to have the Setup wizard install required Windows prerequisites.
If possible, please try to install the tool on Windows 7/8 client to test.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
Frank Wang
TechNet Community Support

Error when trying to install MS Exchange 2010 Management Tools Windows 7 x64 SP1

When I try to install Exchange 2010 Management Tools on my Windows 7 Pro x64. I get the message ExSetupUI.exe has stopped working? Has anybody else gotten this message? It doesn't even load into the install screen. It is stopping before then.

Hi
Have you installed the admin tools for windows 7 and all the prerequisites? Try running the setup from an elevated prompt or "as Administrator"
for ref:
http://social.technet.microsoft.com/Forums/en-US/63880f4e-6b6e-4ea9-b3b6-8a535657288f/installing-exchange-management-tools-on-a-win-7-x64-box-getting-error-on-readiness-checks?forum=exchange2010

Reading Exchange Online tenant version failed due to an exception when trying to install Exchange 2013 in a hybrid environment.

We currently have an Exchange 2010 hybrid install and we have migrated all of our email accounts to Office 365. Now, I want to do an on-premise install of Exchange 2013 to better manage the hybrid setup. When I try to install Exchange 2013 it
asks for my O365 credentials to do a hybrid check but always fails with the above message. I've done quite a bit of searching but haven't come up with anything useful.
Here is what appears in the exchange setup log:
[09/22/2014 15:48:27.0024] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0147] [0] Session=Tenant Total Cmdlet Time=1.6931035s
[09/22/2014 15:48:27.0148] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log
for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,

Hi,
I recommend you post this in
office 365 forum also, as they should have more professional knowledge on hybrid deployments
and you may get effective solution timely.
In addition, I found a similar thread for you reference:
http://community.office365.com/en-us/f/156/t/255739.aspx
According to the reply of this thread, if you run the HCW (Hybrid Configuration Wizard) to deploy the Exchange Hybrid environment, there will generate an HCW log
file for this deployment.
Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V1*\Logging\Update-HybridConfiguration\HybridConfiguration****.log
Best regards,
Niko Cheng
TechNet Community Support

Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

I currently have an Exchange 2010 server with all the roles installed. Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error. When I installed Exchange 2013, I got an error saying I
had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left. There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group. This deletion caused my access
to my public folders to get messed up. I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA. I also get this error when
trying to access either Default or System Public Folders. "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
-server 'ExchangeServer' "
My Public Folder Database exists and is mounted. Any help is appreciated.

Hi Belinda,
Thank you for responding. Yes you do understand my problem correctly. One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA. I followed these steps in the below article:
http://blog.bruteforcetech.com/archives/766
After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
Here are the results to your requests:
et-PublicFolder -Recurse | Format-List Name
Name : IPM_SUBTREE
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
[PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
Name : NON_IPM_SUBTREE
Name : EFORMS REGISTRY
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

Re-install Exchange 2013

I started a basic install of Exchange 2013 on Windows 2012 on a network with an existing Exchange 2007 (SBS 2008) org.
Things went well with prerequisites and AD Prep but the actual install ended up freezing up. I ran it on a VM with 2GB RAM and all I can guess is that services couldn't start etc with only that much RAM. I did the install through a remote desktop session
and when I returned after kicking off the install process that session was completely frozen up with a black screen. All I could do was reboot the server. I noticed messages that implied the completely new/blank Exchange install was unhappy with 2GB so I raised
it to 10GB, but still things just didn't work. Most significantly I couldn't even load the Management Console replacement web site. I just would get 404 not found.
Thinking the original install never completed properly I simply deleted the VM, re-created a new one with the same config (and 10GB RAM) with the same name, joined the domain, installed pre-requisites and re-started the install, but now I'm getting
"Exchange Server in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer"...
Of course now I get other errors because "Disaster Recovery setup needs access to the mailbox database drive (prior install location)" etc. and of course I have no backups or anything because there was nothing but deployed install media on the
prior server.
How do I re-install? Do I need to clean up AD references to the prior install?
Regards,
Steve Ware

Hello,
Yes. You should check if the uncompleted exchange server is in AD. If it is in AD, please remove it and then reinstall it.
And you can remove the VM, and create a new VM, and then install new exchange server whose name is different from the uncompleted exchange server.
Additional article for your reference.
Install Exchange 2013 in an Existing Exchange 2007 Organization
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Error Installing Exchange 2013 CU6

setup startup give me this error
Method 'get_MultifactorRegistrationEnabled' in type 'Microsoft.Exchange.Data.Directory.SystemConfiguration.PushNotificationApp' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does
not have an implementation.
Have you any suggestion to solve it?

Here the result!
Display Name Name Install State
[X] Active Directory Domain Services AD-Domain-Services Installed
[X] Application Server Application-Server Installed
[X] .NET Framework 4.5 AS-NET-Framework Installed
[X] Windows Process Activation Service Support AS-WAS-Support Installed
[X] HTTP Activation AS-HTTP-Activation Installed
[X] DHCP Server DHCP Installed
[X] DNS Server DNS Installed
[X] Fax Server Fax Installed
[X] File And Storage Services FileAndStorage-Services Installed
[X] File and iSCSI Services File-Services Installed
[X] File Server FS-FileServer Installed
[X] Storage Services Storage-Services Installed
[X] Print and Document Services Print-Services Installed
[X] Print Server Print-Server Installed
[X] Internet Printing Print-Internet Installed
[X] Remote Access RemoteAccess Installed
[X] DirectAccess and VPN (RAS) DirectAccess-VPN Installed
[X] Routing Routing Installed
[X] Web Server (IIS) Web-Server Installed
[X] Web Server Web-WebServer Installed
[X] Common HTTP Features Web-Common-Http Installed
[X] Default Document Web-Default-Doc Installed
[X] Directory Browsing Web-Dir-Browsing Installed
[X] HTTP Errors Web-Http-Errors Installed
[X] Static Content Web-Static-Content Installed
[X] HTTP Redirection Web-Http-Redirect Installed
[X] WebDAV Publishing Web-DAV-Publishing Installed
[X] Health and Diagnostics Web-Health Installed
[X] HTTP Logging Web-Http-Logging Installed
[X] Custom Logging Web-Custom-Logging Installed
[X] Logging Tools Web-Log-Libraries Installed
[X] ODBC Logging Web-ODBC-Logging Installed
[X] Request Monitor Web-Request-Monitor Installed
[X] Tracing Web-Http-Tracing Installed
[X] Performance Web-Performance Installed
[X] Static Content Compression Web-Stat-Compression Installed
[X] Dynamic Content Compression Web-Dyn-Compression Installed
[X] Security Web-Security Installed
[X] Request Filtering Web-Filtering Installed
[X] Basic Authentication Web-Basic-Auth Installed
[X] Centralized SSL Certificate Support Web-CertProvider Installed
[X] Client Certificate Mapping Authentic... Web-Client-Auth Installed
[X] Digest Authentication Web-Digest-Auth Installed
[X] IIS Client Certificate Mapping Authe... Web-Cert-Auth Installed
[X] IP and Domain Restrictions Web-IP-Security Installed
[X] URL Authorization Web-Url-Auth Installed
[X] Windows Authentication Web-Windows-Auth Installed
[X] Application Development Web-App-Dev Installed
[X] .NET Extensibility 4.5 Web-Net-Ext45 Installed
[X] ASP Web-ASP Installed
[X] ASP.NET 4.5 Web-Asp-Net45 Installed
[X] CGI Web-CGI Installed
[X] ISAPI Extensions Web-ISAPI-Ext Installed
[X] ISAPI Filters Web-ISAPI-Filter Installed
[X] FTP Server Web-Ftp-Server Installed
[X] FTP Service Web-Ftp-Service Installed
[X] FTP Extensibility Web-Ftp-Ext Installed
[X] IIS Hostable Web Core Web-WHC Installed
[X] Management Tools Web-Mgmt-Tools Installed
[X] IIS Management Console Web-Mgmt-Console Installed
[X] IIS 6 Management Compatibility Web-Mgmt-Compat Installed
[X] IIS 6 Metabase Compatibility Web-Metabase Installed
[X] IIS 6 Management Console Web-Lgcy-Mgmt-Console Installed
[X] IIS 6 Scripting Tools Web-Lgcy-Scripting Installed
[X] IIS 6 WMI Compatibility Web-WMI Installed
[X] IIS Management Scripts and Tools Web-Scripting-Tools Installed
[X] Management Service Web-Mgmt-Service Installed
[X] .NET Framework 3.5 Features NET-Framework-Features Installed
[X] .NET Framework 3.5 (includes .NET 2.0 and 3.0) NET-Framework-Core Installed
[X] .NET Framework 4.5 Features NET-Framework-45-Fea... Installed
[X] .NET Framework 4.5 NET-Framework-45-Core Installed
[X] ASP.NET 4.5 NET-Framework-45-ASPNET Installed
[X] WCF Services NET-WCF-Services45 Installed
[X] HTTP Activation NET-WCF-HTTP-Activat... Installed
[X] Message Queuing (MSMQ) Activation NET-WCF-MSMQ-Activat... Installed
[X] Named Pipe Activation NET-WCF-Pipe-Activat... Installed
[X] TCP Activation NET-WCF-TCP-Activati... Installed
[X] TCP Port Sharing NET-WCF-TCP-PortShar... Installed
[X] Group Policy Management GPMC Installed
[X] Ink and Handwriting Services InkAndHandwritingSer... Installed
[X] Media Foundation Server-Media-Foundation Installed
[X] Message Queuing MSMQ Installed
[X] Message Queuing Services MSMQ-Services Installed
[X] Message Queuing Server MSMQ-Server Installed
[X] RAS Connection Manager Administration Kit (CMAK) CMAK Installed
[X] Remote Server Administration Tools RSAT Installed
[X] Feature Administration Tools RSAT-Feature-Tools Installed
[X] Failover Clustering Tools RSAT-Clustering Installed
[X] Failover Cluster Management Tools RSAT-Clustering-Mgmt Installed
[X] Failover Cluster Module for Windows ... RSAT-Clustering-Powe... Installed
[X] Failover Cluster Command Interface RSAT-Clustering-CmdI... Installed
[X] WINS Server Tools RSAT-WINS Installed
[X] Role Administration Tools RSAT-Role-Tools Installed
[X] AD DS and AD LDS Tools RSAT-AD-Tools Installed
[X] Active Directory module for Windows ... RSAT-AD-PowerShell Installed
[X] AD DS Tools RSAT-ADDS Installed
[X] Active Directory Administrative ... RSAT-AD-AdminCenter Installed
[X] AD DS Snap-Ins and Command-Line ... RSAT-ADDS-Tools Installed
[X] DHCP Server Tools RSAT-DHCP Installed
[X] DNS Server Tools RSAT-DNS-Server Installed
[X] Fax Server Tools RSAT-Fax Installed
[X] Print and Document Services Tools RSAT-Print-Services Installed
[X] Remote Access Management Tools RSAT-RemoteAccess Installed
[X] Remote Access GUI and Command-Line T... RSAT-RemoteAccess-Mgmt Installed
[X] Remote Access module for Windows Pow... RSAT-RemoteAccess-Po... Installed
[X] RPC over HTTP Proxy RPC-over-HTTP-Proxy Installed
[X] Telnet Client Telnet-Client Installed
[X] User Interfaces and Infrastructure User-Interfaces-Infra Installed
[X] Graphical Management Tools and Infrastructure Server-Gui-Mgmt-Infra Installed
[X] Desktop Experience Desktop-Experience Installed
[X] Server Graphical Shell Server-Gui-Shell Installed
[X] Windows Identity Foundation 3.5 Windows-Identity-Fou... Installed
[X] Windows Internal Database Windows-Internal-Dat... Installed
[X] Windows PowerShell PowerShellRoot Installed
[X] Windows PowerShell 3.0 PowerShell Installed
[X] Windows PowerShell 2.0 Engine PowerShell-V2 Installed
[X] Windows PowerShell ISE PowerShell-ISE Installed
[X] Windows Process Activation Service WAS Installed
[X] Process Model WAS-Process-Model Installed
[X] Configuration APIs WAS-Config-APIs Installed
[X] Windows Server Backup Windows-Server-Backup Installed
[X] WINS Server WINS Installed
[X] WoW64 Support WoW64-Support Installed

Can not install exchange 2013

Hai
I try to install exchange 2013 but there is a problem showed at below:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
Finally I follow it to install the Microsoft Unified Communications Managed API 4.0, but i got error like this:
Microsoft Unified Communications Managed API 4.0, Runtime cannot be installed side by side with the following components. Installation cannot continue.
Microsoft Server Speech Platform Runtime (x64)
I already uninstall the Microsoft server speech, but i still got the same error.
How can I solve this problem, installing MUCM API 4.0 without error?
Thank you

Duplicated. Will help you move to
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/5a2061ec-ac34-4369-81c2-069c85f2e5df
Fiona Liao
TechNet Community Support

Installing Exchange 2013 CU 6 failed

Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
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;
          Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
          Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
-ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
          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: "Microsoft.Exchange.ProvisioningAgent.RusException: Failed to generate proxy address. Additional information:
General Error.
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
   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>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
Any ideas how to solve this?

Hi,
From the description of the error “ Microsoft.Exchange.ProvisioningAgent.RusException: Failed to generate proxy address. Additional information: General Error. ”
Appeared to have some valid proxy address. Please check if there are invalid characters in the admin account proxy address.
To find the proxy address, take the following steps:
Open ADUC, Click View in the menu then click
Advanced Features.
Navigate to yourOrganization >> Users, choose the admin account, right-click to
Properties.
Under Attributes Editor tab, find the proxyaddresses
Attribute, then check the address.
Hope this will be helpful for you.
Best Regards.

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

Installing Exchange 2013 on Windows Server 2012 R2

Now that SP1 has been released, it is supported to run Exchange 2013 on Windows Server 2012 R2
But since it is not yet possible to download Exchange 2013 with integrated SP1 (slipstreamed), is the following installation procedure supported:
- Install Exchange 2013 (without SP1) on Windows Server 2012 R2
- Install SP1 on top of Exchange 2013
If this is not supported, can someone tell me when the Exchange 2013 with integrated SP1 (slipstreamed) download will be released?

yes the SP1 is the full product. if you need step by step instruction to migrate to this new version you can get info here : http://buenoflex.com/install-exchange-2013-sp1/
Arnaud Buonaccorsi - GSX Groupware Solutions
http://www.buenoflex.com
http://www.gsx.com <= The monitoring solution for Exchange and Sharepoint

Getting Error while installing Exchange 2013 on server 2012

Error During Exchange 2013 Mailbox Transport
Role Install On Server 2012
Exchange
Server forums
>
Exchange
Server 2013 - Setup, Deployment, Updates, and Migration
Question
1
Sign
in to vote
I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this:
Step 8 of 15: Mailbox role: Transport service
Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;
          while($currTime -le $timeout)
            $setSharedCDCErrors = @();
            try
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
              if($successfullySetConfigDC)
                break;
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            catch
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          if( -not $successfullySetConfigDC)
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "Unable to set shared config DC.".

Hi Deepak,
From the error description, I would like to clarify the following things:
1. Please ensure that IPv6 on the network adaptor is turned on.
2. Please check if the account that you used to install Exchange has necessary permissions to perform the installation.
3. Make sure that DNS is configured correctly.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Is it ok to install Exchange 2013 on Windows Server 2012 Standard?

Hello everyone,
I'd like to know if it is ok/safe to install Exchange Server 2013 on Windows Server 2012 Standard?
As I started doing some research and noticed a page where Microsoft states they don't recommend running Exchange on Server 2012 Standard, and recommend making 2 different servers one for Active Directory and another for Exchange.
On that page they also listed some features that wouldn't work in case of Exchange is running on Server 2012. And that it may put a larger data load if setup this way.
I am hoping someone knowledgeable can explain and tell me if it is safe to use such setup or if it is better to use something like SBS 2011 Standard instead, which has Exchange included?
Has anyone installed Exchange 2013 on Server 2012 Standard successfully and used it for more then several months without problems?
Also just to give an idea on my background, I've been in IT field fairly long but haven't really updated to newer versions much and mainly used SBS 2003 and 2008 only with a few clients so haven't used 2008 too much.
Thanks in advance.

Few things to note.
There is
NO SBS in 2012
All you need is a Std edition of Windows for Exchange 2013, as there is no difference in features between Std and Datacenter as far as Exchange is concerned.
For 10 users, you can have one box with both AD and Exchange. It is not MS recommeded, but it IS supported.
Rajith Enchiparambil |
http://www.howexchangeworks.com |

Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

Dear all
During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".
Any advice please !!

I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive. Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
error messages saying the database does not exist. It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting. To get around it, I deleted the database and created a new one on the drive
where we wanted it.
I discovered this when I was configuring the Antispam settings. I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server. The shell on 2013 was making changes to 2007.
I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens. Or maybe my issues will be fixed if I just remove the Exchange 2007 server? I'm not ready to do that yet because I can't configure the spam filtering
on 2013 yet with its shell not being able to make the changes that we need.
I don't know if your environment is in coexistence mode like mine.
Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server. Does this happen after the 2007 server is removed?

Installing Exchange 2013 management tools

Similar Messages

Maybe you are looking for