Fix: Incompatible device specified for device ‘0’ when cold migrating VMware guest

I received the following error message when using the vSphere Client to cold migrate a VMware guest running on ESX 3.0.2 to a new datastore : 

Incompatible device specified for device ‘0’
The migration failed at 99%.  VMware KB 9105247 suggested the problem was an attached .ISO image file.  No .ISOs were showing as attached in the VI client, so I edited the guest’s .vmx file.  I found the following in the .vmx file:
ide0:0.fileName = “/usr/lib/vmware/isoimages/windows.iso”
So although the VI client did not indicate there was an .ISO file attached to the CD-ROM, the guest thought there was one.  I removed the CD-ROM from the guest’s configuration and re-added it, and the .vmx file was changed to the following:
ide0:0.deviceType = “cdrom-raw”
I then started the storage migration once more, and it completed successfully.

Fix for path not found (8209) when loading Groupwise POA

My error was path not found (8209) \\nw1\vol1\logs\testpo when trying to load a POA on a SLES 10 SP1 Groupwise 7.0.3 server.  I had just migrated the POA named testpo from Netware to SLES manually rather than use the Groupwise Server Migration Utility since I wanted to have a good understanding what had to happen behind the scenes before I tried migrating my live system.

The path to \\nw1\vol1\logs\testpo was the POA log file location on the old Netware Groupwise server.  I knew that I needed to fix that path, but couldn’t find where Groupwise was pulling it from.  Things I tried to resolve the problem included:

  • Verified /log path to location reported was not specified in testpo.poa file on the SLES server
  • Verified in ConsoleOne that the POA object for testpo did not have the Netware path in question specified in the Groupwise > Log Settings > Log File Path
  • Deleted and recreated POA object for testpo
  • Deleted testpo.poa file and re-ran Groupwise install from SLES box, specifying post office named testpo and path to testpo database on the SLES server
  • Verified path to old Software Distribution Directory on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Software Directory Management 
  • Verified path to old restore area on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Restore Area Management 
  • Used gnome-search-toolto search the entire SLES server for files containing the text \\nw1\vol1\logs\testpo
    no files containing that text were found on the SLES server

The Fix ended up being rebuilding the testpo post office.  To do this:

ConsoleOne > Tools > Groupwise Utilities > System Maintenance > Rebuild Database

Interesting technical links for Monday June 30

While I was mindlessly surfing I came across a few interesting links I thought I’d share.

Justin Ho posted about the D-Link router emulator pages and Blue Lock.

The D-Link router emulator pages show you what the configuration pages look like for various models of D-Link devices, which makes it nice when remotely supporting friends and family and you can’t see what they see.

Blue Lock is an open source program that locks your Windows PC if a particular Bluetooth device is not detected. For example, if you register your Bluetooth mobile phone with the program but then move away from your desk, the program will detect your phone is out of range and automatically lock your system, requiring the password to be entered to reactivate the system. Full Delphi source code is provided.

Dan Cunningham has released version 1.01 of his Workstation Migration Assistant program. As Dan puts it,

“The Workstation Migration Assistant is a visual wrapper for Microsoft’s User State Migration Tool, designed to simplify the capture / restore process for your end-users, and at the same time being highly configurable so that it can be customised to suit your organisations needs. Some of it’s features include:

  • Migrate via a pre-defined network storage location, external USB drive, or user-specified location. USB drive detection is automatic, and you can decide whether drives below a certain size are ignored (ie, memory sticks)
  • Optional Hard Disk Health Check will run a CHKDSK prior to capture and fix errors if any are found
  • Optional Encryption using a pre-defined company encryption key, or per-user customised encryption (for highly sensitive data that can’t be stored on a server without being encrypted)
  • Use different configurations for “XP Only” (XP > XP) migrations via Standard (XP > Vista and Vista > Vista)
  • Automatically run pre and post-capture / restore scripts and programs (very useful to further configure machine settings)
  • Migrate domain only accounts, or domain and local
  • Automatically exclude certain domain or local accounts from the migration
  • Automatically send log files to an e-mail address via SMTP after the migration
  • On-screen status during every stage of the migration, including ETA
  • Option to limit migrations to a certain size, i.e. if over 20GB of data to backup, then fail and inform user. This is also overridable
  • Automatic checks for USMT installation and optional download
  • Command-line automation
  • Super-pretty UI “

Cameron Fuller writes about his experience with Adding the first Windows 2008 DC running Server Core to a Windows 2003 Domain. I’ve previously used his data posted in Active Directory Stress Testing and Memory as a basis for sizing my virtual domain controller’s memory allocation.

The Sean Blog discusses diagnosing Windows crashes (blue screens), and mentions the Crash Analyzer Wizard. I’ve played with this tool before, since we get it with our Microsoft Volume License agreement. The wizard is a component of the Microsoft Diagnostics and Recovery Toolset, which is available from Microsoft as a 30 day evaluation.

Howto: Extend the Grace Period for having two SBS Servers in the Same Domain

When migrating your Windows Small Business Server 2003 domain to a new machine, there is a seven day grace period where the two SBS servers can co-exist as members of the same domain. This is because the license agreement for SBS enforces a limitation that permits the presence of only one Windows SBS server in the domain.

Microsoft has released an update that extends the grace period from seven to 21 days.

For more details, see KB 943494.

Posted in SBS. Tags: , , . 2 Comments »