Thank you for clarifying this. I strictly use fog for imaging and joining multiple lab computers to the domain. Kudos to all that make this possible.

Thanks James…

@jpaul Ok that error is saying it can’t find the image to deploy. (btw: excellent picture having the kernel variables will help to debug this issue).

Can you post the output of this command. You will need to key it into the linux console of the FOG server. ls -la /images

@jpaul As a test place a dumb (unmanaged) switch between one of the troubled target computers and the building switch and try it again.

If this works, then you need to get with your networking admins to check the network switches to ensure that (if) spanning tree is enabled, you are using one of the fast stp protocols (RSTP, MSTP, fast-STP, or what ever your switch port manufacturer calls it).

@joe-schmitt That fixed it. Thank you… Sometimes the most obvious gets overlooked.

James P…

But, back on your original post. You can either define the VL Key in the proper field for the host, or you can define it in the global key configuration in the fog configuration->AD (I believe). You can also use the FOG group set function to assign a key to a group of existing computers. This will update the key in the individual host management page.

As you can see there are a number of ways to go about doing what you need.

@jpaul You’ll most likely have lots of problems using 1.2. I recommend you update to 1.4.4 - instructions are here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@jpaul said in network printers not coming in when imaging with fog 1.2.0:

ill not populate even after all the forced group policy updates per machine . Has anyone found the the problem might be with fog imagining or is it just something wrong with our group policies,

@jpaul it sounds like an issue with your GPO. Is there also a reason why you just started using 1.2.0? It’s fairly outdated and doesn’t support newer operating systems (like Windows 10) very well.

Thanks Tom. Just the switch on the AD Username did the trick. Thanks for your help so quickly…

James

@jpaul 0.32 is VERY old, but I’m glad you got it working.

@Wayne-Workman I don’t know when the global max size stopped being used, but I’m fairly certain it was removed when 1.0.0 released. (more or less).

I’ll look through the code to verify if anything is using it anymore.