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.

Similar Messages

Exchange Server 2013 Standard User CALS

Hi there we have exchange server 2013 Standard with 300 User CALS installed on Windows Server 2012 R2 Standard.
We bought 300 User CALS for Exchange Server 2013 Standard , do I need to Buy the same amount (300) user CALS for Windows Server 2012 r2 too .. for people to have acess to the outlook
web app , or just the user cals that are bought for Exchnage server 2013 will be sufficient ?
please some one let me know asap

Hi,
As you known, software license is a legal instrument governing the use or redistribution of software. However, software license is NOT universal for whole world. The license content is different for countries or regions.
Please suggest customer contact local Microsoft customer support to confirm this issue.
Thanks for your understanding.
Best regards,
Belinda Ma
TechNet Community Support

Exchange Server 2013 installer will not start or complete

Hello,
I am trying to MS Exchange Server onto a Windows Server 2012R2 with Active Directory network. I had started an installation process and it shot out a list of pre-requisites that server need before it can attempt to install. I fulfilled every pre-requisite.
Rebooted the server. Now whenever I attempt another installation process again. It starts, gathers information, and quits with event log:
Windows Installer installed the product. Product Name: Microsoft Exchange Server. Product Version: 15.0.516.32. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.
MS Exchange Server is not listed in Programs and Features to even remove, is it a faulty Microsoft Installer? I have already rebooted numerous times to no avail.
EDIT: Here's a copy of the MSI log, I couldn't find anything to indicate what's going wrong myself, http://pastebin.com/LwCAimuF

Hi,
I've downloaded (as per instructions above):
Microsoft Exchange Server 2013 Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Again, the installer repeats the same behavior as before, right now I am running a repair tool on .Net repair tool.
New log http://pastebin.com/SDynMaDe
Edit: Looks like there's long list of issues trying to fulfill Exchange Pre Requisite.
Windows Management Framework 4.0
http://www.microsoft.com/en-us/download/details.aspx?id=40855
"The certificate for the signer of the message is invalid or not found"
It would probably be best to re-install Windows Server again

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

Exchange Server 2013 SP1 CU5 - The Microsoft Exchange Replication service VSS Writer encountered an exception

We have 2 server DAG with a witness all servers are Server 2012 R2. Both members of the DAG are Exchange 2013 SP1 CU5.
We haven't seen this until recently, but during a VSS enabled storage snapshot the following errors occur. All of which are related to MSExchangeRepl and the Exchange VSS Writer.
Event IDs 2140, 2026, 2028, 2030.
The errors start with the 2140 seen here:
The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PrepareSnapshot. HResult -2147467259. Exception Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError:
Unable execute Prepare on snapshot. (hr=0x80004005, ec=1108)
Diagnostic context:
Lid: 1494 ---- Remote Context Beg ----
Lid: 56264 StoreEc: 0x1388
Lid: 46280 StoreEc: 0x454
Lid: 1750 ---- Remote Context End ----
Lid: 59216
Lid: 34640 StoreEc: 0x454
Lid: 52264
Lid: 46120 StoreEc: 0x454
at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass1c.<SnapshotPrepare>b__1b()
at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotPrepare(Guid dbGuid, UInt32 flags)
at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PrepareSnapshot().

Hi Julez K,
According to your description, you could try upgrading to CU6.
In addition, you could review the Exchange Application (App) Event log and the Exchange System (Sys) Event log for errors , and some related resolutions for your reference.
http://www.symantec.com/business/support/index?page=content&id=TECH209938
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.
Hope it can be helpful.
Best regards,
Eric

(BUG??) Team Foundation Server 2013 Update 4 Support for SQL 2014

Scenario: On Windows 2012 R2 x64 I have installed SQL, Reporting Services & AS 2014 (applied all updates through Windows Update), SharePoint 2013 Foundation, and installed Team Foundation Server 2013 RTM (did not configure).
Before configuring TFS, I applied Update 4 to the server (not update 1,2 or 3 directly). When trying to configure I get the following error:
==========================
TF255146: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance you supplied is version 12.0.2254.0.
TF400403: The Report Server instance specified is version 12.0.2254.0, the minimum supported version is 11.0.3000.
TF400070: A required version of a component is not installed on the application tier. You must exit the Team Foundation Administration Console and install a supported version of either SQL Server Analysis Services of the SQL Server Client Tools on the application
tier to ensure that the Analysis Services object model is present for warehouse processing.
====================================
My understanding is that as of Update 2 (or was it 3) that SQL 2014 was supported. However it appears if that particular update is not installed directly it bypasses the check. Can someone verify I am seeing the intended result or is this a bug?

Hi Jazzy,
Thanks for your post.
And thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Exchange server 2013 sp1 hardware requirement for 500 user

please give me details like
CPU ?
RAM?
HDD?
SERVER BRAND NAME?

Hello,
Before you install the Exchange, see the prerequisites below:
https://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Windows Server 2012 R2 Will Support for UEFI boot in WDS.

Hi
Currently we had issue in WDS while deploying the image via UEFI boot in the DELL Optiplex 3010. We already deployed the Windows 8 install image and boot image in the Windows Server 2012 R2. After selecting the Network boot its show Start PXE IPV4 and it
will immediately flicker and get back to Network Boot option. Any one please help me out of this.....
But the same is working in Legacy boot and it doesn't activate the Windows 8.

Hi,
As I cannot confirm the exact settings on your side, please see the suggestions provided in following thread:
WDS: EFI BIOS won't PXE boot into EFI mode
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode?forum=winserversetup
The same issue is discussed a lot in this thread and several possible suggestions are provided. See if it is helpful. If there is anything unclear please just let us know.
If you have any feedback on our support, please send to [email protected]

Deploying Windows Server 2012 and Exchange Server 2013

Hi All,
Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
Warm Regards,
Prosenjit Sen
Thanks & Regards, Prosenjit Sen.

Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users. It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
365, if it would ever be less expensive. There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
perform those functions capably.
Just a suggestion. I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment. I just know that if I were running my own business, I would have to be convinced that my business required its own internal
mail system when there are so many fully functional and capable mail systems available via subscription.
. : | : . : | : . tim

Windows Server 2012 C Drive gets always full with exchange server 2013 installed

Hi All
My C drive gets full always with exchange server 2013 installed what would be the reason because this is causing extremely bad to my environment can somebody help me please
Thanks & Regards, Santosh Chowdary Vasireddy System Administrator Prolifcs DHFLVC Silicon Towers, 5th Floor, Survey #14, Kondapur, Hyderabad – 500 032. Work +91 40 3999 1999 Ex.1656 l Cell +91 9849277255 l [email protected] A Global
Provider of IBM, Microsoft and Testing Solutions Award Winner for Technical Excellence, BPM, SOA, Portal and Governance

Hi,
Based on your description, I understand that this issue (C drive gets always full) occurred after Exchange
Server 2013 installed.
à
But my exchange server is installed in different Drive (EX: D)
I suggest that you should check file system to see what folders or files are taking up the space recently.
This issue may be not related to Exchange server.
Please refer to the following article and enable Disk Cleanup Utility. Then monitor the result.
Enabling
Disk Cleanup Utility in Windows Server 2012
Meanwhile, please check if the winsxs directory is growing bigger.
How
to Reduce the Size of the Winsxs directory and Free Up Disk Space on Windows Server 2012 Using Features on Demand
By the way, please check if you have installed update rollup 2836988. I noticed that Windows.edb file grows
very large. For more details, please refer to the following KB.
The Windows.edb file grows very large in Windows 8 or Windows
Server 2012
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Error occurred at the 7 of 15 step of Microsoft Exchange Server 2013

Hi all to every techies ....
I'm a new to exchange server 2013 , I tried to install exchange server 2013 on windows server 2012 but couldn't get the success , It stops either 7 or 8 step of 15 , I tried to google it out but can not getting any progress , I tried to remove it , I deleted
by using ADSI Edit then I removed from the IIS then I delete the Microsoft folder from the Installed directory , and also I removed it from the registry editor as well , Thing thing is pulling my hair out my scalp , Any related help highly appreciated ,
The registry key (pickup / transport) doesn't exist in specified registry location , (i.e HKEYLM_SOFTWARE_MICROSOFT_EXCHANGESERVER
Thank you all
Neil Patric

Hi,
To understand more about the issue, I’d like to confirm the detail error when the installation failed.
As far as I know, deployment of an Exchange Server 2013 server goes through three main stages.
1. Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
2. Installing the Exchange Server 2013 pre-requisites on the server
3. Running Exchange Server 2013 setup
For more information, you can refer to the following article:
http://exchangeserverpro.com/how-to-install-exchange-server-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,
Angela Shi
TechNet Community Support

Exchange Server 2013: Outook Clients and OWA keeps on disconnecting/connecting every 5-10 mins

We have a new exchange server 2013 installed but also has exchange 2007 up.
MX records are now pointing to the new exchange server, all were working ok after DNS records were changed but after the weekend it Outlook clients and OWA keeps on disconnecting and reconnecting from exchange.
Exchange 2013 CU6
Anybody else experienced the same?

hi Jheycie,
can you please check if you have .local and .com (different internal and external domain)
almost similar thread.. it worked for me
http://social.technet.microsoft.com/Forums/office/en-US/cc7d2300-0e1f-499f-a8f1-97f84687b6cc/emails-stuck-in-outlook-have-to-restart-transport-service?forum=exchangesvrgeneral
http://social.technet.microsoft.com/Forums/office/en-US/9b9bf607-f882-4f73-a7b2-611ace3f3115/users-unable-to-connect-to-exchange-unless-they-close-and-reopen-outlook?forum=exchangesvrgeneral
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

SOFS support for Exchange Server 2013

Hi all,
I am aware of the following factors:
1. Exchange only supports block-level storage
2. Using SoFS as DAG FSW is not supported.
But may I confirm whether Microsoft supports the scenario below?
==============================================
My client has one set of Windows 2012 R2 Scale-Out File Servers to support their hyper-V farm. Storage is Dell MD3000 with Windows 2012 R2 Storage Space. Is it supported by Microsoft to run Exchange Server 2013 and Exchange Server 2010 in the virtual machines
which are running on SoFS? Assume IOPS has been properly sized.
==============================================
Regards,
William
William Yang

Hi,
There is no official documents talked about whether the Windows server 2012
Scale-Out File Server is supported for Exchange 2013 and Exchange 2010.
Generally, the supported storage configuration in Exchange 2013 is listed in the article below:
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Hope it helps.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Outlook 2010, 2013 on new 2010 exchange server get windows security popup for password

We recently migrated exchange 2003 on 2003 server to Server 2008R2 and Exchange 2010 SP3. The installation had multiple problems and we resorted to Microsoft technical support for the server resolution. On the server level it seems to function
as expected. Our problem is with outlook 2010 and 2013. Some of these outlook 2010 installs existed prior to the exchange 2010 upgrade and worked as expected prior to the upgrade
Now with new machines (never been connected to our Domain) and some existing windows 7 machines with outlook 2010 and 2013, we get a windows security popup requesting the password.
We have spent a couple of weeks reading blogs, how two's and guaranteed fixes that don't fix. The best we can do is start outlook, get the folders to sync and shortly thereafter it will request the password. You can enter the password and
it comes right back requesting the password. You can cancel the request and you will get needs password in the area where it shows connected to exchange server and then will not prompt for another password until you need an update from the server
or you try to send and email. The email will not send until provide a password and immediately press send. Once in the outbox it will require the password again to send and then cancel the popup and repeat the process again.
Outlook test, turn off discovery, remove all credentials do not help. Outlook anywhere turned off. So far nothing seems to help.
Does anybody have a solution to my dilemma?

Hi,
Please check the problematic users' Outlook settings by the following steps:
1. Click File > Account Settings > Account Settings > Change > More settings.
2. In Security tab, make sure "Encrypt data between Microsoft Outlook and Microsoft Exchange" option is checked, "Always prompt for logon credentials" is unchecked.
3. Change the logon network security to Negotiate Authentication, and Apply > OK to set it.
Restart Outlook to have a try. If the issue persists, please
re-create Outlook profile to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support
Thank you for the response.
I did as you suggested and the problem persists

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???

Similar Messages

Maybe you are looking for