Why sysprep? The whole point of cloneing the parent image is to make sure the sid doesn't change, which is what sysprep does.
I clone it so as far as the software and configuration and updates are concerned the Provisioning workstation is identical to the Parent.. but it is a separate VM so I just run Sysprep and give it a new name.
This just something I've always done in windows 7 world as part of my provisioning process.
Try cloning it directly, you can change the name without syspreping it. If its added to the domain just remove it and add it as new object
Ok going though this process has enlightened me to what I think may be issue.
My parent is not domain joined but the pool is however in order to provision applications i cannot find my provisioning workstation unless I join it to the domain... but in your reponce you said IF its domain joined... how do I provision on a non domain joined workstation?
as I'm thinking they need to be the same.
if this is not possible I may have to rethink my Parent and join it to the domain my windows 7 one has always been domain joined but I was led to believe with the Creating an Optimized windows image for VMware horzon guide I was using for windows 10 that I wasn't supposed to do that.
I suggest not joining the parent, the cloning process does this, and only join the provisioning machines to the domain. If you must once you clone the provisioning machine, remove it from the domain and read it as the new name, then read the parent to the domain. Technically there is a setting to allow non domain entities to use appvolumes but the best practice is to join te provisioning machines.
Well that is the state they are in... the parent is not domain joined but the Provisioning workstation is... I was hoping that would be the issue but if this is how it should be then.
The new Provisioning workstation is all set up but just NO Sysprep this time only renamed
I will create a blank appstack in the morning and we will see how it goes.
thank you for all your help
So after yesterday I was able to create a new appstack that was blank with a new Clone of the parent and same issue... office does the set up now again... if I remove the appstack office is happy
its even a bit worse as it says you have to reboot now after the config changes and well instant clones just makes that a round and round process and if you hit NO it just does the config set up again... so totally
There must be something in the template that is messing something up... I put in a support call with VMware
thank you for your help anyway
1 person found this helpful
I just learned that Appvols 2.16 doesn't support Windows 10 1903 I need to update to at least 2.17
I made a comment on this thread the other day that may help you with this issue: Visio 2016 - Keeps running Office 2016 configuration
Basically you need to add several registry keys to the HKCU hive, so it would need to be scripted or done with a profile management tool at logon:
reg add HKCU\Software\Microsoft\Office\16.0\Word\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Excel\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Access\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Powerpoint\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Outlook\Options /v NoReReg /t REG_DWORD /d 1