HP World Demonstration TDEFs

[Scott Shaffer]

Here are several interesting Windows TDEFs that I discussed during my HP World presentation last week. These are provided without official HP support, but if you have any questions put them in this thread and I'll do my best to answer them.

[David Claypool]

Some folks might find this link to the manual page for the 'mxtool' command helpful to go along with this: http://h18004.www1.hp.com/products/servers/management/hpsim/info-library/mxtool.1m.html

[Mike Kanakos_1]

Could an HP person please explain or provide a link as to how I could implement the XML files into my current SIM 4.1 console?

[Scott Shaffer]

The TDEF XML files can be added to HP SIM through the mxtool command.

Specifically 'mxtool -a -f ' adds it.

[Paul Kratz]

For all who were not able to visit your session at HP World.
Can you please provide a small description what this TDEFs are doing.

Thanks!

[Matthew Kelner]

I am getting an authentication failure whenever I attempt to run any of these. Any suggestions?

[Scott Shaffer]

Here is a quick description. Note that these are for Windows 2003 Server only.

sysinfo.xml - runs the systeminfo command returning an interesting set of information about the target node (including what hotfixes are deployed)
svcstart.xml - configures the service startup mode (automatic, manual, disabled)
svccntrl.xml - controls a service (starts, stops or pauses it)
spcheck.xml - checks to make sure the latest service pack is still properly applied
rdenable.xml - enabled the remote desktop feature (useful if you've forgotten to do it and now need it)
ps.xml - returns a list of running processes
printjobs.xml - control print jobs (assumes the server is acting as a print server)

[Scott Shaffer]

I suspect auth failures are cuased by SSH not setup properly. Refer to the white paper (in the HPSIM information library on hp.com/go/hpsim) for more details.

[Jeff Cottrill_1]

Do these types of tools require OpenSSH on the target servers, CMS, or both?

[Scott Shaffer]

Both - we have to run the command (in most cases) on the managed servers.

[Randy Price_1]

I installed the tools but when trying to run on any servers that I have listed other than the CMS I get the following error under Tool Launch Ok? :

No, does not support the SSH protocol.

I am able to use ssh from the CMS server to connect by using the following command:

ssh user@server and then entering the password. SSH seems to be working properly but I can't find anything on this error. I would really like to get these tools working. Any help would be appreciated.

[Scott Shaffer]

I suspect this is because the remote systems don't have the CMS key installed. Have you run mxagentconfig against the managed nodes?

[Randy Price_1]

Do I have to run this on the CMS or on the managed node?

[Scott Shaffer]

You should probably read the documentation and white papers on setting up SSH on the managed nodes - it covers this and a host of other potential issues. See the Information Library at www.hp.com/go/hpsim.

Specifically, mxagentconfig is run on the CMS and targets a managed node to setup the SSH keys.

[David Claypool]

Bumped to be above moved questions...