FOG Client sometimes doesn't work

tesparza

@tom-elliott Yeah that want I thought but it never does it, It has only happened maybe a few time that i’ve tried it but majority of the time it doesn’t work. I make sure to do the reset encryption data button before doing it but still nothing

Joe Schmitt

@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

Wayne Workman

@joe-schmitt That post is #wiki worthy. Client debugging steps.

tesparza

@joe-schmitt

{
  "autologout":{
    "error":"time"
  },
  "displaymanager":{
    "error":"ng"
  },
  "hostnamechanger":{
    "enforce":false,
    "hostname":"TECH_5318_01",
    "AD":false,
    "ADDom":"",
    "ADOU":"",
    "ADUser":"",
    "ADPass":""
  },
  "powermanagement":{
    "onDemand":"shutdown",
    "tasks":[]
  },
  "printermanager":{
    "error":"np",
    "mode":0,
    "allPrinters":[],
    "default":"",
    "printers":[]
  },
  "snapinclient":{
    "error":"ns"
  },
  "taskreboot":{
    "job":false
  },
  "usertracker":{
    "":""
  }
}

Joe Schmitt

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

tesparza

@joe-schmitt Okay thank you. I saw On Demand shutdown but in previous times it wouldnt do that. Do I have to reset encryption data before or after doing an ondemand shutdown or even snapins

Tom Elliott

@tesparza No, you should not have to do reset encryption data, unless the host gets out of wack for the security token (such is the case when @Joe-Schmitt had you reset data for using the debugger, and when you stop using the debugger and go back to using the regular client). (Some other cases have occurred that may require this action as well, but this is not a “normal” action that needs to be performed).

Joe Schmitt

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

Joe Schmitt

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

Joe Schmitt

@tesparza I have been unable to reproduce this with 0.11.12. Are you still having the issue?

tesparza

@joe-schmitt sorry I didn’t check my notification until today. It hasn’t happened anymore I think the problem was that i was resetting the encryption data every time i did something new because a friend told me he did it like that but turns out I didn’t have too. Thanks for trying it out. Sorry I made you search a dead end

Joe Schmitt

@tesparza well that would certainty do it. Reset Encryption Data is generally not advised to be done unless you specially do something to the client that would require it.

FOG Client sometimes doesn't work

157

12.0k

17.3k

155.2k