• Content count

  • Joined

  • Last visited

  • Days Won


RP1 last won the day on April 17 2014

RP1 had the most liked content!

About RP1

  • Rank

Profile Information

  • OS
    Windows 7 x64
  1. The cpi:offlineimage line would be unique to your installation and what folder you use for building your image, so mine probably isn't applicable. Likewise, the syntax on the component name line can differ depending on whether you're doing an x86 or x64 image, and possibly by edition. I'd use WSIM or some other off-shelf autounattend.xml generator to set up a default file for your installation. Maybe just doing some placeholder setting in oobeSystem > Microsoft-Windows-Shell-Setup to make sure there's no syntax differences there, either. Then if you want to raw-edit the XML just template and build it out from there. If it's dropping the file in the correct $OEM$ folder you should be able to execute it with any switch as if it were a normal command line if set up as a FirstLogonCommands > SynchronousCommand execution. The only thing that does is time the execution after user creation when you're safely in the clear to install any of the packages in this switchless installer; what you execute and what command line switches you use are no different at that point than they'd be with any other standard means of integrating a switchless into Win7/8. I built mine in WSIM on Win7 Ultimate x64 as the first-and-only command in FirstLogonCommands, so I can confirm that method + the correct $OEM$ placement produces a working switchless installation. I don't use WinToolkit myself, opting instead for a combo of Windows Hotfixes Downloader for update/driver integration, WINNT True Integrator for addons and switchlesses, and WSIM/autounattend for settings and switchlesses with special post-logon requirements like this one. If you're having no luck you may want to try creating the autounattend file with WSIM--at least as far as setting up this installer--to produce a reliably working template before doing as you wish with the rest of your XML file via manual edit or adding/merging to it in some other program. That's the most fail-safe troubleshooter I can suggest, since I'm not terribly adept at writing or debugging XML by hand.
  2. You can stick it in your autounattend.xml file. I do it like this: 1. Create the $OEM$ folder in the Windows source to dump the switchless into the %SystemRoot%\Temp folder, like so: (Windows installer source root)||-- $OEM$ | |-- $$ | |-- Temp2. Copy the switchless to "Temp". 3. Set up your autounattend.xml to do a "SynchronousCommand" under "FirstLogonCommands" in the "Microsoft-Windows-Shell-Setup" settings, "oobeSystem" pass. Here's a snippet from my autounattend.xml (Win7 Ultimate x64) using the VB/C++-only installer: <?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai</CommandLine> <Description>Microsoft Visual B/C++ Redistributables (AIO)</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/win7dvd/grmculxfrer_en_dvd/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>You can run multiple commands as well if you only install certain components. For example, to do VC++ 2005 and 2008 only executing the /ai5 and /ai8 switches: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai5</CommandLine> <Description>Microsoft Visual C++ 2005 Redistributable</Description> <Order>1</Order> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai8</CommandLine> <Description>Microsoft Visual C++ 2008 Redistributable</Description> <Order>2</Order> </SynchronousCommand> </FirstLogonCommands>Add as many commands as you need, just bumping the "<Order>" number for each successive entry. Notes: -- You can change the install directory to whatever you want, so long as you put it in the proper $OEM$ folder structure. I chose Windows\Temp so the installer gets auto-deleted after use. -- It must go under the "oobeSystem" pass to launch after user creation, or else you'll get the same errors as before. -- Same method should work for most programs that have the same requirement of being run after user creation. -- There are probably other methods of doing it which other posters could elaborate, but this one has worked flawlessly for me with this particular switchless. And is good if you already use autounattend.xml and want to keep things nicely consolidated there. -- WSIM automates creation of autounattend.xml graphically if you don't want to deal with raw XML syntax. Download the Windows ADK from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=30652) if you need that tool.