Skip to main content

Rebuild an Exchange 2007 server after a crash

 Rebuild an Exchange 2007 server after a crash

If Windows wasn't damaged during the crash, it's best to leave the operating system alone. This will save you work, and will also help to preserve some of the things that are unique to that server.
For example, client access servers almost always have SSL certificates installed. These certificates are stored locally on the server and they are not a part of Exchange. Because of this, certificates will have to be reissued unless you're able to preserve the operating system.

If you're rebuilding a damaged Exchange 2007 server, the first thing you need to do is return Windows to a functional state. After reinstalling Windows you must make sure that your server's disk is configured identically to how it was on the failed server.
You also need to install all of Exchange Server's required components, just as you did when you initially installed Exchange 2007. I also recommend that you apply the same set of patches to the OS that were in place before the crash.

After you've installed and configured Windows, you need to attach it to the domain. And it's critical that you do this correctly. Your Exchange Server configuration is tied to the computer account, which is connected to your old server. Before connecting your server to Active Directory, you must reset the computer account.

To reset the computer account, open Active Directory Users and Computers and select the Computers container. Next, right-click on the name of the failed server and select the Reset Account command. Finally, assign your Exchange Server the same name as the failed server and then join the domain as you normally would. Do not delete the old server's computer account. If you do, it will be impossible to rebuild Exchange Server.
After you've properly configured Windows, it's time to rebuild Exchange Server 2007. To begin, insert your Exchange installation media and run the following command:

Setup.exe /M:RecoverServer
Be sure that your installation media includes the same service pack that was previously installed.
When you execute this command, Setup will:

  1. Check the prerequisite to ensure that all necessary components are installed
  2. Copy Exchange binaries to the server
  3. Use Active Directory to configure the server.

When I first attempted the recovery process, it would not complete because my edge synchronization had broken. A TechNet article advised me to use the Exchange Management Shell (EMS) to remove the edge subscription, then to manually reestablish it once the server was functioning.
At first I was discouraged because the crash had destroyed the Exchange Management Console and Exchange Management Shell. However, I was pleasantly surprised to find that the management tools had been reinstalled and returned to a functional state when I copied the Exchange binaries. This made it easy to use the
command to remove my edge subscription. After that, I was able to rerun Setup and rebuild my server.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664