MrJinje

Like I told Max, to change the image after the first reboot, you need to edit the install.wim spwizimg.dll copy. The boot.wim spwizimg.dll (and DVD\sources\spwizimg.dll for that matter) are only used for the initial boot, when installing from DVD or via setup.exe respectively. Everything after the first reboot is contained inside install.wim. That is why you have to change it in multiple places, because Microsoft included multiple copies in the installation process. It's more like you have to customize two OS'es to fully control the process. The Boot.WIM is actually a self contained Windows PE OS, but it only controls the installation process up until the first reboot. After reboot, the boot.wim hands off to the spwizimg.dll inside the install.wim (now on the HDD), and the HDD controls the process from first reboot to first login.

Technically speaking, yes, no point on a home network, "UNLESS" you want to be able to type your addresses by hand. having single number octets is quicker. I use 10.1.1.1 / 255.255.255.0

Have you tried this ?

Try this one. The free-ware "Simple" template can do everything you need. The crippled professional functions are nice, but can be duplicated by hand using the simple template. Since you are doing group policy and not online sales, you don't need most of the advanced features (emailing keys to customers, etc). You'll find the "simple" template is actually pretty advanced in it's own right. I'll let you know in thirty days if I can still create MSI with the basic template or not, the one I just made installed just fine with the /QN switch.

What happens when you try to access \\Computer2\C$ from your first computer ? Does mapping them as network drives work ?

Yes, this is normal, MS changed all the user variables, see breakdown table at the end of this page. http://en.wikipedia.org/wiki/Environment_variable#Default_Values_on_Microsoft_Windows

Try running your TimeZone from the OOBE pass. or Integrating it into the WIM with DISM /SET-TIMEZONE command.

Seems like a lot of trouble for something that can be done with a regedit. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Personalization] "ThemeFile"="C:\\Windows\\Resources\\Themes\\CLASSIC.theme"

There are various "Synchronous" and "Asynchronous" commands you can use. Mostly the syntax is the same but each is called from a different Pass and Component pairing. For instance. To do so from the Oobe Pass, you use Microsoft-Windows-Shell-Setup | LogonCommands | RunSynchronous (these do not run until install has fully completed and your user has logged in) From the Specialize and/or Audit pass you need to instead use the Microsoft-Windows-Deployment | RunSynchronous (this installs before your user is created, similar to setupcomplete.cmd) There is yet another for WindowsPE (but do not use it, OS is not installed yet), where the command comes from Microsoft-Windows-Setup | RunSynchronous From there, they are about the same and should look kinda like this. <RunSynchronous> <!-- First synchronous command to execute --> <RunSynchronousCommand> <Order>1</Order> <Path>\\MyNetworkShare\MyApplication.exe</Path> <Description>DescriptionOfMyApplication</Description> <Credentials> <Domain>FabrikamDomain</Domain> <UserName>MyUserName</UserName> <Password>MyPassword</Password> </Credentials> </RunSynchronousCommand> <!-- Second synchronous command to execute --> <RunSynchronousCommand> <Order>2</Order> <Path>C:\AnotherApplication.exe</Path> <Description>DescriptionOfMyApplication</Description> </RunSynchronousCommand> </RunSynchronous>

Under Boot Images you need to Create Capture Boot Image and then choose the Capture image after sysprep.

Maybe CMENU can determine the correct syntax (using "Identify Installer" feature).

Then you definitely need to check out WUD by jcarle. It allows full choice of which updates to exclude/download and puts them all in a folder for you. Basically it's just a list of every update and the tool auto downloads them. Trust me, very easy to use. I prefer it over gathering them from the Software Distribution folder (or yikes, manually downloading them from Microsoft.com).

My mistake I assumed you already knew that a batch file (.cmd extension) is just a .txt (text file) that has been renamed to install.cmd. That will not happen again. Please use notepad.exe to create your batch file. Then call "install.cmd" from the same place while creating your SFX instead of the regedit command. If I was you I would re-read/combine the good parts from post #18 + #27 until you figure it out. Everything you need to know has already been discussed in this thread. If you need a step by step. 1) Open Notepad 2) Paste Regedit command 3) Hit Enter 4) Paste delete reg file command 5) Save file as "Install.cmd" (use quotes or it gets named Install.cmd.txt and you will have to manually rename the file) 6) Remake your SFX including the "Install.cmd".

Good luck, it isn't very complicated once you have your domain all set up. Let me know if you need assistance with GPOs and getting them to apply to the right set of computers/users.

Yes, the files directly from Microsoft are the same, save for being encapsulated inside an .EXE so people can install them manually. The rule is if the KB # matches it is the same update. Windows Updates used cab format because it is an automated process and users do not have to be able to install them manually when downloaded via Windows Update. Does that make sense ?? Can't remember if nLite could integrate cabs, but if not you can also download the correct files you need for nLite using WUD or like John said, RyanVM has a pack for this. (but at times is hard to download or unavailable)

After installation what is the path to the registry file you want deleted. If it is "Program Files\Stars\Test.reg" here is the command. DEL /F "C:\Program Files\Stars\Test.reg" Otherwise, go here and adjust as needed. Instead of calling the TEST>REG directly from your SFX, you will need to create a .cmd file and include both commands. Be sure to put the registry command before the delete command, otherwise it won't work. Then repackage your SFX with the .cmd file and you are all set.

Take a look at this, there seems to be a fix after the OS is installed. But you would have to figure out how to push the needed reg settings into your profile before the synchronous commands run. http://social.technet.microsoft.com/Forums/en-US/itproxpsp/thread/e3008c75-48b4-4a6c-bc14-5a20ce72cd7f One method might be to mount your WIM offline and edit the hives manually, another could be to script it to occur during the setupcomplete.cmd stage. I haven't had this problem at all with any .EXE during setupcomplete.cmd, maybe before going to all the above trouble, first try installing your apps using SetupComplete.cmd via the $OEM$ folders. HINT: SetupComplete.cmd runs in an administrative context, while any synchronous commands only run as the logged in user.

This doesn't use the force command (run it separately if you need) but it seems to integrate them, because I get a pop up during installation asking permission to install an unsigned driver.

Neat script, but what about this. According to Wikipedia, using the RunAs command is similar to running the "SU" command from linux, not SUDO.

Well, don't forget that the WINRE.WIM (inside install.wim) also contain a few copies of these files as well. If you mounted it and changed them, then you have a fully SevenUA recovery environment as well.

Likely the closest thing will be using a Group Policy to install software. http://support.microsoft.com/kb/816102

Figured out what this was, it turned out to be the "License" folder containing the R2 EULA. See here.

What app are you trying to install. What command are you using to install it.

Maybe on Vista DVD's, but like I said, I don't think that is supported anymore with Windows 7. Are you saying you have success with that method ? You should be using DISM /SET-PRODUCTKEY

Are you getting the powder puff in the spwizmg.dll that is inside the Mount\Windows\System32 folder ? (HINT: it's inside install.wim)