Deployment Solution

Has anyone had the SBSServer.EXE process running at 99% for over an hour?

Here is my environment:

New install of SMP 7.5

Single server running SMP (v7.5.1670), Notification Server, Deployment Solution with the default Task Service and the Network Boot Service.

OS = Windows 2008 R2 SP1 (running as a guest VM on VMWare Esxi 5)

DB = SQL Express 2008 R2 (running on same box, installed during install of Altiris DS from SIM)

VRAM = 4GB

vHDD = 40GB (SQL is installed here). Additional Storage is on a 250GB LUN on an HP SAN. Altiris folder is here.

If I reboot the server, the SBSServer.EXE process shows 00 CPU in Task Manager.

However, if I go to PXE boot a computer, I notice the SBSServer.EXE process jump to 99% and it stays there

I have added the WinPE drivers in the Driver Management, and can verify they are in the location E:\Program Files\Altiris\Deployment\BDC\bootwiz\Platforms\WinPE\x86\Drivers\CUSTOM\Drivers

I have created the WinPE environment, and can verify BootWiz showed up in Task Manager, and the WinPE image is in the location E:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Bootwiz

I have created a job and set it in the Initial Deployment (for Unknown Computer)

When I attempt to PXE boot the computers, I see the message "Symantec NBS: Pre-Select Automation Processing. PXE-MOF: Exiting Intel Boot Agent"

I confirm that I have selected the following in MBS General Settings:

• Apply NBS Settings Immediately
• Enable the NBS Service
• Respond to unknown computers (and set the PXE Boot image to be my WinPE environment)
• Respond to predefined computers (and set the PXE Boot image to be my WinPE environment)
• Respond to managed computers (and set the PXE Boot image to be my WinPE environment)

I have also tried setting the NBS to OFF, and then back to ON again (after about 5 mins) but get the same problem.

First, for your managed computers, you should NOT be setting it to boot to your PE environment, but to "next device" instead.  Otherwise, you're telling ALL your computers to boot to PE.  I don't think you want that.

If you stop and start the service, does that help?  There should only be 2 services, not 4.  Be sure you're not seeing an old service running along side the new.  The new service IS called SBSServer.exe in the task server list, but making sure is never a bad thing.

Do you have logging enabled on that same page?

Hi Thomas

1)

This is a brand new install, so I set the Managed computers to PXE boot into the PE environment

Once it became a production server (with our managed computers imported in), I was going to turn off the option for managed computers to boot to PE.

2)

I have tried restarting the two services (the Symantec Network Boot Service PXE + TFTP) but have the same result

3)

I do have logging enabled - level 5