Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
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 http://technet.microsoft.com/en-us/sysinternals/bb...

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:
http://technet.microsoft.com/en-us/sysinternals/bb...

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\microsoft.net\framework\v1.1.4322\temporary asp.net files\application1\c11b43f6\....' . The directory name is invalid.

See screen shot below for more detailed error:

Resolution:

    ...
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 http://technet.microsoft.com/en-us/sysinternals/bb...

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

CondorMan | 28 Aug 2008 | 0 comments

The DSWeb Console and NS Console require .Net Framework 1.1 to be registered with IIS.

A quick way to fix this (or script this for multiple installs) is to run the following command:

%SystemRoot%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i -enable

haim96 | 26 Aug 2008 | 0 comments

Recently I started to get a lot of warning messages like this in the Altiris log:

Log File Name: C:\Program Files\Altiris\Notification Server\nsLogs\a.log
Priority: 2
Date: 6/25/2008 10:30:16 AM
Tick Count: 8747765
Host Name: XXXXXXX
Process: w3wp.exe (1928)
Thread ID: XXXX
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.Web.GetClientTaskServers.LocateServersBasedOnSubnet
Description: Cannot find any TCPIP information for machine XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

The message appears every 5 minute after collection update task.

Since there is no computer name, only a GUID. I assumed that the computer was deleted from the database (probably by maintenance task) and some leftover caused the NS to think that it still exists.

In that case, I thought, I can clean the leftovers from the DB and every thing will...

BRING | 21 Aug 2008 | 2 comments

EvtQueue, EvtQFast, EvtQLarge, and EvtQSlow. These folders within the Altiris folder structure are the lifeblood of data processing for your Notification Server.

One might wonder if EvtQueue is more important than EvtQFast, EvtQLarge, or EvtQSlow? Or could EvtQFast get preferential treatment? What happens when multiple NSE files are captured at the same time - does one queue get a priority over any other and if so, what is that priority?

Well, in the interest of fair play, the Notification Server does not play favorites. No queue has priority over another. Each one has been assigned one or more processor threads, (with the exception of EvtQLarge), and the remaining queues all process concurrently. The default threads for each queue are different however. EvtQFast has 10, EvtQueue has 3, and EvtQSlow has 1.

So maybe EvtQFast is...

haim96 | 11 Aug 2008 | 2 comments

I'm using NS to run schedule tasks with VB scripts on my network computers. Recently I posted a question on the forum about NS tasks not running and just skipping to the next time they should be running.

I couldn't find anything in the NS log nor in the windows event logs, the tasks just skip without warnings or errors.

After some trail and error I found that the name of the task was the cause to that behavior!

The name was something like this:

Task name run at 12:00

I notice that when I'm using colon character (:) for the time description the task is not running! - even if I right click on the task name and select "Start now" the task didn't run.

I tried other characters like comma, single dot and underline and it runs just fine. So it's seems that the problem is with the colon (:) and...

Bcomp | 04 Aug 2008 | 5 comments

How will you be able to remove old computers that were placed by resource discovery into the database? This tech tip will tell you how to do so.

The easiest way is to create a collection which shows unmanaged computers for a discovery method. Once the collection is created, review the set of computer resources, then select the needed computers, right-click, and choose Delete.

Run the following SQL query to create this collection:

USE Altiris   --Or your database name
select vc.[Guid]
, Name
, IsManaged
from vComputer vc
join Inv_AeX_AC_Discovery dis on dis.[_ResourceGuid] = vc.[Guid]
where dis.[Discovery Method] in ('DomainMembership') AND IsManaged<>'1'
GO