Consider this information before installing IBM® i
Access for Windows on your computer.
Attention: It is recommended that you exit all applications
before installing IBM i
Access for Windows.
This includes applications that may be running in the background such
as spyware, adware, anti-virus, and other malware detection programs.
- Administrative authority and privileges are required
to run the install.
- Only users with administrator authority can install
new releases. You can use the Windows Scheduled tasks feature with
remote access to let your users install without administrator
privileges.
- IBM i
Access for Windows only
supports a per-machine installation. It does not support a per-user
installation.
- IBM i
Access for Windows does
not support the Windows Installer
advertisement feature.
- It is recommended that you use the default destination
folder. However, if you change the folder, consider the following:
- It is not advisable to select the root directory of a drive.
- It is not advisable to select a directory that already contains
files not related to the IBM i
Access for Windows product.
- You should not select a network drive. Installing to a network
drive is not supported.
- You should use setup.exe or cwblaunch.exe to install
the product. You should not use cwbinstall.msi directly.
- Manual intervention is required to install the AFP and SCS printer drivers features.
See the Installing printer drivers topic for
details.
- IBM i
Access for Windows supports
64-bit versions of ODBC, OLE DB, and Secure Sockets Layer (SSL) features.
The 64-bit versions do not appear as separate features, but are simply
included with the 32-bit versions of these features when installed
on a 64-bit edition of Windows.
If you uninstall the 32-bit versions, the 64-bit versions will also
be uninstalled.
- IBM i
Access for Windows supports
a 32-bit and 64-bit version of the AFP Printer Driver; however, the 32-bit version
of the AFP Printer
Driver does not install on a 64-bit edition of Windows.
- The SCS Printer Driver does not install on 64-bit editions of Windows.
- The IBM i
Access for Windows .NET
provider can be called from both 32-bit and from 64-bit applications.
The mode it runs in is dependent upon the application calling the
provider.
Before installing the .NET Managed Provider, the
.NET Framework 2.0 or later must first be on your PC. See www.msdn.com 
for instructions about downloading and installing the .NET
Framework. If you plan to use Microsoft Visual
Studio with the .NET Provider, Visual Studio must be installed before
installing the IBM i
Access for Windows .NET
Provider.
- If you want to use the features of the .NET Managed
Provider which provides integration with Visual Studio 2005 or Visual
Studio 2008, install Visual Studio onto your PC before installing
the .NET Provider feature. If you did not install Visual Studio first,
you can use a maintenance install to remove the .NET Provider feature
and then install it again.
- If Toolbox for Java™ is
not installed, then the IBM Key
Management shortcut can not be opened. This is because this shortcut
requires the JRE to be installed. The IBM Key
Management shortcut is part of SSL. If a user wants a minimum configuration
but needs SSL, then he will not want to install the JRE because the
JRE takes up a large amount of space. If you are unable to use the IBM Key Management shortcut or if
this shortcut is missing, remove SSL and then install both Toolbox
for Java and SSL.
- The IBM i
Access for Windows ODBC
and OLE DB features require MDAC 2.5 or newer. The Windows operating
systems that are supported by this release of IBM i
Access for Windows already have the required
MDAC level.
- To install IBM i
Access for Windows on
a PC that is running Microsoft Windows Terminal Server Edition
or Terminal Services, follow the install instructions in Information
APAR II11373. For information about obtaining APARs, see Information APARs .
- To install IBM i
Access for Windows on a PC that is running Microsoft Windows 7, follow the install instructions
in Information APAR II14522. For information about obtaining APARs,
see Information APARs .
- In rare instances where a problem occurs during
the installation or uninstallation of IBM i
Access for Windows, it may happen that
you can not use the regular installation or uninstallation method
to repair or remove the product. Microsoft provides
a cleanup tool for this situation, described here: Description of the Windows Installer
CleanUp Utility .
This tool does not remove
any files installed with IBM i
Access for Windows,
it only removes the Windows Installer
configuration information that is related to those programs. After
the cleanup utility is run, the you can install again, but you should
install to the same location as before to prevent multiple copies
of files.