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
macten | 03 Nov 2006 | 5 comments

I was recently asked to figure out how to prevent workers from changing the contents of an incident's history and it turns out this is easier than you might think.

First of all, unless you have already done so, you should follow the customization guidelines as described in the Helpdesk documentation to utilize a customized WorkItemView.ascx template. Once that is done simply search for this line...

[aw:HyperLink ID="imgEditComment" RunAt="server" Command="editItemComment" ImageUrl="icnEdit" ToolTip="sidTipEditComment" Wrap="False"] your custom WorkItemView template and change it to....

[aw:HyperLink ID="imgEditComment" RunAt="server" Command="editItemComment" ImageUrl="icnEdit" ToolTip="sidTipEditComment" Wrap="False" privileges="privAdminister"]

Note: due to the formatting of this forum I...

macten | 30 Oct 2006 | 5 comments

Helpdesk does not push the status of a parent incident to child incidents out of the box unless the incidents have certain properties set. To enable parent->child status updating, simply import the incident rule in this XML.

The specific property that must be set on an incident in order for it to inherit the status of the parent incident is "Parent Link Type" which must equal "Inherit Status". By default all incidents have a "Parent Link Type" of "Simple" so the built in automation rules that allow for parent->child status updating don't apply.

This XML file will set the "Parent Link Type" on all incidents that have been linked to a parent incident to "Inherit Status".

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License
ericg | 25 Oct 2006 | 2 comments

Windows 2003 R2 introduced enhanced security in Internet Explorer that prevents the installation of the Altiris agent package through a Web page.

Placing the Altiris server in the trusted zone or permitting file downloads in the Internet zone will correct the problem.

ericg | 25 Oct 2006 | 2 comments

If you decide to change the default port the NS client uses to communicate with the server, you should know that even if you specify http://myserver:newport/altiris, Software Delivery Solution won't read the new port.

The snapshot file will be published according to your IIS primary port setting and not any others.

There is no known way to avoid this. This can cause a problem if a client/server doesn't have access to both ports while you are still migrating other clients/servers or if you have multiple Web sites published on different ports on the same IIS server.

kyle_campbell | 23 Oct 2006 | 4 comments

Can the Dell Client Manager 1.0 be used to configure BIOS setup passwords? I can get it to configure settings in the BIOS but can't figure out how to set the BIOS Setup password to prevent users from changing the BIOS Settings.

Dell Client Manager 1.0 SP1 and 2.0 allow you to Configure BIOS passwords. You would do so by creating a BIOS profile and setting the password field, then distributing the profile with the BIOS settings policy. Please note that the Dell Client's BIOS must support setting a BIOS password (this may not be available on older Dell machines), however DCM 1.0 and 2.0 will provide details as to the success or failure of the BIOS Settings policy.

jjesse | 17 Oct 2006 | 2 comments

In the newest ASDK there is a .DLL for working on scheduling jobs in DS through script. However, there is not a help file or anything in the examples folder.

Does anyone have an example of scheduling jobs through the ASDK for Deployment Server?


John Doyle | 09 Oct 2006 | 4 comments

Here's some code to allow you to attach existing documents to an incident using Incident Rules, Automation Rules or Tasks. It can also be used to add an attachment to a Quick Incident.

How this works

Attachments are stored in a table in the database called workitem_attachment. The following data is stored in this table:

this refers to the incident number in the workitem table
this is the revision of the incident. For a new incident this will be 1. It increments by one each time an incident is modified.
this is the string that will be used in the hyperlink on the helpdesk pages
the link to the document's location on the web server
name the physical path to the document on the web server
the size of...
John Doyle | 06 Oct 2006 | 7 comments

The HISTORY_LIST macro allows you to create a HTML table in e-mails that you send out from the Helpdesk containing the complete history of a workitem.

The following example, taken from the reference manual, shows how to create a simple table.


This table will contain the version number, the modification date and the name of the worker that modified the incident.

We can use the same format to output the comments:


However, if this is used in an e-mail to the users, they will see all the comments added to the incident including ones which were set as not visible to guests. In order to remove these comments I came...

BRING | 05 Oct 2006 | 0 comments

Can the web services portion of Notification Server be run on a separate server? Many larger companies like to divide the services to reduce the load on a single computer and to distribute processing -- Web services (IIS) on one server, applications on another, and database services (SQL) on a third, etc.

No, only the database services and data may be housed on a separate server. The web services are a very integral portion of Notification Server, and therefore cannot reside on separate computers.

keason | 21 Sep 2006 | 0 comments

Hello all,

I am looking to repackage some of my applications. DS 6.5 contains the scaled down SetupCapture and MSI Editor. I would like to know if any one has been successful in using those products. If those were not used what "economical" products have you had success with?