Rolling FOG out to US Site

[RobTitian16]

@george1421 Indeed, this is something I’ve just found out - the SetupComplete.cmd is there with the FOGService.msi, but the .cmd is never actually executed. The target OS’s are always Windows 7/8/10/Server 2008/2012 R2/2016.
I’m currently testing this with a Windows 7 x64 OS.
I can’t see where the post install script is actually telling the SetupComplete.cmd to run, though. I can see it copies, but nothing tells it to run.

[Tom Elliott]

@RobTitian16 It will run as soon as the system completes sysprep steps (Setting up your device).

The last thing it does is “SetupComplete.cmd”.

The path should be:

C:\Windows\Setup\Scripts\SetupComplete.cmd (though you can try with setupcomplete.cmd) as well.

Of not, for Windows 8 and Windows 10, if the image is sysprepped using an OEM version of the software it will NOT run the setupcomplete.

[RobTitian16]

@Tom-Elliott Ahh okay. Is there a way to run this without the image being sys-prepped?

[george1421]

@RobTitian16 yes if you are using an unattend.xml file.

[george1421]

@RobTitian16 said in Rolling FOG out to US Site:

I can’t see where the post install script is actually telling the SetupComplete.cmd to run, though. I can see it copies, but nothing tells it to run.

See I think there is where you may be a bit confused (and rightly so). The FOG post install scripts run in linux so they can’t touch any windows programs or windows behavior. All we are doing with the post install script is placing things where windows expects to find them. As Tom posted Windows OOBE will run what ever is in the setupcomplete.cmd file after OOBE is done and before the first login window is displayed. This is a windows thing and has nothing to do with fog other than fog placed that file there. That file could and should have been there when you captured your master image. But since it was not you are using the fog post install script to kind of patch what should have been there prior to image capture.

[RobTitian16]

@george1421 I didn’t think the unattend.xml file would, considering you say in the tutorial:

“Note: the unattend.xml file is only used if the reference image was sysprep’d before image capture.”
Unless you’re basically saying to sysprep it. In which case… I guess I’ll have to as I can see the benefits of doing so now with this script, etc.
Thanks for the help and support as always! It’s been a challenging one, but hopefully one that will be immensely beneficial

[Quazz]

@RobTitian16 SetupComplete only runs at the end of OOBE state (Out Of Box Experience).

Might I ask why you can’t sysprep?

[george1421]

@RobTitian16 First of all I’d like to state for anyone that find this thread in the future this current issue that Rob is facing is not a FOG issue but a Windows image creation one. This thread really needs to be marked solved as the original issue has been addressed. I’m not saying that your current issue isn’t important, only based on your original post this issue has been resolved.

With that said, Rob I think you need to take a look at how you are creating and managing the imaging process. I can give you an option on how I do this today, but that may not fit in with your overall plan. I use MDT to create my reference image using the lite touch process. From there I sysprep and capture the image with FOG. I use FOG to deploy the image and inject the model specific drivers using a post install script. During OOBE windows picks up the drivers and installs them and then by using a post install script (that I placed in the proper location before syspreping the system) run any last minute activities like installing AV or GUID based applications that are required. Even with sysprep the system takes about 15 minutes to go from bare metal to ready to deploy using FOG. If a new computer model comes out, I just update the drivers cab and thats it. I can/do use the same captured image for every computer model.

[RobTitian16]

@Quazz Simply because it removes some settings we like to keep, otherwise users can spend ages getting everything up and running again.

Anyway, thanks to everyone who pitched in with this It really is appreciated!
The original issue was answered some time ago and this thread has evolved with the problems associated with it. As such it can be marked as answered.

[Tom Elliott]

I wonder if it would be worth while to capture the idea of the whole thread into the scope of a wiki?

For example, showing how to use the Location plugin.

Multiple “fog servers” cross communicating images.

Post scripts that are useful for customizing the client information and installation.

Etc…

[george1421]

@Tom-Elliott Tom I feel you are right here. While this is a pretty lengthy thread, there is a bunch of information that can be gleaned from it. What Rob is doing is pushing the envelope of the FOG infrastructure (which is great since it forces FOG to mature and grow). This is the type of activity I would like to see in the FOG Project. I would (personally) like to see enhancements around the “fog servers” cross communication to eliminate the human involvement. Maybe for FOG 1.3.1 or a brilliant plugin (hint, hint)

My intent was not to cut this thread short of completion, just as a moderator it thing its gone a bit past the original post which hides the rich content of the post. I do think Rob’s current issue should be forked into a new thread since his complete issue is not resolved just yet. Its close but not solved.

[RobTitian16]

@george1421 +1 for a wiki page. This is really useful stuff and I only found out about it when coming onto the forums and talking with George. Without the forums, I wouldn’t have ever found this out/get it working.