Exchange 2010 PrepareAD issues

cmb991
cmb991 used Ask the Experts™
on
I have exchange 2010 installed on server 2008 standard.  Our systemmailbox, discoverymailbox, federation objects were curropted.  So we deleted the objects and tried to run "setup.com /preparead".  It keeps erroring out saying theres a pending restart, so we tried to restart and its doing the same thing.  Heres the error logs:


[
[05/25/2012 13:00:42.0181] [0] **********************************************
[05/25/2012 13:00:42.0197] [0] Starting Microsoft Exchange Server 2010 Setup
[05/25/2012 13:00:42.0197] [0] **********************************************
[05/25/2012 13:00:42.0197] [0] Local Time Zone: (GMT-05:00) Eastern Time (US & Canada).
[05/25/2012 13:00:42.0197] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2.
[05/25/2012 13:00:42.0213] [0] Setup version: 14.1.218.15.
[05/25/2012 13:00:42.0213] [0] Logged on user: domainname\administrator.
[05/25/2012 13:00:46.0385] [0] Command Line Parameter Name='nologo', Value=''.
[05/25/2012 13:00:46.0385] [0] Command Line Parameter Name='preparead', Value=''.
[05/25/2012 13:00:46.0385] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[05/25/2012 13:00:46.0385] [0] Command Line Parameter Name='fromsetup', Value=''.
[05/25/2012 13:00:46.0416] [0] ExSetup was started with the following command: '/NoLogo /preparead /sourcedir:D:" /FromSetup'.
[05/25/2012 13:00:47.0213] [0] Setup is choosing the domain controller to use
[05/25/2012 13:00:47.0619] [0] Setup is choosing a local domain controller...
[05/25/2012 13:00:49.0682] [0] Setup has chosen the local domain controller DOMAINCTRL.domainname.org for initial queries
[05/25/2012 13:00:50.0135] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use DOMAINCTRL.domainname.org
[05/25/2012 13:00:50.0135] [0] Setup is choosing a global catalog...
[05/25/2012 13:00:50.0150] [0] Setup has chosen the global catalog server DOMAINCTRL.domainname.org.
[05/25/2012 13:00:50.0166] [0] Setup will use the domain controller 'DOMAINCTRL.domainname.org'.
[05/25/2012 13:00:50.0166] [0] Setup will use the global catalog 'DOMAINCTRL.domainname.org'.
[05/25/2012 13:00:50.0166] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=org'.
[05/25/2012 13:00:50.0182] [0] Exchange organization container for the organization is 'CN=domainname,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=org'.
[05/25/2012 13:00:50.0213] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCHANGE01'.
[05/25/2012 13:00:50.0416] [0] Exchange Server object found : 'CN=EXCHANGE01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domainname,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=org'.
[05/25/2012 13:00:50.0728] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[05/25/2012 13:00:50.0728] [0] The following datacenter roles are unpacked:
[05/25/2012 13:00:50.0744] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[05/25/2012 13:00:50.0744] [0] The local server has some Exchange files installed.
[05/25/2012 13:00:50.0869] [0] Setup will use the path 'D:\' for installing Exchange.
[05/25/2012 13:00:50.0869] [0] Setup will discover the installed roles from server object 'CN=EXCHANGE01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domainname,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=org'.
[05/25/2012 13:00:50.0885] [0] 'BridgeheadRole' is installed on the server object.
[05/25/2012 13:00:50.0885] [0] 'ClientAccessRole' is installed on the server object.
[05/25/2012 13:00:50.0885] [0] 'MailboxRole' is installed on the server object.
[05/25/2012 13:00:50.0900] [0] The installation mode is set to: 'Install'.
[05/25/2012 13:01:26.0230] [0] An Exchange organization with name 'domainname' was found in this forest.
[05/25/2012 13:01:26.0245] [0] Active Directory Initialization status : 'True'.
[05/25/2012 13:01:26.0245] [0] Schema Update Required Status : 'False'.
[05/25/2012 13:01:26.0245] [0] Organization Configuration Update Required Status : 'False'.
[05/25/2012 13:01:26.0245] [0] Domain Configuration Update Required Status : 'False'.
[05/25/2012 13:01:26.0245] [0] The locally installed version is 14.1.218.15.
[05/25/2012 13:01:26.0245] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[05/25/2012 13:01:26.0386] [0] Applying default role selection state
[05/25/2012 13:01:26.0433] [0] Setup is determining what organization-level operations to perform.
[05/25/2012 13:01:26.0433] [0] The command-line option preparead has been specified.
[05/25/2012 13:01:26.0433] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareOrganization.
[05/25/2012 13:01:26.0433] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareDomain.
[05/25/2012 13:01:26.0433] [0] Because the value was specified, setup is setting the argument OrganizationName to the value domainname.
[05/25/2012 13:01:26.0433] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[05/25/2012 13:01:26.0448] [0] InstallModeDataHandler has 1 DataHandlers
[05/25/2012 13:01:26.0448] [0] RootDataHandler has 1 DataHandlers
[05/25/2012 13:01:26.0448] [0] No server roles will be installed
[05/25/2012 13:01:26.0480] [0] Validating options for the 0 requested roles
[05/25/2012 13:01:26.0511] [0] Performing Microsoft Exchange Server Prerequisite Check
[05/25/2012 13:01:26.0542] [0] Setup is determining what organization-level operations to perform.
[05/25/2012 13:01:26.0542] [0] The command-line option preparead has been specified.
[05/25/2012 13:01:26.0542] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareOrganization.
[05/25/2012 13:01:26.0542] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareDomain.
[05/25/2012 13:01:26.0542] [0] Because the value was specified, setup is setting the argument OrganizationName to the value domainname.
[05/25/2012 13:01:26.0558] [0] Setup is determining what organization-level operations to perform.
[05/25/2012 13:01:26.0558] [0] The command-line option preparead has been specified.
[05/25/2012 13:01:26.0558] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareOrganization.
[05/25/2012 13:01:26.0558] [0] Because the command-line option preparead was specified, setup is adding the argument PrepareDomain.
[05/25/2012 13:01:26.0558] [0] Because the value was specified, setup is setting the argument OrganizationName to the value domainname.
[05/25/2012 13:01:27.0526] [0] **************
[05/25/2012 13:01:27.0526] [0] Setup will run the task 'test-setuphealth'
[05/25/2012 13:01:27.0526] [1] Setup launched task 'test-setuphealth -DomainController 'DOMAINCTRL.domainname.org' -DownloadConfigurationUpdates $true -ExchangeVersion '14.1.218.15' -Roles 'Global' -ScanType 'PrecheckInstall' -SetupRoles 'Global' -PrepareDomain $null -PrepareOrganization $true -CustomerFeedbackEnabled $false'  
[05/25/2012 13:01:30.0558] [1] Active Directory session settings for 'test-SetupHealth' are: View Entire Forest: 'True', Configuration Domain Controller: 'DOMAINCTRL.domainname.org', Preferred Global Catalog: 'DOMAINCTRL.domainname.org', Preferred Domain Controllers: '{ DOMAINCTRL.domainname.org }'
[05/25/2012 13:01:30.0605] [1] Beginning processing test-setuphealth -DomainController:'DOMAINCTRL.domainname.org' -DownloadConfigurationUpdates:'True' -ExchangeVersion:'14.1.218.15' -Roles:'Global' -ScanType:'PrecheckInstall' -SetupRoles:'Global' -PrepareDomain:$null -PrepareOrganization:'True' -CustomerFeedbackEnabled:'False'
[05/25/2012 13:01:36.0761] [1] Active Directory session settings for 'Get-OrganizationConfig' are: View Entire Forest: 'True', Configuration Domain Controller: 'DOMAINCTRL.domainname.org', Preferred Global Catalog: 'DOMAINCTRL.domainname.org', Preferred Domain Controllers: '{ DOMAINCTRL.domainname.org }'
[05/25/2012 13:01:36.0777] [1] Beginning processing Get-OrganizationConfig
[05/25/2012 13:01:36.0777] [1] Searching objects of type "OrganizationConfig" with filter "$null", scope "SubTree" under the root "$null".
[05/25/2012 13:01:36.0949] [1] Previous operation run on domain controller 'DOMAINCTRL.domainname.org'.
[05/25/2012 13:01:36.0949] [1] Preparing to output objects. The maximum size of the result set is "unlimited".
[05/25/2012 13:01:37.0730] [1] Ending processing Get-OrganizationConfig
[05/25/2012 13:02:28.0497] [1] [REQUIRED] A reboot from a previous installation is pending. Please restart the system and rerun setup.
[05/25/2012 13:02:28.0653] [1] Ending processing test-setuphealth
[05/25/2012 13:02:28.0669] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[05/25/2012 13:02:28.0684] [0] End of Setup
[05/25/2012 13:02:28.0684] [0] **********************************************
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Designer | Developer | Programmer
Commented:
SouthMod: http://technet.microsoft.com/en-us/library/cc164360(v=exchg.80).aspx




Microsoft Exchange Server setup cannot continue because a restart from a previous installation or update is pending.

The Exchange Server Analyzer reads the following registry key to determine whether a system restart is required after installation or removal of a software update such as a security update, critical update, or hotfix.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

The Exchange Analyzer also checks the following registry key to determine whether a previous software update installation was not completed and the system must be restarted to finish the installation.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

The Exchange Analyzer displays an error message if one of the following conditions is true:.

    * The value of the UpdateExeVolatile registry key is anything other than 0.
    * The PendingFileRenameOperations registry key has any value.

This error indicates that a restart from a previous install or update is pending and the system must be restarted before Exchange Setup can continue.

To resolve this issue, restart the system and then run Exchange setup again.

If the Exchange Analyzer is still reporting this error after a system restart, the registry keys may contain orphaned values that must be removed. Possible values for these keys are listed below.


To remove an orphaned UpdateExeVolatile registry key value

   1.

      Open a registry editor, such as Regedit.exe or Regedt32.exe.
   2.

      Navigate to HKLM\SOFTWARE\Microsoft\Updates\
   3.

      In the right navigation pane, double-click the UpdateExeVolatile key.
   4.

      Configure the key with a value of 0
   5.

      Close Registry Editor.

To delete the orphaned PendingFileRenameOperations registry key

   1.

      Open a registry editor, such as Regedit.exe or Regedt32.exe.
   2.

      Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\
   3.

      In the right navigation pane, right-click the PendingFileRenameOperations key and select Delete.
   4.

      Close Registry Editor.

Author

Commented:
I dont have the value UpdateExeVolatile   Should I create it?  If so, is it a dword?

Author

Commented:
I just deleted PendingFileRenameOperations

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial