iamtheky

its a shortcut created by WAIK, you can also just run C:\WINDOWS\system32\cmd.exe /k "C:\Program Files\Windows AIK 3\Tools\PETools\pesetenv.cmd" Your argument path might be different depending on your system architecture and version of WAIK. Just search for pesetenv.cmd and use that path, if its not there, go install WAIK.

i believe it's referencing the boot.wim in case you havent tried going back to the beginning, open your deployment tools cmd window 1) ' COPYPE X86 C:\WinPEx86' 2) 'mkdir c:\winpex86\export' 3) imagex.exe /export C:\winpex86\winpe.wim 1 C:\winpex86\export\x86boot.wim replace your boot.wim in WDS with that x86boot.wim in your export folder and see if the issue persists...

Think I jumped the gun on the context menu stuff, that was all directly related to mmc.exe forcing closed when detecting an ie version of lower than 5.5 (the autoit GUI was doing its damnedest to keep the diskmgmt window painted, and i was doing my best to click on stuff that had already been terminated). I'll let you know how the IE stuff goes. IE error is gone, however blank menus still persist (File, action...and all the top level menus and icons exist, all context menus are blank), all the Registry Entries I checked existed. To confirm, Im just compiling your regwrites to an exe, and calling that from startnet prior to the mmc GUI. Does that seem kosher?

closer, now i get the GUI with a message "could not create snap-in Disk Management CLSID {DBFCA500-8C31-11D0-AA2C-00A0C9274983}" Havent even googled it yet, in hopes you saw this in your efforts as that is a beastly amount of registry entries and certainly took a fair amount of time to gather. Once again thanks for the assist. **I could not find: %SystemRoot%\System32\dmdskres2.dll %SystemRoot%\System32\dmvdsitf.dll on my local system. I will try and hunt those down to see if they are the culprit, but they were also not referenced in your registry adds. Found everything in a win7 sys32 and added those, the files fixed the error. It is showing the Drives, however the context menus are all blank, and anything i click it returns "windows could not report the error". I also get an error on launch of the GUI saying it cant run on anything prior to internet explorer 5.5...looking at that now

many thanks sir. I will certainly keep this updated with my progress.

awesome, any direction you can point me in is better than where im at now!

Straight PE3 with a startnet that calls our autoit goodness: We are building an extensible menu for deployments from WDS. The user selects a catalog from the treeview, we tell them how many indexes there are, then throw the GUI for them to partition the drive (currently it is behind the scenes, and can only handle a single drive, dividing it evenly based off the number of indexes. And if the # of drives = the number of indexes it will do one per). However, when we were thinking through edge cases like, how to adapt for someone that has 2 drives and 5 indexes and only wants 3 of the 5 indexes, we decided its best to just give them a GUI.

Is there a way to use in a standalone manner the "drive options (advanced)" GUI from a standard install? http://www.sevenforums.com/attachments/tutorials/45431d1262556182-partition-hard-drive-windows-7-install-partition_08.png We would like to offer this menu in our WDS pushes. If that is not feasible, is there a quality partitioning GUI y'all would recommend for the PE environment. *Just found IceMan's diskmgmt.msc gui stuff in the autoit forums, playing with that.... That blew up, after adding the files from the most recent mmc KB, diskmgmt.msc, and apphelp.dll. it blew up with a fat "class not registered" error. and any attempts to regsvr32 the dlls excepted with the "no entry point" error.

i would throw all your commands in to a batch file with a bunch of cmd /ks and pauses or an autoitscript with some error handling. so that your setupcomplete.cmd has one line calling that script. At least then whatever is blowing up should be visible on screen. Its just a biatch to troubleshoot something that does not appear on screen nor log.

this in case you have dagent installed. And it is normal for it to be gone when your system comes back up all prepped.

can you post the contents of your setupcomplete.cmd, my crystal ball is leaning towards syntax error. And it only runs once and under system authority prior to any logons, would be of no use but evil to leave that for a user to browse to.

can you still do this from setupcomplete.cmd? Set this: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\ControlPanel\NameSpace\{025A5937-A6BE-4686-A844-36FE4BEC8B6D} to one of these: Type 381b4222-f694-41f0-9685-ff5bb260df2e to use the Balanced plan. Type a1841308-3541-4fab-bc81-f71556f20b4a to use the Power saver plan. Type 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c to use the High performance plan. **You can also type the power scheme GUID for a custom power plan that you have created. To determine the GUID for all existing power schemes, type Powercfg /List at the command prompt, and then press ENTER. http://support.microsoft.com/kb/935799

the switch on cmd.exe, cmd /c = keeps it open till you are done with it and then closes it automatically. If you are having to troubleshoot maybe cmd /k as that should cause it to persist (though you will end up with many persistent cmd windows if you use cmd /k in multiple places) maybe change your lines to - 'Start /wait cmd /c foo.exe'

probably in something like this format. my items arent so much starting as they are waiting for you to press any key, and then subsequently close the app. but you should get the idea. Maybe echo something more useful and take out the pauses as they only exist because so you can step through it. Not exactly a progress bar proper, but will still inform the user of what is occuring. @echo off cmd /c echo first item starting... pause start /wait notepad.exe echo first item complete... pause echo second item starting... pause start /wait iexplore.exe echo second item complete...

Throw those 6 commands in C:\Windows\Setup\Scripts\SetupComplete.cmd minus the "cmd /c " at the front of them all.

i vote throwing it all in setupcomplete.cmd, if the title was asking a preference. The error(s), if any, should be visible and its equally as functional.

The I/O Panel: "We Take Hard Disks in the SAS" official name, not so much with the slogan....

what are you mouseclicking? and if you are only sleeping 35 seconds, if you were trying to sleep 35 min = sleep(2100000) my aim would be to wait for all the other exes in the cs5 suite to finish. which process is last? if its not going to be completely automated just hang a msgbox after your commands and click it when you are done.

i would run a blocking function like a msgbox autoit script and then a line to restart in the script, rather than in setupcomplete. should prevent it from running off without you being able to see what is occuring. My guess is you are running adobe***.exe from setupcomplete but that process is spawning another installer and ending - when seupcomplete sees that first process end it moves on. something like the below should allow you to wait for a complete installation (edit.: and watch the process) run ("taskmgr.exe") msgbox(0, '' , Click Ok when complete") run ("shutdown -r -t 0" ) ...once you have it installing completely i would see if there is a logfile or something it writes last, or get the last process and use that to queue up that shutdown i.e. while 1 if processexists("lastprocess.exe") Then if not processexists("lastprocess.exe") Then run ("shutdown -r -t 0" ) sleep (50) ;edit 2 - no need to loop as hard as possible Endif

with the autoit window info tool, hit that second tab 'control' and see if its changing over the different checkboxes. If they are usable you can avoid mouse commands altogether opting for just controlclicks. that combined with a blockinput(1) would for the most part alleviate the issues allen2 described. Though if you can get away with a commandline full of switches I would very much recommend that route.

Provided there is no available command line argument for the exe: have you used the auotit window info tool? if you can get a proper control name I would recommend using controlclicks over mouse clicks. It might help make the install more consistent on varying resolutions. or if you install it with its silent switch does it still execute automatically or the below code which wont uncheck it, but would kill the executed process as soon as the installer kicked it off runwait ("installer_odock.exe") While 1 If processexists("executed_odock.exe) Then processclose("executed_odock.exe") Wend Edit: making it legible

I would still go simple using the Find command to filter as needed, the IPenabled=true whittles it down greatly as well. but using the miniports as example wmic nic get name | find /i "miniport" wmic nic get name | find /i "miniport" | find /i "WAN" wmic nic get name | find /i "miniport" | find /i "WAN" | find /i "L2TP" but in your case i think it might be easier to work with what is not included, thus post #5 or a more generic: wmic nic where netconnectionID="Local Area Connection" get name | find /V "VPN" Setting this return, and using it in reg query however.... I'm rooting for that next, I need to learn.

that sounds like a fun problem, ill post back if i find a workable solution. Other than that, it is the intended effect?

here is the autoit code to do so, runs pretty quick. It will dump all the resized images into the directory you run the script from. 98% of the credit goes to the authors of the functions I just drove. Edit: added spoiler tags to avoid the WOT

wmic nic where netconnectionID="Local Area Connection" get name | find /V "Cisco"