Missing ECP directory in Exchange 2013/2010

Hi Folks,
I have an exchange 2013 and 2010 server running in a domain.
I was trying to log into the Exchange Admin Centre on Exchange 2013. After typing the credentials the page just refreshed and set the prompt back in the password field.
Doing a Get-ECPVirtualDirectory results in the message "An IIS directory entry couldn't be created. The error message is Access is denied", Category Info: Not Installed (myserver\ecp (Default Web Site):ADObjectId). FSComputername:(name of exchange
2010 server).
I am unable to either create or remove the ECP directory (although it claims one exists). Opening the exchange management console on my 2010 server shows OWA is set up, but the ECP entry is blank.
If I try and login to OWA I get the login screen, but after entering credentials I just get HTTP 400 bad request.
In IIS on my 2013 server, there is an ecp directory with just a web.config and auth directory under the default website, there is also an ecp directory (containing contents) under the 'Exchange Back End' site.
Does anyone know how to go about re-creating the ECP directory etc.
Regards
Andy

Hi Andy
Ensure that Microsoft Exchange Security Groups and Exchange Trusted Subsystem group should be a member of the local admins and restart the server
Steps:
Launch IIS Manager Navigate to -> Web Sites -> Default Web Site Right Click on Default Web Site and choose Permissions Add Exchange Trusted Subsystem and grant Full Control Restart IIS Restart the server
If none of the above works then try the following
First remove the affected one
Get-ECPVirtualDirectory | Remove-ECpvirtualDirectory
Then create a new one by following below
http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
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)

Similar Messages

Exchange 2013/2010 - Co-Existence, URLs.

Hey Team,
I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
1) All servers in the same ad site
2) mail. autodiscover, pointed to the 2013 server
3) 2013 server is internet connected.
Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
Thanks,
Robert
Robert

This is well documented in the below post, I would recommend you check it:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
In Exchange 2010/2013 coexistence scenario, CAS 2013 will proxy all connections to Exchange 2010.
How CAS2013 Picks a Target Legacy Exchange Server
It’s important to understand that when CAS2013 proxies to a legacy Exchange Client Access server, it constructs a URL based on the server FQDN, not a load balanced namespace or the InternalURL value.
When a CAS2013 starts up, it connects to Active Directory and enumerates a topology map to understand all the Client Access servers that exist within the environment. Every 50 seconds, CAS2013 will send a lightweight request to each
protocol end point to all the Client Access servers in the topology map; these requests have a user agent string of HttpProxy.ClientAccessServer2010Ping
Mohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://lyncrocks.wordpress.com/

Exchange 2013 / 2010 coexistence with different public domains

Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

OWA/ECP Custom Theme Exchange 2013

Hello,
I've read numerous posts on customizing OWA themes and currently have them in place in my 2010 Exchange environment. I've also used them in 2007 Exchange infrastructures. I've been trying to roll out a similar design in my lab before we go live
with our 2013 migration but I have a few questions. I've read the tech net article (http://technet.microsoft.com/en-us/library/bb201700%28v=exchg.150%29.aspx)
and found no issues with it. Everything works as it should. However, in my current 2010 environment, the paths to the image files are slightly different than they are in 2013.
The biggest problem is that I have to place the headerbgmain.png and headerbgright.png in the ECP folder (Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\version\Themes\Default) in addition to the OWA folder (Program Files\Microsoft\Exchange
Server\V14\ClientAccess\Owa\version\themes\default). If I don't do this, the header and the OWA logo won't match when switching between OWA and ECP. So this has worked since the 2010 release of Exchange. Not certain if this is supported or
not.
Moving forward, how do I ensure that the two image files get propogated between OWA and ECP without a disconnect as the file path no longer exists for ECP and there is no documentation on how to go about doing this? I've got the OWA part working
without any issues in 2010. Just not certain how to go about it in my 2013 lab and would like to know before I can go ahead with the migration. Thanks for any help!

Hi,
Please refer to the following article :
How to Customize the Outlook Web App (OWA)Sign-In page in Exchange 2013
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled
by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2013 & 2010 coexist problem. Authentication Credentials Prompt in Outlook

Hello Forum
We have two Exchange servers coexisting together. A new 2013 and a old 2010.
Everything was setup with the help of the Exchange Deployment Assistant.
I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.
I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/
and installing this update for Outlook:
http://support2.microsoft.com/kb/2899504/en-us
Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.
The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?
This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])
We use the same domain for external and internal autodiscover connections.
Test Exchange Connectivity Analyzer shows everything ok.
If i run
get-outlookanywhere | fl *external*
(2013 server)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl          : True
(2010 server)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.
What do you Guys have setup in your environments and can you point me towards any troubleshooting?
Thanks!

For us, the changes made in IIS are permanent, there quite possibly is a powershell way of doing it but I am still getting to grips with PS myself so I don't know.
I wont plagiarise others work but these two links here give a good explanation between Basic and NTLM. personally, I have always used basic because I always seem to get problems with NTLM, though one time it did work as expected but I forgot what I did to
get it working now.
https://social.technet.microsoft.com/Forums/exchange/en-US/92178beb-3310-4363-8848-d022a6e2a77f/basic-vs-ntlm-authentication-outlook-anywhere
http://www.sysadminlab.net/exchange/outlook-anywhere-basic-vs-ntlm-authentication-explained

Exchange 2013/2010 Co-existance Outlook Users Always Prompted for Password

Hello,
We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions. Our outlook clients are a mix of Office 2007, 2010, and 2013. When a user is migrated from 2010 to 2013,
they start getting prompted for their password in Outlook every few minutes. They can click cancel and continue working, but they continue to get prompts for their password. If they click the update folder button in outlook, it updates fine, and
the password prompt goes away for awhile.
Most topics on this state that this is caused by a certificate issue. We have an internally deployed CA, with the Root certificate trusted by all clients. The exchange 2013 server has a certificate that was created by this CA.
I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail. Is there anyway to test this without breaking outlook connections for the users that
are on Exchange 2010? Or is there any other reason that this would occur?
Thanks for any assistance.

Sorry for taking so long to reply, other items came up that rank higher then this migration.
I ran the Test-OutlookWebServices CMD and got this result:
[PS] C:\Windows\system32> Test-OutlookWebServices
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
EXCHANGE13.company.local           exchange10.company.local           Autodiscover: Outlook Provider Failure     229
EXCHANGE13.company.local
Exchange Web Services          Skipped       0
EXCHANGE13.company.local
Availability Service           Skipped       0
EXCHANGE13.company.local
Offline Address Book           Skipped       0
I
am currently thinking that this may be the error. Is there a way to
change the first failing result to the hostname of the
exchange13.company.local without breaking the current settings for the
exchange10.company.local autodiscover?

Exchange 2013/2010 coexistence DAG functionality?

Hi, so this is a bit of a silly question. But I need to make sure I understood the situation correctly.
I currently have an Exchange 2010 DAG with 2 servers and I am mid way through (In the Exchange Server Deployment Assistant) introducing my first Exchange 2013 server.
The plan is to make the new 2013 server the active DAG member one of the old 2010 servers the passive member for a short term until that 2010 server is rebuilt to 2013, but that's not going to work is it? Once I migrate a 2010 user to a 2013 database, that
user only exists in 2013, right?
Theres no way of adding a 2013 database into a 2010 DAG, so that if the 2013 server is down, the 2010 server will become active?
Thanks

No, there is not. You will build a new Exchange 2013 DAG and move mailboxes from Exchange 2010 to Exchange 2013 mailbox databases.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

User calendar sharing problem on Exchange 2013 & 2010 co-existence

Recently, I am trying to upgrade my site to Exchange 2013 from 2010. Most of the functions are work without problem except 2013 mailbox user try to access the sharing calendar on Exchange 2010 mailbox server.
e.g. User A is exchange 2010 mailbox user
user create a calendar 'testing' and sharing with user B
who is exchange 2013 mailbox user when user B try to add the calendar in OWA, user B get
'The action couldn't be completed.
An error occurred and your request couldn't be completed. If the problem continuesm contact your helpdesk with this HTTP Status code: 500.'
Actually, the error is 'The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.'
But there are no problem if user A sharing his own calendar. User B could add it without problem.

user B can access the calendar from outlook ? if its still not working from outlook please try to repair outlook profile and check
Regards
John
Thanks for your reply. However, user B could not add the calendar in OWA 2013. I think, it doesn't related to outlook profile.

Exchange 2013 / 2010 / 2007 - Public Folders

I have read that legacy public folders and 2013 public folders canot co-exist.
If I have legacy public folders A, B and C, does this mean...
that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
..or..
If I migrate folder A to 2013, I must migrate folders B and C also.
If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
2013 PF has that the users will lose if the folders are down graded to legacy?
Thanks!
Tom

Hi,
User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
Please refer to the following article.
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
Besides, here is a related thread for your reference.
http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
Best regards,
Belinda Ma
TechNet Community Support

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Exchange 2013 ECP failure after installing RDP

I have a fresh install of Server 2012 and Exchange 2013, everything was working great and I could access the ECP, I then installed Remote Desktop Services and I could no longer access the ECP or OWA, I have now removed the Remote Services but still cannot
access the ECP, does anyone know how to repair this without having to wipe and start again? any help appreciated.
Thanks
J

Have you tried to recreate the ECP virtual directory?
http://www.curu.ca/2013/01/how-to-re-create-ecp-virtual-directory-in-exchange-2013/
For OWA -
http://exchangeonline.in/re-create-owa-virtual-directory-exchange-2013/

Exchange 2013 - Exchange Admin Center unable to login

Hello
I am experiencing issue with the ability to login to the ECP in Exchange 2013 SP1 living in Co-Exist with Exchange 2010 SP3.
It is very random, at times I can login and everything works fine, other time I try to login and nothing happens the page recycles back to the login page without outputting any error. I am trying to recreate the ECP virtual directory by the following:
Remove-EcpVirtualDirectory -Identity "2013CASSERVER\ecp (default Web site)"
And then recreating it. below is the output? Can anyone assist?
[PS] C:\Windows\system32>New-EcpVirtualDirectory "2013CASSERVER\ecp (default Web site)"
Creating a new session for implicit remoting of "New-EcpVirtualDirectory" command...
<RED TEXT>Argument: -Role ClientAccess
    + CategoryInfo          : InvalidArgument: (:) [New-EcpVirtualDirectory], ArgumentException
    + FullyQualifiedErrorId : [Server=2013MAILBOXSERVER,RequestId=ee3e37b7-0ec3-4697-ab51-8156a72bee1a,TimeStamp=7/24/2014 3
   :31:30 AM] [FailureCategory=Cmdlet-ArgumentException] 38C9FD83,Microsoft.Exchange.Management.SystemConfigurationTa
sks.NewEcpVirtualDirectory
    + PSComputerName        : 2013casserver.domain.local </REDTEXT>
[PS] C:\Windows\system32>

Hi,
Please make sure access the EAC by using the correct URL. If you’re in a coexistence scenario and your mailbox is still housed on the Exchange 2010 Mailbox server, we should access the EAC in Exchange 2013 by using the following URL: https://CAS15-NA/ecp?ExchClientVer=15.
Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL: https://CAS14-NA/ecp?ExchClientVer=14.
To rebuild the ECP virtual directory in Exchange 2013, we can try the following commands:
Remove-EcpVirtualDirectory -Identity “Exch13\ecp (Default Web Site)”
New-EcpVirtualDirectory -Server Exch13 -WebSiteName "default Web site" -InternalUrl “https://Exch13.domain.com/ecp”
Remove-EcpVirtualDirectory -Identity "Exch13\ecp (Exchange Back End)"
New-EcpVirtualDirectory -WebSiteName "Exchange Back End" -Server Exch13
Then restart IIS service by running iisreset /noforce from a command prompt window.
Regards,
Winnie Liang
TechNet Community Support

How many CALs do i need? Server 2012 - Exchange 2013 - RDP

Hi,
(I apologize for the grammar and spelling mistakes, but im confident in the fact that the text is understandable. If not, please let me know. I have used UK English for spelling.)
I did some research and read the following:
(unable to post links, my email needs to be 'verified')
And some MS pages regarding the CALs for Windows 2008 R2 (don't ask why).
This is basically what i want to do:
OS:
Windows 2012 R2, possibly 2x because of the RDS role.
Roles Server1: Active Directory and Exchange 2013
Roles Server2: File server and RDS
Users:
20
PC’s:
Approx. 15. Not sure about the exact numbers, but i am sure that there are more users than client pc’s.
Users RDP:
Starting with 10 but eventually every user will be using RDP, so it might be also 20. The 10 we start with will not have the ability of logging into a client PC but RDP only.
MS Software:    Outlook 2010 or 2013, depends on the support by MS.
We are going to start with an AD with a home folder, roaming profiles and an email account. If everything go’s whell, we plan to start letting users connect tot heir workspace via RDP.
I came to the following conclusion and need your input on this:
20 User CALs, As far as i know, I need 1 user cal for an AD account and a RDP cal for
one RDP account. Without a User CAL, i cant issue a RDP user cal, is this correct?
20 RDP User CALs, does this mean that all my users can log into a RDS session via any client, even their own private pc?
No Device calls, redundant?
20 Exchange CALs, I am not sure about this one, the second link i found only mentions acces via web and mobile. I would also like to know if the Exchange CAL is per user or email. If it’s per user, then wat do i do with an email that is meant for multiple
users?
2 Server CALs, This is just buying 2012R2 isnt it? Does this also allow me to use one physically and the other as a VM in the physical one? Just asking, im not really going to use a VM.
Hope you guys can help me out on this one, i didn’t expect the CALs would bet his complicated.

Hi,
Under Per User licensing, you need a license for each unique human that will access the software. Based on what you have written above, below is a general description of the licenses you need:
20 Per User Windows Server CALs
20 Per User RDS CALs
20 Per User Exchange Standard CALs
1 Exchange Server 2013 Standard license
2 Windows Server 2012 R2 Standard licenses
Notes:
Each Server 2012 R2 Standard license allows you to install it on a physical server (up to 2 CPU sockets) with the Hyper-V role installed, and install it in 2 VMs. The key here from a licensing perspective is the installation on the physical server
is only being used for Hyper-V--if you use it for some other purpose (like AD, SQL, etc.) then you are only permitted to run 2012 R2 on 1 VM without an additional license. Running your servers as VMs is the common and recommended method now, unless
you have a specific reason not to.
I listed two 2012 R2 licenses above because from your description I get the idea that you will have 2 physical servers.
It is preferred to split key roles/functions onto separate VMs if possible. For example, it would be preferred to have Exchange on its own VM(s). This is obviously subject to your specific situation, budget, etc. In smaller environments
some roles will be combined in order to save money.
I did not include licenses for Office in the list above.
Yes, Per User licensing means the user can access the software from any device, even their own private pc.
I recommend you purchase licenses through a MS volume licensing program that fits your needs. Adding Software Assurance (SA) to your licenses will allow you to get the new versions when they are released as well as give some additional licensing rights.
As always, it is essential to read the Product Use Rights (PUR) document, licensing agreements, terms and conditions, etc., as applicable to your licenses.
I recommend you also take a look at the Office365 plans that include Office/Exchange/etc. There are Exchange-only plans as well. Depending on your needs it may be preferred to have your users access Exchange in the cloud and run RDS on premises.
Licensing Windows Server 2012 R2 Remote Desktop Services and Microsoft Desktop Applications for Use with RDS
http://www.microsoft.com/licensing/about-licensing/briefs/winserv2012-rds.aspx
Exchange Server 2013 licensing
http://products.office.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview
-TP

How to enable S/MIME in OWA MS Exchange 2013?

Hello,
I can't find in ECP for MS Exchange 2013 function to enable S/MIME for OWA. Can somebody help me? I found only registry update for MS Exchange 2010 SP1 or download S/MIME function for IE7+ for MS Exchange 2010, but I am not sure if I can use it for 2013.
Thank you,
Pavel Hula

As Martina has pointed out, no S/MIME support in 2013 yet!
Rajith Enchiparambil |
http://www.howexchangeworks.com |

Missing ECP directory in Exchange 2013/2010

Similar Messages

Maybe you are looking for