Altiris performance problems caused by web debugging being enabled on Resource Management, Activity Center, and pcAnywhere

Problem

Performance problems caused by web debugging being enabled on Resource Management, Activity Center, and pcAnywhere

Cause

Web debugging is enabled on some pages for Resource Management, Activity Center, and pcAnywhere

Solution

Turn off .NET web debugging on Resource Management, Activity Center, and pcAnywhere.

1. Each component has a Web sub-folder where a web.config file is located.
2. In the web.config file, find debug and set its value to false.

http://www.symantec.com/docs/TECH175109

Don't forget to click on an Ad if you found this information useful.
thx,
Gert

Nice to know: 'Devices' view in Altiris Activity Center still shows a client in the (IsManaged='1') search filter even after uninstalling the Symantec Management Agent (AexNSAgent.exe)

Problem

After manually uninstalling the ‘AexNSAgent.exe’ from a discovered and previously manageable client system, the computer is still viewed in the Altiris 'Activity Center' under devices with an 'Installed Agent'
The filter, (IsManaged='1') is used to filter computers and as seen on the attached screenshots, the computers with the AexNSAgent uninstalled are still listed.  However, the icon is not active (grayed out).
Creating a filter set to, (IsActive='1') will NOT show the clients that have had their AexNSAgent.exe files uninstalled.
EXPECTED RESULTS:
If the AexNSAgent.exe file is uninstalled from the managed client, an (IsManaged='0') switch should be sent to the Notification Server to indicate it is no longer being managed. This should be reflected in both Altiris Activity Center and First Time Setup.

Cause

Known Issue. Altiris Symantec Management Agent (SMA or Altiris Agent) does not send any inventory information while uninstall of the agent itself. Only sub-agents (plug-ins) send the inventory information, using the agent which is still exist.
This is actually a design restriction, since the client-side uninstall could be performed when no NS connection is available. In that case we can't send the inventory neither postpone the uninstall process.

Solution

This issue has been reported to the Symantec Development team. They are working in providing a solution for this in a future release.


pls click on an AD if you found this information useful.

thx,

Gert

Beware : Altiris enhanced console views and updating to Altiris ITMS 7.1 SP2

http://www.symantec.com/docs/HOWTO61133

To update to enhanced console views 7.1 SP2 from a 7.1 SP1 environment

1. Start Symantec Installation Manager.
2. On the Installed Products page, click View and install updates.
3. On the Product Updates page, search for Altiris Deployment Solution Complete Suite 7.1 SP1a MR1a and take one of the following actions:
   
   Option 1:
   If you find Altiris Deployment Solution Complete Suite 7.1SP1aMR1a in the list of updates on the Product Updates page, then you have an environment that does not include installed hot fixes. You must use the View and install updates option in Symantec Installation Manager to update to enhanced console views 7.1 SP2. You must select the Altiris Deployment Solution Complete Suite 7.1 SP1a MR1a update.
   
   Option 2:
   If you do not find Altiris Deployment Solution Complete Suite 7.1SP1aMR1a in the list of updates on the Product Updates page, then you have an environment that includes installed hot fixes. You must use the Install new products option in Symantec Installation Manager to update to enhanced console views 7.1 SP2. This option lets you install the 7.2 version of your product on top of the 7.1 version of your product.
   
   How to install New Products in SIM:
   
   1. On the Installed Products page, click Install new products.
   2. On the Install New Products page, select the 7.1 SP2 version of your Suite or individual Solution. For example, if you have IT Management Suite 7.1 SP1, select IT Management Suite 7.1 SP2.
   3. Click Next, and continue with the installation process.

Don't forget to click on an AD if you found this information useful.

thx,

Gert

Altiris SQL Database growth issue : InvHist_Policy_Compliance_Status table

Problem

You are facing a database growth issue due to the InvHist_Policy_Compliance_Status table within your Altiris SQL environment.

Cause

Every time a compliance check is ran for a Managed Software Delivery policy a compliance status update is submitted.
When the new status is updated into Inv_Policy_Compliance_Status a copy of all the existing compliance statuses for that client is added to the InvHist_Policy_Compliance_Status table.
How large the table grows all depends on how many MSD policies each client has ran, number of clients running MSD policies, and how often the compliance check is scheduled to occur for each policy.

Solution - http://www.symantec.com/docs/TECH146168

Possible approaches:

1. Change configuration so this table grows more slowly.
   This can be done by modifying MSD policies, so the policy compliance checks are run less often. If the policy check schedule to occur during a time range, the check may occur multiple times during that time range. So, changing the policy to check at certain times will reduce the number of times the check is perfomed, while accomplishing the desired results. If checks are peformed at specific times, consider how often these checks need to be performed. Perhaps daily or weekly will be sufficient.
   Slowing the growth will reduce the work which is done on the various managed computers, and the amount of data they forward to the SMP server, which the SMP server has to process.
   To see which policy are contributing the most to the recent growth of this table, use first attached SQL; the second query show the computers that are the largest recent contributors.
2. Disable the saving of this historical information.
   If you have slowed the growth of this table, and it is still growing to rapidly, then you may want to disable the saving of the history for this data class. Note that this table is used by some reports.
   The history settings can be found in Settings\Notification Server\Resource and Data Class Settings\Resource History.
   Disable check box for this data class in history settings. Note that existing table is renamed to InvHist_Policy_Compliance_Status_Backup_1 (or similar). This table is no longer in use and can be deleted/moved to regain space.
3. Slowing the growth of this table, will not reduce the size of this table immediately. The table should eventually shrink through the normal data class purge processes. But if want to free up this space immediately, then if appropriate precautions are taken, this table can be truncated.
   First perform a complete database backup, prior to implementing the following change.
   Second, the query can be used to truncate the table.
   TRUNCATE TABLE InvHist_Policy_Compliance_Status

Following SQL queries can used to identify the problem

• InvHist_Policy_Compliance_Status-count-by-policy-1d.sql
• InvHist_Policy_Compliance_Status-count-by-resource-1d.sql

Don't forget to click on an AD if you found this information useful.

thx,

Gert

Changing the package codebase of your Altiris Symantec Management Platform

This can become handy when your clients can’t resolve the Full Qualified Domain Name (FQDN)
By default, during the installation of the Symantec Altiris Notification Server, SIM (Symantec Installation Manager) populates this regkey with whatever server name you selected during the configuration page during the initial installation, which usually is the Full Qualified Domain Name (FQDN). So, in order to modify the preferred Notification Server hostname for SWD codebase and snapshot URLs, you need to do the following:

• Open the Registry Editor (Open the RUN prompt and type regedit and click OK)
• Go to HKLM>Software>Altiris>eXpress>Notification Server and open the PreferredNSHost regkey.
• Modify the PreferredNSHost regkey by adding the NetBIOS, FQDN, or IP Address that you want to use for SWD codebases and snapshot URLs.
• Restart the Altiris Service
• Then go to Control Panel>Scheduled Tasks and run the NS.Package Refresh schedule (by default it runs everyday at 3:30am). By running this schedule, the SWD codebases and snapshot URLs should be updated.

Note: If for some reason the PreferredNSHost regkey is not present but there is the reference of it on the coreSettings.config, just recreate the regkey. Create a String Value and call it 'PreferredNSHost'.
Additional Note: Do not add ports to the PreferredNSHost setting (such as nsServer:5814 or 10.x.x.x:5484). Adding a port will cause the NS.PackageRefresh to FAIL
http://www.symantec.com/docs/HOWTO10091

Altiris ITMS 7.1 SP2 release notes available

http://www.symantec.com/docs/DOC4893
A short overview of some changes in regards to ITMS

• Symantec Management Console supports Internet Explorer 9 (in IE 8 compatibility mode)
• Support for additional OS's
• o Mac OS X 10.7
• o RHEL 6
• o RHEL 6.1
• o Solaris 10 U9 (includes Zones Inventory)
• o SUSE 11 SP1
• All documentation is now available under Symantec Help Center
• ESX/ESXi 4.1 & v5 support for Server Management Suite
• Several reliabiltiy and performance enhancements
• Some changes around Software Products within Software Management

Running IE6, IE7 and IE8 Side-by-Side on Windows XP Using Symantec Workspace Virtualization

More Information and a detailed how-to can be found on this page

http://www.symantec.com/connect/articles/running-ie6-ie7-and-ie8-side-side-using-symantec-workspace-virtualization

Symantec Workspace Virtualization is the successor of the Altiris Software Virtualization Solution ( SVS )

If you find the information usefull please leave a comment and don't forget to click on an AD, thx !

Symantec Altiris ITMS 7.1 released

The latest version of Symantec Altiris ITMS 7.1 has been officially released !

Symantec Altiris PcAnywhere Solution fix 31/1/2011 - The Domain drop-down list is empty, multiple domains are not listed, or "No Data" is displayed– Fix

Problem

In the Symantec Management Console (SMC) under the Authentication tab of the pcAnywhere Settings policy for Windows, the Domain drop-down list is empty.  Or, if multiple domains should be listed, they are not.  In addition, "No data" may be displayed in the grid where Active Directory users and groups should be present.
Also, on a managed client computer with the pcAnywhere Solution plug-in installed, the following error may appear at startup:

"The pcAnywhere host you are attempting to run is configured for caller authentication, but no caller items could be found.
You must define at least one caller before you can use this host item."

Environment

pcAnywhere Solution 12.5 in an Active Directory (AD) environment

Cause

There are multiple causes for this behavior.  Here is a list, presented in the recommended order for troubleshooting:

1. There was a defect in pcAnywhere Solution which results in a delay in populating the active directory information, or a timeout, or an error, when the Add button is clicked within the Authentication tab of the "pcAnywhere Settings - Windows" policy or a clone of it.
2. The SMP server is not properly joined to an Active Directory domain.  A possible contributing factor is that the server has been recently rebuilt without first deleting the computer account from AD.
3. You are attempting to add callers from a different domain than the one to which the Symantec Management Platform (SMP) server belongs, and a proper trust relationship is missing.
4. NetBIOS over TCP/IP is disabled on the Symantec Management Platform server.
5. The Notification Server cannot fully communicate with the domain.
6. During installation of the SMP, the Application Identity specified was a local account rather than a domain account.

Solution

1. Attached to this article is the latest patch for pcAnywhere Solution 12.5 SP2 (Symantec.pcA.Web.dll_Jan312011.zip).  Inside the zip file is Symantec.pcA.Web.dll.  This latest patch contains a fix to a memory exception error, plus the latest optimizations in the code for browsing AD.  Please apply this latest patch over previous versions of the patch.

   Before copying the new Symantec.pcA.Web.dll to the Symantec Management Platform server, close all instances of the Symantec Management Console.  Copy the original file from C:\Program Files\Altiris\pcA\Web\Bin into a completely separate folder (do not paste the copy into the original folder). Then overwrite the existing file with the new file. Ensure that there are no extra copies of the file in the C:\Program Files\Altiris\pcA\Web\Bin folder.  Finally, open a Command Prompt and run the command "iisreset".  The command should return "Internet services successfully restarted".
   Note that with this new file, the "Add Users or Groups" console page will initially display the first 100 AD user objects, while the thread which queries AD is still running. Eventually, once all of the AD user and group objects have been returned to the console, it will be possible to scroll down and to search for the object. The number of AD objects will affect the duration of the query.  Clicking the scroll bar to the right of the window will show the number of user and group objects that have been retrieved to that point.

2. To test for the second Cause listed above, verify domain membership of the SMP server.  One method of verification is to open My Network Places and check that the expected domain(s) are visible and available for browsing.  A blank Domain entry in the SMC has been reported when the expected domain(s) were not browsable from My Network Places. 
   To resolve this, it may be necessary to temporarily configure the server to be a member of a workgroup, reboot the server, delete the computer account from AD, and then join the server to AD.
3. To resolve the third Cause listed above, ensure that a proper trust relationship exists from the domain containing the SMP server to any other domains that you plan to specify for caller authentication.  As noted immediately above, a simple test that the domains trusts are properly configured is to open My Network Places on the SMP server and check that the expected domains are visible and available for browsing.  Also, see the article "Cross-forest (or cross domain) authentication issues when accessing the Altiris Console", TECH133262, for information about issues found with the SMP core in case they impact pcAnywhere Solution.
4. You will need to enable NetBIOS on the server ("Enable NetBIOS over TCP/IP" under Advanced TCP/IP Settings).
5. This does not indicate a product issue.  As a test,  try to add a domain user or group to the local administrators group directly on the NS server.  If unable to find the user/group, there may be a problem related to Active Directory (browsing, domain membership of the NS, trusts, etc.). Resolve communication, trust, and permissions issues between the NS and the domain controller.
6. To check that the last Cause listed above is the problem, open the SMC and click Settings > All Settings > Notification Server > Notification Server Settings.  The Processing tab has an Application Identity section.  If the User shown is not in the form of DOMAINNAME\username, then a local account was provided during the initial installation of the SMP.  The pcAnywhere Solution browses the Active Directory using the context of the Application Identity, so the Application Identity must be an Active Directory account in order to browse Active Directory.
   The following steps are based on Method 3 from the following Knowledge Base article:
   How to change Application Identity in NS7.
   WARNING: There are several places to check when changing the Application Identity, and mistakes can result in failures of services to start and failures accessing the SQL database!  Symantec recommends a full server and database backup before proceeding with the steps below.  Please contact Symantec Technical Support with any questions prior to proceeding with these steps...
   
   A.  In Active Directory Users and Computers, create the account that you plan to use as the new Application Identity and leave it a member of the Domain Users group.
   B.  On the SMP server, add the new domain account to the local Administrators group.
   Verify that the domain account can login to the SMP server, and can login to the SMC.

C.  Open the SMC and click Settings > All Settings > Notification Server > Notification Server Settings
Change the Application Identity to your domain account in the format DOMMAINNAME\username, provided the password twice, and click OK (the OK button is located in the lower-right corner of the page).

D.  In the SMC click Settings > All Settings > Database Settings.  Verify that "Use application credentials" is selected (this is the default). If it is not selected then ensure that the database credentials are valid. 

E.  In the SMC, click Settings > Security > Roles > Symantec Administrators > Membership tab.  Verify that the domain account specified as the new Application Identity appears here.

F.  In the Service management console on your SMP server, look at the Log On As column.  If any of the services listed show the old local account under this column, right-click service, click the Log on tab, and set the "This account" value to the domain account you specified for the Application Identity in the format DOMMAINNAME\username.  Also, set the correct Password and Confirm Password values.  Click OK.
Following is a list of services to check:  Altiris Client Message Dispatcher, Altiris Client Task Data Loader, Altiris Event Engine, Altiris Event Receiver, Altiris File Receiver, Altiris Object Host Service, Altiris Service, Altiris Support Service.

G.  On your SMP server (or your SQL server if this is an off-box implementation), check whether the following services are configured to run as the old local Application Identify account:  SQL Server (MSSQLSERVER), SQL Server Agent (MSSQLSERVER), SQL Server Browser, SQL Server Full Text Search (MSSQLSERVER).  If they are, similar to the step above, configure those services to run as the new domain Application Identity.
H.  On your SMP server (or your SQL server if this is an off-box implementation), open Microsoft SQL Server Management Studio and click SERVERNAME > Security > Logins.  Add the domain account used for the new Application Identity.   Under Server Roles for that user, add both "public" and "sysadmin" roles and click OK.
Once you have made these changes, reboot your SMP server and verify that all of the services you changed have started.  If a service fails to start, then correct the account and password used to start the service as shown above.  Finally, verify within the SMC that you can now add users and groups from the Active Directory to the Authentication tab for the pcAnywhere host configuration policy.

Fix can be downloaded on

http://www.symantec.com/docs/TECH41883

SQL Server 2008 R2 officially supported with Altiris CMS/SMS 7.1

SQL Server 2008 R2 will be officially supported with CMS/SMS 7.1 http://www.symantec.com/docs/HOWTO26164

Symantec Altiris - Find all tables that contain a specific GUID

A very nice knowledgebase article which can help you during troubleshooting. Works for version 6 and version 7.

The following SQL script will traverse an Altiris database and find all tables in which a specified GUID appears. It reports both the table and the column. The only requirement is to change the value of the guid being searched (Under the line that reads "Enter Search Guid here")

http://www.symantec.com/docs/HOWTO1191

Creating new IIS application pools - the magic solution to SMP 7 slow console operations?

A howto can be found here

http://www.symantec.com/connect/blogs/creating-new-iis-application-pools-magic-solution-smp-7-slow-console-operations

Additional Knowledgebase Information:

http://www.symantec.com/docs/HOWTO4592

Using NS6 Custom Inventory in NS7

Custom Inventory in NS7 is significantly different than in NS6. In fact, the two methods are incompatible. NS6 custom inventory will not run in an NS7 environment as an inventory process. However, by utilizing the data class creation and software management capabilities of NS7, it is possible to continue using the NS6 custom inventory files in an NS7 environment, thus preserving the investment in NS6 custom inventory

More information and a How-To can be found here…

http://www.symantec.com/docs/HOWTO10489

Setting Up and Configuring a Handheld Emulator to Use the Symantec Barcoder Application

There are many times where testing an application or configuration are useful, prior to rolling out in a production environment. Such is the case with Barcode Solution. It is necessary to test the functionality or usage, prior to allowing production based use, or to troubleshoot problems. The costs of providing an actual barcode reader can also be prohibitive, especially if the reader is only used for troubleshooting.

A complete setup description can be found here…..

http://www.symantec.com/connect/articles/setting-and-configuring-handheld-emulator-use-symantec-barcoder-application

Upgrading Altiris Inventory Solution -- Best Practices

http://www.symantec.com/connect/articles/upgrading-inventory-solution-best-practices

Solution Upgrade

The main solution upgrade will take the NS offline as it commences. This includes pausing the Server so no incoming NSE files will be processed. The queues will fill up with files as the NS Event Router is still moving files from the postevent.asp page to the respective queues. Other internal tasks (including client configuration updates) will not process during this time.
The upgrade might take a long time if Normalization and other data class upgrades are required during the upgrade, and depending on the size of the Database. It is recommended to use the 'Update' button under the Solution Center to upgrade as this will check all prerequisites:

Click to view.
Note: Inventory Solution 6.1 SP2 requires Notification Server 6.0 SP3 R4 as Vista Support is added in these two products and versions.
The following issues should be considered when Upgrading:

• Upgrade completes but console items are missing: https://kb.altiris.com/article.asp?article=19921&p=1 Note: If you are using the SP1 or SP2 installer this should be resolved.
• Error is reported in the Notification Server log when upgrading from Inventory Solution 6.0 to 6.1 SP1. When upgrading from Inventory Solution 6.0 to 6.1 SP1, the "Class Name: AeX HW ActiveTcpUdpPorts Class Guid: b50e2401-5865-43ed-95e7-75f06b77d7ce Trying to register a Split Table to a common data table that either does not exists or is not 'common' classtype" error is reported to the Notification Server log file. This error is reported because the AeX HW ActiveTcpUdpPorts data class being accessed in 6.1 SP1 did not exist in 6.0. Note: This error will not affect the upgrade process.
• IMPORTANT > The upgrade deletes all custom files not originally part of the Inventory Agent Package (located at \Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\Inventory Solution). This includes all custom scripts, INI files, custom inventory XML files, or any file not created by Inventory directly.

Normalization

The splitting of the data classes was done to improve performance of reporting. Since Inventory Solution's usefulness comes from reporting and secondly Collection usage, it is essential to get the most out of the upgrade by understanding what is occurring.
A utility page for Normalization data classes has been provided in the Altiris Console. Under View > Configuration (Configuration tab in the 6.0 Console) > Solution Settings > Asset and Inventory > Inventory > Windows > Normalize:

Click to view.
Use the following steps to analyze if Normalization is required after an upgrade:

1. After an upgrade is completed, browse to the above location. To check if it is completed, look in Task Manager for a dcsplit.exe process. If it is running, leave it running until it is completed.
2. Grayed-out entries are already Normalized. If Normalization is not successful, browsing back to this page will show the entries 'active' again.
3. Check the boxes if those classes to normalize. Note that this process takes considerable resources and time to complete depending on the size of the Inventory tables being split.
4. It is recommended to check the 'View progress of Normalization' so that the status can be directly checked. Once running, do not try to access this page for additional normalization until the process is completed.

The following issues should be considered when Normalizing the database:

• Reports not working after Upgrade: https://kb.altiris.com/article.asp?article=17277&p=1
• Normalization fails on the Software data classes: https://kb.altiris.com/article.asp?article=21235&p=1
• If Normalization is not done, what are the results?: https://kb.altiris.com/article.asp?article=27396&p=1

Special Group Deprecation

New installations of Inventory Solution 6.1 Sp1 or SP2 do not have Special Groups. This document will not cover the use cases for Special Group Deprecation, but will cover the process of doing it. To see the reasons for deprecating Special Groups, please see Juice Article: Improve Inventory Solutions Performance: Deprecate Special Groups
If you installed Inventory Solution 6.1 SP1 or SP2 as a new install, nothing needs to be done as Special Groups were never setup. Note that while they do not exist, the Special Group tab is still available for use.
Upgrades to SP1 or SP2 will still have all default and custom Special Group Data classes present. To remove the default ones, a utility has been provided to accomplish this.

1. Browse to the following folder: NS_install_path\Program Files\Altiris\Inventory\Special Groups Upgrade.
2. Launch the .EXE: Altiris_SpecialGroupsUpgrade_6_1.exe.

This executable removes the separate Special Group data classes from the Notification Database. It updates the files, such as AuditPls.ini, win32invFloppy1.exe, and AeXWebInvPkg.exe files. The Special Groups inventory will now be collected into the standard AeX SW Audit Software data class.
For more information, please see the following Article:

• Details on Special Group deprecation: https://kb.altiris.com/article.asp?article=27989&p=1

Data Class Upgrades

Changes made to data classes outside of Normalization provide additional support and functionality previously unavailable. The following items detail the changes that have occurred to provide this functionality:

1. UUID value captured > Previous to Inventory 6.1 SP1 we did not capture the system UUID with AeXSNPlus. Now we capture this as part of the AeX HW Serial Number table. Note: It is recommended to use SP2 as there was a known issue with the new UUID column that has been resolved. See the following KB for details: https://kb.altiris.com/article.asp?article=25625&p=1
2. VM GUID column added > In Inventory 6.1 Sp1 the AeX VirutalMachine data class now has this column capturing the Guid of the virtual machine, allowing you to better distinguish between host and clients. Note that a bug caused this column to be empty until 6.1 SP2.
3. Physical Memory Size > Previous to Inventory 6.1 SP1 we incorrectly reported memory sizes above 2GB. This has been corrected by both AeXMachInv and the database table that houses this information.
4. Software File Size > Previous to Inventory 6.1 SP2 the data type for the file size column was an INT or Integer. This limited the largest size we were able to record to 2GB. Now the data type is BigINT, allowing a much larger size value to be captured.
5. 64-bit Support > We've added support for 64-bit computers to Inventory 6.1 SP2. While we still captured some data in previous versions, we now officially support it and capture more data. In AeX OS Operating System we added an 'Architecture' column with the possible values of 32 or 64, respectively.
6. Vista Support > In Inventory 6.1 SP2 we've added native support for Vista.
7. CPU Core Count > We now track the CPU core count as of Inventory 6.1 SP2. Note: See the following KB for a known limitation: https://kb.altiris.com/article.asp?article=32370&p=1

Inventory Agent Package

Inventory Solution does not have a standard plug-in Agent for the Altiris Agent. The Inventory Agent is a collection of files including Inventory Agent 'EXE's that execute individually. These Agents have had improvements and upgrades made to them, some of which are required for the upgraded Data Classes.
Normally after the upgrade the Agents running the Inventory Tasks will automatically update to the new version of the package. This is done through this process:

1. The Altiris Agent requests a new configuration
2. New snapshot information is received for the Inventory Agent Package.
3. The Altiris Agent downloads the files that have changed.

If Package Servers are used in the environment, make certain they are working properly and have received the new version of the Inventory Agent Package.
Note: Failure to do so may result in Inventory being thrown out at the Server! If the old Inventory Agents send data to the new database schema, the NSE will likely be thrown out because the schema in the NSE containing the data will not match the database.

Inventory Reports

Don't forget to upgrade the Report Pack for Inventory Solution! The reports used to reside as part of the main Solution installer, but now the Reports install with a separate execution. This allows new builds of the reports to be released without touching the main Inventory Solution installation (most definitely recommended).
The main version for SP1 and SP2 is Report Pack for Inventory Solution for Windows 6.2. The complete build numbers are as follows:

• Inventory Solution 6.1 SP1 > 6.2.1036
• Inventory Solution 6.1 Sp2 > 6.2.1046

If you use the Solution Center, the Report Pack should automatically be upgraded to the correct version. If you are not using the Solution Center, you should download the Report Pack from http://www.solutionsam.com/solutions/6_0/; Filename: Altiris_ReportWinInv_6_2.exe.

Computer import function isn't working after upgrading to DS 6.9 SP2

After upgrading  the computer import function

Upgrading from DS 6.9 SP1 MP1 to DS 6.9 SP2 apparently breaks the Import Computers function.

Everything seems to work but at the end you get the following message:"An unhandled win32 exception occurred in Express.exe" and the DS console shuts down without importing the computers.

A workaround for this issue has been found by "Stefan Cleuren"

Step 1: File > New Computer

Step 2: Now you get the option of importing once more

Step 3 : Select your import file

Step : Done !

What Primary Lookup Key should I use with Deployment Server?

If you choose a Primary Lookup Key that is identical on two or more of your computers or if that key is missing on any of your computers, Deployment Server will not be able to identify them. To identify which Primary Lookup Key is best, open SQL Query Analyzer, select to the Deployment Server database, and run the the query against the Deployment Server database. The result will tell you which keys have duplicate computers and which ones don't. It will also show you which keys have duplicates.

DECLARE @sn INT SET @sn=(SELECT COUNT(1) FROM (SELECT T.serial_num AS [Serial Number], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, serial_num FROM computer GROUP BY serial_num HAVING COUNT(1) > 1) T WHERE C.serial_num = T.serial_num) T )
DECLARE @at INT SET @at=(SELECT COUNT(1) FROM (SELECT T.asset_tag AS [Asset Tag], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, asset_tag FROM computer GROUP BY asset_tag HAVING COUNT(1) > 1) T WHERE C.asset_tag = T.asset_tag) T )
DECLARE @uuid INT SET @uuid=(SELECT COUNT(1) FROM (SELECT T.uuid AS [UUID], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, uuid FROM computer GROUP BY uuid HAVING COUNT(1) > 1) T WHERE C.uuid = T.uuid) T )
DECLARE @mac INT SET @mac=(SELECT COUNT(1) FROM (SELECT T.mac_addr AS [MAC Address], T.duplicates AS [Duplicates], N.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM nics N, (SELECT COUNT(1) AS duplicates, mac_addr FROM nics GROUP BY mac_addr HAVING COUNT(1) > 1) T, computer C WHERE N.mac_addr = T.mac_addr AND C.computer_id = N.computer_id) T )

IF @sn = 0
  SELECT 'Serial Number OK' AS Message, 'You may use Serial Number as your Primary Lookup Key' AS Details
ELSE
  SELECT 'You have computers with duplicate Serial Numbers' AS Warning, 'Do not use Serial Number as your Primary Lookup Key' AS Details
IF @at = 0
  SELECT 'Asset Tag OK' AS Message, 'You may use Asset Tag as your Primary Lookup Key' AS Details
ELSE
  SELECT 'You have computers with duplicate Asset Tags' AS Warning, 'Do not use Asset Tag as your Primary Lookup Key' AS Details
IF @uuid = 0
  SELECT 'UUID OK' AS Message, 'You may use UUID as your Primary Lookup Key' AS Details
ELSE
  SELECT 'You have computers with duplicate UUIDs' AS Warning, 'Do not use UUID as your Primary Lookup Key' AS Details
IF @mac = 0
  SELECT 'MAC Address OK' AS Message, 'You may use MAC Address as your Primary Lookup Key' AS Details
ELSE
  SELECT 'You have computers with duplicate MAC Addresses' AS Warning, 'Do not use MAC Address as your Primary Lookup Key' AS Details

SELECT T.serial_num AS [Serial Number], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, serial_num FROM computer GROUP BY serial_num HAVING COUNT(1) > 1) T WHERE C.serial_num = T.serial_num
SELECT T.asset_tag AS [Asset Tag], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, asset_tag FROM computer GROUP BY asset_tag HAVING COUNT(1) > 1) T WHERE C.asset_tag = T.asset_tag
SELECT T.uuid AS [UUID], T.duplicates AS [Duplicates], C.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM computer C, (SELECT COUNT(1) AS duplicates, uuid FROM computer GROUP BY uuid HAVING COUNT(1) > 1) T WHERE C.uuid = T.uuid
SELECT T.mac_addr AS [MAC Address], T.duplicates AS [Duplicates], N.computer_id AS [Computer ID], C.name AS [Console Name], C.computer_name AS [Computer Name] FROM nics N, (SELECT COUNT(1) AS duplicates, mac_addr FROM nics GROUP BY mac_addr HAVING COUNT(1) > 1) T, computer C WHERE N.mac_addr = T.mac_addr AND C.computer_id = N.computer_id

During the Altiris Agent Installation window I get the following error: 'The following error occurred on the page InstallClient.aspx: Failed to Render the control'

Problem/Symptoms

During the Altiris Agent Installation window I get the following error:
The following error occurred on the page 'InstallClient.aspx: Failed to Render the control'
In the logs, the error looks like this one:
Priority: 1
Date: 10/4/2006 9:44:34 AM
Tick Count: 183687687
Host Name: NSServer
Process: w3wp.exe (4592)
Thread ID: 7528
Module: AltirisNativeHelper.dll
Source: global.asax
Description: Unhandled exception.  Type=Altiris.NS.Exceptions.AeXException Msg=Failed to render the control.
StackTrace=
   at Altiris.NS.UI.Controls.CollectionPickerCtrl.Render(HtmlTextWriter output)
   ....(obmitted section)

Inner exception.  Type=Altiris.NS.Exceptions.AeXException Msg=Failed to get the names of the selected collections.

Inner exception.  Type=Altiris.NS.Exceptions.AeXException Msg=Failed to fetch Collection datarow from database. No rows returned.

Looking on the Notification Server logs, you may find another error like this one close to the error above:
Priority: 1
Date: 10/4/2006 9:45:01 AM
Tick Count: 183715343
Host Name: NSServer
Process: aexsvc.exe (1740)
Thread ID: 6720
Module: AltirisNativeHelper.dll
Source:
Altiris.NS.StandardItems.Collection.DeltaCollectionUpdateSchedule
Description: Error occurred during delta collection updating: Altiris.NS.Exceptions.AeXException: Failed to fetch Collection datarow from database. No rows returned.

Resolution

For this error, The following error occurred on the page 'InstallClient.aspx', please try the following article:
Article ID: 18945 "Object reference not set to an instance of an object—Altiris Agent Installation Page"

If you still get the same error please try the following:
--Use the following query to find out if any defined collections are missing from Collection table:

select guid, name
from item
where classguid in
    (
    select distinct classguid
    from item
    where guid in
    (select guid from collection)
    ) and
      guid not in
       (select guid from collection)

--Use the following SQL query to move missing collections into a temporary table to be used for an insert into the Collection table.  This should resolve the collection inconsistencies causing the errors:

SELECT Guid, '34BE747F-C855-4F8F-93E7-50176076A200' as LegacySolutionGroupGuid, createddate, modifieddate into #t
FROM Item WHERE Guid in
    (select guid
    from item
    where classguid in
        (
        select distinct classguid
        from item
        where guid in
        (select guid from collection)
        ) and
          guid not in
           (select guid from collection)
    )
begin tran
insert into collection (Guid, LegacySolutionGroupGuid, CreatedDate, ModifiedDate)
  select Guid, LegacySolutionGroupGuid, CreatedDate, ModifiedDate from #t
commit tran
drop table #t

Windows Boot Manager error after laying down a 2008 r2 or Windows 7 image

Article ID: 45191

Problem/Symptoms

Windows Boot Manager gives the error "winload.exe 0xc000000f " after placing down a 2008 r2 or Windows 7 image.

Resolution

By creating a run script task that runs before capturing the image while in windows, this error should be resolved.

Place the following script into that run script task.

REM Execute BCDEdit and prepare for imaging.
REM Find the system root and append system32 and BCDedit
%SYSTEMROOT%/system32/Bcdedit.exe -set {bootmgr} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} osdevice BOOT
shutdown /r

Manually run Altiris Patch Management Inventory Policies on a client

A command-line utility called "AeXPatchUtil.exe" is a new feature for Altiris Patch Management 6.2. It has been placed in the directory C:\Program Files\Altiris\Altiris Agent\Agents\PatchMgmtAgent and can be used on a computer with the Altiris Software Update Agent installed to run Inventory policies.

There are four Inventory policies that the above Patch command line utility is supposed to run when used with the "/I" option.

Under the Global folder:

•   Default Windows OS Inventory Policy
•   Default Windows Software Release Inventory Policy

Under the Microsoft folder:

•   Default Microsoft Software Inventory Policy
•   Default Microsoft Vulnerability Analysis Policy

When the user runs the Patch command line utility AeXPatchUtil /I only three of the four Global and Microsoft policies are run. Currently the Default Windows OS Inventory Policy is being missed. Additional information can be found on https://kb.altiris.com/article.asp?article=29549&p=1