I have not had much luck with Software Distribution. It always seems that I send out a job only to see about 70% of the machines fail. I know each job is different, but I keep thinking I must be doing something wrong. I have been working on deploying a package for Rate Assessor by EMB. This is an insurance industry application. I setup 2 distribution packages. One is a .exe and the other is a batch file.
The EXE job is running: \\landesk2\landesk$\EMB\RateAssessor\RateAssessor2.3.140\apps\RateAssessor\setup.exe
this is in the command line options: /s /v/qb-!
I added the additional files which includes the setup.iss
The BATCH job runs next and is running: \\landesk2\landesk$\EMB\RateAssessor\ra23_inventory.bat
Both Jobs run under a single Policy scheduled task with the local system account.
We are on 8.8 SP3.
Here are the contents of my batch file:
REM SetACL to open up the data directory for Rate Assessor DBs to all users
copy \\landesk2\landesk$\SetACL\SetACL.exe C:\LDPackages\SetACL
C:\LDPackages\SetACL\SetACL.exe -on "C:\Program Files\EMB\Rate Assessor\Data" -ot file -actn ace -ace "n:users;p:change;i:so,sc"
REM Create the Registry key for Landesk Inventory
> "%temp%\ra23.reg" ECHO Windows Registry Editor Version 5.00
>> "%temp%\ra23.reg" ECHO.
>> "%temp%\ra23.reg" ECHO [HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\Iventory\Custom Fields]
>> "%temp%\ra23.reg" ECHO "ra23"=dword:1
REM Adding Landesk Inventory Registry Entry to Registry
regedit.exe /s "%temp%\ra23.reg"
"C:\Program Files\LANDesk\LDClient\LDIScn32.EXE" /NTT=LANDESK2:5007 /S=LANDESK2 /I=HTTP://LANDESK2/ldlogon/ldappl3.ldz /NOUI /NOCD /sync /f
Can anyone tell me what might be going on when I deploy this? I am getting failed messages for each machine. So far, the machines are returning a result of "Software distribution task has been started" with a status of "Failed"