Symantec Management Platform (Notification Server)

Hey Everyone, when we try to run Agentless Inventory on our NS, we get the following error page.  Does anyone have any ideas on how to fix this?  Everything else seems to be running properly from what we can tell.

An error has occurred that prevents the Symantec Management Console displaying correctly.

If this page is shown in place of a page or web part in the Symantec Management Console, navigate back to the page using the menu or tree and continue working. If the problem persists, see your local network administrator.

If this page is shown in place of the Symantec Management Console, one of the following could be the cause:

• The "Altiris Service" service is not running. Start this service on the server and reload the console.
• The account used for either the "Altiris Service" or the Notification Server webs is incorrect, disabled or the password for the account has expired. On the Notification Server computer, run "C:\Program Files\Altiris\Notification Server\bin\AeXConfig.exe /svcid user:(user name) password:(password)]", substituting the correct installation path if a non-default location was used, to provide a new account.
• The name of the Notification Server computer has been renamed. The following steps will need to be taken to correct this:
  • If SQL Server is installed on the same machine as the Notification Server:
    • Visit this link How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server 2005.
  • Open the file [NS INSTALL DIRECTORY]\Notification Server\Config\CoreSettings.config, search for the word 'key=DBServer'. Replace the 'value' attribute of the found XML element from the previous server name to the new server name.
  • If account used for either the "Altiris Service" or the Notification Server webs is a local user (i.e. Not a domain user), you will need to update the account to the new name. You can do so by following the 2nd bullet points on this page.
  • Open Registry Editor, browse to the registry key "HKLM\SOFTWARE\Altiris\express\Notification Server\". Find and replace any value that contains the old server name with the new name.
  • Re-push the agent out to all previously managed machines. (#)
  • Run the Windows schedule named "NS.Package Refresh" to re-validate site/package server packages. To get to the Windows schedules, go to 'Start' > 'Control Panel' > 'Scheduled Tasks'.
  • If you have hierarchy set up, you will need to remove and re-add the renamed server to the hierarchy. To do so, go to the "Hierarchy Management" page under the menu "Settings" > "Notification Server" > "Hierarchy".

In both cases, the Symantec Management Server log and the Windows Event log may contain useful information. The Symantec Management Server log can be accessed on the server by running "Start" menu > "All Programs" > "Altiris" > "Diagnostics" > "Altiris Log Viewer".

(#) If the NS hosted computer has yet been renamed, a better alternative would be to point all NS clients to the new server name first. You can do this by going to the menu "Settings" > "Agents/Plug-ins" > "Targeted Agent Settings". For each policy in the list, select the "Advanced" tab and specifies the new server name under the "Alternative URL for accessing NS" section. By doing this, all the clients will work automatically once the NS server has been renamed."

Also, does anyone have a spreadsheet or a comparison page that lists the different values and data collected between Agent versus Agentless Scans?  Can you scan just a subnet or a single resource or do you have to do a full scan over the whole network across all subnets and vlans?

Is Network Discovery supposed to be missing in 7.0 SP2?

https://www-secure.symantec.com/connect/videos/asset-discovery-and-tracking-using-inventory-solution-discover-hardware-assests-client-manage

Checking the SIM, it shows Altiris Network Discovery SP4 7.0.7416 as "Product is not properly configured.  You man need to manually configure or install this product again to resolve the problem."

I tried Repair, but it didn't work.  Does anyone know how to manually configure Network Discovery?

I think I am going to have to nuke this NS box and start over.  It seems like something is wrong with it.  We are having silverlight errors for DS7.1 and now network discovery can't even install.  I tried to reinstall the CMS suite and during the Inventory piece it gives me the following error:

( Exception Details: Symantec.Installation.ConfigTaskException: Product failed to install. See log for details. )

Inside the SIM, I did a search in the top right and typed "Network Discovery" and it showed Acer CMS, Altiris CMS, Altiris SMS, etc, but also showed Network Discovery SP4 I believe.  I went ahead and choose that, installed, and it seems like it worked as Agentless does not display errors anymore and Network Discovery is available on the list.