Microsoft Windows Active Directory Errors

Disaster Recovery Leave a comment

When you’re buying a new desktop or server, it’s not uncommon to receive the device with a copy of Microsoft Windows already installed. This convenience provided by the manufacture is designed to alleviate the microsoft windows active directory problems disaster recoveryadditional steps for the customer of having to purchase and install Windows in order to use their new device. These copies of Microsoft Windows that have been installed on machines prior to shipment are called OEM copies, and seem like a benefit to have – until you have a hardware melt down.

There’s an economic benefit of receiving a unit with the software preinstalled, but the downside is that you cannot move it to any other server or environment. The MAC address for the computer is forever tied to the specific copy of Windows, and designed as such so that software piracy can be kept at bay. However if you have a legitimate need to reinstall your copy of Windows on another machine, you’ll receive error messages and it simply will not work.

Dealing with Microsoft Windows is significant. Any Windows network of any size will have an active directory which is the repository of user names, user permissions, passwords, permissions and connections that make the network run. It’s tricky to back up and restore the active directory properly because its very sensitive to changes in configuration, and that sensitivity prompts error messages when the restore process begins. There’s a pretty big chance the active directory won’t start in most system restores.

Not only are those “active directory” messages annoying, they can be a detriment to business in downtime and loss productivity. Consider the common disaster recovery strategy to move a full-blown server image, including that OEM copy of Windows. The problem occurs when you have to restore the backup to another machine because Windows won’t recognize the new MAC address. Its alarm bells go off, paired with a warning message that says you have to call Microsoft… and that’s when the torture begins.

You can avoid calling Microsoft and try calling the machine manufacturer instead, but they’ll ask you to retrieve the original activation codes that came with the hardware or server, which can be a significant challenge in the event of a real disaster. What if those activation codes just blew across Kansas in a tornado?

GDV avoids these errors entirely by using a separate and proprietary tool that tracks any changes to hardware or network configuration changes. GDV is alerted to any changes within our client’s active directories, allowing us to adjust and restore to the right environment with a significantly greater likelihood of success. Our extensive experience restoring these active directories and professional contacts within Microsoft means we can cut through the red tape to get your system restored ASAP. GDV provides this service for our customers on a routine basis and we even test it on a quarterly basis. We are confident that in the event of a real disaster recovery scenario, we can have your system restored in short order because we’ve already done it during our test cycles.

Leave a Reply