Skip to main content

How Swing Migration Works for exchange server Just for Egypt Engineers

 How Swing Migration Works

Swing Migration is a process to accomplish either a version upgrade or server replacement migration without giving up the domain, or the server name, or the Exchange Information Store in the process, all while working offline with an open time line.
You get a clean server installation retains all the critical Active Directory domain information and predictable results. It's the most transparent method for bringing all versions of SBS, NT4, Win2K, or Win2003-based domains as upgrades to SBS 2003. This methodology works for non-SBS projects as well. You can learn a process flexible enough for most any project in any production environment regardless of the hardware changes involved.
Swing Migration solves technical issues, business interruption, and scheduling challenges. Construction is performed almost entirely offline, with an open-ended timeline. No repairs are needed if a problem halts the upgrade. Swing migration minimizes the preparations and changes to the production server, and that server remains in operation during the upgrade. Only during the final transition do you move the data and Exchange Stores to the fully constructed new server, which you then slide into service to replace the previous server. The domain accounts remain unchanged, you can keep the server name, and alternate paths in the process use the previous hardware. These upgrades have predictable outcomes; they are safe even for entry level technicians.
What is shown below is a diagram of the process, and further below is a simple outline of the process.

  • [TempDC] Clean install a Windows 2003 Server (using SBS media) as a workgroup server only.
  • Manually join it to the existing SBS domain, preparing this server as a Temp DC.
  • Install DNS, perform DCpromo and designate as a Global Catalog Server.
  • Replicate DNS and AD then shutdown and disconnect
  • Seize all FSMO roles
  • Purge the Active Directory metabase and DNS of all previous Domain Controllers, Exchange and DNS Server references
  • [FinalDC] Clean install Windows 2003 Server just as before, reuse the original SBS Server name and IP. This server will look just like the previous SBS for name, IP, AD, and UNC/URL paths.
  • Install DNS, perform DCpromo, designate as Global Catalog Server.
  • Replicate DNS and AD.
  • Seize all FSMO roles, purge the Temp DC from DNS and AD
  • Finish normal SBS Setup using this Server
  • Complete the balance of migration of Exchange, all Data, and shared resources
  • If desired, perform a migration of the intact Exchange Information Store as a direct mount of the previous Information Store as if it were an offline restore. Reconnect mailboxes.
  • Perform a direct substitution of the new server for the old SBS
  • Deploy Applications as normal for SBS.


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