Posts made by Brian David

@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.

@joe-schmitt I followed your instructions, but the FOG Service won’t start after the .dll file is replaced. There were two relevant errors in the event log.

First:

Log Name:      Application
Source:        .NET Runtime
Date:          11/6/2017 8:24:03 AM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     xxx
Description:
Application: FOGService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
   at Zazzles.Settings..cctor()

Exception Info: System.TypeInitializationException
   at Zazzles.Settings.get_Location()
   at FOG.Program.Main()


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-06T14:24:03.000000000Z" />
    <EventRecordID>4459</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: FOGService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
   at Zazzles.Settings..cctor()

Exception Info: System.TypeInitializationException
   at Zazzles.Settings.get_Location()
   at FOG.Program.Main()

</Data>
  </EventData>
</Event>

Second:

Log Name:      Application
Source:        Application Error
Date:          11/6/2017 8:24:18 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxx
Description:
Faulting application name: FOGService.exe, version: 0.0.0.0, time stamp: 0x58f267cf
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f32841
Exception code: 0xe0434352
Fault offset: 0x00015608
Faulting process id: 0xa6c
Faulting application start time: 0x01d3570ae56270de
Faulting application path: C:\Program Files (x86)\FOG\FOGService.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 2c30df72-c2fe-11e7-8288-408d5cd5089b
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-06T14:24:18.000000000Z" />
    <EventRecordID>4460</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FOGService.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>58f267cf</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.3.9600.18666</Data>
    <Data>58f32841</Data>
    <Data>e0434352</Data>
    <Data>00015608</Data>
    <Data>a6c</Data>
    <Data>01d3570ae56270de</Data>
    <Data>C:\Program Files (x86)\FOG\FOGService.exe</Data>
    <Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data>
    <Data>2c30df72-c2fe-11e7-8288-408d5cd5089b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

@joe-schmitt Okay, sounds good. I’ll keep an eye out on future updates and I appreciate the work you do.

Fog Version: 1.5.0-RC-9
Fog Client Version: 0.11.12
Server: Ubuntu Server 16.04.3 LTS

We recently used GPO to force all our computers to require FIPS compliant encryption suites whenever using encryption to communicate (this is a requirement for PCI compliance). Unfortunately, this seems to have broken the FOG Client. Here are the relevant log entries:

----------------------------------------------------------------
----------------------------------UserTracker-------------------
----------------------------------------------------------------
 11/4/2017 5:27 PM Client-Info Client Version: 0.11.12
 11/4/2017 5:27 PM Client-Info Client OS:      Windows
 11/4/2017 5:27 PM Client-Info Server Version: 1.5.0-RC-9
 [...extraneous lines snipped...]
 11/4/2017 5:29 PM Middleware::Communication URL: http://fog/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 11/4/2017 5:29 PM Middleware::Response Success
 11/4/2017 5:29 PM Middleware::Communication URL: http://fog/fog/management/index.php?sub=requestClientInfo&mac=40:8D:5C:D5:08:9B&newService&json
 11/4/2017 5:29 PM Data::AES ERROR: Could not decrypt AES
 11/4/2017 5:29 PM Data::AES ERROR: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

I don’t suppose anyone else has run into this issue and has any workarounds?

@Tom-Elliott This fix works for me. Thanks!

Server

• FOG Version: RC-15
• OS: Ubuntu 14.04 LTS

Client

• Service Version: 0.11.5
• OS: Windows 8.1

Description

We’ve had FOG set up to do a scheduled reboot on all our clients every Monday at midnight. However, FOG seems to only be shutting the computers down; all workstations have to be powered back on in the morning. When checking the client log, it clearly says its shutting down and not rebooting.

I can confirm that this fix works on my end, too. I deployed an image and then sent out all snapins, and everything worked as expected.

Thanks, Tom.

@Claude-Girard Here’s the test I just ran:

1. Removed all snap-ins from host.
2. Added two snap-ins (both at once): Inkscape and Python
3. Ran ‘All snapins’ on host.

The SnapinClient originally errored out on Python with this message:

9/15/2016 4:06 PM Client-Info Client Version: 0.11.5
9/15/2016 4:06 PM Client-Info Client OS: Windows
9/15/2016 4:06 PM Client-Info Server Version: 1.3.0-RC-10
9/15/2016 4:06 PM Middleware::Response Success
9/15/2016 4:06 PM SnapinClient Snapin Found:
9/15/2016 4:06 PM SnapinClient ID: 326
9/15/2016 4:06 PM SnapinClient Name: Python
9/15/2016 4:06 PM SnapinClient Created: 2016-09-15 16:05:11
9/15/2016 4:06 PM SnapinClient Action:
9/15/2016 4:06 PM SnapinClient Pack: False
9/15/2016 4:06 PM SnapinClient Hide: False
9/15/2016 4:06 PM SnapinClient Server:
9/15/2016 4:06 PM SnapinClient TimeOut: 0
9/15/2016 4:06 PM SnapinClient RunWith: msiexec
9/15/2016 4:06 PM SnapinClient RunWithArgs: /qn /i
9/15/2016 4:06 PM SnapinClient Args: ALLUSERS=1
9/15/2016 4:06 PM SnapinClient File: python-2.7.10.msi
9/15/2016 4:06 PM Middleware::Communication Download: http://fog/fog/service/snapins.file.php?mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&taskid=326
9/15/2016 4:06 PM SnapinClient C:\Program Files (x86)\FOG\tmp\python-2.7.10.msi
9/15/2016 4:06 PM SnapinClient ERROR: Hash does not match
9/15/2016 4:06 PM SnapinClient ERROR: --> Ideal: D7334A6C5D6EDC8494E59E4A24B39DADEB39C63B4275F2F79E2C36422783C6A40DEC3227C81BE9990E033AD8630107279440035A55D4C1C9CDB667D39D0AF6A9
9/15/2016 4:06 PM SnapinClient ERROR: --> Actual: 91975CAE1F0111F655AF5EB66D92EA75A2638D97B06A32C18DAB14F9CFFBB00B6F5782AEB83FAA528816F6C5B6AB58B58ABAFD1B4DEFB0F640E1B812E14B3589
9/15/2016 4:06 PM Middleware::Communication URL: http://fog/fog/service/snapins.checkin.php?taskid=326&exitcode=-1&mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&newService&json

Two minutes later Python successfully installed with this message:

9/15/2016 4:08 PM Client-Info Client Version: 0.11.5
9/15/2016 4:08 PM Client-Info Client OS: Windows
9/15/2016 4:08 PM Client-Info Server Version: 1.3.0-RC-10
9/15/2016 4:08 PM Middleware::Response Success
9/15/2016 4:08 PM SnapinClient Snapin Found:
9/15/2016 4:08 PM SnapinClient ID: 327
9/15/2016 4:08 PM SnapinClient Name: Python
9/15/2016 4:08 PM SnapinClient Created: 2016-09-15 16:05:11
9/15/2016 4:08 PM SnapinClient Action:
9/15/2016 4:08 PM SnapinClient Pack: False
9/15/2016 4:08 PM SnapinClient Hide: False
9/15/2016 4:08 PM SnapinClient Server:
9/15/2016 4:08 PM SnapinClient TimeOut: 0
9/15/2016 4:08 PM SnapinClient RunWith: msiexec
9/15/2016 4:08 PM SnapinClient RunWithArgs: /qn /i
9/15/2016 4:08 PM SnapinClient Args: ALLUSERS=1
9/15/2016 4:08 PM SnapinClient File: python-2.7.10.msi
9/15/2016 4:08 PM Middleware::Communication Download: http://fog/fog/service/snapins.file.php?mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&taskid=327
9/15/2016 4:08 PM SnapinClient C:\Program Files (x86)\FOG\tmp\python-2.7.10.msi
9/15/2016 4:08 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Installing Python”,\r\n “message”: “Please do not shutdown until this is completed”\r\n}”
}
9/15/2016 4:08 PM Bus Emmiting message on channel: Notification
9/15/2016 4:08 PM SnapinClient Starting snapin…
9/15/2016 4:08 PM SnapinClient Snapin finished
9/15/2016 4:08 PM SnapinClient Return Code: 0
9/15/2016 4:08 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Python Installed”,\r\n “message”: “Installation has finished and is now ready for use”\r\n}”
}
9/15/2016 4:08 PM Bus Emmiting message on channel: Notification
9/15/2016 4:08 PM Middleware::Communication URL: http://fog/fog/service/snapins.checkin.php?taskid=327&exitcode=0&mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&newService&json

Fog made no attempt to install Inkscape, yet still registered the task as complete after this. Inkscape never installed.

After this, I repeated the process i.e. removed the snap-ins, re-added them, and ran ‘All snapins’. This time, both Inkscape and Python installed correctly.

I can confirm I have this exact same problem. After imaging a computer I deployed all snap-ins and the process failed on the first snap-in saying that the hash does not match. If I install a single snap-in, it works fine.

@george1421 Mostly Avast (either Pro Antivirus or Internet Security), although we are in the process if switching to Webroot. Funny enough, the reason I wanted to try the virus scan is because Avast recently sent out an update that seems to have caused the boot-time scan to behave very strangely: it will start scanning and then will boot straight into Windows after only checking 1 or 2 percent of the files. As a result, I wanted to check out the ClamAV scan and see what it might bring up.

@Tom-Elliott I’ll see if I can get those logs for you.

Server

• Version: 1.3.0-RC-8
• OS: Ubuntu 14.04 LTS

Client

• Version: 0.11.5
• OS: Windows 7

Description

The ‘Virus Scan - Quarantine’ task fails shortly after loading iPXE. Here is an image of the error (sorry about the blurriness):

I have not found any other tasks that have this issue.

EDIT: Fixed image.