@bc601 There is a section in the FOG Client page on the wiki that talks about what needs to be done if you install the fog client before you sysprep it here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
Or you can install the fog client post imaging using the msi and the setupcomplete.cmd file. Two ways to go about it to get the same results.

@wayne-workman

Yes I did not activate the sysprep application. Once I activated it and recaptured the image. The problem was resolved.

There’s also the more solid way by making the image folder to be read only an immutable.

chattr +i <Filename/folder>

@lee-rowlett I only have one in my list, but it is causing all my problems. I’m still given the option to boot from the hard drive that WBM is pointing too, but it doesn’t boot and kicks me back to the BIOS configuration (no errors given).

Glad it helped.

dpinst.exe was last included with the Microsoft Windows Driver Kit 10.0.10586.0 (v1507) build 10.0.26639.

To install:

wdksetup.exe /quiet /features OptionId.WindowsDriverKitComplete

Then find the dpinst.exe files here:

C:\Program Files (x86)\Windows Kits\10\redist\DIFx\dpinst\EngMui\x64\dpinst.exe C:\Program Files (x86)\Windows Kits\10\redist\DIFx\dpinst\EngMui\x86\dpinst.exe

@weaponode Do you still have that issue?

Already enabled and works like a charm. 🙂

Can be closed, thx for helping out.

@techadmin There is a wiki page that covers this: https://wiki.fogproject.org/wiki/index.php?title=Multicasting

The other thing is your networking infrastructure. If all of your target machines are on the same subnet as your FOG server, then you are good to go. If they are on different subnets then you need to get with your infrastructure team and discuss setting up a multicast router or allowing multicasts to traverse your subnets. This is not something specific to FOG, but rather multicast data paths.

@gob Great, glad I could help. 🙂

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

@george1421 It all uploaded perfectly fine the other day - thanks 🙂

@taspharel @Avaryan

Thanks guys, collectively this helped me achieve what I was trying to accomplish.

Appreciate your assistance

Update to thread: These sed scripts can/could be called from a fog postinit script to ‘patch’ the fog scripts on each FOS boot. This way you would never need to unpack the inits and would fully support updated scripts in the future.

I did write a tutorial on the postinit scripts here: https://forums.fogproject.org/topic/9463/fog-postinit-scripts-before-the-magic-begins

@datastream I would suggest you ask on the ClamWin forums here: http://forums.clamwin.com/

@sudburr hey thank you for this, you are really more advanced with the dpinst usage.
Appreciate your post a lot 🙂

@george1421 So I just logged in and opened word. After it opens it has the window that says first things first and you choose how it will install updates. You have to be an admin to set that. After that the window pops that asks “How do you want to activate your software?”

After you click through those it is ready to go. Is there a way to automate that so it is done already? It’s not a big deal. I can login to each machine and click through those, but if it can be done I would set it up.

@quazz
No I did not, I just thought of that yesterday and was able to get it working fine now. I just now have to try out making the image with removing Edge and the Windows 10 Apps with PS Scripts.

@chris6862 FWIW: Between image captures I’ve used the FOG post install scripts to “patch” the target image as FOG deploys it to the target machine.

In our process we rebuild our reference image once a quarter. We have to go through and validate that the reference image works on all 12 models in our fleet before we can release it in fog for deployment. If we discover a gotcha after its been approved and released (as in needing to add something to the unattend.xml file or setupcomplete.cmd) We will have a post install script run to slide in the correction once imaging is done, and before the system reboots into windows setup. I’m not saying that this process will solve your issue here, but it IS a workable option if you need it.

@x23piracy Well for windows 7 it wasn’t needed to sysprep to activate windows 7 licence and since we don’t have a microsoft domain it wasn’t necessary to use sysprep anyway… i think… 😄 It was working at least… xD

@aksl Are keen to get your hands dirty and dive into “compiling and debugging iPXE”?? If yes is your answer, there is a way I could lead you.