Posts made by JYost

@sebastian-roth
We are running FOG 1.5.9 on Ubuntu 20.x

During PXE boot I am receiving the following messages -
…
Waiting for link-up on net0…ok
Configuring (net0 MAC…No configuration methods succeeded (http://ipxe.org/0040ee186)
Configuring (net0 MAC…No configuration methods succeeded (http://ipxe.org/0040ee186)
DHCP failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds.

Other models of laptops are imaging fine (Lenovo T480, T14, and L14). I suspect that the Realtek NIC drivers for this particular model/variant are not included in the Kernel. Suggestions/comments?

FYI - Kernel on the FOG server has been updated to 5.10.74 (64-bit)

What order do the snapins install in? Alphabetically by the name of the snapin or the number assigned to the snapin?

Disregard - problem has been solved. I renamed a .msi setup file but forgot to edit the filename in the snapin configuration.

I have a number of snapins enabled on my image, 7 to be exact. According to the fog.log the first one to install, CiscoOpenDNS is failing with an error of “SnapinClient ERROR: Snapin hash does not exist”. It re-tries repeatedly with the same error over and over. All snapins were imported/copied from another working FOG server. I see no other errors in the log. The laptop imaged and renamed properly. Thanks in advance.
Win10 v.21H1, FOG 1.5.9, Ubuntu 20.x

Could you clarify the following instructions for resetting the fogproject password…

Review the file /opt/fog/.fogsettings (this is a hidden file)
In that file there is a entry called password=

1.) Capture that password. You will need it to reset the FOG server.

2.) Now reset the linux user fogproject’s password with sudo passwd fogproject

Am I supposed to reset the password to the password I captured above in step 1 or am I resetting it to something else that I choose?

Thanks in advance!
John

Well, sync’ing everything up a second time worked like a charm. Thank you for your help Sebastian!!

/var/www:
total 16
drwxr-xr-x  3 root     root     4096 Jun 22 13:55 .
drwxr-xr-x 15 root     root     4096 Mar  9 13:44 ..
lrwxrwxrwx  1 root     root       18 Jun 22 13:55 fog -> /var/www/html/fog/
drwxr-xr-x  3 root     root     4096 Jun 28 09:07 html
-rw-r--r--  1 www-data www-data   52 Mar  9 13:47 index.php

/var/www/html:
total 28
drwxr-xr-x  3 root     root      4096 Jun 28 09:07 .
drwxr-xr-x  3 root     root      4096 Jun 22 13:55 ..
drwxr-xr-x 10 www-data www-data  4096 Jun 28 09:09 fog
-rw-r--r--  1 root     root     10918 Mar  9 13:44 index.html
-rw-r--r--  1 www-data www-data    52 Jun 22 13:54 index.php

While attempting to image a device this morning I rececived a “No network interfaces found, your kernel is most probably missing the correct driver!”. So, I went to update the Kernel and received this error during the file transfer:
"Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 465, Message: ftp_login(): Login incorrect., Host: x.x.x.x, Username: fogproject
As a final measure I attempted to reset and sync the service account password which is what I believe the above error is referring to - I followed the procedure here step by step: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password
After re-running the fog installer to re-sync everything I’m still receiving the errors when imaging and when trying to update the kernel. Strange because everything was working fine on Friday. Am I missing something? What should I do from here? (Ubuntu 20.x with FOG 1.5.9)

Do the snapins always install in the order of the numbering? If I need the snapin’s to install in a particular order how can I go about doing that? I’ve downloaded the renumbering tool and I’m able to set the first to run, but the others follow in the order that they were created. Is there a way to place these in a particular order without having to delete all of them and rebuild them in order?

FOG 1.58 on Ubuntu 16.04…
We have a number of laptops which do not have NIC ports on them and we’ve been using a USB-CAT5 adapter to image them. We PXE boot using the USB adapter’s MAC address, then after imaging we change the MAC address back to the internal MAC on the laptop. The next laptop we image using the same method, but this time it says that the MAC address (USB Adapter) is being used by the previous laptop even though we changed it to the internal MAC. We discovered that if we image a device using the USB adapter MAC we must DELETE the host completely after imaging and rebuild it using the internal MAC. Changing it does not wipe out the USB MAC setting. Not sure if you’re aware of this glitch but thought I’d pass it on for future updates/fixes. I didn’t see anything previously reported in the forums.

@george1421

Thanks for the quick followup. Just a couple more pointed questions. I’ve moved the majority of the First Run scripts into the start of SetupComplete.cmd before starting the FOG client. I’ve set the FOG service startup type to Auto…do I need to start it immediately by adding a line after “sc config FOGService start= auto” such as net start FOGService? I guess my question here is whether FOG will attempt to rename the device and join it to the domain BEFORE restarting at the end of SetupComplete.cmd or does it rename & join the domain immediately AFTER the final restart? Since we’re setting the startup type to Auto and then calling a restart immediately thereafter I’m thinking it won’t have time to rename/join domain prior to the restart. So, how long does the FOGService typically take to start and begin the rename/join domain? Will it restart again automatically thereafter?
Here is my setupcomplete.cmd file:

:: Set AutoLogon
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v SecondaryScripts /d C:\Admin\Scripts\FinalSetup.cmd /f
reg add HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /d 1 /f
reg add HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoLogonCount /t REG_DWORD /d 1 /f
reg add HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d Administrator /f
reg add HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassword /d ********* /f
reg add HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v ForceAutoLogon /d 1 /f
:: Disable Scheduled Lenovo System Updates
reg add “HKLM\SOFTWARE\Wow6432Node\Lenovo\System Update\Preferences\UserSettings\Scheduler” /v SchedulerAbility /t REG_SZ /d NO /f
:: Configure Firewall Settings
netsh advfirewall firewall set rule group=Network Discovery" new enable=yes
netsh advfirewall firewall add rule name=“Fog Client” dir=in action=all program=“C:\Program Files (x86)\FOG\FOGService.exe”
netsh advfirewall firewall add rule name=“Fog Service” dir=in action=all program=“C:\Program Files (x86)\FOG\FOGServiceConfig.exe”
netsh advfirewall firewall add rule name=“Fog Tray” dir=in action=all program=“C:\Program Files (x86)\FOG\FOGTray.exe”
:: Disable Adobe Reader Update Service
sc config “AdobeARMservice” start= disabled
sc stop “AdobeARMservice”
:: Enable Windows Store Installer Service
sc config “InstallService” start= Auto
:: Set AutoRemoval of Taskbar Icons
powershell.exe -NoProfile -ExecutionPolicy ByPass -WindowStyle Hidden -file C:\Admin\Scripts\ManageTaskbar\Managetaskbar\taskband.ps1
:: Install MS-Teams (All Profiles)
msiexec /i C:\Admin\MS-Teams\Teams_windows.msi OPTIONS=“noAutoStart=true” ALLUSERS=1
:: Configure Wireless Profile Settings
net start wlansvc
Netsh wlan add profile Filename=C:\Admin\Scripts\Vistex.xml user=all
netsh wlan connect name=‘Vistex’
sc config FOGService start= auto
:: Do I need the following 1 line???
------>> net start FOGService
shutdown -t 0 -r

If the renaming/domain join occurs AFTER the final restart I will need to run a powershell script to install our AntiVirus software and also add a domain user account to the Remote Desktop Users group –
Add-LocalGroupMember -Group “Remote Desktop Users” -Member “vistex\SetupVTX”
obviously the latter needs to be done after it’s joined to the domain so I would need to set the autologon registry keys for two logons…one for immediately after setupcomplete.cmd and one for after the domain join/restart. Hopefully that makes sense and that I’ve got the order of operations down in my mind correctly.

@george1421
Let me see if I have this correctly…I am running some scripts in the FirstLogonCommands section of the autounattend.xml file. These include setting firewall rules, setting services, configuring wireless profile, installing MS-Teams, Disabling Lenovo auto update in the registry. Once the last of the commands in autounattend.xml has completed then Windows setup is complete and the C:\Windows\Setup\SetupComplete.cmd batch file runs (sets the FOG service startup type to Auto, and then reboots the computer). Once the computer restarts the FOG service starts, renames the computer, joins it to the domain, and reboots again. I’m just trying to get the order of operations straightened out in my head.

We will be building a new VM with Ubuntu 20.x…it won’t be an in-place upgrade. I will post any issues we run into…fingers crossed.

I’m unable to determine why about 1/2 of the devices we reimage with FOG do not process the first-run scripts set up in the autounattend.xml file. Sometimes it works fine though which leaves me scratching my head. Perhaps someone could shed some light on why this is occurring. When the scripts do NOT run Windows just comes up to a logon screen “Other User”. WhenFOG log attached is from one of the devices that did NOT process the first-run scripts.

Basically at first run the device should autologon as Administrator - there are some firewall policies that are set for the FOG executables, then it calls FinalSetup.ps1 which will continue on with configuration and software installation. This autologon is what appears to be failing intermittently.
FOG Log, FinalSetup.txt, and autounattend.txt attached.

Mod edit to remove autounattend.xml that was unsanitized

Organization Name: Vistex, Inc.
Location: Corporate Office - Hoffman Estates, Illinois, USA
Approximate Number of systems: 1600 laptops/75 desktops
How long: Since 2017
12 Satellite Offices Worldwide each running a FOG server locally (VM)

We are currently using multiple Ubuntu 16.04 Desktops running in VM’s with FOG on them. I’d like to upgrade to the latest Ubuntu (20.x) but would like to know what is the ‘recommended’ Linux distro and which is better to use…desktop or server? Are there any known issues running Ubuntu 20.x desktop.

Thanks in advance!

That was painless!! Worked great. Thanks guys!!

Running Fog 1.5.8 on Ubuntu 16.04LTS

We just received several Lenovo T14’s and I’m unable to Pxe boot them. We are able to image earlier models (T460,T470,T480,T490 series) without any problem. During Pxe boot it gives me an error “No network interfaces found, your kernel is most probably missing the correct driver!” Looking at a similar issue it appears I may need to update the kernel. Any assistance is greatly appreciated!!
Cheers,
John

@Tom-Elliott
Correct…I understand the image should not be joined to the domain, and its not…I’m referring to devices which I’m either imaging for the first time or re-imaging. I will attach the fog.logs for devices which failed and which succeeded in being renamed and joined to the domain. Sometimes it renames them fine but doesn’t join it to the domain. Other times it doesn’t do either, or does both fine. It’s been hit or miss.