locked
VM deployed from template loses test agent login information RRS feed

  • Question

  • We've created a VM with the test agent installed. We configured the test agent to login in using the local admin account (not part of a domain). We did not give it a machine name, just the user name and the password. We checked the 'Log on automatically' and did not have it register with test controller since this should be done automatically at time of deployment.

    We then created a template from this VM. When we create an environment using this template, the machine comes up without the test agent logged in. We have to manually run the configuration tool again and add the local login information again.

    How do we automate this so that every time we deploy a VM from a template we don't have to run the configuration tool to add the login information? This should be done automatically.

    Brandon

    Tuesday, March 22, 2011 6:56 PM

Answers

  • Hi,

    We definitely cannot make sysprep not cleanup the autologon information.

    Have you tried to use the sysprep.inf to logon with the admin creds. Then using the runonce command list, you can launch the config tool and reboot the machine.

    Allen Mathias

    • Marked as answer by Brandon Hoppe Monday, April 4, 2011 7:28 PM
    Thursday, March 31, 2011 3:59 AM
  • Yes we do. 

    Examples: 

    TestAgentConfig.exe configureAsProcess /userName:domain\user /password:userPassword /enableAutoLogon:yes /testController:"MyController:6901" /port:6910

    TestAgentConfig.exe configureAsService /userName:domain\user /password:userPassword /port:6910 /testController:"MyController:6901"

    Allen Mathias

    • Marked as answer by Brandon Hoppe Monday, April 4, 2011 7:28 PM
    Friday, April 1, 2011 4:10 AM

All replies

  • Hi Brandon,

    I am guessing you selected the "store as template" check box during creation. In that case the VM is generalized and the logon information is lost leading to this issue. A workaround would be to create the template via SCVMM and specify a autologon via the sysprep.inf file to the template (see syspre.inf details)

    Thanks

    Allen Mathias

    Wednesday, March 23, 2011 1:58 PM
  • Hi Brandon,

    I am guessing you selected the "store as template" check box during creation. In that case the VM is generalized and the logon information is lost leading to this issue. A workaround would be to create the template via SCVMM and specify a autologon via the sysprep.inf file to the template (see syspre.inf details)

    Thanks

    Allen Mathias

    This VM is created using SCVMM and not thru Lab Manager.

    I believe with Autologon it needs to be a domain account. This VM is deployed as part of a work group and not as a domain member. The account before making the VM a template is <machine name>/<user>. When the new VM is deployed from a template, the old machine name is no longer valid but the user account is the same.

    Wednesday, March 23, 2011 10:32 PM
  • Hi Brandon

    If you have created it using SCVMM and you are getting a new machine name each time then isnt it sysprepped?

    You can use a non-domain account for autologon. The defaultdomainname there would be the machinename (or you can use "." as well it would help if you dont know the machine name).

    But if you sysprep the machine these keys will be cleared out.

    Thanks

    Allen Mathias

    Friday, March 25, 2011 11:25 AM
  • Hi Brandon

    If you have created it using SCVMM and you are getting a new machine name each time then isnt it sysprepped?

    Yes, it is getting sysprepped.

    You can use a non-domain account for autologon. The defaultdomainname there would be the machinename (or you can use "." as well it would help if you dont know the machine name).

    But if you sysprep the machine these keys will be cleared out.

    Well that's the point. By syspreppin the machine, the login is cleared out. We need it so that when a VM is added to an environment from a machine template, the VM is created with the test agent already configured to connect to the test controller (which requires the login information).

     


    Tuesday, March 29, 2011 9:37 PM
  • Hi,

    We definitely cannot make sysprep not cleanup the autologon information.

    Have you tried to use the sysprep.inf to logon with the admin creds. Then using the runonce command list, you can launch the config tool and reboot the machine.

    Allen Mathias

    • Marked as answer by Brandon Hoppe Monday, April 4, 2011 7:28 PM
    Thursday, March 31, 2011 3:59 AM
  • Hi,

    We definitely cannot make sysprep not cleanup the autologon information.

    Have you tried to use the sysprep.inf to logon with the admin creds. Then using the runonce command list, you can launch the config tool and reboot the machine.

    Allen Mathias

    Does the test agent config tool have a command line driven mode where I can update the user name, password, options, etc?

     

    Thursday, March 31, 2011 1:02 PM
  • Yes we do. 

    Examples: 

    TestAgentConfig.exe configureAsProcess /userName:domain\user /password:userPassword /enableAutoLogon:yes /testController:"MyController:6901" /port:6910

    TestAgentConfig.exe configureAsService /userName:domain\user /password:userPassword /port:6910 /testController:"MyController:6901"

    Allen Mathias

    • Marked as answer by Brandon Hoppe Monday, April 4, 2011 7:28 PM
    Friday, April 1, 2011 4:10 AM
  • Yes we do. 

    Examples: 

     

    TestAgentConfig.exe configureAsProcess /userName:domain\user /password:userPassword /enableAutoLogon:yes /testController:"MyController:6901" /port:6910

     

     

    TestAgentConfig.exe configureAsService /userName:domain\user /password:userPassword /port:6910 /testController:"MyController:6901"

     

    Allen Mathias

    Allen,

    Yes, this works, BUT....

    Now the password is visible to anyone. Since this command would be in the GUIRunOnce list, anyone can go to the library and see the plain text password.

    So there needs to be something provided by the Lab Management system to auto logon the test agent without storing a plain text password in sight of anyone.

    Brandon

    Tuesday, April 19, 2011 9:00 PM
  • Hi Brandon,

    I agree that this will be an issue. This is purely a workaround so there will be somethings that give. For now we do not have an in-product feature that solves your problem. I will pass on your feedback to the relevant folks on this.

    Thank you

    Allen Mathias

     

    Thursday, April 28, 2011 3:39 AM