prophecy408's profile - activity

ok, so I found a work around to this. Basically I would stop the VM mid-script login to the accounts I added, and then start up the logon.ps1 script again. Spawn up the image, and I was able to RDP into the extra users I created.

So we set the script to create 2 addition user aside from the Administrator account. So when we spawn the instance in Openstack there are 3 total users. I know we have to retrieve the password for the admin account, but we hardcoded a password on two addition Users that we created.

After we spawn it in the openstack enviroment. It looks like if we generate the keypair for the admin account we can RDP with that account, but we would like the users that we created to be able to RDP after spawning so we can avoid generating a keypair every time we spawn the instance.

Yeah I'm using https://github.com/cloudbase/windows-openstack-imaging-tools to generate the image.

Yeah I'm using https://github.com/cloudbase/windows-... to generate the image.

Once the installation of a Windows 10 image is installed into the machine and we try to RDP into the machine we always get the error "The credentials are correct, but the host cannot log you on for another reason. Please check if your password has expired or contact your system administrator for assistance" We tried hardcoding the password into the user and it still doesn't work. It looks like RDP starts to work after we login to the machine locally. How do we set this up so that the image doesn't require the first logon and be able to RDP once the image is installed.

btw, thanks for your help. Appreciate your answers.

That seems fair, but the tool seem to process everything. I would normally configure the unattendfile before starting it, once it starts it'll install windows and convert to a qcow2. So How can I add the scripts?There's no Wiki on the tool https://github.com/cloudbase/windows-openstack-imaging-tools

So we basically we have to choose between the Admin account or the Administrator account and we can't have both activate during the first boot?

administrator account installed into the image during the first install. So how can I have it activated the administrator account when creating the image through window-imaging-tool?

So the Admin account is the account that's currently syncing password with NOVA and that account shows up perfectly fine, i'm trying to activate the hidden Administrator account which will activate once i login to the ADMIN account and run the net user command. I want to have both the Admin and the

Hey Guys,

I tried many different ways to try to activate the Administrator account, but can't see to get the account to stay active after sysprep once the image is installed the account is deactivated. I tried editing the unattend.xml to run the command net user administrator /active:yes. but no luck in have that account active in the image once sysprep is done. Any idea on whats the proper want to enable the admin account using the windows-openstack-imaging-tools

https://github.com/cloudbase/windows-...