IBM Tivoli Monitoring, Version 6.3

tacmd createNode

If the createNode command fails, it might be because of the syntax or a connectivity issue. Review the possible causes and resolutions to help you recover.

Windows 7 and Windows 8

You are able to run the tacmd addBundles command for the Windows OS agent, but when you try to deploy the agent with tacmd createNode on the Windows 7 and Windows 8 computers, the command fails.
Cause
The problem is related to being able to connect to the endpoint.
Solution
  1. Enable Remote Registry:
    1. Click Administrative Tools > Services.
    2. Double-click "Remote Registry" (or right-click it and select Properties).
    3. In the General tab, set Startup type to Automatic and click OK.
  2. Disable password protected sharing:
    1. Click Control Panel > Network and Sharing Center > Advanced sharing settings.
    2. In "Password protected sharing" area, select the Turn off password protect sharing radio button and click Save changes.
  3. If you have a domain user account, ensure that the local and the target machine are both members of a Windows domain.
  4. If you are a member of a local administrators group and you use a local user account, complete the following steps on the local computer to enable administrative tasks on the target computer:
    1. Click Administrative Tools > Local Security Policy.
    2. Expand Security Settings > Local Policies > Security Options
    3. To enable the built-in Administrator account for connecting to the target computer, double-click "Accounts: Administrator account status" and select the Enabled radio button.
    4. If a different Administrator user account is to be used to connect to the target computer, double-click "User Account Control: Run all administrators in Admin Approval Mode" and select the Disabled radio button.
    5. Click OK.

Windows OS agent from a UNIX or Linux host when using the "-d" option and "\" as the path separator

Cause
Because tacmd on UNIX and Linux is a wrapper script for the createNode command, the character "\" is removed from the command.
Solution
Specify the path with the "-d" option using either "/" or "\\\\" when you deploy a Windows OS agent from a UNIX/Linux host. The following examples display the correct usage to install the Windows OS agent in the path C:\ITM63\WIN\OSAgent:
Linux or operating systems such as UNIX c:\\\\ITM63\\\\Win\\\\OSAgent
Windows C:/ITM63/Win/OSAgent


Feedback