FOG - Single Snappin

[george1421]

{from discussion via IM}

I might assume this might get you pretty close.

[george1421]

@msaglioc99 After testing with this application I see its throwing the following error and returned a not successful response to the fog snapin tool

But it looks like it installed something though

[msaglioc99]

@george1421 what template and snapin settings did you use to deploy what you were able to install

[george1421]

@msaglioc99 None so far, I just wanted to see if the installer ran to completion without any errors. The next step was to deploy via snapin. But since there was an error I stopped.

[george1421]

@george1421 I was able to deploy the application with these settings

[0_1500920876828_Thumbs.db](Uploading 100%)

[msaglioc99]

Do these look okay @george1421

[Wayne Workman]

If only a single file is being deployed, you don’t need to use SnapinPacks, a regular snapin will work and be more simple.

[Tom Elliott]

@Wayne-Workman I think this depends on the file. Some exe files are self extracting zip files. These often have a script that auto runs which can cause any number of issues.

[george1421]

@Tom-Elliott Just to close the loop on this. I had to extract the teammate program to get to the MSI and install files. Once I did that I created a zip of the contents and then deployed as a snapin pack with a template of MSI. This worked on my dev instance of Win10 1607 but did not install according to the OP on Win10 1703. I don’t have a dev build of Win10 1703 yet to test with to confirm if there is something different. But as the system is currently configured I can install it once I extracted the contents out of the .exe. I could not deploy the .exe directly because it threw a 1619 error when I did.

[msaglioc99]

@george1421 @Tom-Elliott any ideas on why it deploys to George’s 1607 build but not my 1703 build?

[george1421]

I setup our MDT server last night to create our standard image using Win10 1703. I was able to capture it and deploy it this morning with FOG. I was able to install the teammate software with the same snapin that worked with 1607.

So it works as it should. Understand that the system I’m testing on, which as freshly built, has all of our applications on it as well as some management tools. These applications may have installed a dependency that teammate needs. That is why it works in my environment. This is not a FOG issue, but an application issue.

I’m in the process of building a virgin win10 1703 image without any add on applications or windows updates. I will test again to see if the snapin deploys correctly.

If that test is successful then I don’t know what to tell you other than its not a FOG issue.

[george1421]

@george1421 The Teammate software installed correctly on a virgin build of 1703 without an application (minus the ones that come with 1703 ) I’m not sure what else I can say to help your setup, it works for me.