Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
Screenbert | 31 Mar 2008 | 0 comments

Here's a shameless plug for a session at ManageFusion regarding the ASDK.

There will only be one session that highlights the ASDK for the whole conference. Matt Bingham will highlight the information on Workflow and I'll be presenting several ASDK integrations my company has used. We'll have VMs set up so you'll get to see scripts and Web pages in production.

AA B13 Building Integrations with ASDK, Connector and Workflow - Wednesday Morning at 10:30.

Hope to see you there!

cnpalmer75 | 26 Feb 2008 | 0 comments

The release of the newest rollup pack for NS brings about a whole list of added updates.

Have you ever wondered though what was fixed with the current rollup you have installed now?

Well this download will allow you to see what each rollup pack has incorporated for fixes.

This info from taken from KB21248 and can be found in the Altiris KB, but the formatting was way off to read it. This Word doc should help straighten all of that out.

cnpalmer75 | 25 Feb 2008 | 4 comments

In case you were not aware, the newest rollup has been released. The R7 release was previously scheduled to be released a little later but was cut loose to resolve the critical security vulnerability with previous versions of the agent.

The information about the R7 release can be found here:
Release Notes:

cnpalmer75 | 22 Feb 2008 | 0 comments

In case anyone else may have missed the release earlier this month, here are the details surrounding the security vulnerability for any Altiris Agent pre- 6.0.2389 build. Linky here...


February 6, 2008
Symantec Altiris Notification Server Agent Privilege Escalation Vulnerability

Severity: Medium
Remote Access: No
Local Access: Yes
Authentication Required: Yes
Exploit publicly available: No


A privilege escalation vulnerability in the Symantec Altiris Notification Server Agent has been identified.

Affected Product(s)

Product Version Build Solution(s)
Altiris Notification Server 6.X All 6.0 SP3 R7


The Symantec...

BRING | 21 Feb 2008 | 0 comments

Measure twice and cut once. Sometimes not remembering to do that causes trouble, and has sometimes ruined some beautiful wood stock.

Frequently we do something similar in the Task Server environment when we forget to check the collection references that our tasks are assigned to. Like sending a Shutdown, or Restart task to "All Computers".

While this won't be painless to all end users, we can mitigate it and stop it from hitting everyone, using the following procedure:

  1. 1. Delete the Task from the Console. This may also involve deleting any referenced items as well.
  2. 2. Restarting the Altiris Object Host Service. This will clear the Task Server cache, and allow any deleted jobs to be cleaned and not promulgated to other machines.

It's just that simple. And while it won't be painless for you as the...

BRING | 19 Feb 2008 | 0 comments

The error message 'Invalid Character in a Base-64 String' recently appeared in the Notification Server error log. This error occurred immediately after attempting to select a database for the Notification Server to connect to, using the Database Setting option as shown below in Figure 1.

Keep reading for our (ever so humble) solution.

No matter how many times the dropdown was clicked to attempt to select a database, a blank dropdown would show, and the 'Invalid Character in a Base-64 String' error showed up in the Notification Server logs, and on this page as well.

Figure 1 - Blank Database Option


kbuller | 06 Feb 2008 | 5 comments

I did a search for "Macintosh" on the Juice site the other day and came up with 4 results... Hopefully this article will be of interest to at least a few people.

The latest release of the Deployment Console supports Macintosh clients but in its current state it is no match for Apple Remote Desktop. I just wanted to share a couple scripts that I use from ARD to make the most out of the Altiris Client for Mac.

Click the "Unix" button on the toolbar of ARD and place these scripts in it.

Refresh Altiris Client Policies


Send Basic Inventory


Run Inventory

Replace -x on the last line with -r for Full, -h for Hardware, and -s for Software

#! /bin/sh...
BRING | 31 Jan 2008 | 3 comments

SQL and Altiris Products! They go together.... (Not singing that song). But they need to be configured correctly, or you can run into the dreaded slow console, or even worse, data loss.

In troubleshooting a slow console, one area you might consider is the I/O channels on the SQL server, specifically the Network Interface Card. One Altiris user recently discovered that his dedicated SQL server was the bottleneck in his management environment.

His SQL server was using 1 NIC to provide all connection to the rest of the world, including connecting to an ISCSI drive array. By only having one NIC for ALL THAT TRAFFIC, the Notification Server was bound to appear slow, since it could not access it's database data as fast as necessary. The problem extended so far as to cause package codebase creation to fail, thus essentially stopping his...

jeremyboger | 10 Jan 2008 | 5 comments

I work for a large K12 district in Indiana. We have over 16,000 students, 1,800 teachers and staff, 8,000 wired clients, and around 500 wireless clients. Because of all of the security concerns we have to deal with in a school district, we have our firewall setup to lock down any and all items from the outside world. The only way items can come in through the firewall is if we specifically designate the IP address and port.

Updating Altiris Notification Server is not possible because of this. We are unable to use the download feature on the update page. After a whole lot of wasted time (because the boss didn't want to open anything up in the firewall for this), I did find a solution. It is a bit of work, but it does work.

The first thing I have to do is paste the SolutionCenter.xml file to the correct location on the Notification...

robertser | 21 Dec 2007 | 1 comment

Depending on the way you have your SQL database security set up you may end up with stored procedures and other objects having an owner other than dbo. The typical case of this happening is when running the upgrade with an account that is not an SA on the SQL Server.

If unresolved, this naming issue can give you grief. Here's a way to fix it.

This ownership issue will ultimately end up in causing a lot of errors such as the Deployment Console not opening or certain tasks failing. Basically anything that tries to call the stored procedure will fail because the name is wrong. For example: A stored procedure in the DS database called dbo.del_computer may have its name changed during an upgrade to username.del_computer.

To fix this situation run the following SQL script. Change the USERNAME to whatever the owner is for the objects that need to be changed.

 @OldOwner sysname,
 @NewOwner sysname

 SET @OldOwner = 'USERNAME'
 SET @NewOwner = 'dbo'...