@kmonroe79 said in Starting cmain( )...: This now brings my screen to black with flashing cursor :( I can’t seem to find a happy balance Using which settings exactly??

@marted said in FOG Client cannot communicate with the server (token.data missing): I changed the value 0 to 1 in settings.json and started again the fog services Do you actually use FOG with secure HTTPS (installer run with option --force-https)?? Before was just that , now after the message for invalid MAC it says responds successfully… Not really. Take a look at several places in the above logs and you find: 2019-12-12 09:18 Middleware::Communication POST URL: http://192.168.149.43/fog/management/index.php?sub=requestClientInfo&authorize&newService 2019-12-12 09:18 Middleware::Response Invalid MAC address format 2019-12-12 09:18 Middleware::Response Success Not sure if this is related in your case: https://forums.fogproject.org/topic/7032/ignore-tunnel-interface-on-client Try adding a client MAC filter on 00:00:00:00:00:00:00:E0. Don’t think this is needed but doesn’t hurt either. As well take a look at the apache and PHP-FPM logs to see if there are any related messages when the fog-client connects. One other thing that just came to my mind. Is the host registered in the FOG web UI? Please go to the host’s settings and press the bit orange “Reset Encryption Data” button if it’s there.

@craig-stephens Please provide the full replication log you find in /var/log/fog/... on your master server.

@TOXYKILLER Well I would expect that menu if you haven’t told FOG what to do. I take it you have registered the host with FOG by either doing a quick inventory or a full inventory. Once that is done there will be an entry in the host management view. From there if you want to capture an image you need to create an image definition and then go back to the registered computer and link the registered computer with the image definition you created. Then finally on the host definition create a capture task and schedule it. When you reboot the computer and pxe boot it, the target computer will check in with the FOG server and since there is a task, start imaging the computer.

before you capture with fog either use sysprep to power off the computer or issue shutdown -s -t 0 to power off the computer. In windows 10 the shutdown button is really a fancy sleep mode and not really a close everything and power off kind of shutdown.

@kburns Yes, George is probably right. Take a look at /tftpboot/default.ipxe text file and put in the correct IP. It’s important you read this wiki artikle: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

@ITCC Switch your DHCP config to point to ipxe.pxe instead of undionly.kpxe and the issue should go away.

@mikmatcr ok what I would do is run fdisk from command prompt sudo fdisk /dev/sdb d p 2 d p 1 w e Note it may be q to quit and not e to exit. I did that from memory. That should delete both partitions and write them back to the disk. Now you can start with the instructions https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition up to and including step 7. That will create a new partition and then format it. Once you have it formatted then we can go through the steps to copy the files over and then remap the drive.

@renanserrou Looking at the client log again… I See these MAC addresses: 02:00:4C:4F:4F:50|38:EA:A7:19:19:AF|0A:00:27:00:00:12||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0 One seems empty (||) and I see a couple of what are probably virtual network adapters.

@fogQuestions said in Can fog deploy images to a single partition?: However, whenever I deploy images to from my FOG server to my computer, the iPXE software gets wiped by my image. May I ask why you have iPXE installed on disk at all? Usually this is send to the client on PXE boot on the fly and there is no need to have it on disk. Can fog deploy images to a single partition? If so how? Yes you can define an image in the web UI to capture/deploy only one single partition. The problem with this is that on the target machine you already need to have the correct partition layout set from an earlier deploy as we don’t touch that but simply deploy the contents of that one single partition set in the image definition.

@franck25 said in How to boot uefi on ltsp server via ipxe fog: I find myself facing a problem of boot on my server “ltsp ubuntu” Please take a picture of the screen where we see what goes wrong and post that here.

@Shiro228 We didn’t have the time to implement printer management on Linux yet. You are more than welcome to work on this.

If this is accurate shouldn’t broadcast be 192.168.1.255?

@jhumpf Which version of FOG do you have installed? Can you please take a picture with a bit more of what you see on the screen. I don’t really understand where you are in the web UI to get this picture.

I believe the wiki page is based on my tutorial page: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server If you use my dnsmasq configuration file exactly then it will work. In my config file make sure you replace <fog_server_IP> completely with the IP address of your fog server. It appears several places in the config file. Understand out of the box dnsmasq will only work when the pxe booting client and dnsmasq server are on the same subnet. If they are on different subnets then you will need to update your dhcp-relay/helper service on your subnet router. Add the fog (dnsmasq) server as the last dhcp server in the dhcp-relay list. This will make the dnsmasq server aware of the dhcp requests from other subnets. If you still can’t get it we can debug the dhcp/pxe boot process pretty easily.

@hauser said in Issues using driver path in sysprep - Windows 10: It may be that this method just doesnt work any more as I am fairly unfamiliar with the changes in sysprep of Windows 10, but I also was curious if this is even the best way to add drivers to the images. You are rigth, M$ broke this handy feature of defining where the drivers are. What I’ve found to be reliable is using the pnputil command in the setupcomplete.cmd batch file to load in any remaining hardware specific drivers. So for my campus I have 2 golden images (one bios and one uefi) for 15 different hardware models, where the hardware specific drives are transferred to the target computer using a post install script, then I run the pnputil program to load the drivers. ref: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed/4

@Gilberto-Ferraz Try this running this PowerShell script as a snapin. What it does is moves the first non-windows boot selection to the top, in your case it will move “IP4 Intel® Ethernet Connection I217-LM” to the top of the boot order. Works for me…

@egorhan Must have been blind when I looked at this the first time. Now I see something that makes me wonder. Search Base DN: ou=administrators,ou=pm_users,dc=parimatch,dc=local Bind DN: cn=administrator,ou=pm_users,ou=administrator,dc=parimatch,dc=local The OU pm_users seems to be on different levels of your LDAP tree. That doesn’t make sense to me. Please double and triple check all the settings. Better you copy & paste the settings from some LDAP browser tool instead of typing those in.

@amc123 If this is a relatively fresh install of FOG I’d start from scratch (really by re-installing the OS). Then use the latest version from github dev-branch which has the fix for VSFTPd on Fedora 30 already.

@roseward Ok so we are going between models of computers. Also when you removed the network adapter and rediscovered it it still fails. So at this point I’m thinking windows driver. Because the same driver would be reinstalled. The network adapter is functional because you were able to image with FOG, so the hardware and network infrastructure probably can be ruled out on this issue. So on this computer what network adapter is installed (version reported by windows)? Also get the vendor and hardware ID from the driver applet. Also note the driver author and version (i.e. GigaByte Brix i7 LOM driver). You may need to load a model specific driver because the one that windows detected may be close but not exact.