DS7.5 NBS Services don't completely install, or are missing, on an NBS Site Server
Last Updated March 01, 2016
When you have an environment where you have only your SMP as the main server, and you try to install the NBS services on it (you must have at least one NBS server if you want PXE in your environment), it may appear to install but you will notice that the Symantec Network Boot Service (PXE and BSDP) and the Symantec Network Boot Service (TFTP) do not show up in the Windows services.
The same thing may happen on other NBS Site Servers. In the console, under Site Management, the server(s) may show that NBS is installed, but if the services are not actually present, you will be unable to build a PXE environment and will sometimes pop up an error when you try to make changes to the NBS configuration.
Another potential symptom may include having the services installed on a site server, but the NBS settings in the console do not show that. IF you then add the NBS services to those site servers, you may run into the problem above where the services are now missing (they're removed), but in the console, it all "looks" to be running fine.
We're not 100% sure, but we THINK it has to do with an installation of the site components happening a 2nd time. The services appear to be like a switch every time it's installed. First time, they're added, second time, removed, third added, fourth removed, etc. So if, for whatever reason, the MSI has run a second time, the services may go missing even though the rest of the files are still present.
To fix this issue you will probably need to manually uninstall and reinstall the SBS package which is located by default in this location:
For x64 --Program Files\Altiris\Notification Server\NSCap\bin\Win64\X64\Deployment\SBS\Symantec_DeploymentSolutionSBS_7_5_x64 For x86 --Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\SBS\Symantec_DeploymentSolutionSBS_7_5_x86
Run this command from the location of the package, with Administrator rights in a Command Prompt: msiexec.exe /i Symantec_DeploymentSolutionSBS_7_5_x64 skipaim=1
After you run this command it will give you the option to Uninstall or Install the package. This can be done from any site server as well. You can either map to the SMP to pull the packages directly from there, OR pull from the nearest package server.
Additional Solutions: 1) In some cases, It may be necessary to install the 2 NBS services manually through command line:
sc create SymantecNetworkBootServicePxe binPath= "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\SbsServer.exe" DisplayName= "Symantec Network Boot Service (PXE and BSDP)"
2) If the NBS services still do NOT report back to the console as 'Installed', run regsvr32 "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\DeploymentSolutionAgent.dll"
3) Check the 'Details' in the properties of the SbsServer.exe located at --\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS. If the SbsServer.exe is version 22.214.171.12435, please download version 126.96.36.19955 attached to this document and replace existing.
4) In some cases, the NBS services are stuck in a partially-installed state where they cannot be installed, repaired or uninstalled. If this happens, try the below method:
a) Open regedit.exe
b) Browse to: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products
c) Click on the 'Products' key (has a folder icon) in the navigation pane. Then select Edit>Find and search for 'Deployment Solution SBS Handler'
-If 'Deployment Solution SBS Handler' cannot be found, this solution will not be applicable to the resolution of your problem.
d) Once the above entry is found, right click on the randomGUIDkey (i.e. 1234567890ABCDEF) that contains the 'Deployment Solution SBS Handler' entry in the navigation pane and select 'Export.' Create a backup of this key.
e) After the key has been backed up, right click and delete it from the registry.
f) Attempt reinstalling the NBS services again via command line: