Clone PC and change product key
-
@x23piracy said in Clone PC and change product key:
for example ESET’s Agent is creating a unique key, even if you sysprep it’s still the same
FWIW: Its best to install these applications post image deployment with Snapins or other deployment tools.
-
@george1421 said in Clone PC and change product key:
@andre_x Then use a fog snapin to deploy a cmd file to the target computer. The only issue here is that you must have a single key for all Office installs.
Isn’t there a way to pass a field (for example “Other Tag #1”) to a script passed to the host?
On a side note, even if you have custom software installed, you can sysprep the image to make the image generic for all hardwares. Its up to you how you want to manage this, just don’t let preinstalled applications be the reason for not sysprepping a system. The only risk of preinstalling applications are the ones that create a unique GUID upon install (like most AV software). If you install these first then every cloned machine will have the same application GUID which will probably confuse the management console for the software.
All the software installed are specific for our field (AV rental) and without licensing, so for this I don’t have problems.
Well, I have to study the sysprep that I’ve always ignored. How about the drivers? How can he find them for a new hardware? -
@andre_x said in Clone PC and change product key:
Isn’t there a way to pass a field (for example “Other Tag #1”) to a script passed to the host?
There is probably a way. I know during image deployment with a post install script you can have access to this variable.
How about the drivers? How can he find them for a new hardware?
I have examples of how to create a post install script to copy over device specific drivers. I have to admit the examples are only for Dell systems, but you could adapt to other hardwares as long as you have the inf (not exe) based drivers packages. https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed
I use this method to seed (set) some unattend.xml settings to avoid having to use the FOG client to rename and activate the target computers. The word avoid is a bit strong, I have some unique OU naming conventions that are not supported by FOG, so I need to set then via scripting.
