ACT Connector and ACT 5.6

ACT Connector and ACT 5.6

  • Comments 6
  • Likes

[Today's post is provided by Martin Li]

The Application Compatibility Toolkit Connector (ACT Connector) assists administrators with collecting the necessary computer and application compatibility information to help plan for a Windows deployment. A prerequisite for the ACT Connector is Microsoft Application Compatibility Toolkit 5.5 (ACT 5.5), which was replaced by a newer version, ACT 5.6, on June 7th.

Will ACT Connector work with ACT 5.6? The short answer is "Yes." One limitation is that ACT Connector cannot take advantage of the 64-bit compatibility support newly added in ACT 5.6.  Application compatibility data reported by the ACT Connector are always for 32-bit operating systems.

If you upgrade from ACT 5.5 to ACT 5.6 and update the ACT database following the configuration wizard, ACT Connector features will continue to work as before. After you upgrade to ACT 5.6 and run the ACT configuration wizard, select your existing ACT database in the "Configure Your ACT Database Settings" page. You will notice an "Update" button beside the Database name, as shown in the screenshot below. Click the "Update" button and follow the instructions in "Database Upgrade Options" dialog to update the ACT database.

 

 

Alternately, you may make a new installation of ACT 5.6 rather than upgrading from ACT 5.5. In this case, do not use "Configure ACT Server" under Application Compatibility Toolkit Connector/Application Compatibility Toolkit Server node to configure ACT 5.6 database. Instead, use the VB script (ActConfig.vbs) documented in the following blog post to configure ACT database: http://blogs.technet.com/b/configurationmgr/archive/2009/07/01/support-for-act-5-5-with-the-act-connector.aspx. Please note that if the ACT database is hosted in a SQL named instance, be sure to include the instance name in the ACT Server parameter you pass to ActConfig.vbs. For example, ActConfig.vbs <Site server> <Site code> <ACT Server>\<SQL named instance> <ACT database> <Machine Account>.

Configuring the ACT 5.6 database using "Configure Your ACT Server" provided by ACT Connector will result in an error message reporting a series of invalid column errors. This is because ACT Connector has a dependency on ACT database tables whose schema changed in ACT 5.6.  To avoid this issue, uninstall and then reinstall ACT 5.6 and create a new ACT database. You can then configure the ACT database using the ActConfig.vbs VB script described above.

In summary, if you upgrade an ACT 5.5 environment to ACT 5.6, the ACT Connector will continue to work provided you properly update the ACT database using the ACT Configuration wizard. If you create a fresh installation of ACT 5.6, do not configure ACT database using ACT Connector wizard but instead use the ActConfig.vbs script.

--Martin Li

This posting is provided "AS IS" with no warranties and confers no rights.

 

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Does the ACT 5.6 Connector still support inventory from SMS 2003?  If not, it would seem as if I am stuck deploying the ACT inventory collector.

  • After installing the connector, I see it in the SCCM console, but I get the error "[*The ConfigMgr Provider reported an error.*]" on the Application Compatibility Toolkit Server node and when I click Configure ACT Server.  Any idea what's going on?

  • I'm unable to get this ACT connector to update the database in ACT. When I try to apply "Application Compatibility Toolkit Server Properties" I get an error:

    Cannot connect to ACT-SERVER\ACT.

    [-2146232060] Invalid column name 'myRating'.

    Invalid column name 'vendorRating'.

    Invalid column name 'microsoftRating'.

    Invalid column name 'numCommGreen'.

    Invalid column name 'numCommYellow'.

    Invalid column name 'numCommRed'.

    Cannot find the object 'Application_Report_vw', because it does not exist or you do not have permission.

    If someone can assist that would be great, i've ran the .VBS script from both the SCCM server as well as my ACT 5.6 server.

    My install is as follows:

    Fresh ACT 5.6 install on new Win7 machine SQL2k8 Express

    - Created new DB for ACT during installation

    ACT Connector

    - Installed ACT Connector, it see's the SQL from the ACT server

    actconfig.vbs

    - I run this with no errors but I can not tell if it completes successfully or what as nothing is verbose.

    Please help as this is getting old, and Google is coming up with nothing.

  • To Anonymous: System Center Configuration Manager 2007 Service Pack 1 is a minimum prerequisite for installing the Configuration Manager 2007 ACT Connector Update, version 4.00.6044.2000.  Configuration Manager 2007 Service Pack 2 is recommended for Windows 7 deployment support.

    To grossac1: I'm not sure what the problem is based on the information provided. But I would check the provider log smsprov.log first.

    To EvolutionXtinct: For a fresh install of ACT 5.6, it is important to make sure you NEVER run the "Configure ACT Server" wizard under Application Compatibility Toolkit Connector/Application Compatibility Toolkit Server node. Because the wizard will break the 'Application_Report_vw' view in ACT 5.6 database. If you already ran the wizard, you've got to reinstall ACT 5.6 to fix the view. The correct 'Application_Report_vw' view definition should be this:

    SELECT     A.appName, AR.osID, AR.appID, CASE WHEN (AR.myRating32 = 0 OR

                         AR.myRating32 IS NULL) THEN 4 ELSE AR.myRating32 END AS myRating, CASE WHEN (AR.CompatibilityRating32 = 0 OR

                         AR.CompatibilityRating32 IS NULL) THEN 100 WHEN (AR.CompatibilityRating32 = 1) THEN 100 WHEN (AR.CompatibilityRating32 = 10)

                         THEN 60 WHEN (AR.CompatibilityRating32 = 20) THEN 60 WHEN (AR.CompatibilityRating32 = 30) THEN 60 WHEN (AR.CompatibilityRating32 = 40)

                         THEN 60 WHEN (AR.CompatibilityRating32 = 50) THEN 50 WHEN (AR.CompatibilityRating32 = 60) THEN 40 WHEN (AR.CompatibilityRating32 = 70)

                         THEN 40 WHEN (AR.CompatibilityRating32 = 80) THEN 30 WHEN (AR.CompatibilityRating32 = 90) THEN 20 WHEN (AR.CompatibilityRating32 = 99)

                         THEN 10 WHEN (AR.CompatibilityRating32 = 100) THEN 10 ELSE 100 END AS vendorRating, 0 AS microsoftRating, AR.Works32 AS numCommGreen,

                         AR.PartiallyWorks32 AS numCommYellow, AR.DoesNotWork32 AS numCommRed

    FROM         dbo.Application_Report AS AR WITH (NOLOCK) INNER JOIN

                         dbo.Applications AS A WITH (NOLOCK) ON AR.appID = A.identity_hash

  • What do the values in the CompatibilityRating32 field map to, i mean 100-compatible, 80-upgrade available?

  • From ConfigMgrACTConnectorReleaseNotes:

    "Configuration Manager 2007 ACT Connector Update, version 4.00.6044.2000, enables support for 64-bit operating systems for device driver availability status and systems requirement status."