Klintan

Hi Sorry for quoteing from the begining but I did not see any other options here., lets start over What error do you get when xcopy the file? Does the destination path exist? Some "dos" commands will not work if argument 2 end with a backslash (however this is not the case for xcopy). -- Regards Michael K

Windows is not case sensitive in usernames and I prefrerrd that the script do the same. With active diretory I will help you in any way I can.

I can really see benefit if you add two more functions like IsMemberOf("sales") IsComputerInOU("OU=.EMEA,CN=Domain,CN=COM") The first one is easy to explain. Function return true or false if the user is a member of group "sales". This also includes nested groups. Second one I'm open for discussion/alternatives. Let’s say computer belongs to OU=Malmo,OU=Sweden,OU=EMEA,CN=domain,CN=com then the function will return true. All OUs inside domain.com\emea\* will return true. If you don't want to include all, you have to include this in your query (OU=Malmo,OU=Sweden,OU=.EMEA,CN=Domain,CN=COM). It would also be simpler if you don't have to include the hole path. A simple "OU=Malmo,OU=Sweden" should do fine. This way you could also query for a computer like so "CN=computername" Perhaps its better if you add support for a second optional argument to the function. This argument will decide if query string is partial or full. Or even better add wildcard support like "*searchforthis*"

I’ve been searching for a Windows Post installation utility for our business. I’ve tried a few from companies like Microsoft, Altiris, ScriptLogic and more. But none is as good and straight forward as WPI. I use WPI v4.3.6 at home for my personal use and just love it. However the WPI is not very optimized for business use. It would be very nice if you could develop a WPI for business use. It could be based on the existing WPI but example some addons like * More dependencies for corp. use like user group membership, computer belongs to OU etc. * Separate the configuration gui from the WPI so that where will be one gui for users and another for deploy administrators. Are there any plans for this?

Hi I've the same problem with some installers. You start with a setup.exe and after a short wile you get the command prompt back again and the installer is still running (This because the installer have created another process and ended the original). My solution is more general. Create a script that monitors a installer process. Then create a batch script like this. Example from when installing MSDN @setup.exe @Cscript wait.vbs 001msdn.exe --wait.vbs--- Option Explicit 'On Error Resume Next Dim bCheck, quitCode, colItems, objItem, objWMIService, strComputer, sArg1 strComputer = "." If WScript.Arguments.Count > 0 Then sArg1 = WScript.Arguments(0) Else WScript.Echo "Enter <program.exe> as parameter" WScript.Quit 1 End If Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") WScript.Sleep 5000 quitCode = 2 'No program.exe found Do bCheck = False Set colItems = objWMIService.ExecQuery("Select * from Win32_Process Where Caption='" & LCase(sArg1) & "'",,48) For Each objItem in colItems quitCode = 0 bCheck = True WScript.Sleep 1000 Exit For Next Loop While bCheck WScript.Quit quitCode ----