i was able to locate instruction. https://wiki.fogproject.org/wiki/index.php?title=Migrate_images_manually#Image_Definitions please mark this question as answered.appreciate your quick response.

@george1421 Thank you for your answer. You can close the ticket. I will do your technique. Best regards.

@george1421 said: adapter was handled by the cdc_ether driver Got to be careful with this. I do remember we have had issues with this cdc_ether driver in the past. Please search the forum for this. I think we even tossed it out of our kernel builds for some reason…

@Quazz Perfect, You resolv my problems. The first step OK : Web Interface -> Users -> List ALL Users -> fog -> Change password The second point OK : Edit the file /var/www/fog/lib/fog/config.class.php: nano /var/www/fog/lib/fog/config.class.php define (‘DATABASE_PASSWORD’, “MdpROOTsql”); The FOG server is still functional in the Web and the database requires a password to enter! Everything is good for this open ticket. I thank you for the efficiency of your response. Continue like this. Best regards.

Thanks All!.. Solution has worked perfectly!

Hi Guys Two quick updates on this: This ipxe7156.ipxe also seems to be working for some Dell machines we have. To make Hyper-V Generation 2 VM’s to PXE boot UEFI correctly; I had to add a new PXEclient mapping of PXEClient:Arch:00007:UNDI:003000 for the ipxe7156.ipxe boot file. (Secure boot should also be disabled!) (Tested with FOG 1.5.2) Revised Powershell Code: import-module dhcpserver $DHCPserv = "DHCP-SERVER-HOSTNAME" Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 2" -Type Vendor -data 0x505845436c69656e743a417263683a3030303032 -Description "UEFI Architecture Type 2" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 6" -Type Vendor -data 0x505845436c69656e743a417263683a3030303036 -Description "UEFI Architecture Type 6" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 9" -Type Vendor -data 0x505845436c69656e743a417263683a3030303039 -Description "UEFI Architecture Type 9" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7" -Type Vendor -data 0x505845436c69656e743a417263683a3030303037 -Description "UEFI Architecture Type 7" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7 UNDI 3016" -Type Vendor -data 0x505845436c69656e743a417263683a30303030373a554e44493a303033303136 -Description "UEFI Architecture Type 7 UNDI 3016 (Surface Pro 4)" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7 UNDI 3000" -Type Vendor -data 0x505845436c69656e743a417263683a30303030373a554e44493a303033303000 -Description "UEFI Architecture Type 7 UNDI 3000 (Hyper-V)" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE" -Description "UEFI IPXE" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 7*","PXEClient (UEFI x64) 9*" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE32" -Description "UEFI IPXE32" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 2*","PXEClient (UEFI x64) 6*" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE7156" -Description "UEFI IPXE7156" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 7 UNDI 3016*","PXEClient (UEFI x64) 7 UNDI 3000*" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE" -OptionId 67 -Value "ipxe.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE32" -OptionId 67 -Value "i386-efi/ipxe.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE7156" -OptionId 67 -Value "ipxe7156.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -OptionId 67 -Value "undionly.kpxe" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -OptionId 66 -Value "10.20.30.40" -ComputerName $DHCPserv

@george1421 said in Adding storage nodes: For your esxi server, how many network links does it have into your networking infrastructure? 2? or is it 10GbE? The ESXi host is on a segmented network and has 4 physical adapter connections but I don’t think all of them are being used. I’m pretty sure the number is two because I’ve been talking to our network team about the possibility of going to 10GbE which they say will be a possibility down the road but not right now. I’ll definitely test deployments thoroughly before pulling the plug on the current/physical node. Thanks for the tips about adding a LAG group and/or changing the location of /images, good to know about those options.

@mpatel said in Imaging over WAN: now how do i go about transferring my exiting fog setup to new box including images that i have. May I ask you to open a fresh topic on this question just so don’t mix things up too much and people can find things more easily in the forums. Take a look at export/import the image definitions and we’ll give you more of the details in the other topic. Marking this as solved.

@TBCS Mmmmmm cookies… I’m glad you have it worked out and it was simple enough to just update your firmware (which you probably should have done anyways).

You can do it XD First you must to know the name of the System product want to deploy. Go to reports -> Inventory Reports If you have the lastest dev-branch version, you can filter by System Product. If you don’t have this last version, in the report will appears all the hosts Copy the System Product string that you want to deploy Go to Host menu And paste the string in the search box Create a new group with the results

@vervoordeldonk What we are finding is the mainstream hardware vendors (dell, hp, lenovo, intel nuc so far) do an excellent job of making each system unique so coming up with an alternate method of identification isn’t a problem. The issue is like the system below System Manufacturer xxxxr System Product TMB-3010 System Version R0M0 System Serial Number To be filled by O.E.M. System Type Type: Notebook BIOS Vendor American Megatrends Inc. BIOS Version 1.00/636G00WPC76508 BIOS Date 05/06/2016 Motherboard Manufacturer xxxxr Motherboard Product Name WEB-889A/WEB-889AA Motherboard Version R0M0 Motherboard Serial Number To be filled by O.E.M. Motherboard Asset Tag To be filled by O.E.M. CPU Manufacturer Intel® Corporation CPU Version Intel® Core™ i5-3210M CPU @ 2.50GHz CPU Normal Speed Current Speed: 2500 MHz CPU Max Speed Max Speed: 3800 MHz Memory 3.74 GiB Hard Disk Model 2.5" SATA SSD 3ME3 Hard Disk Firmware S15A19 Hard Disk Serial Number xxxxxxxxxx000025 Chassis Manufacturer xxxr Chassis Version Chassis Serial To Be Filled By O.E.M. Chassis Asset I put the lower case “x” in just to mask a few values, but as you can see there is nothing unique on this system from the next system from the same manufacturer other than the disk serial number. I have a few examples of other systems that are very similar. One solution is to go ahead and use the mac address as part of the mix for system identification. In that case we would be no worse off than we are today by only using just the mac address. We also want to bring in the asset tag value so at the very least if FOG can’t identify the system the IT tech will need to populate that field to create a unique ID for that system. (sorry I’m a bit thinking out loud here)

@daguilar if you no longer have the option of exporting from the old server, you’re probably best off just creating each one manually though the interface. just make sure the “Image Path” field and format info matches the info that goes to the files.

@Tom-Elliott yes 10.1.10.2 is the new server’s ip. I’ve also tried moving the contents of fog.postinit to a dedicated patch.reg script, set to 755, and called from fog.postinit as mentioned in another post detailing this and the fog.postinit instructions themselves with no success: #!/bin/bash . ${postinitpath}patch.reg Updated the kernel too. No joy. Also , while in debug mode on the client , I attempted to echo ${postinitpath} and it returned a blank line.

@Sebastian-Roth Thank you for your advice. What you said seemed to be my issue. All I did was uncomment option routers and replace the IP with my DHCP server IP. I can get into the FOG splash screen now. Thanks!

@Sebastian-Roth Yes of course. The networking team will let me know.

@imt_fog If you boot the machine in question in debug mode, you should be able to run parted -l manually and check the flags. I don’t think this is caused by such, however, but interested in seeing the results. Worth noting that partitions that go through the checks but fail to resize get marked as fixed size as well (to prevent issues during deploy)

Hello @Fernando-Gietz, thanks for the awesome help and support, it works now as needed. Is there something I should be aware or edit in our openLDAP implementation to make the plugin work correctly without editing the /var/www/[html/]fog/lib/plugin/ldap/class/ldap.class.php file? Ciao, Antonio

@Jedi exactly this.

@airsine Thanks for posting the issue. We don’t seem to have many Mint users and didn’t notice that obviously they have moved to default to PHP 7.2 being pre installed. At least that is my interpretation of the error without actually having looked into it. If you are not bound to use Mint then see George’s and Wayne’s answers. If you want to stick to it, try running the installer as php_ver=7.2 ./installfog.sh (note this is just from the top of my head, no promise this is working)