1. Login to the JetPatch Console via chrome or firefox browser using https://< IP>/
Note: if there is an issue, please review proxy settings.
- When you first access the JetPatch Console, you will be asked to create an admin user with a strong password (at least 8 characters combining uppercase, numbers and symbols).
- After creating this user, log into the console and accept the license.
2. Discover your servers in your environment (see article)
- Go to Platform configuration (upper right-hand corner)
- Go to Settings → Discovery Sources
- Select “Add Discovery Source”
- Choose Source Type – vCenter, AWS, WSUS or Azure
- Fill in the credentials and test the connection
- Alternative option: discover endpoints manually
3. Provide endpoint user accounts with elevated privileges to give JetPatch access to the endpoints (see article)
- Go to Settings → Server Accounts
- Select “Edit Credentials” to add new accounts
- Select the Account Type and provide an Account Name, Username, and Password
- For Linux you can select and use an SSH private key.
Once you’ve provided user accounts, you need to assign them to endpoints.To assign a user account to one or more endpoints:
- In the Servers tab, select the relevant machines. Make sure all selected machines are of the same OS (Windows or Linux).
- Go to Server Actions > Assign Account, and select the relevant account. If there are many configured accounts, you can search:
4. Deploy JetPatch Connector to all endpoints (see article)
- In the Servers tab, select the endpoints, and click Server Actions > Manage Intigua on Server:
- Select Manage Intigua On Server, and under Configuration package, select a JetPatch services management package:
- Click Apply.
- Alternative option: Policy-Based Endpoint Account Assignment and Deploying the Connector using Policy