09-24-2018, 06:31 PM
Hi Paul,
All depends on the way the system is built, as you stated you use non-domain joined golden images. For VMWare View this is not a requirement. The golden image can be a domain joined system, just put it in a OU with GPO blocking enabled to prevent the annoying lockdown gpo's. Citrix is a bit more picky on this subject, so it would require some testing how it works out (but should work as well...)
The second option works even with your approach. This as the user initiates the install, and the membership in the domain is not required.
However this would be a 'unmanaged client' configuration, with it's own problems like being able to access the installscripts share, permissions to install the software or apply settings on the system.
But even without domain you would be able to identify the golden image (it does have a specific computer name, a local adminuser is logged in, …). You could use this to trigger the installs. Small difference: this would be USER LOGIN actions, not computer startup triggers. An unmanaged system does not have computer startup events. Computer startup actually is the startup of the OSD service, which might be/is not available on unmanaged systems.
Good luck,
Michael Baars
All depends on the way the system is built, as you stated you use non-domain joined golden images. For VMWare View this is not a requirement. The golden image can be a domain joined system, just put it in a OU with GPO blocking enabled to prevent the annoying lockdown gpo's. Citrix is a bit more picky on this subject, so it would require some testing how it works out (but should work as well...)
The second option works even with your approach. This as the user initiates the install, and the membership in the domain is not required.
However this would be a 'unmanaged client' configuration, with it's own problems like being able to access the installscripts share, permissions to install the software or apply settings on the system.
But even without domain you would be able to identify the golden image (it does have a specific computer name, a local adminuser is logged in, …). You could use this to trigger the installs. Small difference: this would be USER LOGIN actions, not computer startup triggers. An unmanaged system does not have computer startup events. Computer startup actually is the startup of the OSD service, which might be/is not available on unmanaged systems.
Good luck,
Michael Baars