vortex0007

It is possible to modify the way the GUI is displayed when running GUIRunOnceEx? I know one change the text of the title, text itself , but what I need to be able to modify is the window size. I currently have more than 25 installations happening and right now the box just runs off of the screen. Is there a way to fix this so that I can actually see what components are installing beyond the first 25?

Is there a way to change the number of columns that RunOnceEX.cmd displays when it runs? I currently have over 50 items that run as part of this setup phase and when it runs it only displays a single column so that it cuts off at least half of the items that are running.

Has anyone been able to make this work using Vista Build 5342?

The Mass Storage driverpack? Haven't heard of that one either.

IcemanND, Thanks for the reply but I've been running sysprep -bsmd for a long time now and have never seen this entry created during this process. If I manually add the [sysprepcleanup] to the sysprep.inf BEFORE running sysprep-bmsd will it actually populate this section?

In researching Sysprep.inf, I've come across several example files that include a section called [sysprepcleanup] but nothing that actually explains any details about what this section is. Can anyone point me to some documentation regarding this section? What's it used for? Should it be used? I only find a single line in the CHM's included with Sysprep and Windows PE so I'm a bit at a loss on this section. Any help would be appreciated.

If a Windows 2003 server has Secure Message Block (SMB signing) enabled, is Windows PE 2005 able to authenticate to a file share on that server? I can't find anything on Windows PE 2005 that states whether this is supported or not.

Well Google helped me out with this one. Problem solved. http://windows.about.com/od/tipsarchive/l/bltip035.htm

I'm using the sysocmgr.exe to add IIS to Windows XP installations after base install. When I run the command as: %windir%\system32\sysocmgr.exe /i:%windir%\inf\sysoc.inf /u:c:\test\unattend.txt" it executes but halts at the standard Windows XP Insert Disk command that reads "Please insert the Compact Disc labeled 'Windows XP Professional Service Pack 2 CD' into your CD-ROM drive (E:) and then click OK. You can also click OK if you want files to be copied from an alternate location, such as a floppy disk or a network server." But when I look in the registry under: HKLM\Software\Microsoft\Windows NT\CurrentVersion the sourcepath is set to point to the i386 directory on the local hard drive and not to the CD Rom. Is there somewhere else I should be looking to change the sourcepath?

RideGuy, Would you be willing to share your step by step for how you did this? I can't get this to work.

Is there a file included with Microsoft WinPE that will tell me the version of WinPE in use?

I'm trying to get an unattended install of Windows 2000 and Windows XP to do the following: Create C:\ with 90% of available space on hard drive 1 Create T:\ with 10% of available space on hard drive 1 The limitations are that I need to accomplish this through Sysprep and not WinPE or Bart's PE. Can anyone recommend how this might be accomplished? I've looked at Diskpart for the XP but I'm not sure if that will work within the context of Sysprep...... and I'm not sure if it works with 2000. Can anyone help?

How do you run an imaging package using Windows PE where the delivery method is PXE without RIS? Powerquest, Symantec, and Altiris all offer some form of support for Windows PE but not a single one of these vendors has documented how their products work with this.... Currently these imaging suites all follow the pattern of booting to a PXE menu, where control is then turned over to DOS to handle network authentication. I'm trying to figure out how to get DOS replaced by WinPE in this process. Can anyone offer any pointers?