Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
Antonp | 18 Jul 2008 | 1 comment

I recently has this error when I logged onto the NS box and opened the NS console. To my surprise I wasn't greeted with the normal NS console, but instead I was faced with this:

The way I resolved this error was either to restart all the services related to the Notification Server or do a repair on the SQL database. If restarting the services didn't do the job for me, then a repair would normally do the trick.

I would like to hear from anyone who has also experienced this error and ways they resolved the problem.

Andrey Shipov | 27 Jun 2008 | 0 comments

I have installed Task Server on three Deployment Servers without a reboot and on all of them deployment web console stopped working, normal deployment console was fine.

After looking at IIS I found that task server installation process has stopped IIS service and never started it.

After manually restarting IIS, deployment web consoles are working fine.

Andrey Shipov | 27 Jun 2008 | 1 comment

We have Altiris Notification Server with a few solutions for about 15 months now. Currently NS manages 1500 client PCs. Altiris provides great solutions and they are very easy to modify for your environment. But a few months ago I discovered two problems that took me some time to investigate...

The first problem was quite easy and straight forward:

IIS log files were in the region of 8 Gb. One day I received an alert message that Notification Server hosting machine is running out of space on the drive C:\.

After looking at folders and files size I have found that IIS log files were in the region of 8 Gb. These log files are created by IIS, but are never deleted.

I have asked people who have more knowledge in IIS than I do and they told me that there is no mechanism in IIS to automatically clean up log files....

CondorMan | 26 Jun 2008 | 4 comments

There are a few ways to have a batch script wait for a number of seconds. The simplest and most widely available without any additional programs is to use the ping command.

The following is is an example... PING!

ECHO Waiting 5 seconds
PING 1.1.1.1 -n 1 -w 5000 > NUL

CondorMan | 25 Jun 2008 | 0 comments

OSQL is a flexible command-line utility that allows you to run SQL Queries, Commands, and Stored Procedures from the command-line or through a Batch script.

In order to run OSQL, you can either run it on your SQL Server or copy OSQL.EXE and osql.rll to a location that a client machine can run them from.

The syntax for OSQL is:

usage: osql       [-U login id]     [-P password]
 [-S server]      [-H hostname]     [-E trusted connection]
 [-d use database name] [-l login timeout]   [-t query timeout]
 [-h headers]      [-s colseparator]   [-w columnwidth]
 [-a packetsize]    [-e echo input]    [-I Enable Quoted Identifiers]
 [-L list servers]   [-c cmdend]      [-D ODBC DSN name]
 [-q "cmdline query"]  [-Q "cmdline query" and exit]
 [-n remove numbering] [-m errorlevel]
 [-r msgs to stderr]  [-V severitylevel]
 [-i inputfile...
EMercado | 23 Jun 2008 | 0 comments

Altiris has released Notification Server 6.0 SP3 R8. It adds support for Vista SP1, XP SP3, and Windows Server 2008. Full details and download can be found here:

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

It has a new Altiris Agent version (6.0.0.2394) so you'll need update your clients.

dougj | 20 Jun 2008 | 0 comments

In order for a Linux client to be setup as a package server, it must be identified as a package server candidate. One of the criteria is that the machine have a role of 'Apache HTTP Server'. The role is stored in the 'AeX AC Roles' data class and 'Inv_aex_ac_roles' table. How does the Agent for Unix on a client machine identify this role?

The client.conf file, found in /opt/altiris/notification/nsagent/etc/client.conf, contains a "ps_send_apache_role" entry in the [MachineID] section. This entry allows for three possible entries: 'always', 'auto' and 'never'.

If set to 'always', the role will be sent if Apache server is installed and detected on the client.

If set to 'auto', which is the default, the role will only be sent if the Apache server is actually running and properly configured. To be properly configured, the...

apascucci | 18 Jun 2008 | 1 comment

Using Terminal Services client to connect to the NS Server, we need to add the "/console" command line switch to prevent installation failures. No surprise there!

But I had some issues while with a customer (corrupt installation or strange behavior...), so I took a few minutes to make sure it wasn't 'my fault'.

I checked the server Terminal Services Manager Session ID, which should be 0 (zero) when connected in Console, and it wasn't!

Then I did

Start
Run
mstsc/?

and...
As I'm running Vista, the /console is /admin

Thanks MSFT,
Nice try to confuse me ;o)

CondorMan | 18 Jun 2008 | 0 comments

If you've ever had a domain join fail, you can understand how frustrating it can be to troubleshoot. There is a log file that will make it much easier to figure out what is wrong.

  • Open the file C:\WINDOWS\Debug\NetSetup.log.
  • Go to the very bottom of the file and find the last "NetpDoDomainJoin: status:"
  • If it is not 0x0, then the domain join failed and the code listed instead of 0x0 is the reason it failed.
  • Now, look at each previous line in the file until you come across the last line in the file that returned the same failure code as your Domain Join.
  • You have found the step of the domain join that failed and the reason it failed.
CondorMan | 18 Jun 2008 | 1 comment

Sometimes a Windows Executable, Script, or Command will fail with an error. What does that mean?

While there is no enforced set of error code meanings, most executables and all system commands follow a standard definition of error codes.

You can find out the meanings by viewing Microsoft's list of Windows Error Codes and their descriptions here.

You might want to add that link to your favorites.