3
I have a Windows Server 2012 in a XenCenter virtual machine. The image is prepared as an IIS server and AD domain controller. The domain contains that single server only, but the AD will be synchronized with O365 directory and used by IIS for authentication.
I now want to deploy that image as an Azure VM, so the machine had to be generalized.
I executed Sysprep /generalize /shutdown /oobe
and after that process finished, I made a snapshot and tried whether the machine would be starting up in Citrix again, and whether it would give me chance to specify domain and user and password and all that stuff.
The error I get on bootup of the generalized system is "Windows Setup could not configure Windows to run on this computer's hardware" - although that Windows is running on exactly the same "hardware" as before.
As far as I now understand from what I read about that error, sysprep does not support generalizing domain computers, so it will try to remove that computer from the domain, which should - to my best knowledge - fail for the domain controller, and I guess no one has ever tried to generalize an (better: the) AD domain controller. Is this correct, and how can I check whether this is causing my issue?
Another possibility are issues with drivers, since "The main cause is due to incompatible driver". The only 3rd party drivers that come to mind are the Citrix drivers which I had to install at some point so I could use the mouse in the Citrix console. I only remember that it was a long and bumpy road to get them installed back then, without a mouse, so I'd like to postpone that test a bit.
Do you have any experiences to share about generalizing a Windows image with said error message, generalizing a Windows image with Citrix drivers or generalizing the image of an AD domain controller?