Implementing HA for On-Premise Exchange Server 2013 using Azure

Hi!
I want to implement Exchange 2013 high availability using Azure.
I have an on-premise multirole Exchange 2013 server and I am wondering if I can implement High Availability for example configuring a DAG with an Exchange Server 2013 running in a virtual machine in Azure.
What is the best option?
Thanks in advance,
Cristian
Cristian L Ruiz
Not supported yet
http://blogs.technet.com/b/exchange/archive/2013/08/07/database-availability-groups-and-windows-azure.aspx
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Your answer is incorrect for my question. The link you gave is for a implementation of 2 datacenters using Azure as the wittness server, and that is not possible because you can make only 1 site-to-site VPN connection to Azure and having 2 datacenters you
would need 2 of them.
But my scenario is different, I have 1 datacenter and I want to use Azure as my 2nd datacenter for Exchange and for my witness server. I suppose that using the only 1 site-to site VPN that Azure provides is enough for that situation, but, the question is....
Is there any issue with that scenario? Did anyone try it?
Thanks
Cristian L Ruiz

Similar Messages

Connecting to Exchange Server 2013 using IMAP command gives authenication error

Hello All,
My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder. In this sometimes,
I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
successfully then again fails for few times and then authenticates. I am not sure why this is happening.
Please suggest how can I resolve this.
Thank you, Santha

Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
My company exchange server is Exchange 2007.
Mail works fine except the occasional Mail crash.
iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
This only occurs when I add a meeting request in iCal.
My Exchange administrator has reset my mailbox on the Exchange server.
This helped for about 4 hours. Now it's the same problem.
I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

The following error occured when searching for on-premises exchange server

I look after a company where I installed a new DELL server last year, The server is running Windows Small Business Server 2011 which we installed. Exchange 2010 was installed as part of the Windows Small Business Server 2011 installation. At the time we
did not configure Exchange because they use external POP accounts for email. Eventually they wanted to move over to Exchange
When we created the user accounts using Windows SBS Console, it created a local mailbox for each user
No problems - [email protected]
Since late last year every time I create a new user within SBS Console, it errors creating the mailbox
Add a user account and assign a user role
Getting "Unexpected error occurred" when Setting up an e-mail account for user
Looking at the error "Unexpected error occurred" & MessagingManagement "Unexpected error occured"
The user account is created ok just no e-mail address is created for the user
I never thought much about this at the time as we weren't using Exchange email accounts. I decided to have a look at this issue over weekend
When I try to open Microsoft Exchange Management Console I'm getting "Initialization failed"
The following error occurred when searching for the On-Premises Exchange server
When I try to open Microsoft Exchange Management Shell, I get a similar error
I've download & run EMTShooter which just identifies there is an error & gives me the same error
I've installed & re-installed WinRM IIS Extensions
I've checked all the settings in IIS, Default Web Site, PowerShell, Modules & Paths...
Still cannot connect to Exchange
I've trawled through the internet for two days checking & testing every solution but no luck
I've checked every setting against another Windows SBS 2011 Server we've installed & works
I cannot find a difference
Can someone help me or point me in the right direction?
Peter Ralphs

Thanks for the reply Cara
Here's the original error I was getting when opening Exchange Management Console
Initialization failed
The following error ocurred while searching for the on-premises Exchange server:
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)
I got similar error when trying to access the Exchange Management Shell
VERBOSE: Connecting to SERVER.myd.local
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [],
PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
When I opened the Exchange Management Console this week, the error had changed slightly
Initialization failed
The following error ocurred while searching for the on-premises Exchange server:
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information,
see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)
I could only run Exbpa from a command prompt (obviously no access from Exchange Management Console)
This is the result of the Health Check Scan
Organization: First Organization
Default Global Address List Changed
The 'msExchQueryFilter' attribute of the default Global Address List 'Default Global Address List' has been changed. Default: '(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass - eq 'publicFolder'))'. Current: '((Alias -ne $null) -and (((ObjectClass -eq 'user') -or (ObjectClass -eq 'contact') -or (ObjectClass -eq 'msExchSystemMailbox') -or (ObjectClass
-eq 'msExchDynamicDistributionList') -or (ObjectClass -eq 'group') -or (ObjectClass -eq 'publicFolder'))))'.
Admin Group: Exchange Administrative Group (FYDIBOHF23SPDLT)
The default public folder database is remote
The default public folder database for mailbox database 'Mailbox Database' on server SERVER isn't local. Public folder database: CN=Public Folder Database 1529293969,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=myd,DC=local.
Server: SERVER
Disk timeout changed
Disk timeout on server SERVER.myd.local is not set at the default of 10 seconds. This is normal if third-party storage software is installed. Current timeout value is 160 seconds.
Client RPC binding found
The 'Rpc_Binding_Order' is set on server SERVER.myd.local. It is possible that either the Exchange or Outlook client is installed on the server. Current registry value: ncalrpc,ncacn_ip_tcp.
One thing I've noticed from the start is that the error occurs when it is "searching" for the Exchange Server, it then goes on to name the server [server.myd.local] it knows it's there but cannot access it ?
Another thing I've noticed is that it always refers to the "remote server" this server is Windows SBS 2011, it's the Domain Controller, DHCP Server, DNS Server & Exchange Server all in the same box
I also noticed that the Health Check stated that "The default public folder database is remote"
Has this something to do with it ?
Regards
Peter

The following error occured while searching for on-premises exchange server

I've previously posted this under the Exchange Forums - Exchange Server 2010
I look after a company where I installed a new DELL server last year, The server is running Windows Small Business Server 2011 which we installed. Exchange 2010 was installed as part of the Windows Small Business Server 2011 installation. At the time we
did not configure Exchange because they use external POP accounts for email. Eventually they wanted to move over to Exchange
When we created the user accounts using Windows SBS Console, it created a local mailbox for each user
No problems - [email protected]
Since late last year every time I create a new user within SBS Console, it errors creating the mailbox
Add a user account and assign a user role
Getting "Unexpected error occurred" when Setting up an e-mail account for user
Looking at the error "Unexpected error occurred" & MessagingManagement "Unexpected error occured"
The user account is created ok just no e-mail address is created for the user
I never thought much about this at the time as we weren't using Exchange email accounts. I decided to have a look at this issue over weekend
When I try to open Microsoft Exchange Management Console I'm getting "Initialization failed"
The following error occurred when searching for the On-Premises Exchange server
When I try to open Microsoft Exchange Management Shell, I get a similar error
I've download & run EMTShooter which just identifies there is an error & gives me the same error
I've installed & re-installed WinRM IIS Extensions
I've checked all the settings in IIS, Default Web Site, PowerShell, Modules & Paths...
Still cannot connect to Exchange
I've trawled through the internet for two days checking & testing every solution but no luck
I've checked every setting against another Windows SBS 2011 Server we've installed & works
I cannot find a difference
Can someone help me or point me in the right direction?
Peter Ralphs

Thanks for the reply Larry
I've added more detail about the error, this server is exactly how I initially installed it. This was a clean install not a migration so Exchange was a new installation. I have not applied any service packs as I did not want to confuse matters
or compound the issue. I was wondering whether to install Server 2008 Service Pack 1 & the Exchange Service Packs. I will check the event logs & report back with what I find.
Here's the original error I was getting when opening Exchange Management Console
Initialization failed
The following error ocurred while searching for the on-premises Exchange server:
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)
I got similar error when trying to access the Exchange Management Shell
VERBOSE: Connecting to SERVER.myd.local
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [],
PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
When I opened the Exchange Management Console this week, the error had changed slightly
Initialization failed
The following error ocurred while searching for the on-premises Exchange server:
[server.myd.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information,
see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)
I could only run Exbpa from a command prompt (obviously no access from Exchange Management Console)
This is the result of the Health Check Scan
Organization: First Organization
Default Global Address List Changed
The 'msExchQueryFilter' attribute of the default Global Address List 'Default Global Address List' has been changed. Default: '(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass - eq 'publicFolder'))'. Current: '((Alias -ne $null) -and (((ObjectClass -eq 'user') -or (ObjectClass -eq 'contact') -or (ObjectClass -eq 'msExchSystemMailbox') -or (ObjectClass
-eq 'msExchDynamicDistributionList') -or (ObjectClass -eq 'group') -or (ObjectClass -eq 'publicFolder'))))'.
Admin Group: Exchange Administrative Group (FYDIBOHF23SPDLT)
The default public folder database is remote
The default public folder database for mailbox database 'Mailbox Database' on server SERVER isn't local. Public folder database: CN=Public Folder Database 1529293969,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=myd,DC=local.
Server: SERVER
Disk timeout changed
Disk timeout on server SERVER.myd.local is not set at the default of 10 seconds. This is normal if third-party storage software is installed. Current timeout value is 160 seconds.
Client RPC binding found
The 'Rpc_Binding_Order' is set on server SERVER.myd.local. It is possible that either the Exchange or Outlook client is installed on the server. Current registry value: ncalrpc,ncacn_ip_tcp.
One thing I've noticed from the start is that the error occurs when it is "searching" for the Exchange Server, it then goes on to name the server [server.myd.local] it knows it's there but cannot access it ?
Another thing I've noticed is that it always refers to the "remote server" this server is Windows SBS 2011, it's the Domain Controller, DHCP Server, DNS Server & Exchange Server all in the same box
I also noticed that the Health Check stated that "The default public folder database is remote"
Has this something to do with it ?
Regards
Peter

Issues connecting Outlook 2011 for Mac to Exchange Server 2013

Could someone help me with the bellow please:
I have a Mac with outlook 2011 on it.
We have recently set up Exchange Server 2013, and all of the Windows Workstation just required the trusted root certificate to be installed and they were working.
However I have spent hours reading different forums trying to get this working on the Mac and no luck.
The auto discover does not work when setting up the exchange email, therefore I have also tried setting up manually but it still will not connect to the server.

Hi,
Please check if the links below help:
How the Autodiscover service works with Outlook for Mac 2011:
http://technet.microsoft.com/en-us/library/jj984202(v=office.14).aspx
A great tool for troubleshooting Autodiscover and Outlook 2011 for Mac connectivity issue:
http://blogs.technet.com/b/johnmak/archive/2012/04/01/a-great-tool-for-troubleshooting-autodiscover-and-outlook-2011-for-mac-connectivity-issue.aspx
Since this forum is for general questions and feedback related to Outlook for Windows, it's better to post your question to the forum for Exchange or for Mac:
Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
Office for Mac forum:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support

Sizing IIS ARR for Exchange Server 2013

Hi Everyone,..
I planned to publish Exchange 2013 through IIS ARR server, but I've had trouble finding any data on CPU / memory usage for a dedicated ARR server based on Microsoft recommendation. There are 8000 users that will be access from ARR server.
Hopefully you can help for sizing so
there isn't bottleneck on that server.
Thanks
~IH~

Hi Irfan
The concurrent connections depends upon appConcurrentRequestLimit which has a default value of 5000. I think you need to increase this if in your case the concurrent connections exceed 5000
I have found few articles for your reference
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/achieving-high-availability-and-scalability-arr-and-nlb
http://blogs.technet.com/b/tristank/archive/2008/03/11/maxuserport-what-it-is-what-it-does-when-it-s-important.aspx
https://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
Its better to submit this to http://forums.iis.net/ since this is more kind of IIS related issue and you will get better response
Good Luck !!
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

High Availability for Existing Single Exchange Server holding Multiple Domains

Hi,
I'm trying to implement solution for Backup/Redundancy/High-availability for the existing Exchange Server 2013.
Currently the Exchange Server 2013 deployed on 2012 Server is holding 4 Domains (1 internal domain & 3 public/published domains). The Exchange Server is hosted Internally & published to send & receive mails from the SMTP relay(Third party
resides on internet) server. Client Access & Mailbox Services are on the same server.
Please advice me which is the best scenario to implement a backup/redundancy/high-availability for the current server.
Thanks in advance.
Regards
Roopesh S

Hi,
The following links will help.
High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Deploying High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Backup, Restore, and Disaster Recovery
http://technet.microsoft.com/en-us/library/dd876874(v=exchg.150).aspx
ecsword

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)

Best practice on mailbox database size & we need how many server for deployment exchange server 2013

Dear all,
We have an server that runs Microsoft exchange server 2007 with the following specification:
4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2
Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
6 mailbox databases
1500 Mailboxes
We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
1500 mailboxes
10GB or 15GB mailbox quota for each user
How many
servers and databases are
required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
Number of the servers:
Number of the databases:
Size of each database:
Many thanks.

You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
2TB is recommended maximum database size for Exchange 2013 databases.
Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
decide to use EWS Managed API over Autodiscovery but I am bit confuse how
I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
try
            ExchangeService _service
= new ExchangeService(ExchangeVersion.Exchange2013_SP1);
            _service.Credentials
= new WebCredentials("service.exchange",
"1234", "domain");
            _service.TraceEnabled
= true;
            _service.TraceFlags
= TraceFlags.All; _service.UseDefaultCredentials
= true;
            _service.AutodiscoverUrl("[email protected]",
RedirectionUrlValidationCallback);
            foreach
(Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
new ItemView(2)))
var test = contact;
        catch
(Exception exception)
            Console.WriteLine(exception);
After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

hi,
when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
Regards,
Désiré GOVIN Refresh IT Solutions

How can i get newly added contacts for a Mailbox User in Exchange Server 2013

Hi all,
I need to synchronize contacts in Exchange Server and Sugar CRM Application, for that
i need to get newly added contacts for a User in Exchange Server 2013 by using EWS Managed API.
I know how get the list of all contacts for a particular user , but in the list how i can find
new contacts ?

Hi Dora,
that's the fun thing:
You add your own property (and it'll be invisible to outlook users, not to worry).
Extended Properties allow you to define custom property on Exchange Items. And it has a
method for setting those too.
Here's a short post doing a very simple intro on using Extended Properties.
Glen's Exchange Blog is a generally useful resource when working with EWS, I'm confident you'll be able to find lots of tips there as well.
Cheers,
Fred
There's no place like 127.0.0.1

If the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

if the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

thanks for your reply!
what's protection software can use for exchange server 2013?
Hi,
Most (if not all) of the bigger vendors has a product that supports Exchange 2013, so look them up.
Exchange 2013 has some Anti-Spam and Anti-Malware Protection functionality that you can read about here:
http://technet.microsoft.com/en-us/library/jj150481(v=exchg.150).aspx
Martina Miskovic

Best way for Email Notifications in EWS Managed API 2.0 [ Exchange Server 2013]

Hi ,
I want to know best way for Email Notifications in Exchange server. My
organisation has
10 users, i want to get notification if any user mailbox got any new mail.
i need to create API,
that was consumed by another Team in their Application.
I am using Exchange server 2013.
Please share Your Ideas.
Thank you

Take a look at EWS Notifications
http://msdn.microsoft.com/en-us/library/office/dn458791(v=exchg.150).aspx .
Cheers
Glen

Installation error for Exchange Server-2013

I am trying to install exchange server-2013 on my Windows server-2012
machine. I have configured per-requisite applications and develop the server environment with active directory roles.
At my readiness check option, it shows the following error:-
"An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later and windows server-2012".
I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
Regard
Azad
Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through the
exchange 2013 management shell
"Get-Exchangeserver"
However still not able to connect to https://localhost/eac and when i re-run setup
01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
[01-28-2014 21:10:16.0804] [0] **********************************************
[01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
[01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
[01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
[01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
[01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
[01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
[01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
[01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked:
[01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
[01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
[01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
[01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
[01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
[01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
[01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
[01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
[01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[01-28-2014 21:10:39.0664] [0] Applying default role selection state
[01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
[01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
[01-28-2014 21:15:30.0513] [0] End of Setup
[01-28-2014 21:15:30.0513] [0] **********************************************

Exchange server 2013 Standard will support for Exchange cal Enterprise???

Hi,
We have Purchased Exchange Server 2013 STD Edition and Exchange server CALs are Enterprise.
is it compatable for this...
can u give reply for this...

Hello Sashys,
Here’s full explanation:
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx. You should have at least standard CAL for each of your users. Enterprise CAL's are an add-on to the standard license, that provides additional
features. Moreover both types of CAL's can be used with either Exchange server 2013 Standard or Exchange server Enterprise.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Implementing HA for On-Premise Exchange Server 2013 using Azure

Similar Messages

Maybe you are looking for