I am creating my first Exchange 2013 server DAG complete with its own dedicated Active Directory in my lab. Currently, I have 4 servers in the domain all running Windows 2012 Datacenter: 1 AD server and 3 Exchange servers (two of which will be configured with just mailbox database role/added to the DAG and the third which is a dedicated CAS as well as my FSW that will not be included in the DAG). Here are the steps I took:

Hi All.

We are currently using just Exchange 2010 with a view to migrating to Exchange 2013

I have read all the recent blogs (specifically from Brain Day) relating to CAS; these include ‘Demystifying the CAS Array Object’ and the very interesting ‘Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations’

I now know that Outlook must always use Outlook Anywhere (RPC over HTTPS) to function correctly with Exchange 2013 both internally and externally.

Therefore Outlook has to be able to resolve 'mail.contoso.com' to a public address for external users to hit the Outlook Anywhere proxy URL, (as it currently does for us), and an internal address for network (LAN) users

Here’s my question…

We use external DNS servers at our ISP for Internet users to resolve our public facing servers, for example (I've replaced our real domain name with ‘contoso’): -

mail.contoso.com (for Outlook Anywhere)

www.contoso.com

ftp.contoso.com

Internally our AD Forest is ‘company.contoso.com’ so we use Active Directory DNS Servers for all internal name resolution, for example: -

               outlook.company.contoso.com (for MAPI Outlook)

               server1.company.contoso.com

               server2.company.contoso.com

How do I ensure that Outlook Anywhere resolves ‘mail.contoso.com’ to an internal address when clients are on the LAN?

Can I add a ‘contoso.com´ zone to our Active Directory DNS Servers to solve this, without affecting any AD or DNS (Internal and External) functionality?

When migrating or adding a new user to Exchange 2013, I get the following error when going into the Mailbox Delegation section in the Exchange Admin Center.

The object <Object CN> has been corrupted, and it's in an inconsistent state. The following validation errors happened:

The access control entry defines the ObjectType 'Object GUID' that can't be resolved.

I have done the following to try and resolve the GUID

Searched via LDP, ADSI, ADUC, Repadmin, with nothing found. I've converted the GUID from string to hex and searched with still no luck.

I get the identical error when running a Get-ADPermissions on the object as well.

There are no inheritance blocks on the object or OUs.

I've opened a Premier case, but wanted to ask the community if they have seen this or had any suggestions. As of right now, Exchange 2013 is the only app that can see this orphaned object.

Exchange 2013 CU2
Mailbox server a member of the DAG
Database mounted and functioning except indexing.

The problem is the indexes. Indexing is enabled and I have rebuilt the indexes repeatedly. I can create a second copy but with errors on the indexes. Any help is appreciated.

There is an event error when searching:
Exchange Server Information Store has encountered an error while executing a full-text index query ("and(or(itemclass:string("IPM.Note*", mode="and"), itemclass:string("IPM.Schedule.Meeting*", mode="and"), itemclass:string("IPM.OCTEL.VOICE*", mode="and"), itemclass:string("IPM.VOICENOTES*", mode="and")), subject:string("SearchQueryStxProbe*", mode="and"), folderid:string("FD00F7A480B3504EB0BE1B5246A7E45100000000000E0000"))"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request
   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)
   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)
   at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

Hi all,

I am trying to find out what is the best practice of maximum of mailbox per exchange 2013 database? And how much storage will be required for my exchange 2013 deployment

I have VMware environment, currently using exchange 2007 and have 500 active mailbox, including resource and users.

I am targeting 1000 users with 5% growth. I don’t need HA and don’t want (not necessary) DAG. I don’t mind to install MBX + CAS in one server or separate in to two, if recommended.

I use Exchange 2013 Server Role Requirements Calculator v5.9 and it makes me confuse and I can see the requirements are huge for 1000 users 

According to calculator,  I need the following,

And I need 64 databases, 16 users in per database, which makes me confuse.

 Please give me some more light

Hi,

I currently have a customer that I am migrating from Exchange 2010 SP3 to Exchange 2013 (CU2). The environment consists of a single Exchange 2010 server with all roles installed, and a single Exchange 2013 server with all roles installed. Both servers are located in the same AD site, and are both virtualised servers.

We have successfuly migrated approximately 200 users across several migration batches. We have now encountered an issue where we start a migration batch containing anywhere from one mailbox to 30+, and the batch and all contained mailboxes goes to a state of "Syncing", however no items are synced and the mailboxes stay in this state for days (up until I cancel the migration batch). I have tried removing and recreating the migration batches, however this has made no difference. I am able to migrate mailboxes between databases on the 2010 server without issue, it is only when migrating to 2013.

I have tried both suggested solutions in the Microsoft KB article http://support.microsoft.com/kb/2807668 as I have seen forum posts that this can cause the symptoms I am seeing, however neither solution has provided any success.

There is nothing in the Event Logs that I can see that relates to this either. We only have around 60 mailboxes to go, however we are simply stuck and cannot migrate any mailboxes. Has anyone seen this issue before, or have any suggestions?

Many thanks,

Cameron

Hi, 

I installed exchange 2013. The installation went bad I had to uninstall it manually from ADSI edit, then deleted the VM. I installed exchange 2013 once again. I log into ecp, I find under recipients the old mailboxes created with the old exchange server. when I try to delete them or move them, the following error shows: 

The object domain/Users/someuser has been corrupted, and it's in an inconsistent state. The following validation errors happened:
Database is mandatory on UserMailbox.

digging around on the net, I followed this link: http://support.microsoft.com/kb/2702446?wa=wsignin1.0

but I noticed that my homeMDB is not set. 

also following this link: http://technet.microsoft.com/en-us/library/dd535374(EXCHG.80).aspx

I noticed that I dont have anything under this location in adsi edit, while it states that there are some child objects

config...\config...domain\services\microsoft exchange\org-name\administrative groups\ex...admin..groups id\servers\mailbox\informationstore

Should I have ran setup /prepschema and setup /prepad, i didn't because in MS documentation it stated that if the account is a member of enterprise admin and schema admins the schema and AD and Domain preparation would be done by the wizard.

If its partially prepared, can I run them commands again without causing problems?

I can create new users just fine, all I want is to delete these recipients and create a new working ones. also I want to know is my exchange setup right, because I don't want to face major problems when we go live.

its been 3 weeks hitting my head against the wall, help please.

 Hi,

 I have in my environment  Exchange 2010 sp3 and I am planning to install Exchange 2013 cu1. I will install it on Windows  2012 r2. In my forrest which is Windows 2008 r2, I have one domain and one subdomain. I am having difficulties to decide which setup commands I need to run to prepare my schema and AD.

 Do I have to run  diffrent form these two?

  setup /PrepareSchema /IAcceptExchangeServerLicenseTerms

  setup /PrepareAD /OrganizationName /IAcceptExchangeServerLicenseTerms

thanks.

Erró

Hi,

We are planning an Exchange Server upgrade from 2003 -> 2013.  The directory servers are all on 2003.  I see that Exchange 2010 and 2013 will run on 2003 directory services.

Are there benefits to upgrading the domain controllers to 2008 or 2012 before we upgrade Exchange?

Thanks!

--Kent

I have to upgrade a customer Exchange 2010 environment to 2013 and during the investigation of customer's current 2010 environment I noticed that the namespace was configured with same URL for CAS Arrays and internal HTTPS services which introduces a serious problem with co-existence as stated in this article (http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx)

This article advices to change the cas array to a unique name that is only resolvable in internal DNS and change RPC endpoint in databases and force all Outlook clients to connect Internally with https to prevent problems before introducing Exchange 2013 servers to organization.

My question is that if I introduce a completely new namespace to Exchange 2013 will this Ambiguous URL problem affect the deployment. Let's say that the old environment uses exchange.company.com in internal HTTPS and CAS Array and webmail.company.com as external namespace. If I install Exchange 2013 to organization and configure it to use new mail.company.com namespace will I be able to prevent this issue? Of course introducing a new namespace means new URLS for OWA and ActiveSync etc but in this particular case it would be easier approach.

Hi I'm new to PowerShell and I've been attempting to migrate an Exchange 2010 SP3 Public folder to Exchange 2013. I'm following the directions found athttp://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx .

I have gotten to Step 3 .\Export-PublicFolderStatistics.ps1 <Folder to size map path> <FQDN of source server>

It runs the command but when it attempts to write the CSV to the drive I get:

Export-csv : Access to the path '\\servername\sharename' is denied

I am running the Exchange PowerShell in Administrator mode

Within File Manager I have given:

the share Everyone Full permissions

NTFS Full permissions to:

Everyone, Domain Admins, Domain Users, Exchange Servers, Exchange Organization Admins,

PS] C:\Windows\system32>C:\ps_scripts\Export-PublicFolderStatistics.ps1 "\\server\sharename" server.domain.local
[11/21/2013 9:59:42 AM] Enumerating folders under NON_IPM_SUBTREE...
[11/21/2013 9:59:50 AM] Enumerating folders under NON_IPM_SUBTREE completed...25 folders found.
[11/21/2013 9:59:51 AM] Retrieving statistics from server SERVER
[11/21/2013 9:59:52 AM] Retrieving statistics from server SERVER complete...45 folders found.
[11/21/2013 9:59:52 AM] Total unique folders found : 45.
[11/21/2013 9:59:52 AM] Exporting statistics for 45 folders
[11/21/2013 9:59:52 AM] Exporting folders to a CSV file
Export-CSV : Access to the path '\server\sharename' is denied.
At C:\ps_scripts\Export-PublicFolderStatistics.ps1:221 char:70
+ $script:ExportFolders | Sort-Object -Property FolderName | Export-CSV <<<<  -Path $ExportFile -Force -NoTypeInformati
on -Encoding "Unicode";
    + CategoryInfo          : OpenError: (:) [Export-Csv], UnauthorizedAccessException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.ExportCsvCommand

[PS] C:\Windows\system32>

Anand_N

Hey all,

I have begun migrating our exchange 2010 setup over to 2013, I have setup two CA servers with live IP addresses and one MD server on a local range, both CA servers are loadbalanced, external and internal URL's are setup to go to  the external load balanced url (for now call it owa.bla.com) a wild card SSL has been installed onto the servers and OWA is accessible via https  with the correct ssl.

imap and pop3 are another matter all together, when assigning the ssl to the system it says I need to use powershell it says this:

 This certificate with thumbprint XXXX and subject '*.blah.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service.

pushing forward I went to the CLI and used set-popsettings -x509certificatename "owa.blah.com" which was successfully completed. going back to ECP I attempted to run this again with no love.

digging further into it I ran a get-popsettings |fl  and get the following information:

seeing this I tried to change the ExternalConnectionSettings to match the certificate name (also tried the internalconnectionsettings)

and got this:

any thoughts?

servers are setup like so:

ca-1.blah.net (live ip) 

ca-1.office.blah.net(internal server)

ca-2.blah.net

ca-2.office.blah.net

both of these are load balanced onto owa.bla.com

Let me know if you need any more information.

Dear All,

I'm trying to install Exchange Server 2013 in the windows server 2012 (PC2) that already join a domain in another windows server 2012 (PC1) as a DC.

But always it's appear the below error on step 7 of 14:

Error:

The following error was generated when "$error.Clear();

                set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController" was run: "The domain is invalid. Property Name: Domain".

i have checked if the server has SPN setup correctly as the below steps, and it's looks fine to me without any problem.

a. On the domain controller, open adsiedit

b. Expand to Domain,CD=Computer,

c. Right-click CN=<var>serverName</var>, and then clickProperties.

d. In the Attributes list, click servicePrincipalName, and then clickEdit.

e. Under Values, make sure that it contains the following Value: HOST/ServerNetBiosName

so please i need your help.

Thanks

I'm on one of my last steps in migrating from 2010 to 2013.  When I issue the command to  Resume the migration request after the Autosuspend happens, I get a StalledDueToMailBoxLock, and it retries but never completes.  I've removed the request and tried it again, but I get the same thing.  The requests were 24 hours apart.  I have no clients that are connecting to the 2010 server anymore, and all the user mailboxes have been migrated to 2013 successfully.  I haven't found much online about this status, so I'm at a loss.  By the way, this is during my Public Folder migration process.  Sorry for leaving that out.

Thank you.

Dear all

During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :

 The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".

Any advice please !!

I have exchange 2013 with TMG 2010.

Running Autodiscover test on testexchangeconnectivity.com shows

	The Microsoft Connectivity Analyzer is attempting to test Autodiscover for erik@contoso.com.
	Autodiscover was tested successfully.
	Additional Details
	Test Steps

I created the TMG Outlook Anywhere rule as per http://www.microsoft.com/en-us/download/details.aspx?id=8946 and also a OWA TMG rule all on the same listener with FBA 

When i start Outlook 2013 on my home pc (non-domain joined) and add an account and fill in the Outlook Wizard my name and mail erik@contoso.com with password i click next and i receive error 

Looking on TMG error&logs i see:

TMG Log type: Web Proxy (Reverse) Status: 12309 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator. Source: 68.144.93.168:63357 Destination: 10.1.250.5:443Request: POST http://autodiscover.contoso.com/autodiscover/autodiscover.xml Filter information: Req ID: 0fd0e583; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=no, logged off=no, client type=unknown, user activity=yes Protocol: https User: anonymous

 &

TMG Log type: Web Proxy (Reverse) Status: 0x80004005 Source: 68.144.93.168:63357 Destination: 10.1.250.5:443 Request: POST http://autodisover.contoso.com/autodiscover/autodiscover.xml Filter information: Req ID: 0fd0e584; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=no, logged off=no, client type=unknown, user activity=yes Protocol: https User: anonymous

We are currently used a non-named hosting provider and want to bring Exchange in house. 

I am considering the pro's and con's of utilizing a Split Domain scenario, with the hosted server as teh primary, my question is once you go down that route and then want to un-do the split domain - is it possible to do this and only have the internal mail server?

I see that my internal server will become a sub-domain, what are the implications for my mailboxes - can I easily move the content from one to the other? 

If this is not advised, what would you suggest?

Thank-you

Hi,

I am performing a migration to a hybrid exchange deployment.

I have looked on the deployment assistant for autodiscover dns information but it just says I need autodiscover.domain.com externally pointing to my on premise CAS which I already have from my current deployment.

My question is... If a user mailbox gets moved to office 365 how does autodiscover work to redirect them to the cloud service for their URL's?

Can someone give me a high level description for internal and external outlook users?

i.e. external user: connect to cas using public autodiscover.domain.com A record, on premise CAS provides alternative autodiscover URL??

***Don't forget to mark helpful or answer***