@TrialAndError if you set the service to delayed start, or manually stop and start up the client after boot, then does it work?

@tesparza the tool Wayne listed should be run a computer where you already have the desired printer installed.

Without any more information, my guess would be that the printer failing to add is due to the inf file being stored on a network share. I’d first try the generic inf file that PrinterManagerHelper.exe will point you to, as it should work. If it does not, and you need to use the network share, then you will need to ensure that the share has Anonymous read privileges for all computers. The client runs as SYSTEM, which causes some issues with network shares. Specifically, even if the machine is already joined to a machine, the client will not be able to access shares enabled for computers bound to a domain.

@TrialAndError @UWPVIOLATOR @x23piracy @dclark I believe I have isolated the issues with Windows 1709 and patched them. Could you try installing this build of the client on a few machines to test? (You may need to hit Reset Encryption Data for the hosts if you are uninstalling an existing FOG Client and installing this build). With any luck it will fix all issues with the service failing to start, and not shutting down the computer correctly.

https://build.jbob.io/Client/nightly/02-01-2018-win1709-04/SmartInstaller.exe

NOTE: This is a nightly build and is not production compatible! Imaging it may produce security warnings from Windows or your anti virus software.

@UWPVIOLATOR @x23piracy after running the debugger in the prior post, can you also try installing this build of the client on a few machines: https://build.jbob.io/Client/nightly/01-32-2018-win-dependencies-01/SmartInstaller.exe ?

It likely wont fix the shutdown issue, but it should allow the client to consistently start up with Windows.

@tesparza Just a heads up, it may be a few days before I can get to this. I’m currently tracking down a severe bug on Windows 1709:

• https://forums.fogproject.org/topic/11342/windows-10-fog-client-failing-to-restart
• https://forums.fogproject.org/topic/11305/client-0-11-12-windows-10-1709-reboot-fails

@tesparza nope! Basically, the client works by “locking” into the server. Once the client is locked in, no other program or computer can easily pretend to be that client. “Reset encryption data” removes the lock, and allows a new program to “lock in”.

So what I had you do was allow the Debugger to “lock in”, or become the FOG Client from the server’s perspective.

@tesparza well that certainly looks correct. I’ll try and reproduce the issue and get back to you.

@tesparza this sounds like a server issue to me; the client is showing no indication that it was told to perform any power management tasks. To be sure, can you try the following steps on this problematic machine?

• Open an administrative CMD, and run net stop fogservice
• Navigate to your FOG server’s web portal, select the host you are working on and perform these steps:
  • Schedule an on-demand powermanagement shutdown
  • Press Reset Encryption Data if its an option
• Download our Debugger.exe and run it
• The Debugger will open a console that has a fog: prompt, please enter these commands, pressing enter after each one:
  • middleware configuration server http://10.154.72.190/fog
  • middleware authentication handshake
  • dump cycle save

The debugger should point you to a FOGCycle.txt file. This contains all the information the server tells the client, completely decrypted. Please post it here, after filtering out any sensitive data (such as active directory password).

To clean up:

• Close the debugger
• click Reset Encryption Data again on the host in the gui
• start back up the fog service if you want

@UWPVIOLATOR @x23piracy can you try the following stops on a problematic machine?

• In an administrative CMD, stop the fogservice if it is still running: net stop fogservice
• Download and extract this file anywhere on the machine: PowerDebugger.zip
• Run the Debugger.exe contained in the extracted folder as Administrator
• Type the following commands into the debugger’s prompt (one at a time, and pressing enter after each line)

bus mode server
power restart

The debugger will then schedule the client’s restart process in 60 seconds. Can you let me know if it successfully restarts the machine? If not I’ll need the full output of the Debugger window.

@UWPVIOLATOR @kwisher @TrialAndError so far it seems to be caused by a faulty Windows Spectre patch. See this thread for what hopefully is the solution: https://forums.fogproject.org/topic/11342/windows-10-fog-client-failing-to-restart/7

Please report back if applying the fix actually resolved the client issue!

@x23piracy a windows service can impersonate one of the logged in users without their password. Essentially the service grabs a process running as the user you wish to impersonate, and obtains a handle on the process’s access token (OpenProcessToken). The service then needs to duplicate the token so it can “impersonate” the user without affecting the process we lifted the token from (DuplicateToken), activate that token, and then perform the work. Finally the token handle must be closed.

Its a pretty win32 api heavy approach. The client does not use this technique as there is no guarantee a user is logged in at any given point.

TL;DR: grab an existing process running as that user, and perform multiple win32 API calls to impersonate that user.

@DarkStorm007 what specifically do you want to change about the form? Is it that its showing in english and not the system language? We do have Spanish-Spain (es-Es) translations, but not for Mexico (es-mx). If you’d like to add a translation, see this thread: https://forums.fogproject.org/topic/9068/help-wanted-client-internationalization and I can include it in the next build/release.

@dclark some thoughts:

• Could you right-click -> Properties on C:\Windows\Microsoft.Net\Framework\v4.0.30319\mscoreei.dll, and check out the Created, Modified, and also the Digital Signatures tab to make sure the file wasn’t overwritten?
• Can you please run sfc /scannow from an administrative CMD? (this is the Windows System File Checker)
• Run a full virus scan. It’s likely not a virus, but I just want to make sure we eliminate that possibility

@dclark can you try reinstalling the .NET framework? I agree this is starting to seem more and more like a bad Windows update, hopefully we can isolate which update is causing this.

Linking with https://forums.fogproject.org/topic/11305/fogclient-0-11-12-windows-10-1709-reboot-fails-after-joining-domain as @TrialAndError has the same issue. It seems to be specific to 1709.

Linking with https://forums.fogproject.org/topic/11342/windows-10-fog-client-failing-to-restart as @dclark has the same issue. It seems to be specific to 1709.

@Greg-Plamondon re-run the installer with ./installfog.sh -K . That will regenerate your certificates using your old server’s private CA key, assuming it was transferred over properly.

@Greg-Plamondon https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

@TomcatKZN @Wayne-Workman that error just means the client hasn’t authenticated with the sever yet and doesnt have a token.

The real error here is 2018/01/22 21:10 Middleware::Response Private key path not found . Try rerunning your fog server install script. @Tom-Elliott would be of help debugging this issue here.

@Rudy-Delsaut can you try opening regedit and checking for the leftover legacy client software entry? Sorry for all the trouble, the legacy client was built a long time ago for Windows XP so it has some issues like leftover registry entries. If the machine is 64 bit you should also check under Wow6432Node, keeping the rest of the path the same:

@tom-elliott said in Client install issues - Legacy uninstall:

Before redoing everything, per @joe-schmitt, the registry is scanned for the presence of a particular GUID for the FOG Legacy Installer.

Please Open regedit and look in:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Remove the key with: {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1} and try reinstalling, this should work (hopefully).