@alfredo-the-pasta you may want to try retrieving the success state of each cmdlet and saving it to a file:
$? | Out-File C:\powershell-log.txt after each command (or something alike)
@Vinay https://wiki.fogproject.org/wiki/index.php?title=FOG_Client has everything you need;
for ubuntu: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Debian_8.2B.2C_Ubuntu_13.10.2B.2C_and_derivatives
The client will not manage domain bindings for linux. You can use a bash script Snapin for that though.
@cojohnson That’s pretty straight forward. Using the tray icon would probably be the most effective yet least intrusive; for example it could have some kind of indicator color on the icon if its pending.
For anyone still having this issue, you can run this tool as Administrator and it will clean up leftovers from the legacy client (only run after you have uninstalled the legacy client): https://build.jbob.io/Tools/CleanLegacyClient.exe.
ill not populate even after all the forced group policy updates per machine . Has anyone found the the problem might be with fog imagining or is it just something wrong with our group policies,
@jpaul it sounds like an issue with your GPO. Is there also a reason why you just started using 1.2.0? It’s fairly outdated and doesn’t support newer operating systems (like Windows 10) very well.
I had thought about that as a work around, didn’t think that would be the actual solution though. Thanks @Wayne-Workman
@Scott-Adams You’d need to post the
fog.log from a problematic host.
@Seydoo uninstalling / installing the client requires additional steps (https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Reset_encryption_data). As for macs, if they are pending, then they do infact exist on that host (they could be tunnel interfaces, VirtualBox interfaces, or any other kind of virtual adapter),
Also be sure to check the
fog.log to ensure that it is still the
private key not found error, and not a new one now. Just because the client is still not authenticating doesn’t mean the underlying issue hasn’t changed.
Your original issue
Private key not found is strictly a server issue. How did you copy over your installation to the new server? On fresh installs or upgrades this issue is not present, indicating its likely a permission issue from when you migrated the server, or something alike. @Tom-Elliott would be best equipped to tell you which files / permissions to check.
Looks like your connection to FOG Project was lost, please wait while we try to reconnect.