Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Features
Showing posts in English
piyushnasa | 27 Aug 2008 | 5 comments

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

While WISE Script is easy to make, I mean takes less effort, VBScript can be very complicated. People who do not know VBScript often find themselves searching for, and copying code from net. WISE Script can be easily written once you have basic understanding of statements. I give this point as an advantage to WISE Script, but people who know how to code in VBScript, will always choose that as an easy option.

Personally, I prefer VBScript over WISE Script because it has some really good advantages. As you might know, we compile WISE Script to an exe and include that in a package. But in doing this, we lose the code which we have written...

WiseUser | 03 Jul 2008 | 5 comments

If you aren't familiar with the WiXConverter utility the following is a brief description of what it is and how to use it.

Wix Converter utility is used to convert WiX projects into Windows Installer Editor projects.

WiX (Windows Installer XML) is a toolset that builds Windows installation packages from XML source code.

The WixConverter utility is provided as a Visual Studio solution, which is installed in the Samples\C# subdirectory of the Wise Package Studio application directory.

To use it, open the solution in Visual Studio .NET, build the solution, and run it. The conversion utility accepts command line parameters and then initiates the WixTOWiseProcessor to perform the conversion. This utility also serves as an example of how to use the Wise Automation object model.

mboggs | 25 Jun 2008 | 4 comments

When using My Helpdesk Console (winuser), sometimes end users try to type their entire issue in the Title field, rather than the Comments field.

I created a Validation Rule which requires the end user to include a Comment when submitting an incident using My Helpdesk Console (winuser).

In addition to this, we renamed the label on winuser from Title to Summary. We had many end users putting their job title in that field, not knowing any better.

Here is the validation rule:

Name: Blank comments not allowed for guests

Comment: Requires guests to enter a non-blank comment.

Display this message: Please enter a comment

Log to Notification Server: If no user interface present

When: Every time incident is saved

And: When ALL of these are TRUE
"Comment" is the same as...

CondorMan | 20 Jun 2008 | 1 comment

I just discovered a nifty utility in the eXpress share called wndctl.exe. You can use it to lock the keyboard and mouse prior to any install/script and unlock it later. It can also activate, minimize, maximize, restore, hide, show, flash, close, disable, enable, tile, cascade, center, move, and resize window(s).

wndctl.exe can be found in any of the following places (in x86 and x64 versions):

  • Bootwiz\platforms\Winpe\x86\Optional\Boot
  • Bootwiz\platforms\Winpe\x64\Optional\Boot
  • Bootwiz\platforms\Winpe2\x86\Optional\Boot
  • Bootwiz\platforms\Winpe2\x64\Optional\Boot

The syntax for wndctl.exe is:

wndctl <command> [<"window title text">] [<n>]

<command> is the command to perform, and is one of the following:

-activate Make the...
BRING | 30 May 2008 | 1 comment

Usually two is better than one. However, in this situation, that is not the case.

When deploying a recently-captured PC Transplant personality, it was discovered that there were 2 Microsoft Excel icons in the Quick Launch Toolbar, as shown in the image below. This was a problem.

To make sure this did not happen again, the PC Transplant personality template was configured to NOT capture Quick Launch toolbar settings. Then, when the personality was deployed, the items in Quick Launch worked correctly.

This only seems to be a problem when migrating settings from Windows 2000 to Windows XP. Migrator, beware!

BRING | 21 May 2008 | 2 comments

Wouldn't you be a bit frustrated if your My Computer icon disappeared? Well, that can happen.

In capturing a PC transplant Personality from a Windows 2000 client computer and restoring that personality to the newly imaged XP computer, upon inspection, it was found that the My Computer icon, and other commonly found shortcuts were also missing, such as My Documents, etc.

The nasty culprit here is the checkbox in the template creation that allows Active desktop settings to be captured. For some reason, when going between Windows 2000 and Windows XP, this causes that to happen.

Alas, simply unchecking the Active Desktop Settings capture item, and re-running the personality capture, gets the personality correctly assembled. Then the restores work just fine!

stebro | 01 Apr 2008 | 0 comments

If you enjoyed the iPhone console prototype, we would be interested in learning more about your mobile device management needs.

Click here to take a short survey.

SandyF | 28 Mar 2008 | 1 comment

With the release of Asset Management 6.5 the whole process of Receiving and Stock Rooms have been added. Here is a summary of how the stock room is used.

Stock rooms are used to house and monitor consumable catalog items. Consumable items are less important assets that are not tracked as individual resources but by quantity in the Stock Room resource type. Stock rooms are linked to a manager who is the recipient of stock allocation requests and order notifications. Stock room order items can be linked to an owner. For consumables this must be a cost center/department (as the cost is attributed to the cost items dataclass), which ensures that accounting details are recorded. Stock rooms are unique based on location.

In the Stock Order Details, the Order Level field for each row, means that when the number of a particular item in the stock room goes down to the specified order level, the stock room manager will be notified, and a purchase order will be...

WiseUser | 23 Jan 2008 | 0 comments

Mobile Device Package Editor is an installation development tool that lets you create an .INF file and compile it to one or more CAB files that install a mobile device application.

It supports the Microsoft® Windows Mobile™ platform for Pocket PC and Smart phone devices.

In the Mobile Device Package Editor's Installation Expert interface, you complete dialogs to specify the installation resources and parameters.

These installation options generate the project file in .INF format, which is used to compile the installation .CAB files.

For advanced customization, you can edit the .INF directly within the Mobile Device Package Editor. Changes that you make in Installation Expert are automatically reflected in the .INF file, and vice versa. You can open an .INF file from any vendor or other third party in the Mobile...

WiseUser | 03 Jan 2008 | 0 comments

The Wise arm of Altiris has come up with a pretty slick technology in their "Linux Package Editor". It basically allows one to use a Windows box to create packages for Linux machines. Here's a list of the key features in this handy tool:

  1. Linux Package Editor lets us to use a Windows computer to create packages that install software on Linux computers.
  2. Using an interface that is similar to that in other Wise installation development products, we can easily create Linux packages without having an in-depth knowledge of Linux commands .
  3. With Linux Package Editor, we can either import an RPM file or Linux archive file, or build an RPM from binary application files.Then we can edit the installation and add scripts to provide additional functionality during the RPM installation.
  4. Linux Package Editor does not build or use a spec file or a source RPM, which typically are used to create RPM packages. Instead, you specify source files and installation...