Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
WiseUser | 06 Jun 2007 | 3 comments

If you get that "deer-in-the-headlights" feeling every time you try to find something in a Windows Installer Log, this list of search terms should undoubtedly help.

?Feature: ?
Feature and component states (Top of list)
?is managed?
Find out if package was installed as ?managed?
?Machine Policy?
Find All Computer Policies (press search again key to forward through list)
?User Policy?
Find All User Policies (press search again key to forward through list)
Find a Specific Policy (include single quotes before and after name)
?ProductCode =?
Properties List (Top of list)
?ProductCode =?
Screenbert | 05 Jun 2007 | 0 comments

Altiris has released Version 1.4 of the ASDK. It's available for download from . The link for the release notes is still linking to the release note for version 1.3. The correct KB article is KB34156.

The most interested changes are that they have added the Patch Management Library (Hurray!), added a 4th layer of interaction (using task manager) and the Altiris.ASDK.SWD.SoftwareManagementBasic library has been deprecated.

Enjoy and remember that you must remove prior versions before installing the new version. Also your old scripts and apps will not work if they use the SoftwareManagementBasic Library.

WiseUser | 04 Jun 2007 | 0 comments

Just in case you forgot exactly what page of the documentation details the Wise switches, here's a list (from user kv17675) that you can bookmark.

Wise Setup.exe Switches

/T test mode
/X pathname extracts files into pathname
/Z pathname extracts files into pathname and reboots
/S silent install
/M prompts for windows, system, temp dirs
/M=filename specifies a value file similar to /d above,
but for standard variables
/M1 same as /m plus it prompts before any file that is self-registered
/M2 reserved for internal use by Wise during debugger sessions

Uninstall (Unwise.exe switches)

/Z remove empty directories, including one with unwise itself in it.
/A automatic mode, no user choices other than cancel.
/S silent mode, automatic mode with no user choices...

Joel Smith | 30 May 2007 | 0 comments

In a secure network environment, it's important to know what Ports are accessed and utilized by your management applications. Network Discovery is an agentless discovery tool that allows the Notification Server to go out on the wire and discover what devices exist. This tech tip covers what ports are used by Network Discovery, including their corresponding protocol.

The following Ports are Required by Network Discovery:

  • SNMP : 161
  • HTTP : 80

The following Ports are Optional, but are used by Default:

  • FTP : 21
  • SSH : 22
  • Telnet : 23
  • SMTP : 25
  • Sun RPC : 111
  • Terminal Services : 3389

The following Ports are used If AMT is Enabled:

  • Small Business Mode : 16992
  • Enterprise : 16993

SNMP uses UDP, and the rest are defaulted at TCP.

*Many of the above items can be configured within the Scan Policy for Network Disocovery. See this...

Joel Smith | 23 May 2007 | 0 comments

How does the Software Portal manage Tasks and Collections for Software Requests?

Get answers to these modern mysteries and a few extras thrown in for good measure.

Collections and Tasks
The Software Portal Creates hidden Tasks and Collections to manage the distribution of Requested Software to the target system.

Request Versus Deployment
When accessing the Software Portal, the Portal is constructed based off the Logged On User. The available packages are those the user had rights to within the Software Portal. Deployment Software switches the focus from the Logged On User to the Computer from where the request was initiated from.

Items created by a Software Portal Request

  • The Software Delivery Solution Agent (AeXSWDAppReqAgent.dll) contacts the Notification Server to have the items created.
  • A Task with the naming convention: Software Request: is created. For example, to bring back every...
Joel Smith | 15 May 2007 | 0 comments

Here are the step-by-steps to follow if you find yourself needing to move your NS Tasks and/or Packages from one server to another.

The following items should be exported from the console. Use the right-click context menu to choose the Export option. It is recommended to simplify the process by exporting folders containing the items rather than each individual item.

Note: There is an Import size limit to the XML files so be aware of how many items are in the folders you are exporting.
  1. Software Delivery Packages located at the Resources tab > Resources > Software Management > Software Delivery Packages > Windows.
  2. Software Delivery Tasks located at the Tasks tab > Software Management > Software Delivery > Windows > Software Delivery Tasks. (Note: You may want to export folders only under this folder as this folder contains the code for the Wizard and Status utility.)
  3. Software Delivery Sequential...
trb48 | 11 May 2007 | 1 comment

You arrive at work and have a voicemail. You listen to it, and your boss explains that they have lost all of their personal settings from their computer. You have to fix the problem fast or someone's head is going to roll. What are you going to do?

I found a great article that goes through several different methods to fix this problem. Here it is:
Recover A Damaged Windows XP User Profile

This article should cover everything you need to know. Good luck!

trb48 | 07 May 2007 | 3 comments

As I have learned more about computers I have come to rely on the command prompt. The command prompt allows a system admin to do almost anything in one place. But there is so much to know with the command prompt we all need a good resource on how to use it.

I ran across the following web site: The Windows XP Command Line, Batch Files, and Scripting

The site concisely covers the basics of the command line. It also has some advanced command prompt tutorials.

Check it out, it is worth your time...

Harsh Mokal | 03 May 2007 | 0 comments

Sometimes in packages ICE03 is encountered, which states that a particular entry is not according to a correct format. Here's some info to help you avoid this this chilly error.

ICE03 occurs mainly because of ESCAPE Characters like [,],{,} and so on.

Windows Installer does not automatically recognize these formats. Hence, they need to be written according to a special construct.

The main rule that should be followed is that:

If a substring of the form [\x] is found, it is replaced by the character x ,
where x is one character, without any further processing.
Only the first character after the backslash is kept; everything else is removed.

For example, to include a literal left bracket ([), use [\[].
The text [\[]Bracket Text[\]] resolves to [Bracket Text].

Some examples are:
1) [ should be written as [\[]
2) ] should be written as [\]]
3) { should be written as [\{]
4) } should be written as...

duijsterj | 30 Apr 2007 | 0 comments

Sometimes it's nice to have someone in-the-know walk you through a complex task or procedure. Here's a dandy (and brief) Flash demo that walks you through the steps it takes to set up Launch Conditions when packaging an application using Wise Package Studio.

View the demo (hosted at here.