As noted in the bug thread located at:
[url]http://fogproject.org/forum/threads/computer-group-limits.492/[/url]
Fog seems to have an issue if a different MAC other than the Lan MAC (eth0) is the default.
Allow FOG to choose which mac is accessing it at that time to be the default or change FOG to not care which MAC is the default.
I’m guessing you are correct, when they export they are in no specific order that I can tell so I would no be surprised if a wlan car or even a bluetooth adapter ended up first on the list.
Unless you think it’s worth looking at getting this changed, I will look at getting this moved out of the bugs, and putting a edit in the first comment about importing from OCS.
I may have made some progress.
i was doing a mysql dump from OCS-NG and importing that.
I don’t think FOG likes the fact that some machines have upwards of 3 MACs and so it’s causing issues.
I found the OCS import plugin located here: [URL=‘http://sourceforge.net/tracker/index.php?func=detail&aid=3184712&group_id=201099&atid=976201’]OCS Plugin[/URL]
I am now using that to import machines in, and groups are working fine.
Again I’m not really sure why this works and that doesn’t, and i’m not sure how to test it.
Stood up a new 2008R2 print server with 1 printer installed, a single Hp laserjet 1320, the only driver installed was the 64 bit OS driver specific for that printer.
Freshly imaged Dell 790 windows 7 64-bit .
Upon adding to the domain, there was an interactive services logon error, that the printer already existed.
Rebooted and the printer is added to devices and printers but then the error from above, “operation could not completed…”
Removed the printer from fog, refreshed printers through the FOG tray. Printer removed from Devices and printers, but stayed in the registry.
Re added the printer in fog, restarted the FOG service,
[CODE] 3/28/2012 11:38 AM FOG::PrinterManager Management level = 2
3/28/2012 11:38 AM FOG::PrinterManager Removing unwanted printers from host…
3/28/2012 11:38 AM FOG::PrinterManager Server Match: \pserver2\TechRoom printer will stay as is
3/28/2012 11:38 AM FOG::PrinterManager Adding new printers to host…
3/28/2012 11:38 AM FOG::PrinterManager 1 found on server side.
3/28/2012 11:38 AM FOG::PrinterManager Printer already installed \pserver2\TechRoom
3/28/2012 11:38 AM FOG::PrinterManager Waiting for tray to load…
3/28/2012 11:38 AM FOG::PrinterManager Setting Default Printer…
3/28/2012 11:38 AM FOG::PrinterManager Setting default for \pserver2\TechRoom
[/CODE]
The printer never shows back up in devices and printers.
EDIT:
Confirmed that if I removed the registry key placed for the print driver, restart the print spooler service, and refresh the FOG service, or refresh printers from the FOG Tray, the printer installs back.
The issues seems to be with FOG looking in the registry for the installed printer. This will also cause an issue with using the Universal Drivers since it only puts 1 driver in the registry no matter how many different models of that brand you install.
[quote=“chad-bisd, post: 2520, member: 18”]I will start experimenting with FOG printers in Windows 7 Pro 32 bit using FOG 0.32.
My plan is to add printers to FOG server.
[LIST=1]
[]Record status of interactive services detection service
[]Assign printers to hosts
[]Verify printers on the host
[]Remove printers from host
[]Add same printers back to host
[]Report my findings.
[/LIST]
[/quote]
That would be great.
Can you also give some information about the print server you are using, as well as the driver you are using.
I am currently using the universal 32/64 bit driver package from HP and Lexmark. I think that may be causing an issue, I am standing up a new 2008R2 print server and will be testing with the basic driver packages for each printer model.
I found out that fog checks for printers in the location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3
If you delete any driver entries below there, the printers uninstall and FOG sees they are gone, and allows them to be re-installed.
Thanks for the update!
Can I contact your privately To try and narrow down what I am doing differently to cause this?
Interesting.
I have tried it on two different freshly installed fog boxes with simply importing Mac and hostname.
Can you try to create a new group with all your machines in it and let me know if it works?
I can create a group with more than 1000, i just have to add them in small amounts.
How were your computers entered into FOG?
By Host Import?
FOG version .32
Ubuntu 10.04 LTS
When attempting to create groups over 960 or so members the task will error out with no output and no group created.
These hosts were imported using host upload.
They contain host names and mac address’s.
With version .29 I was able to create a group of over 1039 host.
There is also no output in the gui for things like, when a group is created and no group is chosen to place the host in.
In version .29 there was an error:
[B][COLOR=#2c2c2c][SIZE=10px][FONT=arial]Please select or create a new group![/FONT][/SIZE][/COLOR][/B]
[B][COLOR=#2c2c2c][SIZE=10px][FONT=arial][/FONT][/SIZE][/COLOR][/B]
These errors seem to be coded inside
hosts.include.php
Another update:
On .32 when creating a group but you do not choose a new group or an existing group the error:
[B][COLOR=#2c2c2c][SIZE=10px][FONT=arial]Please select or create a new group![/FONT][/SIZE][/COLOR][/B]
Does not appear anymore like it does in my 0.29 install.
[SIZE=1][FONT=arial][COLOR=#2c2c2c][B][/B][/COLOR][/FONT][/SIZE]
So i took my old fog box Version 0.28 ubuntu 10.04 and I am able to create a group of 1030 machines fine.
These machines were all registered with the fog service.
If I export this and the do a host import into a freshly installed .32 fog install on Ubuntu 10.04 I am only able to create a hostgroup with around 980 host. But I can then add host 10 at a time until i reach 1030-1040.
Is there hard coded limit somewhere I can change?
What is the proper way to get help reporting a bug?
Do we post it here, or should we still use the tracker at sourceforge?
I’ve got a few issues I’m trying to work out, but without knowing if it’s a one off issue, or a bug, it’s hard to make any head way.
Clean install on another machine, Ubuntu 10.04 FOG .32 [CENTER][FONT=Ubuntu][COLOR=#333333]1197[/COLOR][/FONT][/CENTER][CENTER][FONT=Ubuntu][COLOR=#333333] imported via host import csv.[/COLOR][/FONT][/CENTER]
[CENTER][FONT=Ubuntu][COLOR=#333333]Cannot create a group with all 1197 machines, just wanted to provide ab it more info here.[/COLOR][/FONT][/CENTER]
Thank you. I’m thinking about trying a re-install just to be sure it’s not that.
That would be great. We disable UAC with GPO, I would be more than willing to help test any changes that are made.
Does anyone have this working or any updates on it’s ability to work?
anyone have some input on this? I am able to create a group that is 940 computers in size but not over that it seems
[CODE] 3/22/2012 2:45 PM FOG::GUIWatcher Message found, attempting to notify GUI!
3/22/2012 2:45 PM FOG::PrinterManager Printer update was request from fog tray…
3/22/2012 2:45 PM FOG::PrinterManager Management level = 2
3/22/2012 2:45 PM FOG::PrinterManager Removing unwanted printers from host…
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\HP_Lab1
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\HP_Lab1
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\Science
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\Science
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\HP_Color
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\HP_Color
3/22/2012 2:45 PM FOG::PrinterManager Server Match: \printbox\journal printer will stay as is
3/22/2012 2:45 PM FOG::PrinterManager Adding new printers to host…
3/22/2012 2:45 PM FOG::PrinterManager 1 found on server side.
3/22/2012 2:45 PM FOG::PrinterManager Printer already installed \printbox\journal
3/22/2012 2:45 PM FOG::PrinterManager Setting Default Printer…
3/22/2012 2:45 PM FOG::PrinterManager Setting default for \printbox\journal
3/22/2012 2:45 PM FOG::PrinterManager Remaining: 6 Sending message to FOG Tray…[/CODE]
The steps i took were I added the new printer (Jounal), then removed it. and tried to re add it. This is the log from those steps.
Up until the printers is removed and you try to re-add it, everything is great. Once a printer is removed, the FOG service gets confused, and attempts to continually remove the printer. It will also not re-add the printer that was removed.
attached is the error that pops up with “Sending message to FOG Tray”
[url=“/_imported_xf_attachments/0/78_fog.png?:”]fog.png[/url]
[quote=“MikeyMike, post: 2252, member: 493”]Sorry about the delayed reply. I do not join the domain on my image at any time until after deployment. That way it gets a new unique machine SID on joining. Ive not had any issues with group policy this way and hence havent bothered with sysprep.[/quote]
If you ever use a KMS server on those machines you will still have problems. I was doing it the same way, and found out the GUID is likely the same on all the machines so they will not authenticate to the KMS server.
Sysprep is a MUST on windows 7 domain machines.