SOLVED!

Solved it by adding the line RewriteCond %{REQUEST_URI} !^/utils to the VirtualHost block at /etc/httpd/conf.d/fog.conf so it looks like this now:

<VirtualHost *:80> <FilesMatch "\.php$"> SetHandler "proxy:fcgi://127.0.0.1:9000/" </FilesMatch> ServerName 10.0.0.1 ServerAlias fog.servers.domain.io DocumentRoot /var/www/html/ RewriteEngine On RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK) RewriteRule .* - [F] RewriteRule /management/other/ca.cert.der$ - [L] RewriteCond %{HTTPS} off RewriteCond %{REQUEST_URI} !^/utils RewriteRule (.*) https://%{HTTP_HOST}/$1 [R,L] </VirtualHost>

@george1421 hi and once again let me thank you for your time.
I just managed to get over the problem and disabled the HTTPS redirect for the /utils path.
SystemRescue loaded just fine.

I would suggest, maybe, adding this rule by default when we enable SSL on the fog server, and having therefor a specific path to put boot files that could be blocked by curl’s certificate check.

@bryan-wright said in Can't add snapin to group:

I was expecting the snapins to be attached to the group, but looking at this code in group.class.php, it appears that the snapins just get attached to each MEMBER of the group:

That is not a bug. That’s by design. Search the forums for “persistent groups” to understand that FOG’s concept of a group is not what you think it is. Groups are more or less a too to push settings to all the hosts being member of that group.

On the other hand I am running FOG 1.5.9 here and I do have the snapins listed when I go to Group -> Basic Tasks -> Advanced -> Single Snapin.

Your can find the full list of changes between 1.5.5 and 1.5.9 on github: https://github.com/fogproject/fogproject/compare/1.5.5..1.5.9

We can’t support or even fix older versions of FOG I am afraid. So please update to 1.5.9 and let us know if you still see the same issue.

@lambo Just wondering if you are still looking into that issue or got it solved at some point?

@sebastian-roth Yeahh, it works ! Thanks again !

@george1421 Okay sounds good. I am checking this page frequently so if you need more from me just let me know!

@george1421 mainly I wanted to select raid on so that if a laptop hass issues and looses bios settings it will still work 🙂

Example I have a couple of HP laptops that for some reason if left not being used for a couple of days they loose bios settings even if they have battery life :S

@Fog_Newb Notification loads for me in Firefox 95.0.

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@tom-elliott sweet! Thanks Tom!

@tesparza

I made the same thing with this doc : https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@kilua4650 Can you explain how this is related to FOG?

@doctrg Its always best to migrate same version to same version. The issue is the database since there has been many changes between 1.5.5 and 1.5.9.

On your new fog server go ahead and install 1.5.9, then bring over the 1.5.5 database and raw image files. The first time you attempt to access the web ui it should detect and older database and try to upgrade it. It will take you to the db upgrade page instead of taking you to the login page.

@lerne-nie-aus said in After Deployment - No Configuration Methods succeeded:

So tell me pls how i can solve this.
What you mean with cold startup?

I don’t know how to solve this with VirtalBox, I’ve only seen it before. The problem is specific to VB.

Warm boot == just restarting the OS without powering off the virtual machine.

Cold boot == is powering up the Virtual Machine from a switched off state.

I did find a reference to this in the FOG Forums: https://forums.fogproject.org/topic/9700/solved-unable-to-boot-fog-from-pxe-with-a-vm-virtualbox-guest

@sebastian-roth hey thanks for your quick Help.

With “Grub” Options in Host-Bios-Exit-Typ work all fine.

You are great.

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