Recently arrived at a new company and trying to test a disaster recovery of Windows Server 2003 primary fsmo role holder/dns which has exchange 2003 installed (it is not a SBS box) scenario with no access to existing site and getting the correct media/updates in the right order in place to save time should the s**t hit the fan. Dell Hardware is similar to production.
The order I am thinking about...
1) Configure RAID to be the same
2) Install Windows Server 2003
3) Install Windows Server 2003 SP2
4) Configure same NETBIOS and IP address
5) Create AD Domain as same name and install DNS
6) Install Exchange 2003
7) Install Exchange 2003 SP2
8) Install ARCServe 11.5 and apply service pack
9) restart server in NTDSUTIL mode and perform Authoritative Restore from ARCServe
10) Restart server and Restore Exchange Database.
11) Restore userdata
Does this sound like a workable plan or please point to obvious missing entries or correct the order.
More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease.
The following video show how to bind OSX Mavericks to …