Amvean’s recent project was for a System Upgrade which included network cabling work, server installations, data migrations and demoting of exciting windows 2003 server domain controllers.
Here’s what the setup of the business looked previously:
It was a daunting task since the business couldn’t afford to experience alot of downtime. As it is said “time is money”!
First we cleaned up the cabling. Removing what wasn’t needed, retesting existing cables and phone equipment for issues and rewiring and running cables for the new servers and other hardware.
After, we proceeded to mount the server rack unit, attached two HP Proliant DL360 servers, Network-Grade Rackmount PDU, NAS drive, switch and firewall.
The servers were installed with 2x 1TB in RAID 1 for the Operating System and 2x 4TB drives in RAID 1 for application data and User directory file access.
Active Directory FSMO Roles Migration
For those who don’t know, Active Directory has five special roles which are vital for the smooth running of AD as a multimaster system. Some functions of AD require there is an authoritative master to which all Domain Controllers can refer to. These roles are installed automatically and there is normally very little reason to move them, however since we are de-commissioning the old existing Domain Controllers, which were installed with Windows Server Standard 2003, the industry standard procedure is to initiate the transfer of those existing roles to the new servers which are running Windows Server 2012 R2. For reference, a guide to Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2 can be found here. All this was done during off-peak business hours. Next morning, they were up and running on the new servers using their active directory accounts without the employees ever noticing that there has been a changed over. What they did notice was that their shared networked files were mapped to a different location.
Decomissioning previous Windows 2003 Domain Controller
To decommission an Active Directory Domain Controller (Windows Server 2003/2008) is a fairly straightforward task so long as you make sure nothing is relying on that server specifically.
If you have more than just the DC that you are preparing the demote, then you have nothing else to do as the DCPROMO steps will remove it automatically. You need to make sure that FSMO roles are not present on the server you are demoting by issuing the following command: c:\windows\system32\netdom query fsmo
To demote a domain controller
- On a domain controller, click Start, and then click Run.
- In Open (or Run), type dcpromo to open the Active Directory Installation Wizard, and then click Next.
- On the Remove Active Directory page, click Next, and then continue to follow the wizard.
As with any IT business deployment projects, testing and monitoring of all equipment and user input and configurations is paramount to a successful installation. We at Amvean take great pride in our work and strive for total customer satisfaction.
At the end, this is the final network, hardware installation of the project.