I use a PowerShell script launched from SetupComplete.ps1 to mount a network drive and then pull the relevant files. You could do something similar here. I’m assuming you’re doing this on a Windows PC.

The SetupComplete.cmd and commands are here:
https://forums.fogproject.org/topic/9859/post-deployment-driver-installation-using-powershell-scripts

For mine, I use the USB NIC that came with the Surface 3. After selecting image to boot and restarting into another iPXE boot I have unplug it right after you get the message about random number generation. Wait a second then plug it back in.

With those docking stations, I could get to the FOG menu, but couldn’t get the device to image.

Our media department has a couple dozen fonts that they regularly use. I created this FOG snapin to automate the task. Works for TrueType and OpenType fonts.

$Fonts = Get-ChildItem -Path $PSScriptRoot -Recurse | Where-Object -FilterScript { $PSItem.Extension -eq ".ttf" -or $PSItem.Extension -eq ".otf" }
$FontPath = "$env:SystemRoot\Fonts"
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts"

ForEach ($Font in $Fonts) {
    Copy-Item -Path $Font.FullName -Destination $FontPath -Force
    $Name = $Font.BaseName
    if ($Font.Extention -eq ".ttf") {
        $Name = $Font.BaseName + " (TrueType)"
    } elseif ($Font.Extention -eq ".otf") {
        $Name = $Font.BaseName + " (OpenType)"
    }
    $Value = $Font.Name
    New-ItemProperty -Path $RegPath -Name $Name -Value $Value -Force | Out-Null
}

Put the install.ps1 file and your fonts into a folder and zip archive it. Then upload it as a SnapinPack.

A restart is required before the fonts will be accessible.

@george1421 said in Apache Issue:

@avaryan Interesting, how many computers do you have checking into this FOG server?

I don’t know the exact number, but likely more than a thousand. There’s over 2,500 Windows computers in AD that would have the client on it.

Anyway, it’s been about 4 hours now and the web ui is still running well. I’d say that solved the issue.
Bonus: Got the FOG server updated.

@tom-elliott said in Joining to Domain:

First, disconnect the domain.
Second, install FOG Client.
Third, configure the host/s with the AD Joining Information in the GUI.

Only needed if sysprepping.

Fourth, disable the auto startup of the client.
Fifth, sysprep the machine with shutdown

Done sysprep.

Sixth, create capture task.
Seventh, restart/power on machine.

If doing SysPrep, don’t forget to add something to your SetupComplete.cmd to turn the FOG client back on!

Changed the checking time from 60 to 180. After a few minutes, the web interface became responsive again. I can switch between pages easily now.

@wayne-workman said in Apache Issue:

@avaryan Please be sure to check all the partitions, not just the big one. Use this command: df -h and look for partitions that have 100% usage.

@sebastian-roth said in Apache Issue:

Possibly start by looking at the apache access log to see if this is really clients causing this: tail -f /var/log/apache/access.log

I get no output. I let it sit for about 10 minutes.

edit: Updated to 1.4.4. Still increadibly laggy, but tail is showing some output now… kinda.

127.0.0.1 - - [05/Oct/2017:09:26:27 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:29 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:30 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:31 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:32 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:33 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:26:51 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:29:13 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"
127.0.0.1 - - [05/Oct/2017:09:29:16 -0400] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.27 (Ubuntu) OpenSSL/1.1.0f (internal dummy connection)"

^ Notice that it gets a hit every 1-2 seconds, then stops for about 20 seconds, then over 2 minutes before the next to. Haven’t gotten anymore since that last one.

No, there’s about 700GB of free space on it.

I’ll look into updating to 1.4.4 tomorrow.

The FOG client is version 0.11.12. It’s running on all our Windows computers. The check in time is the default setting.

As for number of devices, maybe around 1,000 online at once. Hard to say. Sent an email to our network admin regarding that.

Ubuntu 14.04
FOG 1.4.2

Apache is starting a ton of processes… needless to say, it’s slowing everything down significantly.

MySQL cpu usage was also very high.

The CPU usage for this VM is capped at 3 Ghz. At idle with no tasks running it was at 2.9.
There’s a few thousand clients registered.

For reference : My test FOG server is running on a HP Compaq 6000 Pro SFF PC. I actually used it this summer to deploy images for one of our buildings (was easier to get multicast up since it was on same vlan. Live server is on different vlan.)

I was doing about 20-30 PC’s at a time with multicast on this server. Deployed image in about 15 minutes. The server was plugged into a 10/100 port at the time.

Was running Ubuntu 16.04 LTS. Although I’d probably do CentOS next time.

So the newer ipxe commits are working again?

I’ve been having issues with the official Surface 4 docking stations on 7156. They boot to the FOG menu just fine, but I can’t inventory or deploy with them. They get stuck at the stage where I normally unplug the USB NIC, but it doesn’t fix it for the docks.

When you boot to Audit mode it puts you into the default Administrator account. Is this the user account you are talking about or did you create another account? Normally, whatever changes you make to this account during this time are what get copied over into new profiles after OOBE.

@martyc81 said in Windows boots as if new:

Hi there,
I’m pretty new to all this fog stuff, but have managed to get it running on a kubuntu vm on our network.

I can capture an image seemingly fine.

The issue I’m having is, once I deploy this image to another pc, upon it’s first startup, it asks me to go through initial setup stuff, and eventually have to also create a ‘new’ user.

Once this is done, my original user is also there, however I want to bypass this startup stuff, and just have windows boot with the user I created prior to capturing the image.

I think this has something to do with the sysprep.

Can someone steer me in the right direction as to how I might avoid this ?

You need to create an answer file to make the OOBE completely unattended.

@sebastian-roth said in Microsoft Surface Pro 4:

@Psycholiquid Please add the has_usb_nic=1 parameter (either in the host’s settings if it is registered already or in the general settings page (you’d see this for all hosts then). On boot it should prompt you to remove and replug the USB NIC. Then DHCP should work.

By the way: Which version of FOG do you have? Tom has added the feature to recognize clients by sysuuid rather than MAC address. See here. AFAIK this should work in FOG 1.4.4

I did not know about the has_usb_nic parameter. That’s helpful for me. Thanks. I was just timing it and unplug/plugging in.

Are these the first Windows 10 computers that you’ve had? Maybe some GPO is present that just doesn’t like 10.

I have to ask : Why not just deploy a clean Windows 10 image?

Are you using SysPrep? Was the image built on the same model PC you’re deploying to?

Auto logon values are stored in the registry. Run the following PowerShell script to determine your current AutoLogon settings.

$path = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon'

$AutoAdminLogon = (Get-ItemProperty -Path $path).AutoAdminLogon
$DefaultUserName = (Get-ItemProperty -Path $path).DefaultUserName
$DefaultPassword = (Get-ItemProperty -Path $path).DefaultPassword
$AutoLogonCount = (Get-ItemProperty -Path $path).AutoLogonCount

Write-Host "Current AutoLogon Settings:" -ForegroundColor Yellow
Write-Host "AutoAdminLogon: $AutoAdminLogon"
Write-Host "DefaultUserName: $DefaultUserName"
Write-Host "DefaultPassword: $DefaultPassword"
Write-Host "AutoLogonCount: $AutoLogonCount"

Output from my Windows 10 1607 laptop:

Current AutoLogon Settings:
AutoAdminLogon: 0
DefaultUserName: Administrator
DefaultPassword: 
AutoLogonCount: 

AutoAdminLogon has two states. If it’s 0, then it’s disabled. If it’s 1, then it’s turned on.
AutoLogonCount indicates the remaining number of automatic logons. This number decreases by one every time the computer restarts, until it reaches 0. When it reaches 0, it changes AutoAdminLogon to 0 and clears the DefaultPassword. Setting this to any number below 0 will effectively set your computer to automatically logon forever.

I didn’t really change that much from Windows 7 to 10. I made the answer file from scratch, but it’s pretty basic. Looks identical to the Windows 7 one.

All of my driver’s are done post-deploy, triggered from a series of PowerShell scripts launched from the Setup complete.cmd.

What are some Windows 10 only features that can be done from the answer file?

Nvm. Fixed. Ran the following from the troubleshooting page.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

DELETE FROM `hosts` WHERE `hostID` = '0';
DELETE FROM `hostMAC` WHERE hmID = '0' OR `hmHostID` = '0';
DELETE FROM `groupMembers` WHERE `gmID` = '0' OR `gmHostID` = '0' OR `gmGroupID` = '0';
DELETE FROM `snapinGroupAssoc` WHERE `sgaID` = '0' OR `sgaSnapinID` = '0' OR `sgaStorageGroupID` = '0';
DELETE from `snapinAssoc` WHERE `saID` = '0' OR `saHostID` = '0' OR `saSnapinID` = '0';
DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC` WHERE `hmPrimary` = '1');
DELETE FROM `hosts` WHERE `hostID` NOT IN (SELECT `hmHostID` FROM `hostMAC`);
DELETE FROM `hostMAC` WHERE `hmhostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `snapinAssoc` WHERE `saHostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `groupMembers` WHERE `gmHostID` NOT IN (SELECT `hostID` FROM `hosts`);
DELETE FROM `tasks` WHERE `taskStateID` IN ("1","2","3");
DELETE FROM `snapinTasks` WHERE `stState` in ("1","2","3");