I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive.  Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V.  I ran the two following commands before trying to install

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Upon trying to run the installer, I recieve the following error.

Error:
The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".

During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck.  I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin.  These four services are the critical services the errors refer to.  I have verified my execution policy is correct

PS C:\Windows\system32> Get-ExecutionPolicy -list

                                                      Scope                                             ExecutionPolicy
                                                      -----                                             ---------------
                                              MachinePolicy                                                Unrestricted
                                                 UserPolicy                                                   Undefined
                                                    Process                                                   Undefined
                                                CurrentUser                                                   Undefined
                                               LocalMachine                                                RemoteSigned

Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|set-service-startuptypeautomatic

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|Start-Service

No matter what I do, the Exchange 2013 CU2 installer seems to fail.  I'd appreciate any possible help with this.

Thanks,

Chris

To add to what I posted, I also have the following error in the event log.

[07/22/2013 13:57:01.0279] [1] Executing:
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                
[07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
[07/22/2013 13:57:01.0373] [1] 0.  ErrorRecord: AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] 0.  ErrorRecord:
System.Management.Automation.PSSecurityException: AuthorizationManager
check failed. ---> System.Runtime.InteropServices.COMException: The
service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. (Exception from HRESULT:
0x80070422)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementObject.Get()
   at System.Management.Automation.PsUtils.GetParentProcess(Process current)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
   at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
  
at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   --- End of inner exception stack trace ---
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   at
System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
context, PSHost host, CommandInfo commandInfo, CommandOrigin
commandOrigin)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
SessionStateInternal sessionState)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String
commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
  
at
System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor
pipe, CommandParameterInternal[] commandElements, CommandBaseAst
commandBaseAst, CommandRedirection[] redirections, ExecutionContext
context)
   at
System.Management.Automation.PipelineOps.InvokePipeline(Object input,
Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".
[07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] [ERROR] The service cannot be started, either
because it is disabled or because it has no enabled devices associated
with it. (Exception from HRESULT: 0x80070422)
[07/22/2013
13:57:01.0388] [1] [ERROR-REFERENCE]
Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
[07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
[07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
[07/22/2013 13:58:09.0121] [0] End of Setup
[07/22/2013 13:58:09.0121] [0] **********************************************

I also have these two errors in event viewer that keep occuring. 

Event 2280, IIS-W3SVC-WP

The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load.  The data is the error.

Event 2300, IIS-W3SVC-WP

The
worker process cannot access the CLR configuration file at 'C:\Program
Files\Microsoft\Exchange
Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'. 
Verify that the file exists and that the worker process has read access
to the file.

Dear All,

I am going an Exchange 2010 to Exchange 2013 migration project, with Exchange 2010 SP3, and Exchange 2013 Cumulative Update 2 installed on one Exchange Organization. (Single forest-single domain)

Exchange 2010 environment consists of two servers, with one on each AD-site (No DAG). Each Exchange 2010 server hosting Mailbox, Transport, and CAS role. Public Folder is configured by using replication between two servers.

Exchange 2013 environment consists of eight servers, with four on each AD-site (DAG is planned, but still not configured). Four servers on each site consist of two mailbox (backend) servers and two CAS servers. Windows NLB is configured between two CAS servers. Autodiscover DNS record is using NLB's IP address. Public Folder is residing on Exchange 2010. It is still not configured and not migrated to Exchange 2013 Public Folder.

Most users is still on Exchange 2010 mailboxes. We did migration on five Exchange 2010 users to Exchange 2013 mailboxes. All migrated mailboxes are still cannot open Public Folder.

On Outlook client residing Exchange 2013 mailboxes, display message window "Cannot expand the folder. Microsoft exchange is not available. Either there are network problems or the exchange server is down for maintenance. (/o=...)".

Some outlook client prompts credential for connecting to Public Folder at most of the time. Users still could send and receive messages, though. I am sure all Outlook versions have complied with Exchange 2013 System Requirements, i.e Outlook 2013, Outlook 2010 Service Pack 2.

I also have done resolution from http://support.microsoft.com/kb/2834139 , using the same setting, but accessing public folder by Exchange 2013 users is still not working at all. 

Any advices for resolution to this case are appreciated. Thanks a lot.

Hi, 

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

Here is my setup:

ExchangeFE1 - Exchange 2010 CAS

ExchangeMail - Exchange 2010 Mailbox Server

ExchangeUM - 2010 UM Role

Mail 13 - 2013 Mailbox, UM

MailExchange2 - SEcondary 2013 Mailbox Server

Exchangecas13 - 2013 CAS Server

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

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

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

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

Any assistance is greatly appreciated. 

Hello Everyone,

I am trying to do a new install of Exchange 2013 on a VM with SRV 2008 R2 SP1.

I am running the Setup wizard and getting the following error after the readiness check -

Active Directory must be prepared with 'Setup /PrepareAD' before domains can be prepared for Exchange 2010.

My AD and DNS seem to be all ok. I am using AD Ent credential. I looked at the Exchnagesetup log file and looks like PrepareaAD went through ok. It syas "PrepareAD has been run and replicated to this domain..".

Where it stopped is -

Failed [Rule:DomainPrepWithoutADUpdate] [Message:Active Directory must be prepared with 'Setup /PrepareAD' before domains can be prepared for Exchange 2010.

Anyone can suggest anything?

Also I must say I am relatively new  to MS environment.

Thanks.

Hi everyone,

I've just installed a fresh Windows Small Business Server 2008 Premium Edition on a new server machine, and I was wondering if I can remove / uninstall completely the Exchange Server that comes pre-installed within the WinSBS 2008?

Thanks for the help, appreciate it.

Dhow here.

I am creating my first Exchange 2013 server DAG complete with its own dedicated Active Directory in my lab. Currently, I have 4 servers in the domain all running Windows 2012 Datacenter: 1 AD server and 3 Exchange servers (two of which will be configured with just mailbox database role/added to the DAG and the third which is a dedicated CAS as well as my FSW that will not be included in the DAG). Here are the steps I took:

I have 2 domains registered on Internet are abc.org.vn and abc.vn. They are used for old mail system (Mdaemon). Now I need to migrate to Exchange system.

My Active Directory Server host domain abc.net ( it’s not registered on Internet).

For some reason, I need to setup a mail Exchange System 2013 with required:

Users can use user@abc.org.vn& user@abc.vn for send and receive emails at the same time. And users out of organization ( gmail, yahoo or so on …)  will see “From” field are abc.org.vn or abc.vn, not abc.net on received mails.

In my oponien, i need to configure Accepted Domains abc.org.vn and abc.vn, and then, add Aliasuser@abc.org.vn& user@abc.vn to actual mail address user@abc.net

So, can you confirm my steps? Or can you give me a solution is as detailed as possible ?

Hello,

We have a newly installed Exchange server 2013 on a 2008 server and we published it in ISA server 2006. We can send out emails but we cannot receive emails from external networks. Could it be an ISA 2006 related issue?

the error says: #550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Thank you

Hi, 

I installed exchange 2013. The installation went bad I had to uninstall it manually from ADSI edit, then deleted the VM. I installed exchange 2013 once again. I log into ecp, I find under recipients the old mailboxes created with the old exchange server. when I try to delete them or move them, the following error shows: 

The object domain/Users/someuser has been corrupted, and it's in an inconsistent state. The following validation errors happened:
Database is mandatory on UserMailbox.

digging around on the net, I followed this link: http://support.microsoft.com/kb/2702446?wa=wsignin1.0

but I noticed that my homeMDB is not set. 

also following this link: http://technet.microsoft.com/en-us/library/dd535374(EXCHG.80).aspx

I noticed that I dont have anything under this location in adsi edit, while it states that there are some child objects

config...\config...domain\services\microsoft exchange\org-name\administrative groups\ex...admin..groups id\servers\mailbox\informationstore

Should I have ran setup /prepschema and setup /prepad, i didn't because in MS documentation it stated that if the account is a member of enterprise admin and schema admins the schema and AD and Domain preparation would be done by the wizard.

If its partially prepared, can I run them commands again without causing problems?

I can create new users just fine, all I want is to delete these recipients and create a new working ones. also I want to know is my exchange setup right, because I don't want to face major problems when we go live.

its been 3 weeks hitting my head against the wall, help please.

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh

Hi All.

We are currently using just Exchange 2010 with a view to migrating to Exchange 2013

I have read all the recent blogs (specifically from Brain Day) relating to CAS; these include ‘Demystifying the CAS Array Object’ and the very interesting ‘Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations’

I now know that Outlook must always use Outlook Anywhere (RPC over HTTPS) to function correctly with Exchange 2013 both internally and externally.

Therefore Outlook has to be able to resolve 'mail.contoso.com' to a public address for external users to hit the Outlook Anywhere proxy URL, (as it currently does for us), and an internal address for network (LAN) users

Here’s my question…

We use external DNS servers at our ISP for Internet users to resolve our public facing servers, for example (I've replaced our real domain name with ‘contoso’): -

mail.contoso.com (for Outlook Anywhere)

www.contoso.com

ftp.contoso.com

Internally our AD Forest is ‘company.contoso.com’ so we use Active Directory DNS Servers for all internal name resolution, for example: -

               outlook.company.contoso.com (for MAPI Outlook)

               server1.company.contoso.com

               server2.company.contoso.com

How do I ensure that Outlook Anywhere resolves ‘mail.contoso.com’ to an internal address when clients are on the LAN?

Can I add a ‘contoso.com´ zone to our Active Directory DNS Servers to solve this, without affecting any AD or DNS (Internal and External) functionality?

ISSUE: Can't RPC Proxy Outlook Anywhere requests for Exchange 2010 mailbox users via the Exchange 2013 CAS.

SYMPTOMS: Externally with TestExchangeConnectivity.com, I get 'RPC Proxy Can't Be Pinged' with 'An HTTP 401 Unauthorized response was received from the remote Unknown server'.

SETUP:

Exchange 2013 CU2
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
InternalHostname: ex2013.mydomain.local
ExternalClientAuthenticationMethod: Basic
InternalClientAuthenticationMethod: Ntlm
IISAuthenticationMethods: Basic, Ntlm, Negotiate
SSLOffloading: False

Certificate on 2013 server contains the names: ex2013.mydomain.local, webapp.mydomain.com, AutoDiscover.mydomain.local, AutoDiscover.mydomain.com, mydomain.local, mydomain.com

Exchange 2010 SP3 update rollup 1
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
ClientAuthenticationMethod: Basic
IISAuthenticationMethods: Basic, Ntlm
SSLOffloading: False

Certificate on 2010 server contains the names: ex2010.mydomain.local, webapp.mydomain.com, autodiscover.mydomain.local, autodiscover.mydomain.com

Outlook providers:
EXCH  CertPrincipalName: msstd:webapp.mydomain.com
EXPR  CertPrincipalName: msstd:*.mydomain.com    (as I use an external reverse proxy with a public wildcard certificate)

ADDITIONAL DETAILS:
- With the above settings, Outlook 2010 doesn't seem to be able to proxy RPC through Exchange 2013.

Testing manually with RPCPING utility:
- Requests for port 6001 directed to Exchange 2010 for people with mailbox on Exchange 2010: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2013: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2010: error 401.1 Unauthorized

OWA and Activesync through Exchange 2013 for people with mailbox on Exchange 2010 are working fine.
Only RPC over HTTP seems to have problems.

- Here are some pertinent lines from the 2010 CAS server's IIS logs for a 2013 to 2010 RPC access:
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll - 443 - 10.62.6.50 HttpProxy.ClientAccessServer2010Ping 401 2 5 780

- Here are some pertinent lines from the 2013 CAS server's IIS logs for the same 2013 to 2010 RPC access:
2013-10-10 13:02:14 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=b6464f37-a9fe-4f84-a32b-ff9af689607c&cafeReqId=b6464f37-a9fe-4f84-a32b-ff9af689607c; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 4726
2013-10-10 13:02:14 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=4acc0118-7fac-49db-976d-152a4a6839b2&cafeReqId=4acc0118-7fac-49db-976d-152a4a6839b2; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 0
2013-10-10 13:02:16 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=a591fb11-98c3-44e6-90c7-f719c7047fe4&cafeReqId=a591fb11-98c3-44e6-90c7-f719c7047fe4; 443 dom\2010user 10.62.7.15 MSRPC - 401 0 64 1544
2013-10-10 13:02:16 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=fbb94579-8d0b-41d7-8103-45c945141bd7&cafeReqId=fbb94579-8d0b-41d7-8103-45c945141bd7; 443 dom\2010user 10.62.7.15 MSRPC - 200 0 64 1700

Any thoughts or comments are highly appreciated. Let me know if additional details are needed.

Hi Everyone,

Currently I am going to deploy 4 units of Exchange 2013 (2 CAS 2 MBX) for my client Exchange 2007 Environment.

As I go through the TechNet documentation, I am required to install 1 Exchange with CAS & MBX role for the 1st Exchange 2013 in the coexisting environment. Does that mean I need to:

A) Install 5 Exchange 2013, decommission the both role Exchange after the migration.

B) Install 4 Exchange 2013, 1 of the Exchange 2013 install both roles, remove the roles after the migration.

Any ideas? Sorry for the bad explanation.

Regards,

Low

I am migrating Public Folder from 2007 (ru11) to Exchange 2013. No problems at all until I get to the New-PublicFolderMigrationRequest that actually kicks off the migration. The command runs without error but when checking with Get-PublicFolderMigrationRequest it shows as QUEUED and it has been queued for over 8 hours. We do have quite a large set of Public Folders - over 18GB. Should it take this long just to parse the folders before moving?  I can email the output of Get-PublicFolderMigrationRequest if requested.

thanks.

I have installed one 2013 CAS and one 2013 MBX. (MBX01)

Today I installed a new MBX(MBX02). Then I move all mailboxes to new one(MBX02).

So I uninstall the old one(MBX01). *retain MBX02 

After that I cannot send or receive mail anymore, once I connect ti EMS on CAS Server it says
"New-PSSession : [cas.domian.com] Connecting to remote server cas.domian.com failed with the following error message : [Server=cas,RequestId=e9f66d77-e016-455c-8e08-30d69e8a9a71,TimeStamp=11/21/2013 1:05:49 PM]Cannot find Mailbox server with Version 15.0 (Build 711.24). For more information, see the about_Remote_Troubleshooting Help topic.

any idea?

I'm getting an error when trying to upgrade EMC on my managment workstation.  this is from the exchange setup log.  It is thrown in the stopping services phase.  This is stange as the admintools roles has no services to stop afaik.  I also tried uninstalling and get a different error.

[11/21/2013 16:18:25.0501] [1] [ERROR] The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "Exception calling "GetFolder" with "1" argument(s): "This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)"".
[11/21/2013 16:18:25.0501] [1] [ERROR] Exception calling "GetFolder" with "1" argument(s): "This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)"
[11/21/2013 16:18:25.0501] [1] [ERROR] Exception has been thrown by the target of an invocation.
[11/21/2013 16:18:25.0501] [1] [ERROR] This operation is supported only when you are connected to the server. (Exception from HRESULT: 0x800704E3)
[11/21/2013 16:18:25.0502] [1] [ERROR-REFERENCE] Id=AllRolesPreFileCopyComponent___2f7e3804a2b340c69e930798211fb8fd Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

Hi,

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

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

Thanks!

--Kent

I have to upgrade a customer Exchange 2010 environment to 2013 and during the investigation of customer's current 2010 environment I noticed that the namespace was configured with same URL for CAS Arrays and internal HTTPS services which introduces a serious problem with co-existence as stated in this article (http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx)

This article advices to change the cas array to a unique name that is only resolvable in internal DNS and change RPC endpoint in databases and force all Outlook clients to connect Internally with https to prevent problems before introducing Exchange 2013 servers to organization.

My question is that if I introduce a completely new namespace to Exchange 2013 will this Ambiguous URL problem affect the deployment. Let's say that the old environment uses exchange.company.com in internal HTTPS and CAS Array and webmail.company.com as external namespace. If I install Exchange 2013 to organization and configure it to use new mail.company.com namespace will I be able to prevent this issue? Of course introducing a new namespace means new URLS for OWA and ActiveSync etc but in this particular case it would be easier approach.