Switching credential during provisioning for Windows servers

[wilber82]

My image configuration process has 3 steps:

1. Basic configure OS via PowerShell script by local 'Administrator' account. (For example, set timezone)
2. Join the VM to domain by PowerShell script.
3. Install a software via PowerShell script by domain account.
4. Leave domain via PowerShell script.
5. Continue configure OS via PowerShell by local 'Administrator' account.

As you can see. It needs domain account to connect the server.
Looks like there is no way to switching credential temporarily during provisioning.

I tried to give "elevated_user" and "elevated_password" in PowerShell block. No lucky.

Even I don't give any additional keys, the audit log shows Packer tries to login the machine by '[email protected]" but not local 'administrator' account. It always failed as I'm not domain administrator.

Is this a bug, or?

My builders block is correct. I'm using winrm as communicator. it works fine for any VM without the need to switch account.

[SwampDragons]

You're right. Currently there is no way to change the communicator credentials halfway through a build.

[allaboutopensource]

you can create a powershell script and inside the script you can mention the new admin credentials so that those commands in the scripts will run using the admin credentials and not the local admin. hope this helps.

[techtryhard11]

@allaboutopensource @SwampDragons Do you know of a way to run a powershell script with packer during the build process? I have only seen the use of custom_script and standard ssh/winrm communicators. I am having some trouble getting the custom_script to execute as suggested here: https://developer.hashicorp.com/packer/integrations/hashicorp/azure/latest/components/builder/arm under custom_script. Do you have any suggestions?