Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
haim96 | 03 Dec 2008 | 1 comment

I deployed Altiris agent to computers in one of our sites and then installed an agent on one of the server in the site and set it as task server for that site.

The next day I notice that none of the computers is managed by the task server that I configured.

I checked the configuration on the NS server and every think looked right. Then I notice something strange, under the configuration part, in the task server roll out there are two collections:

  1. Task server with HTTP.
  2. Task server with IIS.

I notice that my new task server appeared under the IIS collection while other task servers appear under the HTTP collection.

I checked the task server and it had IIS installed (without any use of it). So I dig in it some more and found that when I installed the agent and then set it as task server, if the...

BRING | 11 Nov 2008 | 2 comments

We all like the ease-of-use and access of the Altiris Agent logviewer application. It gives us quick and easy access to look at the agent-side logs. It is a bit cumbersome, and as the graphic below shows, you need to click the browse button to be able to view the other stored files on the computer.

One day, when needing to review the files for a problem that I was troubleshooting, I needed to look at some historical information in the logs, when lo and behold, I clicked on the Browse button and nothing happened. Why?

Well, I came to find out that a new security policy...

CondorMan | 15 Oct 2008 | 3 comments

VMWare is now offering ESX for free! I have been using it on my test system and it works great. I can now run multiple versions of Notification Server and Deployment Server on separate virtual machines.

For me, the best part about ESX is that all the guest OSs share common memory pages. That means you can have four Windows Server 2003 virtual machines up and since most of the data stored in memory is the same, they cumulatively will use about the same RAM as two servers.

Alon | 30 Sep 2008 | 5 comments

I have often been asked if Altiris can work well in a Novell environment. The main reason for concern is the perception that Altiris is tied directly to MS Active Directory. For the most part we work just fine in such an environment. There are only really 2 areas that are difficult:

  1. Initial client installation - There are two issues here. The first being is that you can use AD GPO objects to do the install. This is not really a big deal because you can use Novell login scripts instead which also solves any rights issues when running from the login script.
  2. We can't get user information from the domain (because it's not there). However we can use connector solution to pull contact information from eDirectory using LDAP if it's needed.

Once our agent is on the system then just about all solutions work just like...

CondorMan | 24 Sep 2008 | 1 comment

If you use Sysinternals tools on many different computers for your troubleshooting, go to and you will be presented with a list of all Sysinternals executables.

You can run them directly from there instead of finding, downloading, and extracting them through the regular site. It has been a great timesaver for me.

CondorMan | 24 Sep 2008 | 0 comments

TCPView will display which active and listening sockets an application has created. This can be helpful for troubleshooting network applications.

More information can be found at

haim96 | 24 Sep 2008 | 0 comments

How many times have you tried to delete a file and only to discover that it locked by some application or service?

The "Handle" tool from Sysinternals is a command line tool that shows you the open handles in your system and allows you to close any selected handle.

There are more tools like Handle that show you open files (like "Process Explorer" also from Sysinternals) but using a command line tool allows you, with proper script, to automate things.

NOTE: Closing handles can cause application or system instability.

Handle - the command line tool:

Process Explorer - similar functions (and more) with GUI:

Antonp | 23 Sep 2008 | 0 comments

After installing Notification Server 6.0 SP3 R7 on a new/fresh installation of Microsoft Windows 2003 Standard Edition with Service Pack 2. ASP.NET and IIS is also installed on this server. The Notification Server configuration web page should come up and allow you to configure it. Instead the following error is received.

CS0016: Could not write to output file 'c:\windows\\framework\v1.1.4322\temporary files\application1\c11b43f6\....' . The directory name is invalid.

See screen shot below for more detailed error:


CondorMan | 23 Sep 2008 | 0 comments

Filemon lets you see all file system activity in real-time.

It is useful to discover file requirements for a certain application or to discover the location of files being written to.

You can find more information about this tool at

robertser | 16 Sep 2008 | 0 comments

Out of Band Management Solution makes provisioning AMT and vPro machines a breeze. We discovered an issue with new PCs having the wrong name because we use sysprep. After imaging a PC with Sysprep it will have a generic name. We did not want our new PCs to provision with this generic name since it would break the AMT communication. The way OOBM works, it fully automates the provisioning process and will provision the PC regardless of what the name is.

To prevent this from happening we enabled a nice feature in OOBM called "require authorization".

Under the Out of Band Management solution in the NS Console go to Configuration > Provisioning > Configuration Service Settings > General. Check the box entitled "Intel® AMT requires authorization before provisioning". This will require you to authorize all of your systems before...