There are times the Site Server components for Deployment Solution fail to install, or fail to install completely and/or you find you need to run the installation manually.
The site server components were installed, then removed via policy, and then wont reinstall again
Environmental issues block the full/complete installation
Wrong batch file/version are attempted to be installed (i.e. x86 on x64 or vise-versa)
You can run the installation manually, as follows:
Find the TaskHandlerInstall_x86.bat file in "C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\Task Server Handler" (or look for the x64 file under ...\win64\x64\...)
Run the batch file manually.
If the problem persists (usually portrayed by portions of the product missing, like part of the WAIK folders):
Open the batch file
run each MSI individually in the order shown.
NOTE: The first 5 lines of the batch file are for an uninstall - don't use those lines. Use the ones at the end.
NOTE: The MSI command lines are designed to run hidden (/qn). The best way to run these is to include /skipaim as the LAST switch (remove everything else) so you can see the output.
NOTE: The registry entries have been run (on first run of the batch file), so don't worry about those lines.
The Batch File has weak error handling. If one of the MSI's fail for whatever reason (i.e. on one system, WMI was corrupt and had to be reloaded), a log is generated in the TEMP folder, but the batch file continues to the next MSI and does NOT report up to the NS the. This can be seen often on a manual run, since the MSI's are run hidden.
Imported Document ID: TECH157551
Subscribing will provide email updates when this Article is updated. Login is required.