@Scott-B the address is stored in the settings.json file, as long as the new address its being pointed to has the same certificates (if its the same server then all is good).

I’m not sure how well this would work, but you could try using a snapin, that changes the files, and reboots the machine. I’d suggest trying it on one machine first and see how it goes.

@tywyn the largest difference is that SYSTEM is not allowed (by design) any interaction with the user or userspace at all. This probably also means the user’s account too. This is Microsoft’s design, not ours - and they went that route for security reasons.

When developing snapins, if your snapin will work manually but not as a fog snapin (and you’re sure you deployed the snapin correctly), you can normally assume the problem is because of the above.

Try what @Avaryan posted.

@Obsidian said:

Do I need the fog agent installed or just to register it with the fog server?

As Avaryan said, there is no need to install the client for registering. Though it can make it easier. Clients should come up as pending hosts in the FOG web interface if you have the fog-client installed on the machines. But for domain joining (and host renaming) you need to install the fog-client anyway.

@sebastian-roth Hello yes you can mark this as solved! I also want to point out that @george1421 has been great help with my troubles with getting Fog to work. He went above and beyond to help me get sorted. Really appreciate the hard work you all are doing! Thank you once again and happy holidays!

I think @george1421 is right, it really seems like a uefi image was deployed to a bios system.

@scott-b
These are interesting:

11/29/2017 11:19 AM PrinterManager Adding printers 11/29/2017 11:19 AM PrinterManager CutePDF Writer already exists 11/29/2017 11:19 AM Printer Adding: \\printerservername\Kyocera 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox Color

Because the first one says ‘already exists’ but we don’t see the same message on the others, meaning they were not there already. This is strange. Asking @Joe-Schmitt to look at it.

Thanks @Avaryan and @Wayne-Workman. What you’ve mentioned about Fog running scripts as the System user and it not running for all users is correct. I’m going to have to go about what I wanted to do a different way but there was no issue with Fog or anything, thanks again.

@george1421 Thanks George, using net start seems to work.
@Scott-B The fogclient is included in the Image as this is the way I do it in my Win7-Images without problems.
As for now I’m fine with George’s solution, but I keep your tip in mind if other problems may show up.

@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