Fog deployment with applications

[cwu_doug]

After deplying a succesfull Windows client with Fog, we had some issues with Eset cloud not seeing the new Windows workstation, despite Eset client in a licensed, protected status.

Would there be anything we can do to run scripts, or snapins to rectify a duplicate client application such as Eset?

Also the Leneovo driver software couldn’t detect new updates as Windows was unable to confirm it’s serial number until we had to boot into BIOS which seemed to of registed the serial number. System was not allowing boot into BIOS and had to run the Windows repair to force reboot into BIOS. Anyone had issues of this before?

[george1421]

@cwu_doug said in Fog deployment with applications:

After deplying a succesfull Windows client with Fog, we had some issues with Eset cloud not seeing the new Windows workstation, despite Eset client in a licensed, protected status.

Was eset cloud already on the golden image when you captured it? If yes than this is your problem. Most enterprise AV solutions create a unique GUID to identify the client. If eset was installed before image capture then you deploy it. Every deployed target computer will have the same Eset GUID. Most AV solutions should be installed after cloning is complete.

Would there be anything we can do to run scripts, or snapins to rectify a duplicate client application such as Eset?

I’m not sure of the question here. Can you deploy applications with a FOG Snapin? Most of the time, yes. I would first go about looking to see if Eset had instructions for performing an “unattended install” These instructions will give you the command line parameters needed to install Eset without any prompts in the GUI.

Lenovo driver software…

I have no clue I haven’t been in a lenovo shop since 2008.

[cwu_doug]

@george1421 Thanks for the input, makes alot of sense. Yes it was part of the image!

I guess my lasting question would be, how would we know, or the most suitable applications we can have in an image without any GUID duplications/implications on deployed machines?

I am assuming anything cloud to client based, such as AV solutions to remote software like TeamViewer?

Also lastly would you recommend cloning an imaged domain PC? Or we should only join them after deployed? And possibly a snapin to automatically join if that is possible?

[george1421]

@cwu_doug said in Fog deployment with applications:

I guess my lasting question would be, how would we know, or the most suitable applications we can have in an image without any GUID duplications/implications on deployed machines?

This is very program specific. You will know by doing and then it acting bad after cloning.

I am assuming anything cloud to client based, such as AV solutions to remote software like TeamViewer?

I don’t use teamviewer to know if it creates a GUID or not. I might look in the registry under that software to see if it creates a filed like ID or MachineID or whatever might look like a unique (guid) value. This value might change on a machine to machine basis.

Also lastly would you recommend cloning an imaged domain PC? Or we should only join them after deployed? And possibly a snapin to automatically join if that is possible?

My recommendation would be to NOT connect the computer to the domain before image capture (this might also then guide what software can be loaded before and after domain join). You can either use the FOG Client to connect the computer to AD after deployment, or like in my case I don’t use the FOG Client, but use a post install script to configure the unattend.xml file to connect the computer to AD and to place in proper OU. You don’t want to connect to AD before image capture because the domain will tattoo the machine also the machine’s SSID will be set and then cloned to all other machines. If you are properly sysprepping the computer before capture then the pre capture domain join will be kind of broken too. Simple answer is to connect to AD after imaging is complete.

[cwu_doug]

@george1421 OK thank you for the info.

Eset requires an exe installer rather than an MSI file. However there is no exe option in the snapin type, only MSI and other options. I have tried Powershell but that didn’t work.

Which option shall I choose to deploy exe snapins? I have the latest Fog, 1.5.9.

[george1421]

@cwu_doug It will sound counter intuitive, but pick batch file if you have a single .exe installer file to deploy.

When you pick batch it will put cmd.exe in the command to execute field. Just replace that with your .exe name. And then in command switches it will put /c replace that with your command line switches for your app.

If your package has more than one file you will need to deploy a snapin pack (zip file with all of the files you need for deployment inside).

[cwu_doug]

@george1421 OK great, I will deploy it with a batch and see how I get one. Thanks again