Deployment status sucess but program does not run in client machine

Question

Hello Guys,
I have created a package program to Run a batch script Install.bat
Program Properties:
Command Line: Install.bat
Run: Normal
After Running: No action required.
Run Mode: Run with administrative rights (Allow interact with users)
When i deploy this package i see Success in deployment status very soon, But the program doesnot run in client machine.
Please find my batch script below for more info.(manually installed Install.bat in system context cmd, it works perrfectly )
Please help me, where am going wrong
rem ECHO OFF
SETLOCAL
SET WORKING=%~dp0
echo Installing Office 365 pro plus NY package:
echo ------------------------------------------
%WORKING%setup.exe /configure %WORKING%install32ny.xml
IF NOT EXIST "C:\Program Files\Microsoft Office 15\root\" (goto _ExitInstall)
:_CopyingFile
echo Copying Script to Office 365 INSTALLDIR:
echo ----------------------------------------
XCOPY %WORKING%Pin-Unpin.vbs "C:\Program Files\Microsoft Office 15\root" /C /F
IF NOT EXIST "C:\Program Files\Microsoft Office 15\root\Pin-Unpin.vbs" (goto _ExitActivesetup)
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\Office365ProPlusNY" /v "StubPath" /d "cscript.exe \"C:\Program Files\Microsoft Office 15\root\Pin-Unpin.vbs\""
/t REG_SZ /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\Office365ProPlusNY" /v "Version" /d "1.0" /t REG_SZ /f
%WORKING%Launch.vbs
exit /b %errorlevel%
:_ExitInstall
echo Aborting Installation:
echo ----------------------
echo Office 365 installation failed.
echo %errorlevel%
exit /b 3
:_ExitActivesetup
echo Aborting Installation:
echo ----------------------
echo Activesetup Script error to INSTALLDIR
echo %errorlevel%
exit /b 4

Answer 1

It's just starting the command lines one after the other and after that simply returns a success of starting all the commands.  Two things you should do to successfully use a batch file like this:
Use start-wait constructions, so the next action won't start before the previous action is finished. For the exact command lines see:
http://technet.microsoft.com/en-us/library/bb491005.aspx;
First test the batch file with psexec, to see how it behaves with SYSTEM credentials.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude