Archive for the ‘Windows Server 2003’ Category

Backup Exec 2010 R3 System Upgrade from Windows Server 2003 R2 to Windows Server 2008 R2

February 9, 2013 Leave a comment
  • System Notes: Backup Exec 2010 R3, Windows Server 2003 R2 Standard, Windows Server 2008 R2 Standard

Lately, I have been doing a lot of work upgrading older Windows servers from the 2003 R2 version (both 32 and 64 bit versions) to 2008 R2 (and soon probably 2012 once I get some more testing/learning time in with it).  One of the servers I had to upgrade was running Backup Exec 2010 R3, which was being used to backup other servers in a local domain to an internal RAID array.

The operating system upgrade was no problem, but moving Backup Exec and all of its data was going to be more complicated.  I primarily followed this Symantec Support article (TECH129826), while also referring to this (TECH67768).  The second article is much more comprehensive, but comes with the caveat that it is really only for moving Backup Exec between servers using the same operating system versions.

All data moved over correctly, and as far as Backup Exec was concerned, there were no differences between the two servers, from a job and history perspective.  The only problem I ran into was that I had to create a new temporary backup job and connect to each one of the remote servers that were being backed up by the existing backup jobs (via a Backup Exec Remote Agent).  This prompted Backup Exec to ask if I wanted to add each remote server to the “trusted favorites list,” which I did.  Before I figured out I needed to do this, my backup jobs were failing with authentication errors.

Additional Notes:

I was reusing the same hardware for my upgrade, and did not have to change the paths of the Backup-To-Disk folders that Backup Exec was using.  This simplified things greatly.  If you are using Backup-To-Disk folders with disk locations that are going to change, keep in mind that you will have to re-add each of them to the Backup Exec configuration, then also do a scan and an inventory on each as well before they can be used.


Converting Hyper-V guest systems to VirtualBox

August 4, 2011 4 comments
  • System Notes: Oracle VirtualBox 4.0.12, Windows Server 2003 R2 X64, Windows Server 2008 R2

My main Hyper-V server host system runs four production and three development/testing guests, with the four production and one of the development/testing systems in use 24×7.  Memory was becoming extremely tight on the host system, especially when running either of the two remaining development/testing guests along with the regular 24.×7 guests.

Since the two development/testing guest systems were really just for security patch and software upgrade testing, I decided to try and move them over to Oracle VirtualBox on my main workstation.

If you are converting a guest Windows server that is running anything earlier than Windows Server 2008 R2, you should first remove the Hyper-V Integration Services from the guest, to prevent any BSOD startup problems after you move the guest over to VirtualBox.

When setting up a Windows Server 2008 R2 guest system using an existing VHD file for the primary hard disk, you must make a change in the VirtualBox Settings.  The VHD will be attached as a SATA drive by default, and you will get a BSOD if you try to boot it this way.  You need to remove the VHD file from the SATA controller and re-add it as an IDE hard drive.  See this link for a specific discussion of this problem.  See my previous blog entry Switching from IDE to SATA controller types for older Windows guests in VirtualBox for specific details on working with IDE and SATA virtual drive files.

Additional Notes:

Just a bonus quick reference note for VirtualBox:  you can use Ctrl-Arrow to move systems up and down the list on the main Oracle VM VirtualBox Manager window.  Just highlight the system you want to reorder and press Ctrl-Up or Ctrl-Down.

Switching from IDE to SATA controller types for older Windows guests in VirtualBox

May 7, 2011 1 comment
  • System Notes: Oracle VirtualBox 4.0.6, Windows XP, Windows Server 2003

I have been unable to find a decent source of material online that covers how exactly to switch from using IDE drive controllers to SATA drive controllers for older Windows guest systems under VirtualBox.  After much experimenting on my own guest systems, this is the way I have found that works:

  1. Create the guest system as you normally would, using the default IDE controller and a new VDI file for the hard drive.
  2. Install the operating system and get it up and running.
  3. Download the most recent Intel Rapid Storage Technology drivers from the Intel web site.  Use the one appropriate for your operating system, whether 32 bit or 64 bit (Intel changes things regularly, but the most recent link I have for them is here).
  4. Make sure the new guest system is shut down.  Add a SATA drive controller to the Storage entry under the Settings for the new guest system in VirtualBox.
  5. Restart the new guest system, and do not install any drivers when prompted by Windows.  Run the installer for the Intel Rapid Storage Technology drivers, and shut down the system after install.
  6. Under the Storage entry for the Settings of the new guest system in VirtualBox, remove the existing VDI hard drive file from the IDE storage controller, and re-attach it as a hard drive under the SATA storage controller.
  7. Restart the new guest system.

Additional Notes:

I verified this method works with Windows XP (32 bit), Windows Server 2003 (32 bit), and Windows Server 2003 R2 (both 32 and 64 bit) guest systems.  An Intel ICH8M-E/M controller should be indicated during the install of the Intel Rapid Storage Technology drivers.  I have not retested performance on my systems after this conversion, but I have read elsewhere that it can make a big difference, especially to lower the resource draw on the host system itself.

Hyper-V, Windows 2003 Server, Event ID 1054

November 10, 2008 Leave a comment
  • System Notes: Dell PowerEdge 2950, Windows 2008 Server Standard x64

As I have continued my usage of Hyper-V on Windows 2008 Server, one of the hosted systems continued to receive the following error in the Application Log: “Event Type: Error, Event Source: Userenv, Event Category: None, Event ID: 1054, Description: Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred.). Group Policy processing aborted.” See the posting on 8/15/2008 for some additional details and a previous discussion of this.

It turns out that this only occurs on a hosted system configured for multiple processors and running Windows 2003 Server (same with R2). I verified this across my hosted systems. The solution is to use the /usepmtimer option on the system startup command in the BOOT.INI file. A discussion of this problem can be found here, and this link is to the Microsoft Help and Support article on the /usepmtimer option.