@dambron said in Print management issue: cannot remove printer.:
after manual removal, I’m guessing due to registry entries for the printer.
Sounds like group policy is adding the printer. If the FOG Client were doing it, it’d be plainly written in the fog log.
@jlouie.smart that’s too difficult and not supported and I will not help you with it. Just migrate the data and images to a new box, leaving the old box untouched. When done, shutdown the old box. https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
@Fernando-Gietz said in Please enter the TFTP issues with Cisco WS-C2960X-48TS-L:
Can I send, changing the iPXE menu or using other alternative, the TFTP server?
Your not even getting that far, so this won’t work. Dhcp needs adjusted, this is the most simple, easy, and supportable solution.
You’re NOC should realize you are one of their customers, and should realize you are all on the same team and all have good intentions.
@jlouie.smart said in Issues after upgrading from 1.2.0 to 1.4.3:
isc-dhcp config is completely different from the one saved from before, (which leads me to thing the new file is from the stock file in the 1.4.3 installation). Just more surprised that what seems to be a “configuration file syntax error” occurred.
FOG 1.2.0 built the /etc/dhcp/dhcpd.conf file differently than 1.3+ does. Parts of the file /opt/fog/.fogsettings are used to generate the dhcp config. Since this was an upgrade and not a fresh install, the problem is probably there. Probably older values that weren’t converted over correctly during upgrade.
You would need to share your /opt/fog/.fogsettings file with one of the moderators or developers so we can see what got butchered, as well as the output of ip addr show from your fog server.
@sdorion said in After install FOG my user account's (fog) password seems not to work anymore:
When I installed kubuntu I choose fog as username…
That was your first mistake. Do not create a user called fog, this is a reserved account.
The password for the fog account will be in storage management. Once in, I would advise you to make a different account called something else, and leave the fog account alone.
Typically when you see “Object reference not set to an instance of an object” errors from the fog client, this most typically means tge encryption needs reset for that host.
the reset can be done from the web gui, on the host’s general page. It’s a big button towards the top.
If this fails to fix the issue, try reinstalling the client on that box. Make sure there are reboots between Uninstall and reinstall.
If several hosts have the issue, this points to an image problem - perhaps reboots were not done (two at least) prior to capture after all software has been installed.
@UniSuperBox Run the cleanup commands found in the below link and see if that corrects the issue: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands
Printers are just tough in fog. It can be done, but it’s tough (Group policy for printers is equally tough so maybe printers themselves are just tough). What I recommend is using a snapin to remove all the current IP based printers (I posted a powershell script once that does it somewhere), the fog client will see that the printers are gone and it needs to remake them.
@sbenson According to the below thread, ipxe does not follow redirects, so you just need to edit /tftpboot/default.ipxe to use https instead of http
https://forums.fogproject.org/topic/10384/installfog-sh-force-https-and-ipxe
@sudheerbattu All branches of the fog installer is currently passing the installer tests on those mentioned distributions: http://theworkmans.us:20080/fog_distro_check/installer_dashboard.html
Must be your environment or firewall or web filter.
You’ll also want to turn off DHCP in the fog config file, otherwise it’ll just turn back on the next time you update. Here: /opt/fog/.fogsettings look for dodhcp and set it to ='N'
There’s also this concept: https://forums.fogproject.org/topic/8821/roll-calling-hosts-to-identify-problems
But instead of gathering a list of non-functional systems, you’d be telling them to copy their fog.log files to the share - and skipping the list building parts.
@msaglioc99 Must be your firewall or web filter, because mine is working fine.
@lpetelik Look at the output of this on that node: ls -laht /images it should tell you where the space is going. You can also try du -sh /images/* and you might also look at the output of df -h for 100% full partitions.
@dureal99d If this really is your only fog server, you can just disable the fog image replicator and the problem should go away:
systemctl stop FOGImageReplicator
systemctl disable FOGImageReplicator
@andrewg78 The tokens should not have an “equals” symbol added. My examples have an equals at the end because that was coincidentally part of the token. So if you’re adding an equals, remove that.
And you’re missing this header: -H 'Content-Type: application/json'
@jhalbert said in Snapins does not deploy:
an I reset encryption on 600 pcs? Can I use a script or is their a place where I can reset them all?
Use the web interface - put all of them into a group called “all” and use the group to reset the encryption on them all.
@sebastian-roth said in Image upload & deploy taking a long time:
I just had a quick look at the dislocker code and figured that it’s fairly simple to detect a bitlocker partition. For those interested, see here and here. Should be fairly simple to add some detection code to our inits. I’ve got that on my (long) list of things to do…
I think if we could at minimum accomplish detecting if a disk is a bitlocker partition or not would be a large advancement - if the inits detect it, they can throw a fat error saying “Please turn off bitlocker in the OS, use this command to do it: blah, Then try to capture again”
