Problems moving virtual machines with startup credentials

Problems moving virtual machines with startup credentials

  • Comments 3

Under Virtual Server 2005 R2 you need to provide a virtual machine with specific user credentials if you want to configure the virtual machine to start up automatically when the physical computer is launched.  You need to do this because Virtual Server needs to have a user context under which to access resources like .VHDs.

When you enter these credentials - Virtual Server stores this information in a secure credential store on the physical computer.  The virtual machine configuration then just holds a pointer to the information in the secure credential store.

Now the problem that you can encounter is that if you configure a virtual machine to launch with specific user credentials - and then move it to another physical computer - the virtual machine will fail to launch.  The reason why this happens is because the new physical computer does not have the stored credentials for the user account specified in the virtual machine configuration.

The only way to get around this is to re-enter the user credentials after moving the virtual machine.

Cheers,
Ben

Leave a Comment
  • Please add 6 and 8 and type the answer here:
  • Post
  • Ben, could you also confirm my problem with running guest's under an account?
    when i set the user account for a guest, the guest will start ok. when i restart the virtual host, the guest won't start because the credentials are wrong. i then set the same username and the guest will start ok after a reboot of the host. the guest stays on the same host.

    greetings Jeroen
    jeroen.polman@gmail.com
  • I have the same problem. the guests were built from an old image...but the username and password were set for the second time. But everytime the host reboots, the guests DONOT come back up and complain of the invalid username/password. but if i reenter the password again everything works. What am I missing?
  • Hi Guys -

    I do not know what is going on there - and would recommend that you contact Microsoft product support.

    Cheers,
    Ben
Page 1 of 1 (3 items)