Exchange Server 2013 64bit with SP1 Standard - Readiness Checks/Prerequisite Analysis

I'm trying to install Exchange 2013 with SP1 on Windows Server 2012 R2 Standard, at the Readiness Checks setup, I get 25 errors. Before the Readiness Checks setup, I had selected 'Automatically install Windows Server roles and features that are required
to install Exchange Server'. How come they are not automatically installed? Do I have to manually install these 25 items? That's a lot of work.
The Readiness Checks - Prerequisite Analysis produces this:
Error:
This computer requires Windows Media Audio Voice Codec. Install the Desktop-Experience component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornWmspdmoxNotInstalled.aspx
Error:
The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, and then restart Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.W3SVCDisabledOrNotInstalled.aspx
Error:
The 'IIS 6 Metabase Compatibility' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6MetabaseNotInstalled.aspx
Error:
The 'IIS 6 Management Console' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6MgmtConsoleNotInstalled.aspx
Error:
The 'IIS 7 Dynamic Content Compression' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7HttpCompressionDynamicNotInstalled.aspx
Error:
The 'IIS 7 Static Content Compression' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7HttpCompressionStaticNotInstalled.aspx
Error:
The 'Windows Process Activation Service Process Model' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornWASProcessModelInstalled.aspx
Error:
The 'IIS 7 Basic Authentication' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7BasicAuthNotInstalled.aspx
Error:
The 'IIS 7 Windows Authentication' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7WindowsAuthNotInstalled.aspx
Error:
The 'IIS 7 Digest Authentication' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7DigestAuthNotInstalled.aspx
Error:
The 'IIS 6 WMI Compatibility' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6WMICompatibility.aspx
Error:
The 'ISAPI Filter' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornISAPIFilter.aspx
Error:
The 'Client Certificate Mapping Authentication' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornClientCertificateMappingAuthentication.aspx
Error:
The 'Directory Browsing' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornDirectoryBrowse.aspx
Error:
The 'HTTP Errors' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpErrors.aspx
Error:
The 'HTTP Logging' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpLogging.aspx
Error:
The 'HTTP Redirection' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpRedirect.aspx
Error:
The 'Tracing' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpTracing.aspx
Error:
The 'Request Monitor' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornRequestMonitor.aspx
Error:
The 'Static Content' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornStaticContent.aspx
Error:
The 'Web-Mgmt-Service' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ManagementServiceInstalled.aspx
Error:
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
The 'IIS Management Console' component is required. Install the component via Server Manager.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7ManagementConsoleInstalled.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Thanks

I didn't have to do this during setup with Exchange 2013 non SP1 on Windows Server 2012 Standard non R2.
I just ran the PowerShell command to install the Windows components on win2k12 r2 and Readiness Checks - Prerequisite Analysis came down to 1 error
prerequisites that are needed to install Exchange 2013 on a Windows Server 2012 R2 or Windows Server 2012
Error:
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Looks like I have it sorted out.
Thanks

Similar Messages

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

Hi,
From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
http://support2.microsoft.com/kb/2997209
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Backing up Exchange Server 2013 CU3 with Windows Server Backup Program

Looking at configuring Windows Server Backup Program to backup Exchange Server 2013 CU3 which is a member a DAG Group using a specific Backup Domain Account.
From my understanding from the following technet Article" Using Windows Server Backup to Backup and Restore Exchange Data" at http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx I cannot use wbadmin.exe has it uses an older
unsupported version of Powershell.
My question is what are the minimum AD rights required for an AD account needed to be able to backup/restore Exchange Datastore using Windows Server Backup Program in Windows Server 2012?
Thanks,
NIck

Hi Sathish,
After looking at your response, it all make sense except when I look at what exchange right assigned via RBAC. I understand that the backup service account will require access to the exchange databases
to be able to backing and restoring them. After looking at the different roles
I'm wondering if I require to assign both the Databases roles for Backing up the databases and the Disaster Recovery Role as well to be able to restore the databases has well as having a mailbox on the exchange
server for the backup service account?
Below is explanation of the roles via the ECP
Database Role
This role enables administrators to create, manage, mount and dismount mailbox and public folder databases on individual servers.
Disaster Recovery
This role enables administrators to restore mailboxes and database availability groups in an organization.
Thanks,
Nick

Decommission Exchange Server 2013 after migration to Office365

We had an on-premises Exchange Server 2013 failure with multiple hard disk failures.
Since we already had an Office365 E3 plan, we decided to bite the bullet and move to Exchange Online. Since we did not have ADFS or Dirsync yet and time was against us to get email flowing as quickly as possible, we imported all the users into Office365,
i.e. disconnected from our AD.
We then setup all their Outlook 2013 profiles with Office365 and imported their mailboxes from PSTs, so they are all up and running on Office365 now (still disconnected from our AD).
I would like to decommission our on-premises Exchange 2013, since our current setup is not very common, i.e. Office365 mailboxes which are not linked to our AD.
I would like some pointers and guidance how to go about this.
Thanks
Chris

Hi
As per your description i can see that your on-premise exchange servers are running with no users, no services integrated with Office 365 users and no adfs dirsync
So in this scenario you can do a normal uninstallation of Exchange 2013 servers
Before uninstalling a Exchange 2013 Server,
Make sure all the console related to Exchange server are closed
Mailbox databases on that server has to be removed
Uninstall Exchange server from control panel
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

Dear All,
I have exchange server 2013 running with windows server 2012.
My email server have been send and receive email with internal and external as normal.
Today, i got the problem the email cannot send out to external and get the error below:
Please comment.
BR,
Khemarin
[email protected]

Hi Khemarin,
If it is Smarthost, are you able to telnet your smarthost using 25 port number?
Also please check your Send Connector setting.
http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
Exchange Server: [email protected]
Mailbox: =SMTP:[email protected]
When I fill in the right fields....it won't connect and falls back to the values above...
Something wrong in the Exchange setup?

Hmm...found aguide here:
http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
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.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

Exchange Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

For development purposes, I needed to install Exchange Server 2013 in our environment. Our current environment includes a couple Domain Controllers, a Sharepoint Server, and a SQL Server. So, it's got a very simple topology. The one thing
our environment does NOT have are current Exchange servers.
During the "Prerequisite Analysis" phase of the install it complained that two servers, that I can find nowhere in our active directory domain, are running Exchange 2007. Obviously, this presents some unique problems. Perhaps as a test
many years ago, someone installed Exchange 2007 to "play" with, but we've never run Exchange for any length of time.
So, this is quite the conundrum, given the above does anyone have any suggestions as to a potential solution? Ideally, I'd like to be able to "lift the covers" and cleanup the references to the non-existent servers somehow, but ANY suggestions
for fixes are MUCH appreciated.
Cheers,
Nate

Here is the thing I would do (Only if I am not going to have any exchange 2007 ever in the environment).
On any of windows server 2008 download
Exchange 2010 SP3
Extract the file and run the below command:
Setup.com /ps
This will make Exchange 2013 install. Also Deleting Exchange Administrator Group wouldn't help as Setup will look for the information about schema into AD.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

SharePoint 2013 Enterprise with SP1 on Windows Server 2012??????? What am I missing?

Hi there,
As per MS - SharePoint 2013 Enterprise SP1 is compatible with Windows Server 2012 R2.
I have Windows Server 2012 R2 installed - now it does not let me install SharePoint 2013 Enterprise (Standard without SP1).
AND SP1 can ONLY be installed AFTER SharePoint 2013 Enterprise is installed.
So how to install SharePoint 2013 Enterprise with SP1 on Windows Server 2012?
Thanks.

You can download it at the Microsoft Volume Licensing Service Center:
https://www.microsoft.com/Licensing/servicecenter/default.aspx
or at the Microsoft Developer Network:
http://msdn.microsoft.com/
Please note that if you do not have access to either, you will have to work with the vendor who sold you SharePoint 2013 to get you a new ISO with SP1, or you will have to find a way to make a slipstreamed version on your own. I'm really hoping you
have VLSC or MSDN access, as this will make things much easier for you.

Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.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

I think it's from subnet in site and services
have 3 site A,B,C and new site is "D"I have problem in "D" site
A subnet is 10.33.50.0/24 AD 2012 ,exchange 2013
B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
find event error
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
test-SetupPrerequisites
{Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
Cafe}}

What is the order for upgrading exchange server 2013 SP1 servers to CU7?

Hi All
I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013.
What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
Thanks in Advance .
Joyso Senior Messaging Admin

Hi Joyso,
The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
Some References:
The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
CAS role.
If you're separating your server roles, we recommend installing the Mailbox server role first.
Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
Exchange 2013 Server Roles Installation Order – Mailbox First:
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Messaging tracking logs filename format changed in Exchange Server 2013 sp1

Hi,
I have noticed that the file name format is changed for exchange server 2013 sp1.
Now it will have hh attached to it like
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
So the "hh" will goes from 00 to 23 for single day.
So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
And also how it will be decided to create the first file @ 7.30 AM.
Can anyone explain to me about this ? Why it is happening like this?
Thanks
Sandeep Gupta

Hi Sandeep,
This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
were created on 20140411.
Also, as you mentioned, the file name format is as:
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
However as I know, the format is like
MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
and the date/time information of the file to verify.
Title: Message Tracking
Link:
http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
Regards, Eric Zou

Exchange Server 2013 SP1 - Internal Email Flow slowness

Hi Fellows,
I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
Header analysis shows the message exchange between mailbox servers is taking time. any clue?
Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
Network communication, Storage performance, Server performance are all as good as we love to.
Thanks.
J.A

Hello,
When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
Cara Chen
TechNet Community Support

Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

Hello Guys
I have a mailflow issue, hoping someone can help with detail description, below is the setup
Exchange server 2010 SP3 with all roles in one server
Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
queue ..
Can someone please provide detailed solution what needs to be configured?
MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Hi,
1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
I think I need to create a receive connector in the 2013 to receive from 2010 ?
No need ,by design exchange 2013 cas server default frontend receive connector will be having an
entire ipv4 and ipv6 segment and anonymous connection is checked by default.
I think I also need to create a send and receive connector for 2013 users to each other?
No need , an intra organisation send connector and the default receive connectors in exchange will be used
for internal mail flow between the exchange 2013 users.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange Server 2013 64bit with SP1 Standard - Readiness Checks/Prerequisite Analysis

Similar Messages

Maybe you are looking for