Posts made by noelpd

@george1421 said in LDAP Plugin - ID Must Be Set To Edit Error:

For people to be able to login using ldap they must be listed on the group identified by admin group field.

They are, but the login is still not working.

@jason-shoemake This fix let me successfully add our LDAP. Moving forward, how do I make sure that people can log in with it? Will a reboot be required? Anything else that needs to be configured or installed?

Server

• FOG Version: 1.4.4
• OS: Windows 10

Client

• Service Version: N/A
• OS: N/A

Description

I was messing around with Open LDAP plugin. When I go to save my settings, I get the error message of “ID Must Be Set To Edit”. Any idea why it is giving me that error message? Thank you.

Server

• FOG Version: 1.4.4
• OS: Windows 10

Client

• Service Version: N/A
• OS: N/A

Description

Hey Everyone! I am currently working on getting Windows 10 deployed with our FOG Server. I currently have a functioning Sysprep package for my Windows 7 image that works. However when I use that package on Windows 10 it does not work. I am sure that is due to drastic changes from 7 to 10.

Basically I am looking for feedback as to what you guys are doing to build images in Windows 10 and upload them to your FOG Server. I am sure there will be follow up questions for information I am missing in this initial post. I am just at the point of banging my head into a wall on getting this working, haha.

@wanderson This worked for me. Thank you. Had to edit the line below document root since i had my php file in html and not fog.

@Tom-Elliott

The apache2 folder location does not exist on my server.

@Tom-Elliott

<?php
header(‘Location: http://10.205.1.2/fog/management/index.php’);
die();
?>

@george1421 Yes, I had a redirect setup. See the contents of my file below…

<?php
header(‘Location: http://10.205.1.2/fog/management/index.php’);
die();
?>

Recently updated to the latest stable version of 1.4.0. After going through the following process

1. Yum Update
2. Git Pull
3. Run 1.4.0 Installer/Upgrade

I get a blank white page when trying to type the IP of the FOG Server Directly. However, When I type the full address it works fine getting to the GUI Login.

I double checked my /var/www/html/index.php file and everything looks good and appears to be pointing to the correct location. Any ideas?

@george1421 So rebuilding a custom bzImage file will not effect it at all? I think I am just getting confused between what needs to change with our DHCP Server versus the FOG Server itself.

@noelpd said in HP 210 Netbook (RealTek NIC) - DHCP Failed on PXE Boot:

@Tom-Elliott One problem we may have with 8168 driver is that even when trying to build a custom Kernel, all the RealTek NICS are supported except for the 8168. It is not even an option to include in the build

Edit: This is with the latest 4.9 Kernel base from Linux directly.

@Tom-Elliott One problem we may have with 8168 driver is that even when trying to build a custom Kernel, all the RealTek NICS are supported except for the 8168. It is not even an option to include in the build

@Tom-Elliott The boot file I am having changed on our separate DHCP Server. Not the FOG Server since we are not using it for DHCP Addresses.

@george1421 I have a whole stack of the HP 210 8168 NIC laptops that are not working. I have updated BIOS and NIC Driver on them as well. Still no go. It appears to be a hardware issue with the 8168.

@george1421 Changing it to ipxe.kpxe is not working either. Still works on the RealTek 8136 NIC but not the 8168

@george1421 Ok, so the only place we should ever have to make that change is on the DHCP Server? Nothing to do with FOG? So is that setting on FOG only make a difference if we were using the FOG as a DHCP Server?

@george1421 Ok, So i will have our network admin change it to ipxe.kpxe. On the FOG end do I need to change anything? The only way i knew how at the moment is to change the .fogsettings and then re-run the installer. Is there a place I can manually change it on the FOG Server?

@george1421 Also just an interesting note. It definitely appears to be an issue with the NIC. I just tried another computer that is the same model and it worked without issues. Took a deeper dive into the specific RealTek NIC they are both using and one HP 210 (Non Working) uses the 8168 and the HP 210 (Working) uses the 8136.

@george1421 dhcp net0 did not work. I will let you guys know the results of the undionly.kkpxe, one questions I had was after I have our network admin change it to the .kkpxe, I wanted to double check where I change it on FOG Server. What I have been doing with these tested changes is changing the .fogsettings file and then doing a re-install.