@michael-steiner said in Windows 10 Imaging over low BW Internet/VPN:

What ever became of this thread and to your knowledge did deployments ever take place

I don’t know if this deployment ever took place. From my perspective the OP of this thread has two different issues.

Imaging over a low bandwidth link Imaging over the internet.

For imaging over a low bandwidth link, the real solution with FOG is a mobile deployment server running on a raspberry pi.

For imaging over the internet, I’ve been thinking about this to test with openvpn. The FOS Linux client would run the openvpn client and on the FOG server the openvpn server. Then tunnel all of the communications over the openvpn link. The issue is remote pxe booting. That can’t/shouldn’t be done over the internet. But if we switch to USB booting on the remote end then it might be possible. There are still several hurdles to overcome doing this and I wonder if a different imaging solution would be a better choice like clonezilla on a usb device.

I think the Problems root is that my System, it is manage by Plesk. Plesk has Plesk specific packages and those changed the system dramatcally. I had some other issues with other installer as well. I would try a fresh install and executing the script on the fresh maschiene and hope it wont stop at the same point.

Thank for the help

Turtle

Thanks for your answer, I didn’t have DHCP server. My network is an internal network with virtualbox only. Fog is working but I have to write for each reboot in this thing c0d3f6a5-06d4-4f45-81ff-cf047909e620-image.png
When I wrote the ip of my fog server there it’s working normally

@wayne-workman Thanks you for your aid! Those Powershell scripts helped me. For those in the future with the same problem as me.
{
“name”:“test-api1”,
“description”:“test-api1”,
“storagegroups”:“2”,
“osID”:“9”,
“path”:“test-api1”,
“imageTypeID”:“1”,
“imagePartitionTypeID”:“1”,
“isEnabled”:“1”,
“toReplicate”:“1”,
“compress”:“6”,
“imagemanage”:“5”
}
That’s how the body should more or less look like

Thank you for your swift reply!

I followed the “How to guide” https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy, however, I didn’t configure a lease time as on the guide it didn’t include this.

After turning on a lease time the client got an IP and I was able to image all my machines.

Thank’s again for replying so quickly.

Ali

@sebastian-roth said in MAC address:

I tend to mount new HDs in /images to make things a little easier but let’s discuss this in a new topic.

Thanks for your response.

If it helps:
I was missing the path to HDD/images when doing “showmount -e x.x.x.x”.
However my etc / exports file were good …
I had actually forgotten to restart /etc/init.d/nfs-kernel-server.
After, it’s ok

We can close the thread

@tom-elliott sorry! I meant last deployed date. Is there a way for me to see per host when it was? I am just looking to get an output of that via some sort of command line. I use Powershell currently with the FOG API.

@esmatos You might provide more detailed information on what steps exatly you took and what error occurred (pictures of error on screen!!). Otherwise we won’t be able to help.

@tehcnique DNSMASQ can be installed on the same server as FOG or on a different linux server. It will work well in either case as long as the target pxe bootng computers are on the same subnet as the dnsmasq server. If the pxe booting computers are on a different subnet then you must make a change on your router to make it work.

What configuration file are you using for dnsmasq? It would be helpful if you put it in your post. DNSMASQ can do a lot of things so the configuration file is important to have it correct.

@tom-elliott said in How to use QNAP NAS for image storage?:

@exworker9to5 Or this:
https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node

https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS

https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/1

Thank you!

@jona will you show us the output of this command
ls -la /var/www/html/fog/service/ipxe it almost sounds like your install did not complete correctly. You should have a file called init.xz that is the virtual hard drive for the kernel bzImage. Your kernel panic is saying the kernel doesn’t understand the virtual hard drive.

Where did you get the bzImge you added to stop the first error?

@tom-elliott Hi, thanks for the reply.

Im getting the following errors : in CMD :

curl: (6) Could not resolve host: NjhmN2VkNmFiZWVmZGQ4NjNhNGYyMzAwYmEyZGY4MWMwYzdhZGFmZjQyZjI0Yzc0Mjc1NzNmYWE1MjVlMzBjODM5MTE2YjZlODJhNjNhZmFiMzg1NGU3NmM1MjQzMDc4M2FjYTU0NGExMWQ2NWQxxxxMWJlZjQ’
curl: (6) Could not resolve host: MTM3OWM1YjczZjI3OGZlNmVjNjk0MWQwYTUzOTljNTFjOTc0YmE0OWRiMjQ5MzhhOGE0ZGM4ODRjZjFkOWI2MzI3NjNlYzMxYTY4MWJhNjEzOTFmMWY3OTEwMDJmNTUwM2Q1NTNjMjlhZTA5NmQ3xxxxNDU’

and in powershell console :

Invoke-WebRequest : Cannot bind parameter ‘Headers’. Cannot convert the "fog-api-token:

But nevermind, thanks for the support but im throwing in the towel. Guess this is just 1 of those things thats to complicated for me. Hoped it was simple, but im getting errors left and right. Thanks for your time. Dont waste anymore on me 🙂

@cwgcad As George said this looks like a response packet. With source port 80 this must be the case I would think. So please figure out what the other IP is!

Matching the alerts with httpd log in the FOG server is a great idea.

You didn’t mention your process, but if you are using sysprep and have your reference unattend.xml file in the right locaiton it should work.

Look over this thread, it give you a sanitized unattend.xml file as well as the sysprep switches.

FWIW I use the unattend.xml file to name the PC and connect it to the domain and not the fog client, so I know this route works.

@aheerds said in "Enabling apache and fpm services on boot" failed:

I got much further in the installation by changing to debian:latest and not ubuntu:20.04.

Now I am stuck at this :

insserv: FATAL: service mountdevsubfs has to exists for service hwclock insserv: FATAL: service mountkernfs has to exists for service procps insserv: exiting now!

Currently working on it, but FOG has started and it’s running. But there is still something wrong …

@matthieu-jacquart Sorry I can only write in english.

Its best if you DO NOT connect your mother/master image to active directory before you capture the image. I’m sure my environment is different than you, but we use MDT to create the golden image, sysprep then capture with FOG. At no time is the golden image connected to AD before capture with FOG. The first time the target computer image is connected to AD is on the final hardware.

@cello said in Client should deploy everyday an do a autostart:

Why can’t I synchronize the computer and then immediately boot from the hard disk? The menu always appears and I then have to select the option to start again.

Which menu do you mean? The FOG boot menu has a default option to chainload the OS from disk, pretty much what you want from what I understand.

@george1421 well no also is an awnser 😉 I really appriciate the time you spend on it for me! Thanks a lot!!

@ntex
Nevermind, I’m too tired clearly, fixed the original configuration has another prefix= to empty.
So this line was creating a conflict with one above.

3195ca99-f8a5-45c8-b390-a2ad984f0f78-image.png

Time to rest for today. 😊 long day, thanks anyways!!