SetupComplete.cmd

A

azaghul

New Member
Messages
4
Reaction score
0
I'm gradually migrating from WinToolKit and working with AIO-multi image wim's (Win7+Server2008R2 [8 images in the wim]or Win8.1+Server2012R2 [5 images in the wim]).
I've worked out multi-patch integration across images, still using WinToolkit for addon integration, but have a question on post-setup commands...
Correct me if I've got the wrong end of things, but my "newbie" understanding is that post-setup calls SetupComplete.cmd, which seems to be common for ALL(?) image deployments? Is there a way to deploy one set of apps for a desktop OS or server OS or server core OS, ie: on a per image basis? Or is it that I'm only testing with a single image wim, and its only creating a single SetupComplete.cmd?
 
Last edited:
You are correct that there is one setupcomplete.cmd, usually.
There is a hidden feature of packaging setupcomplete.cmd inside the image itself, thus you get one per edition on that WIM.
To trigger that mode, make sure the WIM is not in the usual ISO folders (.\Sources dir).
For example rename it to "install2.wim" and then load. Don't forget to revert the name back before making the ISO.
The way to see that the tool will switch to that other mode is by the status "Isolated" on the Source page.

Let me know if that's clear, and more to it if it worked out as expected.
Depending how it goes, I could add an option to switch post-setup per edition, without working on an isolated WIM.
 
azaghul said:
but have a question on post-setup commands...
Is there a way to deploy one set of apps for a desktop OS or server OS or server core OS, ie: on a per image basis? Or is it that I'm only testing with a single image wim, and its only creating a single SetupComplete.cmd?
Click to expand...

You can add to the setupcomplete.cmd the OS/architecture detection and from there go to the section for what you want setup.
Autodetection can be done by reading the registry or detecting folders/files unique to those OS.

I can´t help with anything because i'm really busy here, not computer related.
 
Ah...the old "hidden feature" ploy..:)

Took me a couple of goes to work out what was required (NOT rename the wim in place, NOT have a per edition wim and merge them back after processing, BUT move the wim to a new "temp" directory to trigger isolated mode)...but then worked as indicated.
Now I know its there and how to work it, its just some manual handling to implement (copy wim to temp, process, copy wim back to source)...not sure how many people work with multi-edition wim's, but it would be handy if it could be added to the ntLite roadmap.

Much appreciate your assistance.

PS: I know this is an old post (https://www.ntlite.com/discussions/...grate-programs-which-do-not-have-an-installer), but has there been any further thoughts on addon integration?
 
You must log in or register to reply here.
Back
Top