Bootstrapping Platform Manager Using the Default SSH and WinRM Templates
The method you choose to boostrap Platform Manager on a remote machine depends on whether the remote machine has an SSH server. With
Command Central 10.5 and higher, you can bootstrap
Platform Manager on a remote machine using the
sag-spm-boot-ssh infrastructure micro template.
Before you apply an infrastructure micro template that bootstraps Platform Manager, you must:
Define a credentials alias for the SSH user account that you use to connect to the remote machine, for example by using the
sag-cc-creds-dev. Note that Command Central supports only the PKCS #1 definition of the ASN.1 syntax for representing the SSH private keys.
Read the "sag-spm-boot-ssh" template readme and ensure that the
Command Central host machine and the remote machine(s) meet the requirements described in the readme.
Important:
The instructions in the article also apply when you want to use a composite template to bootstrap Platform Manager on a remote Windows machine.
If the target machine does not have an SSH server, you must download the
Command Central bootstrapper to the target machine and install only
Platform Manager on the remote machine as described in
Install Platform Manager Using the Command
Central Bootstrapper. For a Windows remote machine, you can also use the
sag-spm-boot-winrm infrastructure micro template, which uses the Windows Remote Management (WinRM) service. Note that the
Command Central host machine, from which you run the "sag-spm-boot-winrm" template, must have a Windows operating system and meet the requirements listed in the template readme.
Note that with Command Central 10.3 and lower, you can only bootstrap Platform Manager on a remote Windows machine using the "sag-spm-boot-winrm" template.