You must configure target computers that run Windows so
that they can be discovered using IBM Tivoli Remote Execution and
Access.
To ensure access through Tivoli Remote Execution and Access, you
have two options.
Note: The Windows information in this topic is derived from information
available through the following links. For the latest information,
see these links for IBM Tivoli Remote Execution and Access configuration
on Windows operating systems:
- http://publib.boulder.ibm.com/infocenter/tivihelp/v11r1/index.jsp?topic=/com.ibm.tivoli.tpm.scenario.doc/sdi/rept_prereq_win.html
- http://publib.boulder.ibm.com/infocenter/rafwhelp/v7r1/index.jsp?topic=/com.ibm.rafw.install.doc/topics/r_network_connection_reqs_Windows.html
All Windows operating systems
- You must enable the remote registry administration, which is the
default configuration, on the target computers. Open Services as follows:
- Windows XP, Windows Vista: select
- Windows Server 2003, Windows Server 2008: select
In the Remote Registry service, ensure that the status
of the service is started.
- You must enable administrative sharing to use Tivoli Remote Execution
and Access to connect to target computers that run Windows. Examples
of the default administrative disk share are C$ and D$. If you disable
sharing, Tivoli Remote Execution and Access considers directories
that are located within the drives as hidden. In this case, the following
message is displayed:
XCIM0009E: Error connecting to remote target <host_name>. Exception: java.io.FileNotFoundException:
CTGRI0003E The remote path name specified cannot be found: <file_or_directory_path>.
Cause: com.starla.smb.SMBException: The network name is incorrect.
Follow
these steps to enable administrative sharing:
- Click My Computer.
- Right click the disk drive that you are enabling for administrative
sharing.
- Click Sharing and Security.
- Select Share this folder.
- Specify the share name, such as C$ or D$, and click OK.
- If Windows Scripting Host (WSH) or the WMI service is disabled
on the target, or if VBScript is otherwise disabled, some Windows
Protocol methods will not work.
Windows XP Professional
Windows Vista
Windows Server 2003
- Both ports 135 (RPC) and 445 (TCP) must be enabled on the target
computers to ensure successful communication using Tivoli Remote Execution
and Access. If Tivoli Remote Execution and Access finds that port
445 is disabled, it uses port 139 (NetBIOS over TCP/IP).
Windows Server 2008