[systemsmb]

Hi guys.

Anybody know if you can get WPI working with RIS?


Hope everyone isnt as cold as I am. Hurts to type!!


Systemsmb

[Br4tt3]

I have never used WPI but from I get of it, it should defintly be possible to implement. With RIS, u get for example the same time / point of executions as from an ordinary unattend install (GuiRunOnce) where u could launch the app from. I guess it is just a matter of configuration (some cfg file) to point out where to obtain the .exe / .msi files to install..

Best Regards
Tha Sausage Eater

[mmarable]

It works just fine. It all depends on how you want to execute it.

I just put it in $OEM$\$!\WPI and executed it from GUIRunOnceEx.

It will not work running it from the network, unless you map a drive. So, if you're hoping to have a single WPI source on your server that each of your RIS images pulls from then you'll have to keep that in mind.

[systemsmb]

Thanks for the info.

How would you get the client machine to auto map a drive which it looks to for WPI and then get it to auto remove that share afterwards?

WPI looks very cool!

Systemsmb - still really cold here!

[RogueSpear]

Not to sound like a smart alec or anything, but why would you want to run WPI in an environment where you're using RIS to deploy workstations? You would be far better served to deploy as many applications as possible using Group Policy (or SMS if you happen to have that).

As far as mapping drives goes, this is pretty basic batch, VBscript, or AutoIt and a search should yield many hits detailing how to do it.

[systemsmb]

Hey guys I found a solution to my problem and thought I would share with the rest of you. Upon searching google I found the following code which should be saved into a CMD file.

CODE TO BE INSERTED

@ECHO OFF

REM Map network drive since we can't use UNC paths
net use X: \\support01\RemoteInstall /persistent:no

REM Determine the WPI startup path.
REM if wpi should run off the cd the replace %~dp0 with %cdrom%.
set wpipath=X:\wpi

REM Hide this command window.
%wpipath%\Tools\cmdow.exe @ /hid

REM Special registry tweak needed.
regedit /s "%wpipath%\common\wpi.reg

REM Make WPI directory the current directory.
for /f "delims=: tokens=1" %%i in ("%wpipath%") do %%i:
cd "%wpipath%"

REM Start WPI and wait for its end
start /wait %windir%\system32\mshta.exe "%CD%\wpi.hta"

exit

:end

FINISH


All you have to do then is, using GuiRunOnce within your RIS answer file is configure it to run that CMD file once Windows has installed and then WPI loads up.

This meets all of your requirements and does not require any mods to WPI.