Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
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.

DECLARE
 @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.

https://kb.altiris.com/article.asp?article=30639&p=1

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 www.solutionsam.com\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.

A

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.

http://localhost/Altiris/Console/ItemPage.aspx?ItemGuid=%GUID% 

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):

http://localhost/Altiris/Console/ItemPage.aspx?ItemGuid=4b96d980-2e27-42a0-a055-4c44ea3e40ac

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)
    http://download.sysinternals.com/Files/PsTools.zip
  2. Get your NSAgent installation executable from:
    \\YOURNS\nscap\Bin\Win32\X86...