I want to install fresh MS.Exchange 2013 on WinSvr2012 in new server machine with administrator account domain

I've existing server Active Directory for Local Domain which is different from MS.Exchange server

I've follow this instruction :

http://technet.microsoft.com/en-us/library/bb125224%28v=exchg.150%29.aspx

http://technet.microsoft.com/en-us/library/e21cf744-7813-48b3-9293-5cecd89a6c25%28v=exchg.150%29#ADPrep

http://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx

but still got error in step :

Prerequisite Analysis

I've trying to install from setup.exe and here some error :

=======================================================================

Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx

Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

Error:
The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
=================================================================

Any suggest for this issue ?

Thank You,

Dear.

We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?

Thanks for the support.
Regards.

Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Working on a Script that will be run as a scheduled task.  I have most of the script setup but running into one stopping point that's not working how I want it to.

The script runs a Get-Mailuser with some filters that is saved into a variable.

I then have a ForEach loop running through those users and setting them so that the EmailAddressPolicyEnabled is set to False. Then it does and Update-Recipient against that user to mail enable them.  Unfortunately some users still have something wrong with the account so that Update-Recipient fails.  But I haven't been able to detect that failure so that I can have my script do something else if that fails.  Any Ideas on how I can determine if Update-Recipient worked or not.

Jeff C

Hi,

I've been using the exchange team's blog post (http://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx) as a guidelin on configuring my ARR deployment in my lab.

Everything was working perfectly right until i got the last part of the blog on restricting the pattern matches.

The rewrite rules all work fine and everything is working as expected with the excpetion of the fact that i cannot access the options in OWA. ECP itself works great if i access it via thehttps://ecp.domain.com/ecp url, but as soon as i use the https//mail.domain.com/ecp it just wont display anything.
Looking at the failed request logs it just shows that it executes a 302 rewrite to ecp.domain.com, which is what i would expect it to base done rewrite rule matchinghttps://mail.domain.com/ecp to the ecp.domain.com server farm.
If i look at the iis logs it looks like it's getting into some sort of loop (the section below is about a 10% of a single attempt to access the options pages:

2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp/ rfr=owa&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=6983c585-b0ea-4fd0-9bb1-fc747ee8e992 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C) - 302 0 0 15
2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp rfr=owa/&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=d32a3a4f-d8a6-4712-91d4-56360be33793 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C) - 302 0 0 0
2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp rfr=owa//&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=14797897-f1ad-454a-b73c-fde041a43d2b 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C) - 302 0 0 0

Did anyone ever run into something like this? Or have an idea where i may have made a mistake? I've tried everything i could think of.

The rewrite rules i have in place are basically exactly the same as the exchange team's blog but just in case i overlooked somehthing, please se the image below.

thanks in advance for your time

Hi,

I was testing POP3/SMTP connectivity using outlook 2013.

POP3 test was getting passed but i was getting " The target principal name is incorrect" certificate warning while doing SMTP test. When i click on View Certificate it shows the default self-signed exchange certificate, if i say YES at this point of time everything works however this warning comes every time i try to use SMTP services on port 587.



To overcome this issue i have changed the FQDN on Client Frontend ServerNamereceive connector and now it matches the value of SAN value in my public certificate.

After doing this i am not getting any certificate warnings, just wanted to know if this is a right approach to overcome this issue and also wanted to know if this will have any adverse effect on mail flow..?

Another question i have is how can one configure the Default Frontend Receive connector so that it accepts smtp connections on port 25 for exchange users..?

Regards,

Vishal Malhan

I used Exchange 2013 SP1+CU5 to install Edge role on Windows server 2012 R2 workgroup machine

then after installation the service "Exchange server health Service" was not starting automatically or manually with the following error "Error 1075: The dependency service does not exist or has been marked for deletion"

and in the Event Viewer I have this error:

Event Id: 7003

Have an existing ex2010 sp3 organization.

Could not run ex2013cu1 setup from my newly built 2012 server, getting the error in the subject line.  I used the command line to run the AD preparation steps successfully from my 2012 DC/GC, then tried to run setup again from the new 2012 server and still get the same error.  The error itself in the log is pretty useless:

[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0137] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 1 Setup
[05/07/2013 01:19:13.0137] [0] **********************************************
[05/07/2013 01:19:13.0152] [0] Local time zone: (UTC-08:00) Pacific Time (US & Canada).
[05/07/2013 01:19:13.0152] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[05/07/2013 01:19:13.0152] [0] Setup version: 15.0.620.29.
[05/07/2013 01:19:13.0152] [0] Logged on user: DOMAIN\ADMINISTRATOR.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0168] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='sourcedir', Value='\\h1\f$\junk\installers\server\Exchange\2013cu1'.
[05/07/2013 01:19:13.0215] [0] Command Line Parameter Name='mode', Value='Install'.
[05/07/2013 01:19:13.0215] [0] RuntimeAssembly was started with the following command: '/sourcedir:\\SERVER\f$\junk\installers\server\Exchange\2013cu1 /mode:Install'.
[05/07/2013 01:19:13.0215] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:19:13.0793] [0] Finished loading screen CheckForUpdatesPage.
[05/07/2013 01:19:38.0762] [0] Finished loading screen UpdatesDownloadsPage.
[05/07/2013 01:19:40.0496] [0] Starting file's copying...
[05/07/2013 01:19:40.0496] [0] Setup copy files from '\\SERVER\f$\junk\installers\server\Exchange\2013cu1\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[05/07/2013 01:19:40.0700] [0] Finished loading screen CopyFilesPage.
[05/07/2013 01:19:40.0840] [0] Disk space required: 1292445007 bytes.
[05/07/2013 01:19:40.0840] [0] Disk space available: 23767240704 bytes.
[05/07/2013 01:19:59.0762] [0] File's copying finished.
[05/07/2013 01:19:59.0965] [0] Finished loading screen InitializingSetupPage.
[05/07/2013 01:20:02.0934] [0] Setup is choosing the domain controller to use
[05/07/2013 01:20:09.0325] [0] Setup is choosing a local domain controller...
[05/07/2013 01:20:11.0794] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more information on this error.
[05/07/2013 01:20:11.0794] [0] [ERROR] Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.
[05/07/2013 01:20:11.0809] [0] Setup will use the domain controller ''.
[05/07/2013 01:20:11.0809] [0] Setup will use the global catalog ''.
[05/07/2013 01:20:11.0825] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0919] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'.
[05/07/2013 01:20:11.0966] [0] Setup will search for an Exchange Server object for the local machine with name 'WEX1'.
[05/07/2013 01:20:12.0028] [0] No Exchange Server with identity 'WEX1' was found.
[05/07/2013 01:20:12.0044] [0] The following roles have been unpacked:
[05/07/2013 01:20:12.0044] [0] The following datacenter roles are unpacked:
[05/07/2013 01:20:12.0044] [0] The following roles are installed:
[05/07/2013 01:20:12.0059] [0] The local server does not have any Exchange files installed.
[05/07/2013 01:20:12.0075] [0] Server Name=WEX1
[05/07/2013 01:20:12.0137] [0] Setup will use the path '\\SERVER\f$\junk\installers\server\Exchange\2013cu1' for installing Exchange.
[05/07/2013 01:20:12.0137] [0] The installation mode is set to: 'Install'.
[05/07/2013 01:20:27.0591] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
[05/07/2013 01:20:27.0591] [0] Active Directory Initialization status : 'False'.
[05/07/2013 01:20:27.0591] [0] Schema Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Organization Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0591] [0] Domain Configuration Update Required Status : 'False'.
[05/07/2013 01:20:27.0841] [0] Applying default role selection state
[05/07/2013 01:20:27.0872] [0] Setup is determining what organization-level operations to perform.
[05/07/2013 01:20:27.0872] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN.
[05/07/2013 01:20:27.0872] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[05/07/2013 01:20:27.0888] [0] InstallModeDataHandler has 0 DataHandlers
[05/07/2013 01:20:27.0888] [0] RootDataHandler has 1 DataHandlers
[05/07/2013 01:20:27.0903] [0] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more information on this error.
[05/07/2013 01:20:27.0935] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more information on this error.
[05/07/2013 01:21:04.0154] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[05/07/2013 01:21:04.0154] [0] End of Setup
[05/07/2013 01:21:04.0154] [0] **********************************************

Good day

I have an Exchange 2010 SP3 hybrid environment with Azure DirSync.   I have migrated all my mailboxes and public folders to Office 365.   I have also decommissioned one of my Exchange 2010 servers and I have one last server which I would like to decommission so that I'm on the full Office 365 suite.

What are the steps to remove the last Exchange server while still making use of DirSync to keep my AD sync'ed?   Should I upgrade the Exchange server to 2013?   If so, can I use a trial edition for this purpose?

Any help would be greatly appreciated.

Regards
Bradley

I've looked at other answers to this problem but they seem to relate to multi server environments or new migrations - neither apply here. The Exchange 2013 server was implemented last year as a migration from Exchange 2007. It has been running well since. I upgraded to SP1 on Sunday night and since then all users, regardless of Outlook version, are continually being asked to "the microsoft exchange administrator has made a change that requires you quit and restart outlook". Clicking OK loads Outlook normally (no restart). I can delete the Outlook profile and set up a new profile OK but the issue comes back again. Deleting the users roaming or local profile does not help either.

The CAS seems to be set correctly - when I run Get-MailboxDatabase | fl RpcClientAccessserver it returns the correct server.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1

site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1

so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....

When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).

But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)

Problem

EMS on CU5 return very slow result.

EMS on SP1 still ok.

Does anyone face this problem before for CU5??? Please help me figure this out. Thank you

reply from Social.technet

Hi, have a successful federation configured between Exchange 2010 SP3 (latest Roll up) and Office 365. This is to allow free/busy lookups during various migration stages (this is not Exchange Hybrid). Autodiscover works well and all functions work ok.

On-premise users can see cloud users free/busy

Cloud users cannot see on-premise users free/busy.

All local based free/busy works on-premise and in the cloud.

The Exchange Connectivity tool returns the below error from all accounts, this is the only error:

(A wildcard certificate is in use and am wondering if this could be contributing to the problem as I have seen this once before)

	Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
	Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
	Additional Details   Elapsed Time: 4979 ms.
	Test Steps   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URLhttps://autodiscover.company.com/AutoDiscover/AutoDiscover.xml for usertr3@company.com.   The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.   Additional Details   An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN). HTTP Response Headers: Content-Type: text/html Server: Microsoft-IIS/7.5 WWW-Authenticate: Negotiate,NTLM,Basic realm="autodiscover.company.com" X-Powered-By: ASP.NET Date: Sun, 15 Jun 2014 22:33:34 GMT Content-Length: 58 Cache-Control: proxy-revalidate Proxy-Connection: Keep-Alive Connection: Keep-Alive Proxy-support: Session-based-authentication Elapsed Time: 4979 ms.

Any help or guidance would be appreciated as this is the only error we receive now and everything else works.

Kind Regards, Antonio.

Hello,

I am in the process of setting up/configuring Microsoft Exchange Server 2010, which might change to 2013.  I am looking for a plain/simple (the dummies guide) setup guide to setup the Exchange server.  I am new at Exchange so any pointers would be greatly appreciated.

I have a local domain called office.local.com and I want to add a few different websites for email purposes such as abcd.com and xyz.com. If you have any ideas on how to setup Exchange in this way, please post.

Thanks,

Ernie

new server 2012 domain controller, new forest and new Exchange server all clean fresh builds

I can create mailboxes and log in to OWA

connectors for sending were not automatically created

no mx record found in DNS so I added it

checked bindings for DNS to NIC

no joy

so where do I start to make sure all pieces are working ok?

David Sheetz MCP

having problems on new server so I followed instructions to remove Exchange Server 2013 Sp1 using ADSI edit p;er these instructions:

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

now when I re-run setup for exchange 2013 SP1 I get the error :    

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

David Sheetz MCP

Dear reader,

I have an exchange 2010 sp3 organisation with 1 client access server with hub transport and a 2 node DAG. Can I install a stand alone exchange 2013sp1 Edge role on a seperate machine in DMZ and subscribe the exchange 2010 hub transport to it. This in preparation to move to exchange 2013sp1 later this year. The current exchange 2010 edge role is installed on a TMG 2010 machine. Since TMG 2010 is dropped and we also have issues with the current edge's mailflow, i'd like to have a dedicated Exchange edge.

Best regards,

Ruud Boersma

MCITP Enterprise administrator

Hi all, 

i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.

I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS. 

After that the client using Outlook Anywhere started asking for password. 

I configured the Outlook Anywhere with these settings:

Exchange 2007:

OA Hostname mail.domain.com

Client Authentication NTLM

IISAuthenticathion Basic, NTLM

SSL Required True

Exchange 2013

OA Hostname mail.domain.com

Client Authentication NTLM (Both internal and external)

IISAuthentication Basic, NTLM

SSL Required True (both internal and external)

Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.

After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials. 

In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007. 

Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error: (500) Internal Server Error"

Any Ideas?

Thanks for your Help

Hello,

I have a computer running Windows Server 2012 R2 Standard. I have completed all the prerequisites to install Exchange Server 2013. It all was going good until the install started. Then I received the below error. Does anyone have any suggestions? I am new to Exchange Server so would thank and appreciate any help I could get to resolve this issue.

Thank You,

Stan

Error:

The following error was generated when "$error.Clear(); 
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:16cd035a-6201-492f-b85f-1e28cc9f9ee0,CN=Deleted Objects,DC=MULTIAXCNC,DC=local on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MULTIAXCNC,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".