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

Q:
We have the CMS Level 1 and Software License Compliance Suite. The purpose of the SLC Suite was to enter software license purchase information into the NS dbase and have that license information check against the software information collected in the Inventory Solution. How do I configure the Software License Compliance Suite to simply allow me to enter software purchase info (software name, date purchased, quantity, etc.) and view a report that shows me my total number of purchased software licenses versus my total number of installed licenses for one or more software applications?

The Asset Control and Contract Management Solution Product Guide is CRAZY! What I need is someone's Best Practices guide that lays out procedures for initial configuration, procedures for inputing new software purchase info, and relevant reports showing compliance status.

A:
The following is the standard way in which I work with...

Installation of Windows using Linux automation can take 3-6 hours on some systems. This is caused by the memory manager in FreeDOS. Here's a trick that could cut your install time from hours to minutes.

FreeDOS is used to kick off the installation of Windows, because the Windows installer can't run in the Linux environment.

To speed up the installation of Windows, use boot disk creator to install the MS-DOS files.

You'll need a Windows 98 CD to do so.

You don't have to create a DOS PXE image, you only need the MS-DOS files on your system. The Linux scripts will detect that smartdrv.exe is available and use that instead of the FreeDOS memory manager. This will shorten your Windows installations to about 30-60 minutes.

Today we experienced a problem with our Help Desk product in conjunction with using e-mail. We started getting rejected e-mail messages from the Help Desk product that contained a message at the bottom that said "E-mail inbox POP3 protocol failure" (followed by some random text).

When submitting an e-mail to the Help Desk Ticket Submission e-mail address, a new incident was not being created in the Help Desk product.

Furthermore, e-mail notification for manually created incidents were not getting sent out.

After digging around we found that the mailbox contained an e-mail message (a real Help Desk request) that had a 399MB file attachment. The e-mail account has a 250MB quota. We deleted the email message with the large attachment and after a minute or so, notifications started working again and we were able to create new incidents via email.