@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.

@Tom-Elliott Its works! I’m with RC12 version with dev-branch. Thank you very much for your help.

Running Version 1.4.0-RC-12 SVN Revision: 6069

@Tom-Elliott @ftgjason Sorry missed notifying.

Tom You are the best.

I installed 1.3.5 and it is now working.

Thanks!!!

@Tom-Elliott Thanks Tom, I had the same problem and this fixed it for me!

I have solved my problem. The first problem (connection timeout) comes of the switch, I have change for a router and it works ! The second problem, I have reinstall Windows 10 and it works, I can capture my physical machine !

Thank you for all your help !

@george1421 we moved the conversation to IM since turn around time was much quicker.

We got dnsmasq setup with all of the configuration required to pxe boot in a home router environment. DNSMasq probably won’t be needed in a business envionment since a business will typically have a dedicated dhcp server where you can set dhcp options 66 {next-server] and 67 {boot-file}. In the case of the home routers, dnsmasq will provide these missing values.

At this time the OP is able to pxe boot the VM target computer and was in the process of registering the VM with FOG.

Marking topic solved.

@Tom-Elliott there were few corrupted files on windows and fixed them, and after those it worked fine

That solved it @Tom-Elliott thank you very much. Life saver!

@Tom-Elliott I see. Ya it should have at least told me what interface after the “from”, didn’t realize that until now. Thanks Tom!

@Tom-Elliott will try a reboot. If you think another boot file would be better, please let me know.
Thanks man. You are extremely helpful. Have a great day!

@juanflis Please check your /images/ permissions.

Please make sure they’re sudo chmod -R 777 /images and sudo chown -R fog:root /images

@EspenU yes.

@Psycholiquid I don’t mind, I use VMWare myself 🙂

Yes, that portion seems to be working now. On to the next bug…

@Quazz @Tom-Elliott I set the task to capture and the progress bar on the desktop computer goes all the way though
Upgrading to the latest ver worked.

Thanks

A while ago I wrote a proof of concept tutorial for turning a Windows server into a FOG storage node. https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-proof-of-concept-blog

You can not add additional space to your fog server by sharing disks on another server. This method is asking for problems. But you can turn another server into a FOG storage node (so to speak). By using a fog storage node and a the fog location plugin you can train all of your computers to image from the storage node instead of the master node.

@Tom-Elliott

The IP the machine is getting both in PXE and when selecting any menu option is 192.168.91.242… within the specified range for that vlan. FOG server is on 192.168.91.243. No, the nic is an onboard broadcom nic on a dell optiplex 580

thanks. I emptied the drivers folder and it went through - perhaps the extra script information will assist me to find out why it failed when i had drivers in it. let’s mark this resolved.

@mahir I recommend you also update your IP in /opt/fog/.fogsettings (and other relevant IPs) so that when you update FOG it can put everything the way it’s supposed to be.