Alright, I’ve currently got git version 4682. I started from a fresh database and imported my hosts via a csv file, then I adjusted all my service settings. It’s been going for about two hours now, and all the hosts are still in the web interface. Also, I have yet to see any settings change in unpredictable ways. So far so good!

I updated to the latest git version of FOG today, and whatever had been causing this issue is now gone. This thread can be marked as solved.

When adding snapin arguments, any argument that contains a quote will not show correctly when looking at the snapin details.

For instance, let’s say I’ve entered this argument into the ‘Snapin Arguments’ field:

/CLIENTNAME="some-client-name"

When looking at the snapin details after the snapin has been created, both the ‘Snapin Arguments’ and the ‘Snapin Command’ field will cut off the argument at the first quote, like this:

/CLIENTNAME=

However, the snapin will still work as expected, as the information does get correctly added to the database.

After a snapin has been created, if I change any snapin details and click ‘Update’, I am taken to a completely blank white screen. After going back to the snapin details, I can see that nothing has been updated. The only way to update the details is to delete the snapin and create a new one.

This also turned out to be due to our anti-virus settings. So let this be a lesson to us all; check your anti-virus first!

This can be marked as fixed.

@tom-elliott Thanks!

A quick update:

When initially creating an image, setting the image manager to Partclone Gzip works (although it is described is ‘Partclone Compressed’ on the image overview page). However, if I then update the Image Manager to something else (e.g. Partimage), I find that I can no longer set it back to Partclone Gzip.

OS: Ubuntu Server 16.04

When configuring an image, ‘Partclone Gzip’ cannot be set as the Image Manager.

Steps to replicate:

1. Select an image from the Image Management page.
2. Take note of the current Image Manager (in my case it was Partimage, as that is the default).
3. Set the image manager to ‘Partclone Gzip’.
4. Click ‘Update’.
5. The modal indicating the image was successfully updated should appear.
6. Reload the page. The Image Manager selection will have reverted to what it was in step 2.

All other Image Manager options work as expected.

@wayne-workman Okay, so here is some intriguing new information:

I was getting the access denied errors when using the ‘All snapins’ task. However, if I run the snapins individually, they work! I was able to install two snapins (I’ve included the size of the snapins):

• Thunderbird - 39M
• LibreOffice - 233M (this is the largest snapin we use)

So this issue seems to be specifically related to the ‘All snapins’ task.

@wayne-workman Yes, it does exist and contains a public SSL certificate from the looks of it. Just to make sure, I also uninstalled anti-virus to make sure it isn’t a problem while troubleshooting. The issue still remains. Here is the full Snapin entry in the FOG log, with a small amount of sanitizing:

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 11/22/2017 12:57 PM Client-Info Client Version: 0.11.12
 11/22/2017 12:57 PM Client-Info Client OS:      Windows
 11/22/2017 12:57 PM Client-Info Server Version: 1.5.0-RC-10
 11/22/2017 12:57 PM Middleware::Response Success
 11/22/2017 12:57 PM SnapinClient Running snapin 
 11/22/2017 12:57 PM Middleware::Communication Download: http://[SERVER_ADDR]/fog/service/snapins.file.php?mac=[MAC_IDS]&taskid=588
 11/22/2017 12:57 PM Middleware::Communication ERROR: Could not download file
 11/22/2017 12:57 PM Middleware::Communication ERROR: Access to the path 'C:\Program Files (x86)\FOG\tmp' is denied.
 11/22/2017 12:57 PM SnapinClient C:\Program Files (x86)\FOG\tmp
 11/22/2017 12:57 PM Middleware::Communication URL: http://[SERVER_ADDR]/fog/service/snapins.checkin.php?taskid=588&exitcode=-1&mac=[MAC_IDS]&newService&json
------------------------------------------------------------------------------

@wayne-workman No, the snapins were not successful; it resulted in the error that I originally posted. Once again, apologies about the confusing wording.

@wayne-workman My apologies, I did not add enough context to my original post. I did in fact initially run these FOG snapins before installing any anti-virus on this particular workstation, so that definitely wasn’t the issue. I added the comment about the anti-virus to inidicate that I’ve run into this problem in the past in different circumstances. It is not relevant for this issue, though, so I shouldn’t have mentioned it.

I also updated my original post with OS and FOG client version info. Let me know if there is other information I can send your way.

No, it is a 64-bit Windows 7 machine.

I am provisioning a new machine and running into this error when trying to install snapins. Here’s the relevant entry from the Fog client log:

Middleware::Communication ERROR: Could not download file
Middleware::Communication ERROR: Access to path 'C:\Program Files (x86)\FOG\tmp' is denied

In the past I have had this issue when using certain anti-virus programs, but we now have exemptions in place for FOG. I adjusted the permissions on this folder to be open to everyone, but that did not change anything (and then I set the permissions back). Any ideas for a remedy?

EDIT: This is on a Windows 7 64-bit machine. FOG Client is version 0.11.12.

@joe-schmitt Followed your instructions, but unfortunately I am getting the same FIPS error when the client tries to authenticate:

11/15/2017 8:44 AM Data::AES ERROR: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.