Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Configuring
Showing posts in English
Screenbert | 06 Sep 2006 | 2 comments

If you've recently upgraded to Wise Studio 7, you'll probably notice that you're missing a few options, such as build settings (installation .exe name), Media, Screen, Password and so forth. Read on to find out how to get things back to normal.

In order to see these options you have to run the WiseScript Package Editor with the /PE switch. The best way to modify this for new packages is as follows:

Open the Windows Explorer. On the menubar click "Tools", then "Folder Options".

Click the "File Types" tab. Find the file with the extension of WSE and click the "Advanced" button. Make sure the "Open with Wise Package Studio" is selected, then click edit. At the end of the "Application used to perform action line...

CraigM | 23 Aug 2006 | 0 comments

If you do not know all the WMI codes you need to manage your workstations, you can use some simple tools and samples to gather information for scripting.

These locations include:

Rob van der Woude's Scripting Pages
this Microsoft tool.

David_Falcon | 16 Aug 2006 | 3 comments

This procedure will outline the steps needed to create a recurring incident. Recurring incidents are helpful for many reasons; however, they can especially help with trying to satisfy audit control requirements.

For instance, you could set up a recurring incident for the network team to view VPN logs on a monthly or quarterly basis.

To begin, go to your Notification Server > Tasks > Helpdesk > Notification Policies. From this point, you can create the policy here or you can create a custom folder to keep things organized.

Once you determine the exact location of your policy, right click on the folder where it will be housed. Click New > Notification Policy.

You will now see the New...

John Doyle | 16 Aug 2006 | 0 comments

It's a strange thing, but in the English speaking world—although we share the same language—when it comes to writing dates we often do things opposite. What 6/2/2006 means to you depends on where you come from. For someone from the US, it means the second of June; whereas to someone from the UK it is the 6th of February. The way dates are written and interpreted varies from country to country in other cultures as well.

When you open Helpdesk console on a server in the US on a client in the UK, you will see the dates written in the US format. This can be very confusing, so I will show here how a simple edit will allow users to see the dates based on the preferred language settings in their browser.

The change requires you to edit the Default.aspx file in the AeXHD folder. This folder is normally at C:\Program Files\Altiris\Helpdesk\AeXHD. You will probably need to remove the Read-Only property from the file before you can edit it. Open the file with Notepad...

BRING | 16 Aug 2006 | 2 comments

What does the Coresettings.config variable MaxAgentDownloadTryingTimeMins do and how is it set? Also, what does the registry key PkgDownloadFromNS do and how is it set? How do the two interrelate?

  1. The Coresettings.config variable MaxAgentDownloadTryingTimeMins is a value in minutes that tells the Notification Server how long the agent will continue to try to download from a Package Server before bypassing the Package Server and downloading directly from the Notification Server. This setting is more correctly defining a Notification Server behavior rather than Agent behavior. The Altiris Agent always downloads packages from the codesbases that are given out by the Notification Server. In Notification Server 6.0 SP2, the server does not provide its own codebases to agents that are members of the defined site on the Site Maintenance page; this change was the result of a very common customer request.

    This setting is disabled by default, and the value to disable...

John Doyle | 09 Aug 2006 | 7 comments

In the standard Helpdesk code, the winuser console (My Helpdesk Console) provides end users with a dropdown list which will allow them to specify the name of the asset that has the problem. This is populated by the list of assets associated with the user and the first and hence default record is set to None.

While this default behavior might be valid for many organizations, others may consider it a potential drawback for the following reasons:

  1. The end user may not know the name of the machine they are using.
  2. There is no obligation on the user to select an asset and most users do not appreciate the utility of selecting the resource. They just want their problem fixed as soon as possible and may not be in a very good mood. They may not even notice the dropdown list.
  3. The resource may not be associated to the user and so may not show up in the list.
  4. In some situations there is not a fixed relationship between users and computers.
  5. ...
ricodjs | 08 Aug 2006 | 0 comments

If one manages both clients and servers on separate DSs, it's nice to have a way of splitting them to point to their respective management servers - (Servers to Server DS and Clients to Client DS) - before bootworks actually first tries to update the record on the DS.

This can be achieved on HP hardware by running an OS utility called HPSMBIOS.EXE, triggered by autoexec.bat.

This utility give details on the hardware type from the BIOS. Based on the hardware type, one can then add a section in autoexec.bat instructing bootworks to point to a different DS for that hardware and, voila, separate servers and clients without untidy records left in the original PXE server.
I think... ;)

The download also includes a Readme.txt file.

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the...
jsjj01 | 04 Aug 2006 | 0 comments

After countless hours and many days of scratching my head and getting very little help from any forum, I decided to write this article about an error I had with the HP Client Manager implementation in my organization. My hope is to compile a troubleshooting guide that everyone can use to resolve various issues that they may encounter with the HP Client Manager.

All who use the Altiris-HP Client Management tool can see its great benefits. The problem I notice is that the documentation is lacking at best, and it is fairly difficult to find anyone to answer any support questions (without paying at least).

This document will explain an issue that came up in my environment after implementing the HP Client Agent onto my computer, and I hope to show the logic behind the solution and the ultimate resolution to the problem. You may not have experienced this problem, and you should count yourself fortunate for that. The problem seems to appear when using the HP Tool...

John Doyle | 02 Aug 2006 | 5 comments

The number of people using Firefox is growing fast*, and rightly so, as it is a very capable browser.

Out of the box, .NET 1.1 does not support Firefox and many of the other more modern browsers, so they are treated as downlevel browsers.

The Helpdesk application has been written primarily for IE, but you can improve the experience slightly for Helpdesk users using Firefox by editing the web.config file and including a <browsercaps> section under system.web. I personally used the code available for download at

The real improvement I noticed is that the input text areas are now rendered with the correct width.

Figure 1: <browsercaps> section not included.


Admin | 27 Jul 2006 | 10 comments

Austinn wrote: "How do I delete a worker in the HelpDesk Worker Console? There are a couple of dummy accounts created, and I can't seem to get rid of them!"

Good question, Austinn. The current version of Helpdesk Solution will not allow you to delete a worker (default or user created) account. This is by design to preserve the integrity of the database for any worker accounts associated with work items. The only option is to make the worker account inactive. However, because you could theoretically delete an unused worker account without affecting the solution, I have submitted an enhancement request to the product manager to handle this scenario.

Greg Giles