@george1421 Thanks for the response. I think I might’ve actually figured it out. If you Legacy PXE boot, it errors out on a UEFI based machine. However, if you use the Network Stack PXE boot (UEFI), it will correctly boot. The DVD does work for both UEFI and Legacy. I don’t know why I didn’t think to try that first.

Thanks for the help!

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image

@Wayne-Workman Thanks for the response. I ended up renumbering the image name to include 01. through 14 and that did sort them. I appreciate the quick thinking and that fixes my issue!

@wayne-workman This fixed it! Thank you!

Through the API, I am looking to be able to add a snapin task to a host and then run the task and then delete the snapin from the host all via powershell. Is there a way to do this? Here is what I have so far:

#######################################################################################################################
# Configure the variables below for the Fog Server
#######################################################################################################################
    #FogServer
        $fogApiToken = 'ABCDE'
        $fogUserToken = 'FGHIJ'
        $fogServer = "192.168.1.100"
        $headers = @{};
        $headers.Add('fog-api-token', $fogApiToken);
        $headers.Add('fog-user-token', $fogUserToken);
        $baseUri = "http://$fogServer/fog"
       
       #Shows the Deploy Task ID

         $TasktypesURL = $baseUri + "/tasktype"
         $TasktypesResult = Invoke-RestMethod -Uri $TaskTypesURL -Method GET -Headers $headers -ContentType "application/json"
         $TasktypeID = ($TasktypesResult.tasktypes | Select-object name,id | Where-object {$_.name -eq "Single Snapin"}).id


       #Get Snapin List From Fog Server

        $SnapinURL = $baseUri+"/snapin/"
        $SnapinResult = Invoke-RestMethod -Uri $SnapinURL -Method GET -Headers $headers -ContentType "application/json"
        $Snapin = $SnapinResult.snapins | Select-object id,name | Where-object {$_.name -eq "Remote Settings"}

       #GetHost List from fog Server

        $HostURL = $baseUri +"/host/"
        $HostResult = Invoke-RestMethod -Uri $HostURL -Method GET -Headers $headers -ContentType "application/json"

       #Get Specific Host from FOG Server
        $HostURL = $baseUri +"/host/"
        $Results = Invoke-RestMethod -Uri $HostURL -Method GET -Headers $headers -ContentType "application/json" 
        $Hosts = $Results.hosts
        $SpecificHost = $Hosts | where name -match "Computer Name"


        #Start an Image
        $SnapinID = $Snapin.id
        $HostID = $specifichost.id  

        $TaskURL = $baseUri + "/host/" + $HostID + "/task"
        $TaskdataSet = @{
            "taskTypeID" = $TasktypeID
            "deploySnapins" = $Snapin
            }
        $taskdataToSend = ConvertTo-JSON($TaskdataSet)
        $TaskResult = Invoke-RestMethod -Method Post -Uri $TaskURL -Headers $headers -Body $taskdataToSend -ContentType "application/json"

All it does is start an image. At this point, I am just trying to get it to deploy the single snapin. From everything I read, it is supposed to be tasktypeID 13. Any help would be greatly appreciated!

FOG 1.5.9.34
CentOS 7

@jj-fullmer

I will check it out! Late is better than never! Appreciate your work on this.

@george1421 The USB drive piece didn’t work, but the Enabling of VMD did work to get the speed. The only gotcha is that you have to turn it off right after the image is done or you will get a BSOD with “Inaccessible Boot Device”.

I updated the iPXE to the latest version and that fixed some of the initial issue with weirdness, but still, when I go to “Deploy Image” and put in the username and pw, I have to go through that and hit enter 6 times until it exits that menu. Then I get the following screen on the laptop

It looks like some sort of debug screen?

@george1421 On the post you put, I just tried to image with the VMD enabled and that worked. The biggest thing is that I had to disable it after the image came down.

@george1421 I did end up XX-ing out the IP address. I guess I really didn’t need to and it was on the correct subnet.

I checked the /var/log directory and all it had was a “messages”, not a “syslog”, so I have put that below.

#grep -i firmware /var/log/messages
Dec 23 08:20:58 fogclient user.notice kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

The NIC that is being booted from the is the internal NIC

@george1421 Thanks george for the help!

Here is what got returned:

#lspci -nn | grep -i net
00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)
00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:15fc] (rev 20)

The other command didn’t work, either with /var/syslog or /var/messages. When I did a “ls” for that /var/ directory it came up with: cache, empty, lib, lock, log, run, spool, tmp, www. I tried doing “log”, but it returned nothing.

Here is the output for ip a s

2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether e0:70:ea:a6:29:b1 brd ff:ff:ff:ff:ff:ff
    inet X.X.X.X/21 brd X.X.215.255 scope global enp0s31f6
    valid_lft forever preferred_lft forever

Thanks again

@sebastian-roth Thanks for the response. I tried all of the 5.10.x kernels as well. I exhausted the list. I couldn’t remember off the top of my head what the very latest was.

I will try to update to the latest version of ipxe and see if that fixes the first part of the booting process.

I will still need help with the imaging portion though. Is there any sort of debugging/checking I can do as far as the slow imaging?

I am having trouble with the HP Probook Imaging and also sometimes with PXE. It does the boot piece and loads the FOG menu, but after choosing the “Deploy Image” and putting the username and password, you have to hit enter 4 more times for it to exit that screen and then it goes into debug mode with “1. Reboot” being the top option.

I imagine it is due to the hardware or the NIC. The NIC is the realtek, but I can’t find the exact model number. I am using the latest kernel (5.6.18) and have tried several others and it does the same thing. I can deploy an image from FOG and it will image at 10Mb/min which puts the image around 16 hours to download. There is definitely something wrong. I know I can probably use a USB-C to ethernet adapter, but I would rather use the onboard.

Any help would be awesome.

@JJ-Fullmer,

I had a feature request for the API. I am looking at trying to output the last time the computer was imaged so that when I scan the serial I can get that info direct out of PS. Have I just missed it or is that not in there?

Thanks!

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

Hello FOG Developers,

Is there a way with the API to pull the last imaged date? I know you can pull a lot of info, but I didn’t see that. I just saw “createdTime” and “deleteDate”. It would be helpful for me to log that info away.

Thanks!