Deploying a Windows Credential Provider with Virtual System Administrator

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Deploying a Windows Credential Provider with Virtual System Administrator - Connect IT Community | Kaseya

Note: This guide requires Virtual System Administrator ver. R9.1 - newer.

Note: This guide also requires that you have configured the Passly following this guide.

Supported Operating Systems

Currently this method can be used to deploy to the following versions of Windows.

Windows Vista
Server 2008
Server 2008 R2
Windows 7
Windows 8.0
Windows 8.1
SBS 2011
Server 2012 Essentials
Windows 10
Server 2012
Server 2012r2

Managing your endpoints via Agent Groups

You will need to assign the individual endpoints into Agent Groups before you can deploy the Windows Credential Providers.
Note: We recommend that you group your clients endpoints in unique groups.

To create the Agent Groups follow these steps.

Log into Virtual System Administrator
Select AuthAnvil
Select Two Factor Auth
Select Manage Agent Groups
Select Add Group. Name the group something you familiar to the client you are working with. Example: Acme Servers
Select Add once you are satisfied with the entry.
Select the down arrow next to the Group Name.
Select the endpoints you would like to belong to the group.

Note: The Available machines will be dependent on the machine groups you are viewing in VSA.

Deploying the Agent

Log into VSA
Select AuthAnvil
Select Two Factor Auth
Select Deploy Agents
Select the AuthAnvil Agent Group you wish to deploy to.
Select the specific endpoint(s) you wish to deploy to.
Enter the SAS URL. And Site ID.

Note: The Site ID will always be 1 by default.
Note: See this guide On-Prem style SAS URL for information on using an On-Demand SAS URL.
Configuring the Override Settings.
Set the Override Password. It is always recommend to use this option.
Set the Override Group. This security group will need to be manually created in Active Directory for Domain Joined machines. For stand alone machines this is a local group.
Enable or Disable Installing the Config tool in the Control Panel. This setting will hide the control panel tool if not selected.
Enable or Disable setting for Offline Caching mode. This setting is important if the machine may have internet connection failures in normal usage. Example: Portables / laptops.
Enable or Disable an installation password. If enabled this will prevent users from uninstalling the agent or changing its settings.
Select Deploy once all settings are confirmed.