Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
BRING | 03 Apr 2007 | 3 comments

When upgrading our Altiris Agent environment, such as deploying a roll-up or service pack, there are always a few straggler machines that seem to get 'stuck', and don't complete the agent upgrade task.

The tip found in a knowledgebase article can be the key to giving those machines a 'boot', so to speak..

Check out the KB Article below, entitled:

"After NS Core R3 Upgrade, some agents would not upgrade." - KB 33865

It can be found at:

Screenbert | 29 Mar 2007 | 5 comments

There is a KB article available for "Common problems for very large environments" and is #26878. Particularly interesting is the last item under NS relating to IIS and .NET's debug mode for asp pages.

Quite a few solutions that are out right now that mistakenly have Debug enabled. This causes additional load on IIS / NS server.

Turning the debugging off on the pages should help in these three areas according to the KB article.

  1. The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
    This can be seen in the initial viewing of each NS console page
  2. Code can execute slower (since some additional debug paths are enabled)
  3. Much more memory is used within the application at runtime
    This is of particular importance on NS servers with 2GB of...
BRING | 25 Mar 2007 | 0 comments

In this day and age, tight security is something we all strive for. As a means to that end, changing the expected lay of the land (using non-standard server ports) is a route some of you are taking to slow down the bad guys. If you've wanted to use these ports in your Altiris client communication, here's the guide.

On the outset, it can seem to be a daunting task. However, a recent article added to the Altiris Knowledge Base can help you get it done.

Titled "Notification Server and Non Standard Ports", this is the step-by-step guide to getting your environment talking a bit more securely.

See KB Article 33867, found at:

Screenbert | 16 Mar 2007 | 0 comments

The network discovery process is a great feature in Altiris, but you can only input ranges to include or exclude one at a time. The console does not have an option to allow you to enter a list of ranges.

To get around this, right-click on the Network Discovery Policy and choose export. Save the XML file to your hard drive and open it with a text editor or an XML editor. Find the include IP or exclude IP range and just add additional ranges.

<include ip="" endMask="" type="range" /> 
<exclude ip="" endMask="" type="range" />

Just be sure to keep the same formatting and also to keep the includes and excludes in their appropriate sections.

After you add all your new inclusions or exclusions right-click on the folder that has your Network Discovery Policies and choose Import. Select the XML file you saved and edited and you now have all your entries.

This is a great time-saver when entering multiple entries...

dmorrison | 08 Mar 2007 | 0 comments

In large environments, the notification policy for "Managed computers with zero or more than one Agent Settings Policy applied" can run for a very long time due to the structure of the query populating the e-mail for the policy. The query can time-out and ties up valuable resources. Here's a fix.

Note: this policy should only be enabled on client facing Notification Servers, never on a Notification Server to which inventory has been forwarded.

A more efficient query is at the end of this tech tip. It ran in 6 seconds versus 9+ minutes for the standard Altiris query. Databases with larger numbers of clients, collections and policies will benefit most from the more efficient query.

Here are the steps required to take advantage of the query:

  1. Disable the Altiris policy "Managed computers with zero or more...
Ives Ledegen | 08 Mar 2007 | 0 comments

I've noticed when using the Altiris Report Builder and adding user accounts to a report I sometimes end up with incorrect information. The reason is the Report Builder allows you to make a link between tables where information is not unique. This introduces some randomness into the relationship between the two tables and can result in unexpected results.

For Example:

Check out the results I get when I run this query and view the results using a query analyzer:

SELECT PU.*, PC.[Name]
FROM Inv_AeX_AC_Primary_User PU
INNER JOIN vComputer PC ON PC.[Guid]=PU.[_ResourceGUID]
WHERE PC.[Name]= 'pc_names_goes_here'


Screenbert | 06 Feb 2007 | 7 comments

Ever seen "Pimp my ride"? This takes it to a whole new level. This is the last of a three-part installment for Pimp my Console.

With this SQL code you can customize your console header. You could use if for something cool like in the screenshot or something functional in case you run multiple NS Servers and need something big to tell you where you are at. IE "Altiris Server A".

To view the current settings

Select * From String
WHERE (BaseGuid='524C9C33-EE22-4A48-8B20-050120021dB6')
AND (Culture='' OR Culture='en') AND StringRef='title'

To modify the current settings

SET String='Put console name here'
WHERE (BaseGuid='524C9C33-EE22-4A48-8B20-050120021dB6')
AND (Culture='' OR Culture='en') AND StringRef='title'


Screenbert | 06 Feb 2007 | 2 comments

Ever seen "Pimp my ride"? This takes it to a whole new level. This is the second of a three-part installment for Pimp my Console.

Have you ever wanted to customize your background on your console from blue to something cool?

Well now you can.

Just go to the "C:\Program Files\Altiris\Altiris Web\Images" folder on your NS server and modify the bgLine.gif with your favorite editor.

Be sure to backup your image before modifying it and as always, I would doubt this customization is supported by Altiris.

Now go pimp your console!

Screenbert | 06 Feb 2007 | 1 comment

Ever seen "Pimp my ride"? This takes it to a whole new level. This is the first of a three-part installment for Pimp my Console.

Have you ever wondered what Rollup you were running on your console but didn't remember what version it was? Now you can modify your page to display this.

Open the folder called "C:\Program Files\Altiris\Notification Server" and modify the header.aspx file.

About line number 113 change the text that says:

<asp:label id="lblVersion" runat="server" Font-Name="Verdana" Font-Size="x-small" ForeColor="white" /></b> (SP 3)</td>".

Add (R1) after the part that says (SP 3).

Be sure to back-up your header.aspx before modifying it and, as always...

BRING | 09 Jan 2007 | 0 comments

If the error: "...failed with System.OverflowException: Value was either too large or too small for an Int32" appears in the Altiris logs after an Local Security Solution inventory, this explanation and solution should help you get back on track.

The log entry that points out the problem:

Thread ID: 5372
Module: AltirisNativeHelper.dll
Source: MSoft.ResourceDataTable2
Description: Column loading for row in dataclass: a2e5e8a3-8d87-4595-a669-8ac4346e4d5e, Resource e3dac727-73db-4c11-bbd9-0259d33f5444 column = c3, row = '"row c1="0" c2="0" c3="4294967295" c4="-1" c5="0" c6="0" c7="1800" c8="1800" />' failed with System.OverflowException: Value was either too large or too small for an Int32.
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at MSoft.Resource.ResourceDataTable2.ConvertColumnValue(DataColumn dc, String strValue)
   at MSoft.Resource.ResourceDataTable2.LoadRows(XmlReader dataReader).