Hi

I started the update of Exchange 2013 CU2. Everything went fine, but now it hangs since about 3 hours at "Step 9 of 18: Languages".

What can I do???

Regards
Peter

We installed one Exchange 2013 server named EXCH1 with both CAS and Mailbox on it.   Everything was working correctly.

So I installed a second CAS/Mailbox server named EXCH2.

After that, one user started reporting this error.   {Outlook is unable to connect to proxy server exch2.domain.com. (Error Code 8).

(Question 1) Does Exchange 2013 CAS load balance automatically?  Because all of the DNS and external URLs point to EXCH1 (going through a firewall and such of course)

So why is a user being pointed to EXCH2?

So I made sure all the VirtualDirectories in EXCH2 matched those from EXCH1.  Also imported our wildcard cert.

(Question 2) Should that make the error go away or are there other things I need to do?  It's hard to tell if the error is widespread because only 4 users are on the new Exchange environment right now.

Hello,

I started the setup with this command: Setup.exe /mode:Install
/role:MB,CA,MT /IAcceptExchangeServerLicenseTerms /targetdir:"D:\Program Files\Microsoft\Exchange
Server\V15".

But the installation hangs/freeze at 2 points, on server 1 at mailbox role: transport service at 65% and on server 2 at mailbox role: client access service at 29%.

The OS is 2008R2 (virtual), and there is a snapshot running on the hyperv envoirment.

anywhone have an solution for this?

Hello Everyone,

I am trying to install Exchange 2013 on a new windows server 2012 VM that's joined to an exchange 2007 environment.  

When i run the Exchange 2013 readiness check, i receive only two errors -

Like i said before, this is a completely exchange 2007 environment and exchange 2010 isn't installed. For the life of me, i cant figure out why its giving me these errors. I have looked at all our VMs for a 2010 installation, but have not found anything.

How would i check to see if another Sys Admin before me spun up a new VM and installed Exchange 2010 as a test, but then just deleted the VM and didnt uninstall exchange completely? That's the only possibility i can think of. 

Thanks 

I am running two, two node DAG's with Exchange 2013.

One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.

No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".

I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers.  I also receive errors when trying to failover the databases because the content index state is failed.

In my test environment I have a very similar setup working fine with no issues.

Please let me know what I can try to get this resolved.

The error I receive when running the following set of commands is:

suspend-MailboxDatabaseCopy dag2db1\mbox1

update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles

[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles

Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Hi folks,

I've got an on-premise Exchange 2007 and an on-premise Exchange 2013 server, both in the same AD forest and in the same organization.  I've used the migration tool to move some mailboxes and all seems to be working ok.

Do I need to get everyone out of their mailbox (outlook, OWA, activesync) while I'm migrating it?  It seems like a wise thing to do, but it requires extra coordination to pull off.  It would be sweet if the software was smart enough to deal with the mailbox moving while those things were reaching for the mailbox.  The documentation I've read doesn't really address this question.

Thanks

Patrick

I'm trying to install 2013 on a 2008R2 domain controller logged on as an enterprise admin.

I keep getting 1603 errors  "could not open key".   I have uninstalled and tried again multiple times after resetting permissions on what ever key is mentioned

I've tried every article I could google.

I'm missing something.

Anyone have any ideas?

David

Exchange 2013 w/2007 co-existence/ CU2 v1 Uninstall removes Public Folders, Exchange Security Groups Items, then prepareAD duplicates Exchange Security Group items

Written by Noel Dorobek August 2013

I spent 7 weeks on the phone with MS regarding these issues. I ultimately resolved myself. Here are the steps I took to resolve all of the above issues. I have written this up to save anyone else the fumbling. No two environments are alike, but hopefully this information is helpful to someone.

I Installed exchange 2013 RTM, Then applied CU1, and the first release of Cu2. During the CU2 upgrade the process failed. Couldn’t continue. According to technet the issue I faced could easily be resolved if I uninstalled Exchange and Installed Exchange directly from CU2. I uninstalled Exchange & noticed that our public folders, meeting rooms, and the like were removed. (Verified by looking at the Default naming context\ms exchange All Exchange Security Groups in AD were also removed. Running co-existence with Exchange 2007 so without the security groups it is now down, and as AD permissions are now hosed, the services won’t start, with access denied errors, and missing guid’s errors in exchange gui.

**Note - All the following steps assume healthy DC’s & AD replication, and that you have sufficient permissions to perform the steps. (rule of trade – “run as admin” FTW)

Exchange System Objects gone after Exchange 2013 CU2 v1 Uninstall.

1.       Get on a DC (fsmo role schema master preferred), and set it to stop incoming replication. (repadmin /options DCname +DISABLE_INBOUND_REPL)
2.       Drop to Safe Mode & select Directory Restore Mode. I used a Symantec backup to restore AD.
3.       Do a authoritative restore on the Default Naming Context\Microsoft Exchange System Objects. This will get your public folders, calendars, resources restored.
4.       Bring the DC back up, and repadmin /syncall. Wait a good 10minutes before going forward while everything sync’s. (verified by checking the restored AD object on other DC’s and verifying your removed items are back)

Exchange Security Groups Gone after Exchange 2013 CU2v1 Uninstall.

Now we have to correct the missing Exchange Security Groups & Permissions in AD. Before Exchange 2007 will work & before we can go back to Exchange 2013. AD now has permissions and item attributes corrupt/missing/wrong.

1.       First open ADSIEdit & connect to the default Naming context.
2.       Go to the properties of the MS Exchange Security groups & MS Exchange System Objects. Make sure you have no unknown (guid/ssid) items. If you have any remove them. Make sure any inherited unknown items are removed from the location they are inherited from. Make sure to check every folder from MS Exchange * Down.
3.       Now in ADSI edit connect to the Configuration Container\Services\MS Exchange\*enterprise name*\Administrative Groups\*admingroup name*\servers\*exchange server name*. Make sure you have no unknown (guid/ssid) items. If you have any remove them. Make sure any inherited unknown items are removed from the location they are inherited from. Make sure to check every folder from MS Exchange * Down.

That last step will leave orphaned attributes in the MS Exchange Security Group object. You cannot edit these attributes in adsiedit. You will have to use ldp.exe (built into windows).-= CAUTION: LDP.exe is not to be played with, you can get in real trouble using this tool if not very conscious and cautious=-

*NOTE - Exchange prepareAD is what will give us all our exchange security group items back, but exchange perpareAD will choke and won’t complete a run complaining of the following missing items items unless removed first. 

1.       Open ldp.exe on the same DC the above steps were performed. Connect to the local DC, Bind with credentials, View select Tree & give the BaseDN of your default naming context. (DC=domain,DC=suffix)
2.       Locate then double click the MS Exchange Security Groups object & find the otherWellKnownObjects attribute. You will see the deleted Group Objects listed out here. These all have to be removed. Copy them out and make a list.
3.   Right click the MS Exchange Security Groups object & select Modify.

In the Edit Entry Attribute:  type “otherWellKnownObjects” In the Values Field you will paste the objects one at a time here. In the Operation make sure you click the Delete button.

Example: B:32:C262A929D691B74A9E068728F8F842ED:CN=Organization Management1\0ADEL:ddf8a0b2-7683-4af5-9533-fa003645c879,CN=Deleted Objects,DC=Domain,DC=suffix

1.   Now copy the listed objects (example above) one by one into the Values Field, and click RUN. This will remove the attribute.
2.   Open Admin CMD prompt & repadmin /syncall (wait about 10min to do next steps, if a lot of DC’s or slow replication, wait longer.)

Now all remnants of the old deleted groups are gone from AD. We will now propagate the Exchange Security Groups again.

1.   On Exchange 2013 from an Admin CMD Prompt Run

setup.exe /prepareAD /iacceptexchangeserverlicenseterms

setup.exe /prepareschema /iacceptexchangeserverlicenseterms

1.   This will give you back your Exchange 2007 & 2013 Security Groups. Likely we just duplicated groups. Example: Exhange Organization Admin, and an Exchange Organization Admin1 will simultaneously exist, and so on down the list. I actually had 3 of each group.
2.   If your exchange services have been down. The server can now be brought up. Restart the Exchange AD Topology Service on the Exchange server. You may need to mount your store manually depending how bad it has been.

Exchange Security Groups are Duplicated after Exchange perpareAD

After this step I had all my exchange security group duplicate… example - Ex Org Admin, Ex Org Admin1, and Ex Org Admin2. No matter how many are loaded, the last will usually be the one exchange will use (Admin2 from my example above). You can verify this by launching your current exchange server, and looking in the ORG Management Permissions tab, which groups are associated with Exchange.

Now to remove the duplicates & get in position to do 2013 install from CU2 version 2. Unfortunately we will have to perform the above steps again, for the unused exchange security group removal.

1.   Check what group current Exchange is using from above.
2.   Open AD Users & Computers. Delete the Groups Exchange is NOT using. Rename the groups if it is admin1 and so on back to the default with no number, if you like. I did for cosmetics.
3.   Now we have both unknown permission accounts, and orphaned object attributes from above (steps 5-12). So we need torun through steps 5-12, making sure during the ldp.exe that we only remove the accounts we deleted in step17 from the otherWellKnownObjects.

Your current server is now healthy, but we have some work to do for the reinstall of Exchange 2013 CU2v2.

1.   Install Exchange 2013 Cu2 version 2

**NOTE - Unfortunately we will likely get MANY errors (You don’t have sufficient permissions opening exchange shell) due to RBAC being torn up now. The install of Exchange 2013 will fail likely on step 11 of 15 due to AD item attribute issues in the arbitration mailbox’s of Exchange 2013.

Correct Arbitration Mailbox issues

1. Likely the Exchange 2013 install has installed the mail database before you receive these errors. You can verify by checking adsiedit Configuration\Services\Microsoft Exchange\*enterprisename*\Administrative Groups\*exchange administrative group name*\Databases\ If you have one it did.Copy that whole string backwards from DB up.Example:  CN=Mailbox Database 0947437051,CN=Databases,CN=Exchange Administrative Group (blah),CN=Administrative Groups,CN=ENTERPRISE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=suffix
   1.   Now we need to locate and correct the arbitration mailbox’s in AD Users & Computers, make a list of them.Arbitration Mailbox example. (these can be found in default naming context\rootdomain\Users by default.)FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95gb182 SystemMailbox bb558c35-97f1-4cb9-8ff7-hg741dc9289 SystemMailbox*****and so on DiscoverySearchMailbox******and so on Migration******and so on Healthmailbox*****and so on
   2.   In ADSIEdit connect to the Default Naming Context, and open the Users container. Locate the account you collected in the last step. Right click them and select properties.
   3.   Scroll through the attributes tab till you find the HomeMDB Attribute. The value should be your exchange 2013 database path from above (step20). If it is blank or not pointing at the proper database. Correct that now for all the arbitration mailbox’s.

Correct RBAC

1.   Run a powershell session as admin
2. Get-ManagementRoleAssignment
3. Add-PSSnapin *setup
4. Install-CannedRbacRoleAssignments -InvocationMode Install –Verbose
5. Remove-PSSnapin *setup
6. Get-ManagementRoleAssignment

RBAC is now healthy, Group Permissions are now Correct.

You should now be able to open the exchange management shell & complete the install of Exchange 2013.

Issues should now all be resolved.

Hello everyone,

New to exchange... Been a Linux user for years and because of my new job I find myself working with Windows a lot more. Trying to install a trial version of Exchange 2013 on a Trial version of Windows Server 2012 and keep getting an error message saying that no acceptable operating system was detected.  Has anyone come across this error before ??  Or is it simply that I cannot install a trial on a trial :)     Any help would be greatly appreciated !

I started a coexistence upgrade from 2010 to 2013 a couple weeks ago, had 2013 CAS in front proxying OWA and web requests to 2010 and 2013 users alike, all running properly. Then "something" happened, not sure what, and suddenly all Exchange 2013 web requests to login to OWA or to ECP generate a 500 error on the server, no matter if I use localhost, IP address, or FQDN for the internal or external URLs.

Because this is production, I moved back to the 2010 CAS array as the primary and tried to tinker with 2013. Nothing would work, nothing would allow me to access mailboxes hosted on 2013, so I had to disable the mailboxes and re-enable them on 2010 (migration commands wouldn't even work to move them back to 2010). In the end I uninstalled all 2013 servers from my organization and checked ADSI Edit to ensure there weren't any pointers to the 2013 servers I installed.

Fast forward to this week, I wanted to try again, see if the uninstall of the servers fixed the issues. I built two new Windows Server 2012 servers (one CAS and one MBX) and accepted all default settings coming off of the CU2 installer (except one I chose the CAS role and one I chose the MBX role). Fresh install, no users running, I cannot get to the ECP or OWA once again, 500 error no matter what URL I use to access the servers. And proxying to a 2010 mailbox still fails as well.

I've checked out everything I can online, I've removed and re-added the Windows Identity Framework, I've recreated the OWA and ECP directories on CAS and MBX server, and I've run the get-serverhealth command against both servers for the OWA and ECP health sets without errors. Any ideas?

Environment: two Windows servers running AD services and the Hyper-V role, one Windows 2008 R2 SP1 with two virtual guests running Windows 2008 R2 SP1 servers with Exchange 2010 SP3 RU2 and one Windows 2012 with two virtual guests running Windows 2012 servers with Exchange 2013 CU2. Image

I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:

Step 8 of 15: Mailbox role: Transport service

Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013 came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

Hi,

Regarding upgrade from 2007 to 2013.

Earlier the proxy and redirect functinality with the "legacy concept" did not work if the CAS was on a multi-role server. Is this the same thing with 2013/2007 or will this work now also when 2007 and 2013 is on each multi-role sever?

/J

I am having BIG problems installing the Cummulative Update 2 for Exchange 2013.

For some reason, the upgrade keeps failing.

The unattended install gives me this at "Mail Transport Hub installation" (Sorry, the errors are partially in dutch)

        " was run: "Failure configuring SearchFoundation through installconfig.p
s1 - Error occurred while configuring Search Foundation for Exchange.System.Inva
lidOperationException: Kan de service HostControllerService op de computer . nie
t starten. ---> System.ComponentModel.Win32Exception: De service heeft de start-
 of stuuropdracht niet op juiste wijze beantwoord
   --- Einde van intern uitzonderingsstackpad ---
   bij System.ServiceProcess.ServiceController.Start(String[] args)
   bij Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.StartService(String
serviceName, Int32 timeoutInSeconds)
   bij Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Install(String insta
llDirectory, String dataDirectoryPath, Int32 basePort, String logFile, Boolean s
ingleNode, String systemName, Boolean attachedMode)
   bij CallSite.Target(Closure , CallSite , RuntimeType , Object , Object , Obje
ct , Object , Object , Object , Boolean )".

The problem is that the HostControllerService service wont start. When I start it manually, it crashes with the following details:

Probleemhandtekening:
  Gebeurtenisnaam van probleem: CLR20r3
  Probleemhandtekening 01: hostcontrollerservice.exe
  Probleemhandtekening 02: 15.0.712.0
  Probleemhandtekening 03: 5199c4fd
  Probleemhandtekening 04: HostControllerService
  Probleemhandtekening 05: 15.0.712.0
  Probleemhandtekening 06: 5199c4fd
  Probleemhandtekening 07: 7
  Probleemhandtekening 08: e
  Probleemhandtekening 09: System.IO.FileNotFoundException
  Versie van besturingssysteem: 6.2.9200.2.0.0.272.7
  Landinstelling-id: 1043
  Aanvullende informatie 1: ab8c
  Aanvullende informatie 2: ab8c7f0d4887f334a1aa9f1cb12f1875
  Aanvullende informatie 3: 3123
  Aanvullende informatie 4: 3123444efd1f0f58a96f5fa5f54a8618

Lees de onlineprivacyverklaring:
  http://go.microsoft.com/fwlink/?linkid=190175

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
  C:\Windows\system32\nl-NL\erofflps.txt

Naam van toepassing met fout: hostcontrollerservice.exe, versie: 15.0.712.0, tijdstempel: 0x5199c4fd
Naam van module met fout: KERNELBASE.dll, versie: 6.2.9200.16451, tijdstempel: 0x50988aa6
Uitzonderingscode: 0xe0434352
Foutmarge: 0x000000000003811c
Id van proces met fout: 0x2808
Starttijd van toepassing met fout: 0x01cea66d2708a137
Pad naar toepassing met fout: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe
Pad naar module met fout: C:\Windows\system32\KERNELBASE.dll
Rapport-id: 670dbf4c-1260-11e3-944f-000c2918d882
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

Toepassing: hostcontrollerservice.exe
Framework-versie: v4.0.30319
Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.
Uitzonderingsinformatie: System.IO.FileNotFoundException
Stack:
   bij Microsoft.Ceres.HostController.Service.ServiceRunner..ctor()
   bij Microsoft.Ceres.HostController.Service.ServiceRunner.Main()

I am at a loss here. I've tried numerous things. What can this be? It seems a file is missing (System.IO.FileNotFoundException), but does not tell me which one.

In a single domain/forest that coexistence and migration seems straight forward.  We are planning on creating trusts between 2 domains / forests and migrate mailboxes from one domain to the other, from 2010 to 2013.

Is it still possible to have the 2013 servers proxy the connection to 2010 even though it will be across domains?  The domains/forests have 2 way trusts built.

The goal is to be able to make all the ip / dns changes so that the traffic starts flowing through 2013 and we will be able to move mailboxes without the end users feeling the pain of reconfiguring all devices.

Hi

This is probably a basic question for people who have done Exchange migrations to a resource forest. I am seeking a confirmation whether or not a "two way" trust is required for migrating Exchange to a resource forest.

Microsoft documentation for resource forest configurations states that a one-way outgoing trust from the resource forest to the account forest is required. In other words, the resource forest needs to trust the account forest. That's sufficient for a resource forest configuration to work. I'm happy with that.

I did wonder though, whether or not a trust in the opposite direction would be required for the new Exchange in resource forest to be able to connect to old Exchange in the account forest to perform the cross-forest mailbox move. I imagine this would require the account forest to trust the resource forest, so essentially we would need a two-way trust.

Any guidance from more experienced folks please.

Thanks

Nauman.

P.S. The migration is from Exchange 2003 SP2 to Exchange 2010 SP2 set up in a brand new resource forest.

Dear sir/madam,

This week announced the teachers on school that we have to start with a graduation because this is my final year. I will set up an Active Directory domain with an Exchange server 2013 and a client running Windows 7 Professional. All servers will running Windows Server 2012 Standard x64. Today I watched and read the installation instructions, system requirements ect. but I have a question before I will start the project and I cannot find the answer.

My question is: I will use one domain controller and a second server will running as an Exchange server 2013. Will I have to install Active Directory Domain Services and raise it to a second domain controller on the server that will be running as Exchange server or is domain joining enough before the installation of Exchange?

I hope that you can understand my situation and I hope for a quick reply.

Yours faithfully,

Ronald Tempelaar

Since setting up some Windows SBS 2003 many years ago I've mainly been involved with Linux and VMware ESXi

Last couple of month have been testing setup of Windows 2012 and Exchange 2013

So setting up my 1st Production Windows 2012 with Exchange 2013

Plan: - Any comments, suggestions or "that's a big no-no" appreciated

Dual Xeon Processor Server with 64Gb RAM, 3 x RAID1 600Gb SAS 15K Pairs 
1st Windows 2012 Std setup as DC for user files - this will also have hyper-v installed
to run the 2nd instance of Windows 2012 with Exchange 2013

I'm assuming here for users files - the NONE VM Windows is going to give me best performance ! ** correct me if I'm wrong!
(Also by doing this I can run Backup Software on the Host rather than the VM)

Bit confused with a couple of things (ok, ok a lot of this stuff then!)

confused with Domain Naming & SSL (I have run the deployment wizard but still confused)

mydomain.local   or  int.mydomain.com

No DNS for setup at ISP for hosting mydomain int.mydomain.com  ?

Webaccess, ActiveSync, Outlook over the internet, VPN - what kind of Certificate is required ?