Hi @GFm
I had the same issue in the past. The reason this is happening is that the newer revisions of the FOG client are much more efficient than the legacy client. It is basically kicking in too early. The way to fix this is to disable the service before you sysprep it pre-capture (best practice for the FOG Client). You then use the setupcomplete.cmd method shown in this Wiki Article:

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

You are basically telling it to re-enable and start the FOG service after sysprep is finished.

Installing as we speak. Well done! Though I recently joined the active community for this project, I’ve been using FOG since the 0.29 days and am amazed to see where the project is now. It’s come a long way to say the least. You take tools like this for granted when you are forced to do it the old fashioned way. I (briefly) worked IT at a factory that refused to implement any imaging solution. Each PC was built from OEM Windows from scratch. It sucked.

I’m glad to be back using my favorite open source project out there. Though most things we use at my job are proprietary, the support for FOG far surpasses any paid software. I can literally post on the forums and hear from a moderator, developer, or the legendary Tom Elliott himself within the hour. Even early in the morning!

I’m already thinking in the future, but I must ask, will the trunk style of updating disappear once the final revision of 1.3 is out? It would be bittersweet to lose that. On one hand you have the obligatory bugs that come with any testing, but being on the cutting edge of a growing project is actually pretty cool.

But I digress, keep up the good work guys and kudos for the dedication to the project. I look forward to the 1.3 release party

@Wayne-Workman I figured it out! I’m actually kinda proud of this one. Please see below for all of my Windows Server 2012 configs

Please let me know if you need anything else for this. It did indeed work. Thank you so much!

Congratulations everyone! I’m actually going to miss trunk/svn/RC’s in a weird way lol.

@Quazz I just tried both arguments on a surface pro 4. As long as you put

usbcore.old_scheme_first=1

before

has_usb_nic=1

separated by a space like you said, it works with no errors.

@Sebastian-Roth said in Stuck at Task Management Page "Unable to start task. Unable to upload file":

Not because it’s screwed but because more often than not you can learn something by re-doing things.

Amen to that. I learned Linux basics and the finer capabilities of FOG from rebuilding from scratch. Most people who use FOG seem to inherit an old installation from the last regime, myself included. I tried to fix what was there but it was poorly set up and unstable. It took some convincing and getting my hands dirty but I am on Trunk and loving it.

@george1421 I took a complete 180 on the methodology on this problem with the help of my co-worker who is better with Powershell than I am. Below is the sanitized version of our simple script to check Domain PC’s for the FOG Client:

ForEach ($Computer in (Get-ADComputer -Filter * -SearchBase "OU=Sample,DC=yourdomain,DC=com")) {
$ComputerName = $Computer.Name
If (Test-Connection $ComputerName -Count 1 -Quiet) {
    $FogService = Get-Service -Name FogService -ComputerName $ComputerName -ErrorAction SilentlyContinue
        If ($FogService) { Write-Output "FOG is running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append}
        Else {Write-Output "FOG is not running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append }}
Else {Write-Output "$ComputerName is Offline" | Out-File C:\Scripts\FOG.csv -Append}
}

It isn’t the prettiest, but it is versatile in the way that you can really sub the FOGService with any other service name to check if said service is installed and running. I have a initial CSV for the online PC’s that had a broken or not installed FOG Client and set a GPO Startup script to remove any old service, install the new service, and finally start the service. Below is a sanitized batch file for that:

msiexec /q /x C:\LegacyClientInstaller\FOG Service Installer.msi"
msiexec /i "C:\NewClientInstaller" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="YourFOGAddress" WEBROOT="/fog" ROOTLOG="1"
net start FOGService

Hope this may help someone someday!

I just recently used FOG to create a surface pro 4 image. My workaround was to use a port replicator/hub to have both an external USB keyboard and Ethernet adapter plugged into the surface. It seemed to recognize both. It isn’t a permanent solution but It is how I did it.

So, this is really dumb on my part… It was our web filter blocking the calls out to pushbullet. It now displays the email and name in the table and the GUI after I whitelisted it. I will double check that notifications are working tomorrow, but this is looking like a whoopsie on my part. Most likely solved.

@ITSolutions I suppose my method is a band-aid fix of sorts. At my place of work, we are moving to standardize the models of PC’s we are putting in. By the time next school year starts, we will have about 75% of all of the PC’s in the network be Dell Optiplex 5040’s. Ultimately, we are going the model-specific route of images since we only have a handful of models we use. I agree with what you are saying though.

We will need to know what version of FOG you are running for starters. I’m sure now that this is bumped and if you provide this info, the forum members should be able to start helping.

@george1421 said in FOG Post install script for Win Driver injection:

@fry_p said in FOG Post install script for Win Driver injection:

BCDEDIT /set nointegritychecks ON

Right this needs to be put into your golden image. Its a bad hack. But its VERY strange that Dell would release unsigned drivers, that’s so 2015. Are they not signed, or are they signed but have an unidentified certificate?

I legitimately want to ask, is it really dangerous to have that off for that short period of time? I turn it back on after the next automated reboot. I suppose if something failed, it would be stuck in that state… I need to not be lazy and find which one(s) is(are) unverified. Sadly, the message does not specify in sysprep.

This may be a fluke because I am testing and found this issue on an OptiPlex 7020 .cab. It is not the newest gen by any means.

I have successfully gotten the exe to work by doing the following:

1 - Download the latest version of acrobat reader DC for your language and OS version here (this is important because it is the offline installer):

https://get.adobe.com/reader/enterprise/

2 - Compress the file into a .zip

3 - Create a snapin pack with the following content:
a - Choose the .zip you just created to upload
b - Change the file path from “MyFile.exe” to the name of the exe you downloaded earlier
c - Put the following in the Snapin Pack Arguments section:
/sALL /msi /norestart ALLUSERS=1 EULA_ACCEPT=yes

Here is a screenshot of my settings:

Then you save the snapin, and deploy away!
Please let me know if this works for you

I might as well throw my hat in, I think I know enough about imaging with FOG to help. If anything, updating some basic things to reflect newer versions of FOG.

@Sebastian-Roth

https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep

"Place these lines within the file, and then save.

sc config FOGService start= auto
shutdown -t 0 -r

As the filename indicates, the script is called by windows after an image is deployed and post-sysprep operations are complete. It will re-enable the FOGService and then reboot the computer gracefully. After the computer reboots, the FOGService will start automatically and rename the computer if necessary, reboot if necessary, join the domain and reboot if necessary, and then perform any associated snapins. "

@Trev-lchs , please be more specific. What part isn’t working? Do you get any error messages? Please describe what is happening when you try to search.

@Sebastian-Roth Whoops, I did not know that was the norm now. It is in the wiki article as auto. My bad, I can certainly change that before I try again.

EDIT: fixed my first post with the delay and a missing space just in case it works and someone uses it later

I hate to admit it took me a full day to realize there should be no space in the directory structure for the driver folders when I (poorly) read George’s instructions in the 2017 thread (lmao)

I also have a question that is related to the driver injection concept, but it is after the post download scripts.

For one of the machine types, the .cab comes with an unknown amount unsigned driver for some stupid reason. This complicates things because a prompt to “install the unverified driver(s)” during the setupcomplete.cmd. I can’t find a method to force/silently say yes to this with pnputil.

Most fixes involve an extra reboot to turn off driver integrity checks. I am trying a really roundabout method:

Setupcomplete.cmd

BCDEDIT /set nointegritychecks ON
shutdown -t 0 -r

Then, a script that lives in the startup folder found at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup does the following, then deletes itself after it runs once.

pnputil.exe /add-driver "C:\Drivers\*.inf" /subdirs /install
pnputil.exe /add-driver "C:\Drivers\*.inf" /subdirs /install
pnputil.exe /add-driver "C:\Drivers\*.inf" /subdirs /install
rmdir /Q /S C:\drivers
BCDEDIT /set nointegritychecks OFF
(goto) 2>nul & del "%~f0"

Finally, I have a scheduled task built into the image that takes care of the commands usually in the typical setupcomplete.cmd, then deletes itself as well. The reboot should theoretically take care of the client service config and turning the integrity check back on.

sc config FOGService start= delayed-auto 
shutdown -t 0 -r

I got to the point of being ready to test this yesterday, but the workday ended. I will test in a few hours when I am in. I am open to suggestions of how to make this less clunky (if it even works).

@UWPVIOLATOR My colleague and I have a PS script that at least checks if the service is running. It exports the results into .csv file. It can at least give you an idea of how many and which ones need fixed. (I sanitized this a bit, so put in your own stuff where needed)

ForEach ($Computer in (Get-ADComputer -Filter * -SearchBase "OU=XXXXXXXXXXX,DC=MYDOMAIN,DC=COM")) {
$ComputerName = $Computer.Name
If (Test-Connection $ComputerName -Count 1 -Quiet) {
    $FogService = Get-Service -Name FogService -ComputerName $ComputerName -ErrorAction SilentlyContinue
        If ($FogService) { Write-Output "FOG is running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append}
        Else {Write-Output "FOG is not running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append }}
Else {Write-Output "$ComputerName is Offline" | Out-File C:\Scripts\FOG.csv -Append}
}

From there, I am pretty sure you can just add affected PC’s to a group in Active Directory and map a GPO to run the following batch script (Note I sanitized a bit, so insert your own stuff where needed):

msiexec /q /x "PATH TO FOG CLIENT MSI"
msiexec /i "PATH TO FOG CLIENT MSI" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="FOGSERVERIP" WEBROOT="/fog" ROOTLOG="1"

net start FOGService

@LittleTux

How i can pass this post on Solved ?

Done. Glad it worked