Exchange 2013 & Server 2012 R2

Hi

Just a quick question. We have recently purchased Exchange 2013 & Windows Server 2012 R2.

I've noticed that Exchange 2013 SP1 adds support for 2012 R2. Can we install Exchange without the service pack on 2012 R2 and then add the service pack on later?

Cheers
Dom
cbapartnershipAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
Just download Exchange 2013 CU9 from the Microsoft download site. It is the complete product and you can install from it. That will save you having to up date later.

Exchange 2013 Sp1 is very old (basically CU4) so I wouldn't even considering installing that or anything older.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cbapartnershipAuthor Commented:
So we can just use the 180-day trial version from Technet and activate it with our key?
Simon Butler (Sembee)ConsultantCommented:
All instances of Exchange are the trial version - whether you get a download from the volume licencing site or the CU download from the public site.

http://blogs.technet.com/b/exchange/archive/2015/06/16/released-june-2015-exchange-cumulative-update-and-update-rollups.aspx

" Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 9 directly. "

There is only set of files - the download is usually quicker from the public download site.

Simon.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

cbapartnershipAuthor Commented:
Hi Simon

Thanks for the response.

So this (https://www.microsoft.com/en-us/download/details.aspx?id=47679) copy of CU9 from the Download Center includes a full version of Exchange as well? Nothing else needed alongside it asides from prerequisites such as UCMA and Filter Packs?

Cheers
Dom
Simon Butler (Sembee)ConsultantCommented:
Correct.
Most users do not need the additional language packs, which is why they are a separate item.

Simon.
cbapartnershipAuthor Commented:
Thanks for the help Simon.
cbapartnershipAuthor Commented:
Hi Simon.

I installed it as recommended but now the Exchange server has AD DS installed even though it is a member server of a domain with AD DS already. Is this normal? New to Server 2012 & Exchange 2013.
Simon Butler (Sembee)ConsultantCommented:
The Active Directory tools are required by Exchange to interact with the domain during the installation. It shouldn't be a domain controller.

Simon.
cbapartnershipAuthor Commented:
So it's normal for stuff like AD DS, AD DT and ADSIEdit to be installed on the server during process and yeah, it's only a member server not a DC.
cbapartnershipAuthor Commented:
Hi Simon.

I don't believe the install has gone through correctly as following up from the previous AD stuff that's been installed, when I'm trying to go to http://servername/ecp, I'm getting:

Server Error in '/ecp' Application.
--------------------------------------------------------------------------------

Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable. 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ServiceModel.FaultException`1[[Microsoft.Exchange.Data.Directory.TopologyDiscovery.TopologyServiceFault, Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace: 


[FaultException`1: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.]
   System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +14579646
   System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +622
   Microsoft.Exchange.Data.Directory.TopologyDiscovery.ITopologyClient.GetServersForRole(String partitionFqdn, List`1 currentlyUsedServers, ADServerRole role, Int32 serversRequested, Boolean forestWideAffinityRequested) +0
   Microsoft.Exchange.Data.Directory.<>c__DisplayClass10.<InternalServiceProviderGetServersForRole>b__f(IPooledServiceProxy`1 proxy) +152
   Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception) +406

[ADTransientException: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable..]
   Microsoft.Exchange.Data.Directory.ServiceTopologyProvider.GetConfigDCInfo(String partitionFqdn, Boolean throwOnFailure) +507
   Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts(String partitionFqdn) +88
   Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext(String partitionFqdn) +86
   Microsoft.Exchange.Data.Directory.ADSession.GetConfigurationNamingContext(String partitionFqdn) +243
   Microsoft.Exchange.Data.Directory.ADDataSession.GetNamingContext(ADNamingContext adNamingContext) +601
   Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope) +672
   Microsoft.Exchange.Data.Directory.ADDataSession.GetReadConnection(String preferredServer, String optionalBaseDN, ADObjectId& rootId, ADRawEntry scopeDeteriminingObject) +185
   Microsoft.Exchange.Data.Directory.ADDataSession.InternalFind(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects) +3568
   Microsoft.Exchange.Data.Directory.SystemConfiguration.<>c__DisplayClass53.<FindServerByFqdn>b__52() +192
   Microsoft.Exchange.Data.Directory.Diagnostics.ADScenarioLog.InvokeWithAPILog(DateTime whenUTC, String name, Guid activityId, String implementation, String caller, Func`1 action, Func`1 getDcFunc) +239
   Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.InvokeWithAPILogging(Func`1 action, String memberName) +501
   Microsoft.Exchange.Data.Directory.SystemConfiguration.Server.GetLocalServerClientAccessArray() +116
   Microsoft.Exchange.HttpProxy.Common.PerfCounters.UpdateHttpProxyPerArrayCounters() +12
   Microsoft.Exchange.HttpProxy.ProxyApplication.Application_Start(Object sender, EventArgs e) +348

[HttpException (0x80004005): The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable..]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12600621
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable..]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12617668
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12457285
 

Open in new window

Simon Butler (Sembee)ConsultantCommented:
The error means what it says.
The Exchange server cannot see the domain properly.
Loads of reasons for that - bad DNS records, trying to have the server in another AD site etc.

You should probably ask a fresh question though, as that is unrelated to your original question.

Simon.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.