Have you enabled snapins universally?
Have you enabled snapins for the machine that you have sent the snapins too?

My school district has 20 different FOG servers. I have been tasked with the job of gathering information from all servers and compiling it into a single location for reporting to my boss. So far, i have been fairly successful; however, I have run across an issue that has me confused. My report consolidates data from the inventory table and the hosts table and several records are showing hostName as NULL. In some cases, there is a duplicate inventory record, in other cases, there is an inventory record with no host record. My report show 8,519 total computers; however 1,214 of those are missing hosts table information.

We started using FOG at version .28. Some FOG databases have been exported and moved to new servers. Some clients were imaged in one building, then moved to a different building and deleted from the first buildings inventory.

What are some scenarios that could cause this?

Current theories:
FOG client is pointing to the wrong server
Client was imaged in building A and then moved to building B and the client was not changed
CLient was imaged using Ghost, but had the FOG client installed on it

We solved this by creating 2 snapins. THe first copies the cab file to programs (x86)/fog/tmp. The second runs the java msi.

Did you ever find an answer for this. I am finding that the java install exe file wants to install the MSI and a cab file into the user/username/appdata/locallow/sun/java folder. I assume there is no user when FOG goes to run the install; therefore, the snapin fails since there is no folder to install to. If you deploy the MSI, it wants to use the cab file found in FOG/tmp. Which is not there, so again it fails.

[quote=“Neil Mason, post: 1494, member: 545”]I’m getting exactly the same problems when imaging Lenovo E520 laptops. PC’s upload their image to the FOG server no problem, and when I tell the host group to deploy the image to the other PC’s, it works fine. However, when the PC’s re-boot, it’s stuck in the boot loop. If I escape the PXE client, the Windows 7 OS loads fine.

ANy ideas to why this might be happening? I’m really impressed with the capabilities of fug thus far, if I could just tweak the minor problems that I’m having, it would be awesome.

Thanks for any help you might be able to offer.

Neil Mason[/quote]

We have found that reverting back to the PXELinux.0 file that came with version .28 has resolved our boot loop issues.

I would like to see the imaging log include computers that were multicast as well as computers that were unicast.

That worked.

Thanks

A coworker has done something and I can’t figure out how to correct the problem. Here is what I know.

1: He attempted to image a lab, but had a problem
2: Some computers successfully imaged, some did not.
3: He deleted all the machines from his inventory and decided to re-register everything
4: 1 machine that did not complete the image will not allow him to re-register, instead, it it trying to run the previously mentioned task which has been deleted.

My question:

How do I kill the task that is trying to run? How do I get this machine registered?

Thanks for your help.

We are experiencing the same issue. The thinking at the moment is that FOG is rebooting the computer before the setupcomplete runs. I am going to try changing the check-in time from 10 minutes to 20 minutes. I won’t get a chance to test this until tomorrow.

TIMEOUT of 30 or 3 seconds is probably what you want. If you hit the down arrow while the fog menu is displayed, it will not move on to the secondary boot device. A short display time for the PXE menu, insures that the startup process is not delayed too long.