LocoBenno

Think I've worked it out, I've used the SetupComplete.cmd to do the PSP install (the multiple methods mentioned all work) and registry tweaks. Whether or not this is the right way, it works, good enough :-) Thanks again for your reply. Cheers and beers Benno

Hi Leen2, thanks for posting I'll give this a try, which setup pass are you calling the batch file in? Cheers.

Hi all, having a @#$% of a time trying to integrate the PSP (8.30) into my WDS unattended install of 2008. Concentrating on the Standard Edition for now, everything else will fall into place after I get this sorted... There are three ways (I can see) of installing version 8.30 of the PSP unattended. The first is to run "setupex.exe", which fires up HPSUM, automatically runs an inventory and then installs what's it detects is required. The second is to use the prefabricated batch file "bp000613.cmd", the third is (I believe) a legacy installer where from a command line or batch file, run "setupc /use-latest" (that's the method I use for my 2003 RIS installs). Anyway I've tried all three methods in different passes of the install process, both as native synchronous commands and calling from a batch file and none of them work. The closest I have come is calling setupex.exe from in the specialize pass, however it's auto inventory fails and nothing gets installed. I'm using the $OEM$ folder structure to pre-load the setup files to the local hard disk Have any HP people had any success with this yet? Actually there is one other thing if you could possibly help, how does one disable the UAC, and in which pass? Again I've tried calling it from a batch file and synchronous command with no success. And is it perhaps the UAC that is preventing me from installing the PSP? Anyway my main issue is the PSP, if anyone has had success with it and could help me out I'd really appreciate it, thanks for reading. Cheers and beers Benno

I've also found that you have to change the sourcepath in two locations, always worth considering: HKLM\Software\Microsoft\Windows\CurrentVersion\Setup SourcePath= and HKLM\Software\Microsoft\Windows NT\CurrentVersion SourcePath= For some reason I've found only changing one of these values doesn't work. Changing both always works, praps I've just run across a glitch unique to me. Cheers and beers Benno

Hi, newbie here, I've found this site an invaluable resource in the past and pledged that one day, if I found something that can help, I'd sign up and share it. I've seen a few alternative methods posted around but not this one, and I apologise if I've missed it somewhere. But here goes... I've been putting together a RIS environment to deploy i386 and x64 versions of Win2K3 - we're a HP ProLiant shop with 190 servers and counting - and had previously been spending thousands of bucks licensing LiveState Recovery for each of them. So I piped up and suggested RIS as a no-cost option for initial deployment of server images. I'd used RIS extensively in previous jobs to deploy workstations so I knew a ton about it. Into the fray I stepped, and of course the first hitch was to get past that pesky "F6" section of the windows build. Now most of the doco out there (including Micro$oft's) say that you can't use OemPreinstall=Yes if you are deploying MassStorageDrivers via the TEXTMODE setup. "Bollocks!" I said, that totally kills my $OEM$ tree of apps, drivers and such that will make my image as a whole hands free. The last two days I've been racking the brain in white papers and forums, then I thought I'd step out and just try something different; lo and behold: The doco suggests for TEXTMODE setup, you build the image tree as such: .\<ImageName>\i386\$OEM$\TEXTMODE ...and as long as OemPreinstall=No, the "F6" portion will work. And it does sure enough. BUT, if you move the TEXTMODE folder to: .\<ImageName>\$OEM$\$1\SETUP\APPS .\<ImageName>\$OEM$\$1\SETUP\DRIVERS .\<ImageName>\$OEM$\$$\Resources .\<ImageName>\$OEM$\$$\System32 .\<ImageName>\$OEM$\TEXTMODE .\<ImageName>\i386 ...and remove it from under i386, it works! No more copying files in CMDLINES.TXT, no more scripting funky scripts, it simply works just like it ought to. Giddyup!!! I hope this helps out. Please let me know if I've just lucked onto something glitchy (what a great glitch to have btw ) and unique to my build. My RIS installation is by the numbers defaults all the way through, and I'm using RIS images built from setupmgr.exe with additions. No CMDLINES.TXT; apps and tweaks I'm doing using [GuiRunOnce]. Cheers and beers Benno