January 28, 200719 yr In the old WinPE/winnt32 it was not required to reboot the computer *immediantely* after setup completes. With that, you could WinPE OPK a image over and once it was done manipulate the image if required.As an example, you could utilize the Winbom.ini as follows:[Version]signature=$CHICAGO$[Factory]Logging=YESLogFile=%WINDIR%\winbom.logUsername=guestPassword=[ComputerSettings]AuditAdminAutoLogon=YesSourcePath=%windir%FontSmoothing=ClearTypeDisplayResolution=1024x768x32Hibernation=NoExtendPartition=1[NetCards][WinPE]Restart=NoLang=ENGSku=pro.sp2ConfigSet=XP PRO SP2SourceRoot=\\10.210.1.6\OPKToolsUsername=guestPassword=[WinPE.net]StartNet=Yes[StartMenuMFUlist]Link0=Link1=Link2=(notice the RESTART=No)As you can see, this would install pro then continue on in a batch script. So you'd have your startnet.cmd look like so:factory -winpemkdir C:\additional-utilitiesxcopy /s /e /y /i \\10.210.1.6\OPKTools\additional-utilities C:\additional-utilitiesNow... it appears you cannot do that according to MS's documentation...RestartRestart specifies whether to restart or shut down the system after the windowsPE configuration pass. This setting is specific to Windows PE scenarios. Once image-based installation begins, this setting is ignored.ValuesRestart Specifies that the computer immediately restarts after the windowsPE configuration pass. End users cannot disable the restart. This is the default value.Shutdown Specifies that the computer immediately shuts down after the windowsPE configuration pass. End users cannot disable the shutdown.This string type does not support empty elements. Do not create an empty value for this setting. Valid PasseswindowsPE Parent HierarchyMicrosoft-Windows-Setup | RestartApplies ToThis element is available in the following editions and architectures.Editions Architectures the Windows Vista family AllXML ExampleThe following XML output shows how to set the computer to shut down after the windowsPE configuration pass.<Restart>Shutdown</Restart>See Also Microsoft-Windows-SetupHas anyone out there been more successful than myself at this? Edited January 28, 200719 yr by Metzen
March 4, 200719 yr I got the same problem, but created a work around for it;Just edit startnet.cmd;wpeinitnet use s: \\preloadserver\vistadiskpart /s wipe.txts:cd cmdcall xcopy.cmd ;where it finds xcopy /s /e /y /i \\10.210.1.6\OPKTools\additional-utilities C:\additional-utilities cd \cd 32bitDVDsetup.exe /unattend:s:\xml\basic.xmlI will post my complete script tomorrow at work!Good luck![Edit] Forgot to mention I diskpart the HD with "diskpart /s wipe.txt" so I do not need the .xml answer file settings to make a partition. Edited March 4, 200719 yr by Sanderrr
March 5, 200719 yr Author I got the same problem, but created a work around for it;Just edit startnet.cmd;wpeinitnet use s: \\preloadserver\vistadiskpart /s wipe.txts:cd cmdcall xcopy.cmd ;where it finds xcopy /s /e /y /i \\10.210.1.6\OPKTools\additional-utilities C:\additional-utilities cd \cd 32bitDVDsetup.exe /unattend:s:\xml\basic.xmlI will post my complete script tomorrow at work!Good luck![Edit] Forgot to mention I diskpart the HD with "diskpart /s wipe.txt" so I do not need the .xml answer file settings to make a partition.I found that setup.exe has a /noreboot switch. So, setup.exe /unattend:s:\xml\basic.xml /noreboot will remove the reboot.
March 6, 200719 yr Hmm, interesting. That way I don't have to copy files in place (in example c:\blah\background.jpg to c:\windows\blah\background.jpg) with a script via RynSynchronous after install. Thats the problem I ran in, because copy to c:\windows before setup then setup renames it to c:\windows.old.Thanks for the idea mate!
Create an account or sign in to comment