IBM Support

Installing IBM FileNet IDM (IDM) on Windows 7 or Windows 2008

Question & Answer


Question

What are the procedures to successfully install IDM 4.0.3 on a Windows 7 or Windows 2008 machine?

Answer


1. Download the following Software Packages:

    From IBM Passport Advantage: ( http://www-01.ibm.com/software/lotus/passportadvantage/)
    1. IDM Desktop 4.03 Base Installation. (Product ID CZV7FML)
    2. Image Services Toolkit (ISTK) 4.1.2 Base Installation. (Product ID C1TH3EN)
    3. Image Services Toolkit (ISTK) 4.2 Base Installation. (Product ID CIU5RML)

    Downloading ISTK 4.2 is optional and is not required. ISTK 4.12 can connect to Image Services (IS) 4.1.1, IS 4.1.2 or IS 4.2.

    ISTK 4.2 can ONLY connect to an IS 4.2 system.

    From IBM Fix Central: ( https://www-933.ibm.com/support/fixcentral/)
    4. ISTK 4.1.2 Fix Pack 21 or latest Fix Pack
    5. ISTK 4.1.2 Fix Pack 21 Interim Fix 472371 (Interim Fix only needed until ISTK 4.1.2 Fix Pack 22)
    6. The latest IDM Desktop 4.03 Fix Pack
    7. ISTK 4.2 Fix Pack 10 or latest Fix Pack
    8. ISTK 4.2 Fix Pack 10 Interim Fix 472374 (Interim Fix only needed until ISTK 4.2 Fix Pack 11)

    ** ISTK 4.2 Fix packs only needed if you downloaded ISTK 4.2 Base Installation.

2. Log in as Administrator, and verify you have Create Global Objects privileges.
    To verify you have Create Global Objects privileges, open a command prompt as Administrator.
    Then type whoami /priv.
    You should see the following:

    SeCreateGlobalPrivilege Create global objects Enable

    If it is NOT enabled, these steps can be followed to enable Create Global Objects privileges:

    On Windows 7, go to Control Panel -> System and Security -> Administrative Tools -> Local Security Policy -> Local Policies -> User Rights Assignment -> Create Global Objects.

    For a Windows 2008 user, go to Control Panel -> Administrative Tools -> Local Security Policy -> Local Policies -> User Rights Assignment -> Create Global Objects.

3. On Microsoft Windows 7 and Windows 2008 systems, User Account Control (UAC) security policy needs to be disabled.
    On Microsoft Windows 7, follow this path:
    Control Panel -> System and Security -> Administrative Tools -> Local Security Policy -> Local Policies -> Security Options -> User Account Control: Run all administrators in Admin Approved mode, Change the policy to Disabled.

    On Microsoft Windows 2008, follow this path:
    Control Panel -> Administrative Tools -> Local Security Policy -> Local Policies -> Security Options -> User Account Control: Run all administrators in Admin Approved mode, Change the policy to Disabled.

During installation, disabling UAC is a requirement. You may turn UAC back on after the installation is completed, but it is recommended that you leave it disabled.

4. Install IDM 4.03 Base.

5. Install the latest IDM 4.03 Fix Pack.

6. If DLL registration errors occur after reboot, please install the ISTK 4.1.2 Base Installation. If no DLL registration errors occur, you may skip this step.

7. Install ISTK Fix Pack and Interim Fix if necessary.

8. Follow this Technote to install the ISTKservice:

http://www-01.ibm.com/support/docview.wss?uid=swg21698859

9. If the user will have local administrator privileges, FnSysMgr must be granted "Run as administrator" privilege. If the user will NOT have local administrator rights, you may skip this step.
You can perform this one of three ways:
    1. Give FnSysMgr Run as Administrator rights.
      1. Navigate to Program Files(x86)\IBM\IDM.
      2. Right click on FnSysMgr.exe and select Properties.
      3. On the Compatibility tab, check Run this program as an administrator, and click OK.
    2. FnSysMgr.exe error on Windows 7 and Vista
    After logging in right-click on FnSysMgr.exe present in IDM installation directory and Run As Administrator. Rather than doing every time user login, this can be automated with following registry key setting.

    3. For 32 bit environments: Following command has to be run from Administrative command prompt. (in case effect does not take place after a logout and login, or try restarting the system).
    REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\Program Files\IBM\IDM\FnSysMgr.exe" /t REG_SZ /d "RUNASADMIN"

    4. For 64 bit environments: Following command has to be run from Administrative command prompt. (in case effect does not take place after a logout and login, or try restarting the system).
    REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\Program Files (x86)\IBM\IDM\FnSysMgr.exe" /t REG_SZ /d "RUNASADMIN"
10. All users running IDM on a 64 bit workstation must have full access to the
Program Files(x86)\IBM\IDM\TMP64 folder.
This step does not apply to 32 bit operating systems.

11. If any memory mapping errors are reported in the IDM logs, please stop and start IDM, including any other programs that would use the Image Services Toolkit several times, so IDM has a better idea of what memory addresses are typically used by that specific workstation.

Each time IDM/ISTK encounters the Shared Memory conflict, it removes the bad address from the addr_list file that is held in memory. When the ISTK software is completely shutdown, the addr_list on disk is rewritten and the address that had a memory conflict is removed from the file so it will not be used again. If the next time you run into the shared memory issue, the process repeats itself.

[{"Product":{"code":"SS5USE","label":"IBM FileNet Web Services"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IDM Desktop","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.0.3","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 January 2022

UID

swg21648050

Page Feedback