Automatic configuration during Windows provisioning

[kurotan]

About Automatic Settings During Windows Provisioning

I created a Windows virtual image using the following URL as a reference:
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006560en_us&docLocale=en_US&page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html
Note that generalization was enabled when running sysprep.

I understand that when provisioning Windows, it's possible to set the hostname and automatically join the domain, but errors are occurring when Windows starts.
(Unexpected restarts, etc.)

Also, the log shows connection errors /Authentication error with Winrm.

My environment is as follows:

- I set my Windows password in the VME Manager provisioning settings.

- I set my existing AD in the "Infrastructure Network Domain" settings.

- Provisioned VMs are assigned IP addresses via DHCP.
- The VMs and VME managers being provisioned can connect to the domain's AD server.
- The VMs and VME managers being provisioned can resolve domain names.

I also performed the following additional configuration before sysprep, but the situation remains unchanged. (PowerShell)
enable-psremoting
Set-Item WSMan:\localhost\Client\TrustedHosts -Value *

It seemed to work fine in 8.0.7, so are you experiencing any issues?

[kurotan]

I've made some progress, so I'd like to share it with you.

I created a Windows image using the following steps:

1.
VM provisioning
- Clean install of Windows
- Install QEMU agent and drivers
- Eject all CD-ROMs
- Disable firewall
- Enable RDP
- Windows Update (up to the latest version)
- winrm quickconfig (Command Prompt)
- Run the following in PowerShell (to avoid sysprep errors)
Import-Module Appx
Import-Module Dism
Get-AppxPackage -AllUsers | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
- sysprep (generalize option enabled)

2.
Imported as an image

3.
I configured the virtual image as described in the manual.

4.
When I provisioned a VM using the virtual image,
it started up with the hostname changed.

Next, I'd like to verify the automated domain joining.

[dya]

This is very helpful. Thank you for sharing.

As for "winrm quickconfig," I didn't run it because the WinRM service was running.

However, when I provisioned the VM, it started with the hostname changed.

I was wondering if not running "winrm quickconfig" would cause any problems. Do you know?

*This is a machine translation, so I apologize if it's difficult to understand.

[kurotan]

I didn't run that command at first, but the hostname did change sometimes.

It seems to make changes to the registry to enable remote management, so I think it's a good idea to run it.
If you need to perform remote management or operation for other products, similar instructions will be found in the manual.

[kurotan]

I enabled the virtual image's domain auto-joining feature.
When I look at the domain controller, I can see that the computer has been added, so it appears to have joined the domain.

However!
The hostname change was not reflected.
The domain controller has a hostname registered, which is probably an automatically named hostname assigned during deployment.
As a result, it did not function properly as a domain member.

Is there any way to fix this?