That means the printer configuration is bad.
Best posts made by Joe Schmitt
-
RE: Printer not showing in Devices - Fixup to 1.3.0-RC-5
-
RE: install fog offline
@maxiecool2 as for the search function, I’m assuming you’re on mobile, since there’s a search box when you visit the forums on desktop. You can use our search function on mobile here: https://cse.google.com/cse/publicurl?cx=013831856522586480408:mlbymhymgxs&q= , it will search both the forums and wiki.
-
RE: FOG RC-8 - Unable to install windows client using smartinstaller
This issue only appears to happen on windows 10 installations. It would seem the legacy client uninstaller is not fully compatible (of sorts) with windows 10.
-
RE: Printer not showing in Devices - Fixup to 1.3.0-RC-5
Are these all TCP/IP printers?
-
RE: Auto-Join Windows Domain Troubleshooting
@Smennywheek to debug the client, look at / provide the
C:\fog.log
file on the host with issues. -
RE: Fog Client won't join Domain
@Gary-Kulovics could you create a new thread for your Mac domain binding issue with the
fog.log
attached (surround it with code snippet flags (```
) to put it in a nice scrollable box on the forums -
RE: Windows 10 Client 0.11.4 Windows Service
v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).
-
RE: Client rebranding image download question
@utopia you are correct that the client should be using the SHA512 to see if it needs to re-download the banner. It would seem I forgot to put that into production. When 0.11.12 is released I will also include a patch for this, thanks for bringing it up!
-
RE: SnapinPack Error: Version required to extract this entry not supported
@Thiago said in SnapinPack Error: Version required to extract this entry not supported:
Version required to extract this entry not supported (788)
It’s an issue with the zip file’s header. Try making the zip file with a different piece of software.
-
RE: Snapins failing due to hostname not changing
This is why the Debugger was made. Note that there is a bug in the Debugger starting at 0.11.0 with exiting so for the below instructions please use the one from 0.10.6 (https://github.com/FOGProject/fog-client/releases/download/0.10.6/Debugger.exe)
Make a snapin with the following settings:
Snapin File
:Debugger.exe
Snapin Arguments
:user list > C:\user-dump.txt
Deploy this snapin on a problematic host. A listing of the logged in users will be in
C:\user-dump.txt
. -
RE: Service Fog Client
@zago123, @Psycholiquid is correct about not disabling the client being problematic. Failing to do so causes the client and sysprep to both try and manage the computer at the same time, causing many conflicts. See https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
-
RE: Problem deploying cmd script with snapin
@Matthieu-Jacquart a couple things. SYSTEM sometimes won’t have the
TEMP
environment all variable set (yes, I know that’s weird). I also see you are using a batch script to offload to a vbs. Try removing that additional complexity by sticking to one language. Either write it in just batch or just vbs.Also, if its a snap in you can remove all of your UAC checks to further limit potentional points of failure.
But as said before, it may just simply be that SYSTEM can’t clone displays. In which case you could use a snap in to write to a login script that gets run everytime a user logs in.
-
RE: 1.3.0-RC-8 Issues I have found...
@PatrickG the spelling mistake will be fixed in v0.11.6, thanks for reporting.
As for the printer config file, you say you used a network share? Make sure that share has anonymous read access.
-
RE: Service Fog Client
@avaryan said in Service Fog Client:
I believe the latest SmartInstallers have the FOG Service start type set to manual by default.
They default to auto start
-
RE: WSUS with Fog 1.3
@Matthieu-Jacquart you could try enabling wsus via a snap in. That way the client finishes all of its hostname work before it starts wsus.
-
RE: FOG Client - Printer not displaying
@Wayne-Workman thanks for all the info. @JJ-Fullmer also has this issue and brought it to my attention earlier. I know what is causing the issue, but will be extremely tricky to safely patch. I’ll post in this thread with any progress I make.
-
RE: Email confirmed | Invalid Data
@Shiigehiro strange, the forum is showing that your email is validated. You should be fine, if it gives you any issues send me a PM and I’ll look into it more.
-
RE: FOG Client causes unwanted Shutdown of any Windows Host straight after booting
@Tom-Elliott from the logs:
10/7/2016 10:32 AM PowerManagement On demand shutdown requested
. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button. -
RE: Printer defaults not set.
Default printer changes are made by the user service. See the ~/.fog_user.log file.
-
RE: Using snapins to place 2 files on a folder
@tesparza snapins are just a way of executing a file. I’d recommend developing the script locally, and then deploying it as a snapin once it works.
In your case, a batch or powershell script would work great. If you need to deploy the two files with the snapin (e.g. the files arent already on the computers), then a SnapinPack would work great. Using a SnapinPack would let you bundle all the files you need together, so your script has the files-to-copy right next to it.