Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

SBS Netboot service crashing

Created: 04 Dec 2012 • Updated: 11 Dec 2012 | 5 comments

Hi guys,

Need some help.

I'm using DS 7.1.

I'm set up a clean Windows 2003 SP1 R2 server to be a Task/Package server.

I installed the Deployment Site Server Components.

However, it seems like the _Symantec_netBoot_Interface service keeps crashing.

I've followed the instructions on the following KB - http://www.symantec.com/business/support/index?page=content&id=TECH138155

But it's seems to keep crashing.

I'm out of ideas. 

Your help is much appreciated.

Richard

Comments 5 CommentsJump to latest comment

Nelo's picture

check the IP address on the settings file on the SBS file matches the IP address on the PXE Server Settings page.

danzeit's picture

I manage to have the _Symantec_netBoot_Interface service to keep running.

However, _Symantec_netBoot_Mtftp, _Symantec_netBoot_NSiSignal and _Symantec_netBoot_Server services does not stay running for long. Is this by design? If so, what can I do to make it stay running?

Luckily it stays long enough to deploy an image or so.

Ishani Bose's picture

All 4 SBS services, should be in running state and should not stop after certain interval.

IP Address might be missing from in initialPXEConfigPath.txt.  

Location of file -C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\SBS\initialPXEConfigPath.txt and ensure the following two lines are present, with correct IP address:

Server_Listeners="10.3.0.1" (or whatever your site server's IP is)

Mtftp_Listeners="10.3.0.1" (site server's IP)

If this information was missing, or even if it was correct, reset this registry key to 0:
HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Deployment\Symantec Boot Services\HasSbsRegistered

And restart all the 4 services.

 

 

Tim.Jing's picture

Thank your Ishani, that fixed our services issues. Now on to the odd not booting in to PE issues.

Tim.Jing's picture

We had more issues after this. The machine would boot in to PXE but failed to find any Pre-OS files. This was resolved by rebuilading the PXE environment at the top. The file to look at is PXEset.ini, if this is not populated correctly by the Hierarchy, the server and ip filed will be blank.