Posts made by RLane

@Tom-Elliott Am I missing something here? /opt/fog/log is empty.

Also having this problem. Clean install on CentOS 7 x64 using the latest git version (7695).

@Mentaloid +1 — thank you!

@Tom-Elliott The FOG service? Didn’t think of that, either. While we’re on this topic - does anybody else have a more effective way of updating Windows via scripting? I know a lot of things I did on 7 I can no longer do now.

@Mentaloid That’s actually a pretty nifty idea… let me upload a new image without the script running from my batch file. The more I use FOG, the more I start to realize it’s designed to make life easy…

@Jbob No rush This is not my production FOG server - I have a sandbox of 3 devices + a VM I use for testing. I’m planning on rolling out Windows 10 in July - this is just early prep with the scripts.

@Jbob Tested and it worked fine without the AD and renaming. How does FOG handle this? Initially, I added a 45 second reboot task via my unattend file, but it didn’t join and rename until the second reboot.

@Jbob Will reupload and test without the service enabled. I’ll report my findings back after.

@Wayne-Workman Interesting… any reason why you don’t roll updates out?

Also, yes. I’m not sure I understand 100% how the client works. Does the client fetch the domain and rename requests immediately after image competition?

This script should be the last thing that my SetupComplete.bat script calls but for some reason is rebooting prior to finishing. I suspect it’s FOG because my Unattend file has 1 OnFirstLogon flag set for the host administrator account. After that, it requires a domain login – indicating that FOG joined it to the domain and renamed it.

Currently using Client 0.9.12 and cloud version 7092.

@Wayne-Workman I have a WSUS server set up, which this script pulls the updates from. The only problem is we have it designed to push updates out on certain days for certain buildings. If I image a Admin PC Monday, they won’t get updates until Thursday. We did this to conserve bandwidth.

Having said that, I also wanted to use this to install PC-specific drivers from Windows Update since Windows 10 has all of our workstation drivers that work. If I injected them like I use to with WinPE, they would be out of date, etc.

I’m going to be deploying Windows 10 for the first time over the summer. In the past, I had used an HTA/VB script that would run after FOG completed the imaging task. This would require one of our tech’s to input the proper OU and computer name of that machine. After a tech completed that, it would finish up and run Windows update.

Now, with Windows 10, I’m trying to create a process that requires no human interaction. First, I would create my master image. I would upload it with FOG, deploy it. I’m now using FOG to join them to our domain, activate (KMS), and rename.

My question is: I have a Powershell script that should automatically look for Windows updates, download, and install them. The script that I’m using is below:

#Script: WSUS.ps1
#      Author: Gregory Strike
#     Website: www.GregoryStrike.com
#        Date: 02-19-2010
# Information: This script was adapated from the WUA_SearchDownloadInstall.vbs VBScript from Microsoft.  It uses the
#              Microsoft.Update.Session COM object to query a WSUS server, find applicable updates, and install them.
#
#              WSUS.ps1 is a little less verbose about what it is doing when compared to the orginal VBScript.  The
#              lines exist in the code below to show the same information as the original but are just commented out.
#
#
#              WSUS.ps1 can automatically install applicable updates by passing a Y to the script.  The default
#              behavior is to ask whether or not to install the new updates.
#
#              Syntax:  .\WSUS.ps1 [Install] [Reboot]
#                       Where [Install] is optional and can be "Y", "Yes", "No" or "N"
#                       Whether or not to install the updates automatically.  If Null, the user will be prompted.
#
#                       Where [Reboot] is optional and can be "Y", "Yes", "No" or "N",  This 
#                       If updates require a reboot, whether or not to reboot automatically.  If Null, the user will
#                       be prompted.

$UpdateSession = New-Object -Com Microsoft.Update.Session
$UpdateSearcher = $UpdateSession.CreateUpdateSearcher()
 
Write-Host("Searching for applicable updates...") -Fore Green
 
$SearchResult = $UpdateSearcher.Search("IsInstalled=0 and Type='Software'")
 
Write-Host("")
Write-Host("List of applicable items on the machine:") -Fore Green
For ($X = 0; $X -lt $SearchResult.Updates.Count; $X++){
    $Update = $SearchResult.Updates.Item($X)
    Write-Host( ($X + 1).ToString() + "> " + $Update.Title)
}
 
If ($SearchResult.Updates.Count -eq 0) {
    Write-Host("There are no applicable updates.")
    Exit
}
 
#Write-Host("")
#Write-Host("Creating collection of updates to download:") -Fore Green
 
$UpdatesToDownload = New-Object -Com Microsoft.Update.UpdateColl
 
For ($X = 0; $X -lt $SearchResult.Updates.Count; $X++){
    $Update = $SearchResult.Updates.Item($X)
    #Write-Host( ($X + 1).ToString() + "> Adding: " + $Update.Title)
    $Null = $UpdatesToDownload.Add($Update)
}
 
Write-Host("")
Write-Host("Downloading Updates...")  -Fore Green
 
$Downloader = $UpdateSession.CreateUpdateDownloader()
$Downloader.Updates = $UpdatesToDownload
$Null = $Downloader.Download()
 
#Write-Host("")
#Write-Host("List of Downloaded Updates...") -Fore Green
 
$UpdatesToInstall = New-Object -Com Microsoft.Update.UpdateColl
 
For ($X = 0; $X -lt $SearchResult.Updates.Count; $X++){
    $Update = $SearchResult.Updates.Item($X)
    If ($Update.IsDownloaded) {
        #Write-Host( ($X + 1).ToString() + "> " + $Update.Title)
        $Null = $UpdatesToInstall.Add($Update)        
    }
}
 
$Install = [System.String]$Args[0]
$Reboot  = [System.String]$Args[1]
 
If (!$Install){
    $Install = Read-Host("Would you like to install these updates now? (Y/N)")
}
 
If ($Install.ToUpper() -eq "Y" -or $Install.ToUpper() -eq "YES"){
    Write-Host("")
    Write-Host("Installing Updates...") -Fore Green
 
    $Installer = $UpdateSession.CreateUpdateInstaller()
    $Installer.Updates = $UpdatesToInstall
 
    $InstallationResult = $Installer.Install()
 
    Write-Host("")
    Write-Host("List of Updates Installed with Results:") -Fore Green
 
    For ($X = 0; $X -lt $UpdatesToInstall.Count; $X++){
        Write-Host($UpdatesToInstall.Item($X).Title + ": " + $InstallationResult.GetUpdateResult($X).ResultCode)
    }
 
    Write-Host("")
    Write-Host("Installation Result: " + $InstallationResult.ResultCode)
    Write-Host("    Reboot Required: " + $InstallationResult.RebootRequired)
 
    If ($InstallationResult.RebootRequired -eq $True){
        If (!$Reboot){
            $Reboot = Read-Host("Would you like to install these updates now? (Y/N)")
        }
 
        If ($Reboot.ToUpper() -eq "Y" -or $Reboot.ToUpper() -eq "YES"){
            Write-Host("")
            Write-Host("Rebooting...") -Fore Green
            Restart-Computer -Force
#            (Get-WMIObject -Class Win32_OperatingSystem).Reboot()
        }
    }
}

I have a batch file that runs the task – started by my unattend file.

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File "C:\Windows\Setup\Scripts\WindowsUpdate.ps1" Y Y

The Y Y are the Yes flags to install and reboot if required without a user prompt.

My question is: How does FOG add hosts to the domain and rename them? This script takes time to run. I have 1 OnFirstLogon task (this batch script) – but it seems like FOG triggers it to reboot to join the domain and whatnot mid task.

Hopefully this makes sense… If someone else has a better solution for scripting Windows Updates to install automatically post-imaging, I would LOVE to hear how you do it. Working in K-12 education, I typically create images over the summer time and deploy them throughout the year. Obviously updates can add up so this would be an effective way to reduce man power.

Makes sense - now would I have to input that information (key, domain, image, etc.) if/when I add a new host to that group?

Currently using cloud version 7092 - I have two hosts in my lab added to a lab group. I’m trying to assign a group product key, domain information, and image assignment. Every time I hit update, it immediately deletes whatever I input.

Bug or some feature I’m unaware of?

Thanks!

@george1421 @tom-elliott I stand corrected, thanks y’all. Not trying to hijack this, in the past we’ve used a manual PS+HTA script that allowed us to import them to a OU and rename them post-imaging.

Within sysprep and your unattend.xml file you can create a PS batch script to change the hostname. Only problem is this will require manual input rather than have FOG do it automatically.

I will say though that I’ve deployed images on hardware 6+ years old (Win7 x64 compatible) and use the FOG client. It is extremely light weight and uses little to no resources.

Just my 2c.

Now the question, which you may or may not have an answer to. Is there any sort of timeline as to the release of 1.3.0? 2.0 is a long way away like you said - but i’m excited to see what it has to offer.

Gottcha. However that doesn’t apply since I’m using cloud version 3551 and the old client, does it?

Hi everyone -

Perhaps this is a loaded question but I’ll try not to sound too stupid. Each time a major update comes out (0.32 -> 1 -> 1.20) I like to rebuild the server and do clean installs.

I’m in the process of building a new server for the latest (1.3.0 or 2?) release. With the new client being finalized, is there any estimated time frame which we could expect the new release?

Also, is 1.3.0 the same as 2.0? I know some have hinted to completely rebuilding FOG, hence 2.0 – but I’ve also need 1.3.0 thrown around as well.

Just looking for suggestions on how to move forward… as always, thanks for the great work guys. Cheers.

For what it’s worth, if it’s stuck on the black screen + “ipxe initialising devices”, undionly.kkpxe works. Our HP 4520s have the Realtek NICs which have this issue.

x-post here: https://forums.fogproject.org/topic/2807/ipxe-boot-issue-with-realtek-rtl8153/18

Unetbootin:

http://unetbootin.sourceforge.net/ - download it for whichever OS you’re currently using.

iPXE iso:

http://ipxe.org/download

OR as an alternative, you can use the Clonezilla live CD iso and choose the network boot option (which chains iPXE) – that’s located below:

http://clonezilla.org/downloads/download.php?branch=stable