Deployment and Imaging Group

After recently installing the latest hotfixes, the both of my NBS servers are failing. 

Machines boot and spin and timeout with error : Operating System Not Found. 

For some reason when I first went into the settings to check what happened, the NBS Global settings were turned off. Not the first time that I've had settings changed or set back to default after a service pack install or hotfix update. I attempted to recreate the preboot environment, and am still unsuccesfull in booting new or known machines with pxe. 

Found the following in the log for the secondary NBS:

<event date='08/03/2015 14:46:19.1530000 -04:00' severity='1' hostName='DragonberryQA' source='DSTasks' module='DeploymentSolutionAgent.dll' process='AeXNSAgent.exe' pid='5332' thread='5624' tickCount='880883719' >
  <![CDATA[ClientConfigPXEServer_Task.cpp@131: Pxe Server install path empty]]>
</event>
<event date='08/03/2015 14:46:19.1610000 -04:00' severity='1' hostName='DragonberryQA' source='DSTasks' module='DeploymentSolutionAgent.dll' process='AeXNSAgent.exe' pid='5332' thread='5624' tickCount='880883735' >
  <![CDATA[ClientConfigPXEServer_Task P]]>



<event date='08/03/2015 14:46:18.9950000 -04:00' severity='1' hostName='DragonberryQA' source='DSTasks' module='ClientPXEImage.dll' process='AeXNSAgent.exe' pid='5332' thread='5624' tickCount='880883563' >
  <![CDATA[File:ExecuteCommand.cpp,Line:4373 ERROR: The Exception have occured in ClientPXEImage task. 
Exception has occured in function tcube_clientpxeimage.cpp() at Line No 672. Type of exception is ClientPXEException. Error Description is  "PXE service is not installed. Could don't find out path of CurrentControlSetServicesSymantecNetworkBootServicePxe in registry. ". Value of Windows error code = 0 and message is " The operation completed successfully.
"
]]>

 

Any thoughts? Am I missing a setting somewhere? Running ITMS 7.6 HF2 on Server 2012 R2. 

 

NBS General settings set to on : 

• Apply NBS Settings immediately
• Enable the NBS service 
• Respond to unknown computers
• Respond to managed computers

 

Thanks in advance! 

Did you perform the post hotfix steps as described in the HF release notes? To recreate the automation folders 1 In the Symantec Management Console, on the Settings menu, click Deployment > Manage Preboot Configurations. 2 On the Manage Preboot Configurations page, from the preboot configurations list, select the configuration that you want to recreate and click Recreate Preboot Environment option. For Mac, you must recreate all the NetBoot images and the automation folders and create new preboot configurations. Symantec recommends that you wait for 15 to 20 minutes before executing any deployment tasks. To see if the automation folder is updated, check the timestamp for the automation folders that are created at the following locations: ■ PEInstall_x86 <install_dir>:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\Automation\PEInstall_X86 ■ PEInstall_X64 <install_dir>:\Program Files\Altiris\Notification Server\NSCap\bin\Win64\X64\Deployment\Automation\PEInstall_x64 ■ LinInstall <install_dir>:\Program Files\Altiris\Notification Server\NSCap\bin\UNIX\Deployment\Linux\x86\Automation\LinInstall_x86 You can also verify if the automation folder is recreated by checking the task manager to check if the Bootwiz.exe application has completed the task of re-creating the preboot configuration. !!!!!! After recreating the automation folders, you must run the following tasks from the Task Scheduler to update the packages on Notification Server: ■ NS.Delta Resource Membership Update ■ NS.Package Distribution Point Update Schedule ■ NS.Package Refresh !!!! To deploy the automation folders on the client computers 1 Run the following automation folder uninstall policies: ■ Deployment Automation Folder for Linux-Uninstall ■ Deployment Automation Folder for Mac-Uninstall After you enable the Deployment Automation folder for Mac-Uninstall policy, you must manually delete the DSAutomation partition that is present in the unmounted and unallocated state. If you do not want to run the uninstall policy to uninstall the automation folder from the client computer, then you must manually erase the disk and the volume from the client computer. If, you manually erase the disk and the volume of the client computer, then ensure that you clean the Non-volatilerandom-accessmemory (NVRAM) of the client computer. To clean the NVRAM of a client computer, refer to the following article: http://support.apple.com/kb/HT1533 ■ Deployment Automation Folder for Windows (x64)-Uninstall ■ Deployment Automation Folder for Windows (x86)-Uninstall 2 Run the following automation folder install policies: ■ Deployment Automation Folder for Linux-Install ■ Deployment Automation Folder for Mac-Install ■ Deployment Automation Folder for Windows (x64)-Install ■ Deployment Automation Folder for Windows (x86)-Install

Thank you, Rogier_ISSP! That got one of them back online! 

I had recreated the Automation folders, but I missed the bit about running the tasks. 

I have run the tasks and now one of my PXE servers is working, but the actual notification server is still failing to boot machines on it's subnet. It is the oddest thing.

In the Site Server Settings under Settings -> Notification Server It reads like NBS is not installed on the Notification Server (Condor) when viewing it's page, but everywhere else I look, it shows installed. The checkbox is marked under Install/remove services, and under site servers, it shows both. 

Please see attached screen shots. 

Still have issue with the main ITMS server showing as 'not installed' in Site Server Settings, but showing fully installed everywhere else. Created a new machine on that network segment with just NBS installed to resolve / work around the problem, but there is some sort of bug here for sure. :) 

So it's currently not installed on the SMP itself? How have you verified that? I mean not through the console, I'm localy on the server. 

Can you view the above screen shots? For some reason it is stating that it is NOT installed when looking at the Site Server settings for the SMP, although I have installed it manually via the Symantec Management Agent, and the overall section under Network Boot Services shows 3 servers with it installed. Also, under settings -> Deployment -> Manage Preboot Configurations under "status" it shows the PXE policy is only populating to two of the three (not the SMP). 

It is very strange, I've never seen it do anything like this before and I"ve been on SMP since 7.1... 

And the services exists on the server itself?

It exists, it installs and then it says it is not installed. When I click on 'install/remove services' the checkbox is marked, and unmarking it uninstalls the service. When I reinstall it, it still reads not installed. 

Have you tried: 

regsvr32 "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\DeploymentSolutionAgent.dll"

 

I have not. I run that in a command prompt? (sorry) 

 

Thanks! 

Yes, but first check if the path is right for your environment.

Hi! I ran the command, it said it was successful, but still no luck. 

 

Any other thoughts?

 

Just to clarify, am I running this on the Site server or the Main Server? 

 

Thanks! 

On the server that pxe is installed but not listed in the console as installed

Thanks! I'm up and running again!!!