@Sebastian-Roth said in FOG unable to capture/deploy resizeable images correctly.:
@dambron Yeah, Quazz is totally right. We have updated the init files and I totally forgot to ask you to try out the most current ones (32 bit and 64 bit). Hope this will fix the issue for you.
Thanks so much to both of you. I replaced the init file and everything is now working properly. Many thanks for your time and efforts.
@Quazz said in FOG unable to capture/deploy resizeable images correctly.:
@dambron The script grabs the init from this url https://fogproject.org/inits/init.xz
Put it in /var/www/fog/service/ipxe
You are the greatest. I will let you know how it goes!
Wow so that’s funny, I was just following another thread about editing the inits but it was from 2017 or so. I randomly stumbled upon it while trying to find more information on my issue.
So, do you know if there is any way to update the inits without performing the 1.5.6 version update? I suppose I could wait until the weekend since we do half day Fridays all summer and then deploy and make sure everything is working, but I feel like it’s kind of a dicey time to be pushing an update (especially since it will be the first time I’m doing it on my own!).
@Sebastian-Roth said in FOG unable to capture/deploy resizeable images correctly.:
@dambron Ok, that all seems fine so far. I still can make heads or tails of this. Can you please do the debug capture again and step through till you see the message
Processing Hard Disk: /dev/sdaand then take a picture again.As well please post the contents of
/images/<IMAGENAME>/d1.original.fstypeshere.
Processing Hard Disk: /dev/sda
d1.original.fstypes
/dev/sda1 ntfs
I feel bad for making you dig through all this but I really appreciate the time you’ve taken. If worse comes to worse I can always have my team change their process to always pull the image off of the smallest drive size we deploy on site to avoid this in the future, but honestly I’m just so curious as to why this isn’t working now. I feel like it was working previously, but maybe I just never ran into this particular situation.
Here is the screenshot of the stepped process for capturing this image.
I will do that right now, but just to be clear, this was happening earlier today when the image was a Win10 installation with the recovery partition in place as well. I will post the results of the debug shortly.
Thanks so much.
So normally the image sizes look correct, but I did monkey with a few things earlier today and I notice now that a few of my older images list “0.00 iB” and the image I’ve been working on also shows “0.00 iB”.
The size on the server is 16,107,628,413 bytes, so 16GB or so? The actual used disc space is about 33GB on the reference machine.
E: Also I’m like 99% sure it’s not capturing in RAW mode because I’m pretty sure that takes a looooong time compared to a normal capture., and I probably would have noticed.
Sure! So this is the latest iteration of the image, where I deleted all other partitions on the disk so it’s just the single partition.
d1.fixed_size_parititions
:1
d1.minimum.partitions
label: dos
label-id: 0x7bb39a2f
device: /dev/sda
unit: sectors
/dev/sda1 : start= 206848, size= 975588864, type=7, bootable
d1.partitions
label: dos
label-id: 0x7bb39a2f
device: /dev/sda
unit: sectors
/dev/sda1 : start= 206848, size= 975588864, type=7, bootable
Thanks for the quick response.
So I have been using FOG for quite a few years, although normally with support from a much more experience Linux administrator than myself, so please bare with me. Recently we had a large restructuring where I work and now I’m dealing with a much “broader” set of hardware, and this has caused a few image related issues. Previously all of my deployments were captured on 256GB SSD’s and then deployed either to the same, or on very rare occasion to a 500GB magnetic drive. I haven’t in years gone from something larger in drive size to something smaller. Well, now that is happening. I trained a coworker on FOG and the first thing he did was create an image on a 500GB drive and then try to deploy it to a 256GB SSD. The procedure fails and tells you that the target partition size is smaller than the source. I’ve tried it myself and even when selecting “Single Disk- Resizable” and “Everything” it captures the image fine, but is not actually able to distribute to a smaller drive than 500GB. I also tried deleting all recovery/secondary partitions inside Windows 10 and capturing/deploying it again but the same result happened. The image captures fine, but then tells me the target partition is smaller than the source.
Any advice or tips would be appreciated, and of course I can provide detailed logs, I just need to know where to look for them, because I am fairly clueless right now.
Sorry for the delayed response! We were very swamped with semester start at the middle of August, in addition to just opening a new Center for Science and Health Professionals with tons of new hardware. I didn’t get a chance to test out the new DLL but I was planning on it… until a hurricane hit us and we’ve been closed for over a week and won’t reopen until after Labor Day (I’m located in Houston).
I will at some point test it out and let you know how it goes. Until then I will say that FOG has been an absolute champ and has made my life so much easier for this semester start. I have no clue what I would do without it.
It’s no problem. I feel bad even making you go through the trouble to look at this, as it’s obviously a lesser used feature. I did find it odd that such a simple thing wasn’t working when every other module/component worked flawlessly. The real reason I would find it useful is that our Helpdesk team manages some business office devices that print checks, tax forms, and sensitive user data. Access to these devices is obviously strictly controlled, but it would be nice if while removing someone’s access centrally we could also cut out their access to peripherals on their network devices.
PS: I love FOG, it’s made my life so much better even in the short period of time I’ve been using it. We’re a small shop and so anything that A.) cuts down on field time and B.) works 99% flawlessly on first install is really awesome for me. I’ll bump that up to 100% if we can figure out what is with the printer removal 
I am using the “FOG Managed Printers” option for the group/hosts, as I posted previously. There is no “add only” mode that I see. I see an option for FOG to manage only FOG printers (both add and remove), an option for FOG to manage ALL printers (allows it to add and remove Fog and non-FOG managed printers), and an option for it to manage NO printers. I see that the documentation shows the option for “Add-only” and “Add and Remove” but are you sure this is not out of date? I don’t see those options or descriptions in the Print Management menus for any of my hosts and the configuration settings for Print Management don’t contain anything of the sort either.
Also, I’ve tried all the options under that menu, just in case they were incorrectly labeled, and had no different results. The only way for me to remove a printer is by manually running the rundll32.exe print commands on the machine. It seems that the remove commands are not correctly being sent to the host computer via FOG.
PS: I feel like I’m taking crazy pills with all of you talking about add-only mode and patting each other on the back for pointing out something that would be hilariously obvious to me if it were set incorrectly… please let me know if this option is located somewhere I’m unaware of because I do not see it located where the documentation says it should be.
@Sebastian-Roth said in Print management issue: cannot remove printer.:
@dambron
This is what the fog-client used to manage printers on Windows clients. Maybe try calling those by hand and see if it properly cleans it all up. Start a cmd window as Administrator and run:rundll32.exe printui.dll,PrintUIEntry /dn /n "\\*server*\NCC2100" rundll32.exe printui.dll,PrintUIEntry /gd /n "\\*server*\NCC2100"
Huh, well that seems to work just fine, which I guess makes sense. I know that if you add a printer using
RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /z /n\\computername\printername
Then you can’t remove that printer using the traditional add/remove method in Windows, you must run the /dn /gd commands to remove it.
So it looks like it’s being added properly but the remove command isn’t working for some reason. Very interesting… at least I feel like I understand what’s happening now, if not why! Thanks so much for the assistance.
@Sebastian-Roth said in Print management issue: cannot remove printer.:
@dambron Sorry this has been unanswered for some days. I’ve had this on my list but couldn’t find the time to spin up a test setup as I don’t usually have windows clients around.
@Moderators Is anyone of you able to replicate this issue?
Even with the FOG client removed and after removing both the printer and computer from the FOG console, the printer still adds any time an account logs in to Windows. So back to my original theory, it’s the registry entry for the printer. Somehow the way that FOG is adding the printer enforces it through the registry for every user after it is added, even if you “remove” it via FOG.
In order to prove this I flushed out every entry for the printer in the registry using a manual search of the registry, and now the printer no longer automatically adds for every user.
Just for the hell of it, here’s what the log shows when I add and then “Remove” a printer.
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
6/22/2017 10:58 AM Client-Info Client Version: 0.11.12
6/22/2017 10:58 AM Client-Info Client OS: Windows
6/22/2017 10:58 AM Client-Info Server Version: 1.4.2
6/22/2017 10:58 AM Middleware::Response Success
6/22/2017 10:58 AM PrinterManager Adding printers
6/22/2017 10:58 AM Printer Adding: \\*server*\NCC2100
6/22/2017 10:58 AM PrinterManager PrintUI return code = 0
6/22/2017 10:58 AM PrinterManager Invoking add \\*server*\NCC2100 for all users
6/22/2017 10:59 AM PrinterManager PrintUI return code = 0
6/22/2017 10:59 AM PrinterManager Restarting spooler
------------------------------------------------------------------------------
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
6/22/2017 11:01 AM Client-Info Client Version: 0.11.12
6/22/2017 11:01 AM Client-Info Client OS: Windows
6/22/2017 11:01 AM Client-Info Server Version: 1.4.2
6/22/2017 11:01 AM Middleware::Response Success
6/22/2017 11:01 AM PrinterManager Adding printers
6/22/2017 11:01 AM PrinterManager \\*server*\NCC2100 has already been configured
------------------------------------------------------------------------------```
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
6/22/2017 11:06 AM Client-Info Client Version: 0.11.12
6/22/2017 11:06 AM Client-Info Client OS: Windows
6/22/2017 11:06 AM Client-Info Server Version: 1.4.2
6/22/2017 11:06 AM Middleware::Response No Printers
------------------------------------------------------------------------------
@Wayne-Workman said in Print management issue: cannot remove printer.:
@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.
The test group for this print issue happens to be an IT training room with 12 identical machines. I only added the printer to 4 of them via FOG and the others don’t have any printers managed or showing up. All the machines belong to the same OU, so it’s not a policy being applied at the computer level. It’s also not at the user level because I’ve tried a multitude of users and we don’t use GPO to manage any print settings at all generally. For the heck of it I browsed through and don’t see any local group policies that were applied, so I don’t think it has anything to do with GPO at all.
It occurs to me that this issue must relate to one of two things:
1.) Either the way FOG adds a printer is causing an issue, since the printer reappears after manual removal when the same or any other domain user logs in again. I can manually add and remove network printers all day long and it works just fine.
or
2.) FOG is not actually trying to remove the printer once it has been removed from the host using the printer management tab in the console, and is in fact still trying to add the printer to the hosts continually. I haven’t seen any failures or log errors, so I am leaning more towards this being the case.
I am using the “FOG Managed Printers” option for the group/hosts, I assume this is correct? Do you know of anything else I could check on the FOG side of things?
@Tom-Elliott Sorry I should have added that I already tried rebooting them several times after updating the host print settings. I also went through and double checked all of the server settings that I could think of and didn’t see anything out of the ordinary.
I really wish I was getting a specific error message from FOG but there’s nothing at all, and every other component works seamlessly! Maybe I will just have to live without print management. I actually don’t mind so much but I feel like it would benefit our helpdesk team a lot.
I’m home from the office now and need a break from this stuff, but I’m going to go through the windows logs more thoroughly tomorrow to see if this could be a windows issue, or maybe even a permissions issue? I dunno, I’m just brainstorming here cause I’m at a loss.
Howdy, I’m fairly new to FOG but I’ve gotten things up and running this week so we can do away with our Ghost licensing shortly. Pretty much everything is working exactly how it is supposed to on my end: inventory, pulling images, deploying images, multicasting, domain member management, hostname changing, and even adding printers.
The one issue I am having is that removing printers does not function. Even worse is that after the printer has been removed from the host, the printer still appears for new users on the machine, ones who hadn’t ever previously logged in on that computer and thus had no printers associated with their account locally. The printer is also re-adding after manual removal, I’m guessing due to registry entries for the printer.
The client log file hasn’t given me any idea how to fix this, but here it is:
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
6/13/2017 6:43 PM Client-Info Client Version: 0.11.12
6/13/2017 6:43 PM Client-Info Client OS: Windows
6/13/2017 6:43 PM Client-Info Server Version: 1.4.2
6/13/2017 6:43 PM Middleware::Response No Printers
------------------------------------------------------------------------------
Has anyone found an elegant solution to fix this that doesn’t involve manually flushing out registry entries? Or maybe I’m doing something stupid and I just haven’t been using FOG long enough to realize it…
Any feedback would be greatly appreciated. TIA.