@JJ-Fullmer I am sure you are incredibly busy. I was just wondering if you had a few minutes to help me out with the FOG API and changing inventory values?

@george1421 said in Fog Server on Hyper V can not found from other Maschines:

@lerne-nie-aus I think I understand the problem (your english is good by the way no problem to understand).
yes it is it, you got my Problem. And i try to learn more English:)
Let me see if I understand your problem by me saying the problem using my words.

" I installed FOG on a centos server running as a hyper-v virtual machine. The centos server has 2 network interfaces. One network interface is connected to my business LAN and the other interface is connected to a dedicated imaging LAN (vlan inside hyper-v). When I installed FOG I tell it to use the dedicated imaging network adapter for FOG. I also tell FOG installer to create a DHCP server on the imaging network. FOG is installed OK and I can take image of a second VM connected to the imaging VLAN.
yes with VMs i have no problem to connect fog server, all are OK
So my problem is how to I image a physical computer using this configuration? "
Yeah that it the Point:)
If I understand this problem, you need to extend the imaging LAN outside of your Hyper-V server. Right now your imaging network is only inside hyper-v. You need to connect this internal vlan to a physical network interface on the hyper-v server then plug an external network switch into this interface. From there you can plug physical computers into this imaging network switch.

Could you pls explain litte bit more, how i do step by step?

Cause i tried all virtuel Switches and had no Success:(
I had already troubles while installing the Fog on VM, cause Fog need internet connections and i want a static ip and i had 2 Nics, i know it sound for an expert so easy but it is for me so difficult and i try to learn by doing:)

So wait for you Reply, ho i can solve this problem with my Hyper V VM and Pyhsical Computer.

Bye the way, i have no vlan on hyperv, just 2 nics, one private and one default(extern)

Thanks:)

@george1421 There wasn’t any doubt on my end…but I can imagine you read that and said to yourself “of course it did…”.

@chris_unit As I said, this is a legacy BIOS partition layout and we can’t move around partitions on that.

Sorry if you got my last message wrong. Simply deleting the first partitions won’t help. You’d need to move the still existing ones forward. But doing that in a rush could kill your Linux system. Depending on the boot loader used it might point to a certain sector on the disk.

With several people asking about a bootable ISO/transportable imaging I am wondering if there might be an “easy” solution to this. While I don’t have the time to add this to FOG I might still spawn the discussion so others can look into it.

I looked into building a FOG boot ISO some weeks ago. While possible to do I still think it’s more complicated to use than needed - see next bullet point. Converting our FOG images to something that clonezilla can work with should be possible. I have not looked into it yet but from what I know it should be possible I reckon.

Update: Forgot to add the link…

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