0

We have a Windows 2008 R2 DC and we are installing Exchange Server 2013 (New installation) on a Windows 2012 R2 Server. During the installation I noticed it is getting stuck after completing 18% or 19% during the ADPreare step. Following are my findings

1) While the installation is stuck, on the DC LSASS.exe is using 100% CPU

2) I have narrowed it down to the series of LDF files (Named PostExchange20XX_SchemaYY.ldf) the installation loads on the AD using the LDIFDE tool.

3) If I run the entries in the LDF file that gets stuck individually, it loads successfully. But when there are multiple entries this issue happens.

4) While the LSASS.exe is 100%, even if I cancel the Exchange Setup the CPU usage does not come down and only way to bring it down is to reboot.

5) Tried running Active Directory Diagnostics performance counters to troubleshoot, but it does not log any data at all.

Any ideas?

Improve this question

1 Answer 1

Reset to default
0

First of all, make sure you are running the latest release of Exchange 2013, Cumulative Update 6. You can get it here. It's a full setup package, you can (and should) use it to install Exchange 2013 even if there is no previous version installed.

Then, try to manually run only the setup step which performs the AD schema extension:

Setup.exe /PrepareSchema

If you still have trobules, then there probably are problems and/or performance issues on the domain controller which holds the Schema Master role; try transferring it to another domain controller and running the schema preparation again.

Improve this answer
6
  • 1
    I am using the latest update and also tried the Setup.exe /PrepareSchema without any luck. I even took the LDF file only and tried to manually load it with LDIFDE outside the setup and same issue. I can try transferring to another DC, but would appreciate any help in identifying why this issue happens.
    – YSR
    Oct 8, 2014 at 22:28
  • How long have you let it run? The AD schema extension does indeed take some time, during which high CPU usage on the Schema Master DC is normal.
    – Massimo
    Oct 8, 2014 at 22:32
  • BTW, you should not attempt to manually load the schema extension files; they are meant to be used only by the Exchange setup.
    – Massimo
    Oct 8, 2014 at 22:35
  • I have let it run for over 14 hours and throughout the LSASS process was 100%.
    – YSR
    Oct 8, 2014 at 22:50
  • 1
    @YSR - Yikes. Something seems very fishy with that. Given that it's the AD schema we're talking about I'd be really, really tempted to bring MSFT support in on this. Don't monkey around w/ the AD schema-- it's hard as heck to restore from backup.
    – Evan Anderson
    Oct 9, 2014 at 0:23

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .