Posts made by dclark

Here is the basic white paper on how it helped the district during a tough budget year and ended up being one of the better finds we have made within the IT department.

As a follow up, I am starting to see the Fog Client issues on machines that have been imaged for quite some time. It is starting to look like an error within the latest patches from MS. This is the tail of the log that is starting to show up on existing machines with stopped clients.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 1/10/2018 8:58 PM Client-Info Client Version: 0.11.12
 1/10/2018 8:58 PM Client-Info Client OS:      Windows
 1/10/2018 8:58 PM Client-Info Server Version: 1.4.4
 1/10/2018 8:58 PM Middleware::Response Success
 1/10/2018 8:59 PM User ERROR: Unable to get logged in users
 1/10/2018 8:59 PM User ERROR: Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
------------------------------------------------------------------------------

 1/10/2018 8:59 PM Service Sleeping for 303 seconds
 1/10/2018 9:01 PM User ERROR: Unable to get logged in users
 1/10/2018 9:01 PM User ERROR: Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
 1/10/2018 9:01 PM Power Creating shutdown request
 1/10/2018 9:01 PM Power Parameters: /s /c "FOG PowerManagement" /t 0
 1/10/2018 9:01 PM Bus Emmiting message on channel: Power
 1/10/2018 9:01 PM Log Unhandled exception caught
 1/10/2018 9:01 PM Log     Terminating: True
 1/10/2018 9:01 PM Log     Hash code: 34170346

Also catching an error related to .net on a few if these machines when trying to re-install the client.

I always Sysprep. For me it removes any questions of there are any device independent licenses for software installed on the image.

@george1421 We also have a White Paper I wrote about our initial integration of FOG if you are interested - PM an email address if you would like.

@george1421 That’s a tough question. One thing I have been toying with is some Active Directory integration as far as comparison between FOG hosts and AD hosts. I currently have a framework in PHP to pull records from both and do a daily comparison. I use this to both find hosts that don’t have the FOG client installed for whatever reason, or possibly a client that has broke and also find hosts that have gotten deleted from FOG and not AD or vice-versa. It helps to keep both the FOG host records and AD cleaner and keep clutter to a minimum. If FOG could be directly integrated that when you delete a host you have a choice of also deleting it from AD if it exists. I don’t know if that is something that the community would use or if it would be more of a one-off type of feature, maybe an optional plug-in.

Greener? - I have to say as it stands it has changed things for us dramatically already! We used to average at least 2500 machines left on all the time, now with the shutdown features available in FOG we have it down under 100 most nights/weekends which are mostly machines that need to be on (HVAC controllers, etc…).

@george1421 We originally looked at FOG as a cost cutting measure but have found that we probably get more imaging done with less issues with it than my experience with Altiris. I have written a standalone PHP application that pulls data from the FOG database in order to inventory equipment, track power management, track user logins (by user), and track image aging and OS versions we have in the wild among other things. I use a batch file to collect and record software inventory records and a few other parameters and deploy it periodically via the snap-in system. I use FOG’s post image script to detect the machine and copy the appropriate drivers to the new install. In most instances imaging speed is tremendously better, usually in the 6-8gb range with about a 3 minute average for a 20gb image.

We originally re-purposed a used Dell T-110 tower server as the master and Dell 780 desktops as the storage nodes in order to evaluate the system and ended up running on that for about 6 months of production use. We have since upgraded for hardware reliability which was an easy migration compared to any other migration I have been involved with.

The only issue we have had that has not easily been solved either in house or on the forums is Multi-Cast but I believe that it is a network configuration issue on our end tied into VOIP operations, just haven’t had time to sit and follow the breadcrumbs.

So… Yes, we have found FOG to meet all our needs and then some. What it doesn’t include we can easily add with a little creativity.

Organization Name: Indian River School District

Location: Sussex County, Delaware USA

Approximate Number of systems: 5200 PCs/6000+ Chromebooks/300 Apple Devices

How long: Since 2/2017 (Formerly Used Symantec Altiris Solution)

14 Locations - 1 master server with 13 storage nodes.

2 - High Schools
3 - Middle Schools
7 - Elementary Schools
1 - Special Needs School
1 - K-8 Magnet School with attached Administration Building

Thank You for the link - Yes, it seems very similar. Also looking at the timing of the post, about a week ago, I believe that my issue began appearing at almost the same time. I am thinking that the latest RollUp from Microsoft is the culprit and possibly running in the background when the Fog Client is trying to perform its duties but have not been able to prove it. The machines I am having this issue are restarting and joining the domain but the Fog Client is not starting again after that.

It is possible that the actual restart is being performed by Windows update or another process. Does the Fog Client maintain some type of flag that it is waiting for a restart that may not be getting reset when the restart comes from another process and then hanging the Fog process on the next startup? The downside of this theory is that I have created a new image and installed all available updates prior to capture and am getting the same behavior with it.

Server
FOG Version: 1.4.4
OS: Ubuntu 16.04

Client
Service Version: 0.11.12
OS: Windows 10 Education 64bit

I have had a Windows 10 (1709 Education) deploying since November without issue, auto domain join, snapin install, etc. (Approximately 1200 deployments)

Suddenly I now have a situation where after the image completes and Windows sets up the expected domain joining occurs and restarts the machine. Issue is that after it reboots the FOG Service never restarts even though it is set to automatic. Multiple reboots end with the same situation. If you manually start the FOG Service again it works fine and will be started on the next reboot.

I am thinking it is something in Windows 10 wanting to update but am curious if anyone else has/is experiencing this and if you have found a solution?

Log from the initial startup:

 1/8/2018 2:02 PM Main Overriding exception handling
 1/8/2018 2:02 PM Main Bootstrapping Zazzles
 1/8/2018 2:02 PM Controller Initialize
 1/8/2018 2:02 PM Controller Start

 1/8/2018 2:02 PM Service Starting service
 1/8/2018 2:02 PM Bus Became bus server
 1/8/2018 2:02 PM Bus Emmiting message on channel: Status
 1/8/2018 2:02 PM Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 1/8/2018 2:02 PM Client-Info Version: 0.11.12
 1/8/2018 2:02 PM Client-Info OS:      Windows
 1/8/2018 2:02 PM Middleware::Authentication Waiting for authentication timeout to pass
 1/8/2018 2:02 PM Middleware::Communication Download: http://10.40.25.165/fog/management/other/ssl/srvpublic.crt
 1/8/2018 2:02 PM Data::RSA FOG Server CA cert found
 1/8/2018 2:02 PM Middleware::Authentication Cert OK
 1/8/2018 2:02 PM Middleware::Authentication ERROR: Could not get security token
 1/8/2018 2:02 PM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
 1/8/2018 2:02 PM Middleware::Communication POST URL: http://10.40.25.165/fog/management/index.php?sub=requestClientInfo&authorize&newService
 1/8/2018 2:02 PM Middleware::Response Success
 1/8/2018 2:02 PM Middleware::Authentication Authenticated


 1/8/2018 2:02 PM Middleware::Communication URL: http://10.40.25.165/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 1/8/2018 2:02 PM Middleware::Response Success
 1/8/2018 2:02 PM Middleware::Communication Download: http://10.40.25.165/fog/management/other/SMALL.png
 1/8/2018 2:02 PM Middleware::Communication URL: http://10.40.25.165/fog/management/index.php?sub=requestClientInfo&mac=48:4D:7E:DA:32:67&newService&json
 1/8/2018 2:02 PM Middleware::Response Success
 1/8/2018 2:02 PM Middleware::Communication URL: http://10.40.25.165/fog/service/getversion.php?clientver&newService&json
 1/8/2018 2:02 PM Middleware::Communication URL: http://10.40.25.165/fog/service/getversion.php?newService&json

 1/8/2018 2:02 PM Service Creating user agent cache
 1/8/2018 2:02 PM Middleware::Response Invalid time
 1/8/2018 2:02 PM Middleware::Response Module is disabled globally on the FOG server
 1/8/2018 2:02 PM Middleware::Response Module is disabled globally on the FOG server
 1/8/2018 2:02 PM Service Initializing modules

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 1/8/2018 2:02 PM Client-Info Client Version: 0.11.12
 1/8/2018 2:02 PM Client-Info Client OS:      Windows
 1/8/2018 2:02 PM Client-Info Server Version: 1.4.4
 1/8/2018 2:02 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 1/8/2018 2:02 PM Client-Info Client Version: 0.11.12
 1/8/2018 2:02 PM Client-Info Client OS:      Windows
 1/8/2018 2:02 PM Client-Info Server Version: 1.4.4
 1/8/2018 2:02 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 1/8/2018 2:02 PM Client-Info Client Version: 0.11.12
 1/8/2018 2:02 PM Client-Info Client OS:      Windows
 1/8/2018 2:02 PM Client-Info Server Version: 1.4.4
 1/8/2018 2:02 PM Middleware::Response Success
 1/8/2018 2:02 PM HostnameChanger Checking Hostname
 1/8/2018 2:02 PM HostnameChanger Renaming host to SDSA-LAB104-22
 1/8/2018 2:02 PM HostnameChanger Joining domain
 1/8/2018 2:02 PM HostnameChanger Success, code =  0
 1/8/2018 2:02 PM Power Creating shutdown request
 1/8/2018 2:02 PM Power Parameters: /r /c "Indian River School District needs to rename your computer" /t 0
 1/8/2018 2:02 PM Bus Emmiting message on channel: Power
 1/8/2018 2:02 PM Power Attempt 1/6 to shutdown computer
 1/8/2018 2:02 PM Power --> API call returned 1, will re-attempt in 5 minutes

Here is the end of the log file for a newly imaged machine this morning which is still working on downloading a snapin. The 10.24.25.165 IP is our main Fog server. The building where the machine resides local nose is at 10.40.25.165. The image itself deployed correctly from the local node.

-----------------------------------------

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 6/20/2017 10:29 AM Client-Info Version: 0.11.11
 6/20/2017 10:29 AM Client-Info OS:      Windows
 6/20/2017 10:29 AM Middleware::Authentication Waiting for authentication timeout to pass
 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/ssl/srvpublic.crt
 6/20/2017 10:29 AM Data::RSA FOG Server CA cert found
 6/20/2017 10:29 AM Middleware::Authentication Cert OK
 6/20/2017 10:29 AM Middleware::Communication POST URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&authorize&newService
 6/20/2017 10:29 AM Middleware::Response Success
 6/20/2017 10:29 AM Middleware::Authentication Authenticated


 6/20/2017 10:29 AM Bus Registering ParseBus in channel Power
 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 6/20/2017 10:29 AM Middleware::Response Success
 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/SMALL.png
 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
 6/20/2017 10:29 AM Middleware::Response Success
 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?clientver&newService&json
 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?newService&json

 6/20/2017 10:29 AM Service Creating user agent cache
 6/20/2017 10:29 AM Middleware::Response Invalid time
 6/20/2017 10:29 AM Middleware::Response No Printers
 6/20/2017 10:29 AM Middleware::Response Module is disabled globally on the FOG server
 6/20/2017 10:29 AM Service Initializing modules

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11
 6/20/2017 10:29 AM Client-Info Client OS:      Windows
 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5
 6/20/2017 10:29 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11
 6/20/2017 10:29 AM Client-Info Client OS:      Windows
 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5
 6/20/2017 10:29 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11
 6/20/2017 10:29 AM Client-Info Client OS:      Windows
 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5
 6/20/2017 10:29 AM Middleware::Response Success
 6/20/2017 10:29 AM HostnameChanger Checking Hostname
 6/20/2017 10:29 AM HostnameChanger Hostname is correct
 6/20/2017 10:29 AM HostnameChanger Attempting to join domain
 6/20/2017 10:29 AM HostnameChanger Host is already joined to target domain
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11
 6/20/2017 10:29 AM Client-Info Client OS:      Windows
 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5
 6/20/2017 10:29 AM Middleware::Response Success
 6/20/2017 10:29 AM SnapinClient Snapin Found:
 6/20/2017 10:29 AM SnapinClient     ID: 86642
 6/20/2017 10:29 AM SnapinClient     Name: MS Office 2013
 6/20/2017 10:29 AM SnapinClient     Created: 2017-06-20 09:34:39
 6/20/2017 10:29 AM SnapinClient     Action: 
 6/20/2017 10:29 AM SnapinClient     Pack: False
 6/20/2017 10:29 AM SnapinClient     Hide: False
 6/20/2017 10:29 AM SnapinClient     Server: 
 6/20/2017 10:29 AM SnapinClient     TimeOut: 0
 6/20/2017 10:29 AM SnapinClient     RunWith: cmd.exe
 6/20/2017 10:29 AM SnapinClient     RunWithArgs: /c
 6/20/2017 10:29 AM SnapinClient     Args: 
 6/20/2017 10:29 AM SnapinClient     File: Office2013-32.exe
 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/service/snapins.file.php?mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=86642

Server

• FOG Version: 1.3.5
• OS: Ubuntu 16.04

Client

• Service Version: 0.11.11
• OS: Windows 7 pro 64bit

Description

We migrated to Fog from another platform about 4 months ago and have had amazing results so far. Every issue that I have come across was able to be corrected with a little searching through the docs or the forum. I have come up against one issue that I am not sure if is a configuration issue or something else.

We have 14 locations (1 main server and 13 nodes). My issue is coming in the form of snapin downloads at the locations of the 13 nodes. For some reason when a snapin is trying to deploy to a machine at one of these locations it seems to be trying to download from both the local node and the main server. Files have replicated and are verified to be at each location. A snapin deployed to a machine in the building housing the main server only downloads from there, and is about 3 times quicker, which is what originally drew my attention.

I have the location plugin installed and in use with each node set to use the local repository.