If the error: "...failed with System.OverflowException: Value was either too large or too small for an Int32" appears in the Altiris logs after an Local Security Solution inventory, this explanation and solution should help you get back on track.

The log entry that points out the problem:

Thread ID: 5372
Module: AltirisNativeHelper.dll
Source: MSoft.ResourceDataTable2
Description: Column loading for row in dataclass: a2e5e8a3-8d87-4595-a669-8ac4346e4d5e, Resource e3dac727-73db-4c11-bbd9-0259d33f5444 column = c3, row = '"row c1="0" c2="0" c3="4294967295" c4="-1" c5="0" c6="0" c7="1800" c8="1800" />' failed with System.OverflowException: Value was either too large or too small for an Int32.
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at MSoft.Resource.ResourceDataTable2.ConvertColumnValue(DataColumn dc, String strValue)
   at MSoft.Resource.ResourceDataTable2.LoadRows(XmlReader dataReader). 

Office 2003 patches w/ batch files on Citrix Servers are failing. A 9009 error appears in the log files. As the batch file executes, it seems to not be able to find the executable file for the patch. Essentially, it is attempting to call the file from a folder where the file is not located.

Environment

Patch Management 6.1 and 6.2

Cause

An entry in the HKLM\Software\Microsoft\CommandProcessor\Autorun subkey was executing prior to the contents of the batch file. The Autorun value was 'CD\'. This, or any entry takes precedence and executes. In this case, because the patch was opening a separate command processor (CMD.exe), the HKLM Autorun entry executed prior to the batch file running, and changed the directory back to the root of the current drive, in thie case 'N:' Normally this should have been 'N:\Temp\cache or %temp%\cache.

For further information, see...

From time to time I have been asked how Altiris is using Recovery Solution internally. Here are some facts that might be useful to you:

Altiris has over 600 machines that are protected using Recovery Solution. These machines are spread out globally, with many concentrated in Altiris offices.

1. Lindon, Utah which also covers remote users in the Western United States as well as the Albuquerque, New Mexico development site.
2. Detroit (Plymouth), Michigan which also covers remote users in the Eastern United States
3. Boston (Newton), Massachusetts (a development site)
4. London, England which also covers remote users in EMEA (the Landau cluster is being decommissioned soon)
5. Tallinn, Estonia (a development site)
6. Sydney, Australia which also covers remote users in Asia-Pac

We have a cluster at each of the these locations with an additional one in the corporate office to handle our data center servers. The servers...

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 to view.

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