Sample

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).

If your workstations are using the NTFS file system, you can use COMPACT.EXE that is included with Windows to compress files with a certain extension. For example, to compress all of the .CHM files (which are rarely used), use the command: COMPACT /C /S:C:\ *.CHM

PowerShell is the new powerful scripting language created by Microsoft. You can install it to Windows XP and above and it is included in Windows Server 2008.

Here is how to run a PowerShell Script through Deployment Server.

I recently got an e-mail about a company that wanted to push out 40+ layers to most of their computers and were seeing a huge performance hit because of this, I'm assuming they were activating all those layers from what the descriptions of their experience was and it got me thinking about the best way to deal with this situation. Well obviously you'd reply "have the users activate them when they need them and deactivate when they're done", the problem here is with the nature of SVS Admin-it's an admin tool and while you can do some permission stuff to limit its features it's not designed to customized in that way.

In this scenario, we are a corporate repackager with the full power of Wise Package Studio 7.0 SP2 at our disposal. Our assigned task is to deploy a Microsoft Office 2003 SVS package to all of the machines in the company. The problem is that each department within the company has a specific Office Profile Configuration setting that they are required to use. We don't want to create a separate MS Office VSA package for each department with the customized settings baked into it and we don't want to configure the MS Office layer after it has been installed because resetting the layer will wipe out all of our settings. So, what can we do...?

As I mentioned in Part I, Inventory Solution was built to maintain a CURRENT running inventory of Managed Computers and as such it does not maintain an archive of historical or changed data.

This article is meant to teach people who completed part one to change their report for use monitoring changes to specific inventory information for their resources in a non-software table. In this article we will discuss enabling and using history tables as well as reporting changes to resource inventories using the Notification Servers history tables. For this test we will monitor changes in Memory for all resources.

One of the most common questions Altiris Inventory Support handles is how to know which machines have a specific software executable or product.

In order to find all computers with a specific file from the audit scan, in the past it was necessary to create a new report for each software you were looking for.