Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
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'...
BRING | 13 Dec 2007 | 0 comments

Why are my SQL server transaction logs growing each day to the point they overrun available disk space? This is really getting annoying. I am having to truncate them manually. Why isn't the automated procedure working?

After checking EvtQFast and EvtQueue thread settings, and adjusting the Throttle delays as found in KB 2344 and KB 17079, the problem just won't go away. The transaction logs were getting still getting a lot of pressure.

We are going to need some more information. So we set the following Performance Monitor counters on the SQL Server:

  • SQLServer:Buffer Manager: Buffer Cache Hit Ratio
  • SQLServer:Buffer Manager: Checkpoint pages/sec
  • SQLServer:Buffer Manager: Page writes/sec
  • SQLServer:Databases: Log Bytes Flushed/sec (Select correct Altiris database...
MBHarmon | 07 Dec 2007 | 2 comments

Sometimes, when it comes time to manage computers, IT and Accounting don't always see things eye-to-eye. A department based collection -- while may be important for Asset Management -- may not meet the needs you have for delivering software.

A good example is in our organization where we recently migrated from Novell ZENworks to a fully Microsoft environment. Altiris has been a great help in getting this done, but our department information didn't match up with that old NDS tree. Luckily, Active directory did. By using the following query we were able to map computers to a collection by using the Owner's Fully Distinguished OU name.

select DISTINCT r.[ParentResourceGuid] AS 'Guid' 
  from ResourceAssociation r   
  inner join Inv_OU_Membership uo on uo.[_ResourceGuid] = r.[ChildResourceGuid]  
  Where r.[ResourceAssociationTypeGuid] = 'ED35A8D1-BF60-4771-9DDE-092C146C485A'   
  AND uo.[Distinguished Name] = '<OU INFORMATION HERE>'

When finshed your...

Andrew Souter | 26 Nov 2007 | 5 comments

I recently found a good article in the Altiris KB about creating new menu items in the right click menu. The article shows how you can create a link for remote desktop but can be used to create any link.

For example, you might want to link to the Dell Website's model driver page or link to a report that shows the last logged in user.

I'm not sure why you need to create the virtual directory though.

KB article 30639 found at the below link.

Andrew Souter | 19 Nov 2007 | 0 comments

For those that are not connected to the Internet, you may notice that when you install the Notification Server and click on Solution Center to download new solutions that the NS will sit there and wait while it tries to resolve to\solutions\6_0.

It will eventually time out and allow you to change the location. But for a shortcut, go to the registry, browse to HKLM > Software > Altiris > express > Notification Server.

You can now create a new String Value called SolutionCenter and simply paste your location to your solution center local copy. You will need to put a \ at the end.

Then go back to your console, refresh and it should come up immediately.


Alex Held | 25 Oct 2007 | 2 comments

If you find yourself stuck and unable to access a page on the Altiris Console because it's hidden or otherwise MIA, here's the syntax that's sure to help.

You can use a URL to access the web page using the following URL in the browser.


Just replace the guid with the item guid for that page. Also if needed, change the localhost if you are not on that NS.

Example (AD Import rules):


MBHarmon | 23 Oct 2007 | 6 comments

In our organization we have some very security sensitive managers, one of whom was wholeheartedly for Local Security Solution (LSS). However, he quickly became concerned that passwords, after being disclosed, were opening security holes. While limited to those computers, he was still concerned enough and he has enough pull to have this issue block our full implementation of Local Security Solution. Therefore, it quickly became important to address his issues. Instead of upping our password reset interval for everyone, I came up with the idea of just reseting those passwords that had been disclosed.

After looking through the default LSS reports I found one that almost immediately fit our needs. After ripping it apart I was able to come up with a collection of computers that have had their current Local Security Solution passwords disclosed....

PeeGee | 18 Oct 2007 | 1 comment

In some instances it is not possible to utilize the Notification Servers own infrastructure to do a push installation of the NSAgent. The reason might be that the NSAgent needs to be installed to computers in a non-trusted domain environment.

The following article describes how the free utility psexec can be utilized to perform a push-installation of the NSAgent.

Download needed files

  1. Get the latest version of PSEXEC from the link below (you need to download the pstools, extract them and then simply copy psexec.exe)
  2. Get your NSAgent installation executable from:
BRING | 12 Oct 2007 | 0 comments

We love task server. It lets us get a near real-time task or job to machines, and pretty close to immediate feedback. We just have to be careful about what types of tasks we send.

Let's say you are needing to update the Altiris Agent from the 2386 version to the 2387 version. Being the Task Server expert, you decide a Software Delivery Task Server job is the best method to get it out there quickly.

This task is simple a software delivery job that uses the "Aexnsc.exe /reinstall" command line.

Now, after you distribute this task to all targeted client machines, all of the sudden, nearly all of those machines are constantly restarting the Altiris Agent Service.

And errors such as "Agent Altiris.ClientTaskAgent has not stopped", and "Unexpected error in ServiceMain: Unknown error" show up on the client, and errors such as Source: Altiris.ClientTask.*
Description: Dropping event (Resource: CWI-RTP-020-D, TaskInstance: 7d61d5e9-4500-4c39-8165-...

Jason Gallas | 08 Oct 2007 | 4 comments

Here's a tip that probably won't get you a raise but it will make troubleshooting Altiris Agent issues or peeking at NS log files a tad bit easier.

(We'll work on the raise in another tip.)

Copy the following files from the (install drive)\program files\altiris\Diagnostics folder on your Notification server to a local folder on your computer:


Then create a shortcut to LogViewer.exe on your desktop or wherever you would like it.

Now you can run the logviewer locally to diagnose issues with your Altiris Agent or to review log files on your Notification server.