Technical Bulletin - IDM 4.0.2 on Windows Vista

© Copyright IBM Corporation 2007. All Rights Reserved.


This document describes installation, upgrade scenarios and known issues for IDM on Windows Vista. It also includes alternative methods to overcome the known issues.

Contents

IDM Installation on Windows Vista
Upgrading Windows XP Service Pack 2 with IDM to Windows Vista
Known Issues for IDM Installation on Windows Vista
Known Issues for IDM on Windows Vista
Contact customer support
Notices
Trademarks


IDM Installation on Windows Vista

Follow the procedure below for installation of IDM Desktop on Windows Vista:

  1. Install IDM Desktop 4.0a.
  2. Install IDM Desktop 4.0.1.
  3. Install IDM Desktop 4.0.1 Fix Pack 7 or later
    OR
    Install IDM Desktop 4.0.2.
  4. Edit the "services" and "hosts" files.

Upgrading Windows XP Service Pack 2 with IDM to Windows Vista

The following scenarios are applicable once the user upgrades to Windows Vista:

For upgrading Windows XP Service Pack 2 with IDM Desktop 4.0.1, with or without respective Fix Packs up to Fix Pack 6

  1. Install IDM Desktop 4.0.1 Fix Pack 7 or later.
  2. Edit the "services" and "hosts" files.

For upgrading Windows XP Service Pack 2 with IDM Desktop 4.0.1 Fix Pack 7 or later applied:

  1. Install the same or later IDM 4.0.1 Fix Pack after upgrading to Windows Vista.
  2. Edit the "services" and "hosts" files.

For IDM 4.0a installation and upgrade scenarios on Windows Vista, the following steps need to be performed for editing "services" and "hosts" files:

  1. Open the "services" file located at <System Drive>:\WINDOWS\system32\drivers\etc.
  2. Add "cor 32769/tcp" and "nch 32770/udp" entries under the <service name> <port number>/<protocol> sections of this file.
  3. Open the "hosts" file located at <System Drive>:\WINDOWS\system32\drivers\etc.
  4. Add "<IPaddress> <library_name>-filenet-nch-server" entries for all IS libraries. For example: "10.224.1.123 islib-filenet-nch-server".

Return to Contents


Known Issues for IDM Installation on Windows Vista

Due to security enhancements in Windows Vista, once system is restarted after running IDM Desktop 4.0.1 setup, FnSysMgr.exe throws an error stating failure to update registry. However, these registry entries are created successfully once IDM 4.0.1 Fix Pack 7 or later are applied.

The title bar of the post reboot IDM components registration dialog box shows “IDM Setup (Not responding)”. However, registration continues successfully and there is no functionality loss.

After silent installation of IDM on Vista through SMS server, a report is generated by "Problem Reports and Solution" application of Vista. This application logs a warning stating, ‘The program might not have installed correctly'. However, installation is successful and there is no functionality degradation.

Return to Contents


Known Issues for IDM on Windows Vista

Microsoft has stopped supporting .hlp help file format on Windows Vista. Consequently, IDM Help File(s) cannot be viewed. A message stating that the Windows Help format used is not supported is displayed when attempting to view IDM Help File(s). To view the .hlp files, download the Winhlp32.exe by following the instructions at Microsoft Download Center.

"Set preferences for currently logged on user” and “Set preferences for all users" radio buttons to enable user preferences are not visible to a non-default administrator/standard user. This problem occurs due to the security feature of User Account Control (UAC) in Windows Vista. A non-default administrator can set the user preferences by running IDM Configure as default administrator by following the procedure below:

Right click the idmcfg.exe located at IDM install path and select "Run as Administrator".

or,

Right click the IDM Configure shortcut in the Windows start menu and "Run as Administrator".

Due to security enhancements in Windows Vista, IDM Desktop Application Integration macros do not run with macro security set to High. This is applicable for all scenarios on upgrading Windows XP Service Pack 2 with IDM to Windows Vista. However, this issue can be overcome by setting the macro security to Medium.

Clicking "FileNet IDM Desktop" link on the IDM 4.0.1 Splash screen does not invoke the setup.exe. The following procedure can be used to overcome this problem:

  1. Locate setup.exe in IDM 4.0.1 Media.
  2. Run setup.exe.

Microsoft Internet Explorer 7 runs in Protected Mode due to security features of Windows Vista. This enables Internet Explorer to run with restricted privileges thereby protecting users from online threats. Due to this security feature, IDM Web Client users face the following issues:

The following procedure can be followed to overcome these issues:

  1. Click Tools --> Internet Options in the Internet Explorer Browser and select the Security tab.
  2. Select "Trusted sites" and click "Sites".
  3. Uncheck the "Required server verification (https:) for all sites" combo box.
  4. Add web-server URL http://<servername>/IDMWS to the "Trusted sites" list and click Ok.
  5. Click Custom level and go to Downloads Settings.
  6. Enable "Automatic prompting for downloads" and click OK.
  7. Click "Yes" for the prompt and OK to continue.

Explorer Integration is not currently supported with IDM 4.0/4.0a on Windows Vista as the following document operations through FileNet Neighborhood are not working due to certain Third party software limitations:

  1. Updating document properties through document properties dialog box (IS/CS)
  2. Checking-in a document (CS)
  3. Publishing a document (CS)
  4. Committing a document to libraries through drag and drop (IS/CS)
  5. Committing a document to libraries through copy and paste (IS/CS)

The following alternative methods can be used to perform the above mentioned document operations:

For Updating document properties:

  1. Open the document in IDM Viewer.
  2. Click File -> Properties to open the document property dialog box.
  3. From the "Properties" tab change the required document properties.

For Checking-in a document:

  1. Open the document in IDM Viewer.
  2. Click File -> Properties to open the document property dialog box.
  3. Go to "Version" tab in the property window to view the document versions.
  4. Right-click the checked-out version of the document and select check-in option.

For Publishing a document:

  1. Find the document through IDM Find.
  2. Right Click the document and select "Publish" option to publish the document.

For Committing a document:

  1. After installing IDM 4.0.1 Fix Pack 7, reboot the system and access the Task Manager.
  2. Go to the "Process" tab, select "FnContextint.exe" and click "End Process".
  3. Exit the Task Manager.
  4. Right-click the document to be added.
  5. Select "Add to FileNet Library" option to add the document.

Return to Contents


Contact customer support

For more information about contacting customer support, see the IBM Customer Service and Support web site for FileNet customers. You will need a IBM-issued login name and password to access the web site.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Trademarks