Posts made by Dustin

I don’t know about the rest of you, but the first time I had to figure out how to multicast, it was a pain in the butt! I couldn’t figure out how. Turns out the button is hidden in Task Management > List All Groups. This seems silly, so I added a second option.

Upload the attached files and you will be able to access multicasting by going to Group Management > List All Hosts.

I’m also going to add a unicast button to the host listing shortly. However, I didn’t include this because my host list files are a little messy right now. I’m working on making it so you can see which group(s) the host is a part of.

[url=“/_imported_xf_attachments/0/346_FOG-Group-Multicast.zip?:”]FOG-Group-Multicast.zip[/url]

Good work around for our one offs! Thanks!
[quote=“madeyem, post: 12134, member: 797”]If no kernel works:

• Take the HDD out of the machine, that can’t boot FOG
• Put it in a machine, that can boot FOG
• Assign the right image to that machine
• Choose “Shutdown after task completion” in task configuration
• Start task
• After task is finished, put the HDD back in the original machine
• Start the machine

This is a workaround, if you have generalized images (Sysprep for Windows).[/quote]

I’m at a loss because NONE of the Kernels will boot our new Lenovo E420 laptops. Still have MDT I can revert to for one offs but this will be difficult when having to do an entire lab.

Found the setting! Going into the menu right on the printer, disable BOOTP. I was unable to do this on the back-end setup site because the printer kept giving me a 503 error and HP Jetadmin wasn’t able to change it either. Originally thought that turning the reservation in DHCP to DHCP only instead of DHCP/BOOTP only would fix the issue, but it had to be turned off ON the printer. Grr…So all is good!

Made some progress. We did a complete reset on the printer and things started working. Still trying to figure out the exact setting causing the issue though. But at this point, we now know it’s with the printer settings and not our FOG server…which is awesome. Hope this helps someone else down the road. If we discover that setting, I’ll post it.

I’m curious if anyone else has had this issue or has any ideas how to remedy it.

We have over 150 printers which we use DHCP reservations to give them IPs. Everything worked fine until we turned FOG on by applying the Boot Server Host Name (option 066) and Boot Filename (Option 067). At this point ONLY the HP 4000 series printers would grab the IP address and DHCP server, but not the gateway. If I remove it from the scope options, it works again with the loss of FOG.

I have set the reservations up to do DHCP only thinking that maybe it was BOOTP messing it up, no go. The JetDirect cards in them are up to date on their firmware.

We do not want to program static IPs into each printer, especially when we will be re-IPing everything this summer…plus it’s just not ideal.

All other printers work fine (larger Sharp office printers), just the 4000 series that is having this issue.

Thank you.

Try a different Kernel for that machine. You can setup multiple kernels so if one kernel works on one model, but not another, you can fix that. The newest kernel necessarily work on all computers that the old one did from what I’ve seen.

Dell makes great business computers (I stress the business end end, not talking home PCs). Dell is also the only company to allow you to mass edit BIOs settings and other settings remotely. No other company has ever given that option. So if we wanted to change 2000 computers to boot to PXE first, with a flip of a switch we could. We have recently switched to Lenovo due to a big price difference when purchasing 300-600 PCs, as we do yearly.

Back on topic. I have a couple bugs to work out, then yes, I’ll post the files.

How are you mapping your drives? Are you mapping them then pushing the image up? Or are you letting Novell map them? If Novell is suppose to do it, nothing FOG does would stop that. If you map then push the image up, it’s possible sysprep takes them out maybe? I’m not sure.

What browser are you using? Chrome can be weird. You should have a side menu. Something is definitely screwy.

[url=“/_imported_xf_attachments/0/277_snip.PNG?:”]snip.PNG[/url]

Just discovered that FOG is ignoring setting changes in FOG System Settings. For example I changed FOG_PXE_MENU_TIMEOUT to 1 (second) and it still is starting at 5 seconds. Also tried to change FOG_PXE_MENU_HIDDEN to 1, menu still appears. Not sure how I broke all this. Again, only thing I’ve really done was installing phpMyAdmin.

No problem, glad it worked!

edit /fog/management/includes/hosts.edit.include.php
At the VERY bottom, after [PHP]?>[/PHP] add [CODE]<a href=“http://<?php print $host->getHostname(); ?>:8005”>CONNECT TO CLIENT VIA VNC</a>[/CODE]

Let me know if that works. I’m still working on figuring out how to edit the side menu.

Hi YuYo, So when you go into an individual host, you want it to show up as a side menu option? Does your VNC client allow you to click website links and know to open them? If so, let me know what you’re using and I’ll code it up real quick for you.

3.6.9 Caused issues. FOG would hang during deployment. No issues with 3.3.3. I was asking what kernel actually came with FOG (which makes sense since the kernel page isn’t automatically updated) in case a kernel issue caused this. Don’t believe it has since this is a after FOG is done deploying issue.

I’ve been testing for a couple of weeks now, finally have all my images built and now my deployments are no longer joining Active Directory.

They were working. The only change I’ve really made has been installing phpMyAdmin. FogTray is installed.

Computer is marked to join AD after imaging. username/password is right and has not changed. The odd thing is, the same computer, same image, randomly joined this morning. I thought the issue was randomly fixed. I imaged it again to test, and it didn’t join.

FOG log is attached. Thanks for any input.

**UPDATE: Correction, I also installed Kernel - 3.3.3 Core. I then went to the newest one, still didn’t work. Which Kernel comes with FOG 0.32? I went to 3.3.3 because it fixed hanging issues on our network.

[url=“/_imported_xf_attachments/0/275_fog.txt?:”]fog.txt[/url]

I work at a school and we manage several buildings. I’d like to not only break hosts down into groups (School buildings), but also rooms/students/staff.

School 1 > Lab 001
School 1 > Lab 002
School 1 > Staff
School 2 > Lab 001
School 2 > Lab 002
School 2 > Staff

Thanks!

Jackson, MI

Personally, I wanted to be able to move around FOG faster, so I ditched the icon menu and built a new one. Also, here’s my custom PXE menu.[ATTACH]273[/ATTACH][ATTACH]274[/ATTACH]

These are on my test server, the real one is not a 192.168.x.x network, haha.

[url=“/_imported_xf_attachments/0/273_CustomLayout.jpg?:”]CustomLayout.jpg[/url][url=“/_imported_xf_attachments/0/274_531570_10100294349278887_1028605766_n.jpg?:”]531570_10100294349278887_1028605766_n.jpg[/url]

Ahoy. We are move away from MDT and going to FOG. If I install Windows 7 fresh, everything works smooth from creating a FOG image to deploying that image. However, I’d prefer not to remake tons of MDT images from scratch. I MDT’d a computer, tried to push it up to fog but an error id detected while running resize test. Then the next error after that is that “New size can’t be bigger…” which appears to be talking about the second partition that MDT creates.

I’ve deleted the partition and set the OS as active, computer boots up fine after. I then tried to push up the image, this time it will push up, but in RAW mode, so it copies the entire 80GB hard drive instead of just the 12GB that is in use. Image is set to Single Partition (NTFS Only, realizable).

Any way to avoid having to recreate all the images and have it capture as NTFS instead?

Ubuntu 12.4
FOG .32

Thank you.