Evo Cloud is our answer to a cloud directory. If you do not have a domain, or do not use another directory, we offer this service as part of Evo so that you can utilize a directory for yourself and for your users. This could be an answer for you if you are trying to protect workstations that are non-domain joined and all users are local. Let's take a look at how we accomplish this:

Getting started with Evo Cloud

1. First, head on over to "Directories" within your portal of the selected Customer (or your own company) and create a new directory:

2. Select "Evo Cloud Directory as a Service"

3. Enter a name for your directory

4. Click complete, and your directory will now be created.

Adding Users

Now that your directory is created, you will now need to add your users. Let's take a look at how to add users by following this support article - Adding an Evo Cloud User

NOTE: If you plan to use Evo Cloud as your directory type, the usernames you create MUST match the usernames that exist locally on the machine. For Example:

Local Username: Thomas

Evo Cloud: Thomas@domain.com

Evo considers the username to be the text before the @ symbol.

Installing the Evo Credential Provider

So, you now have your directory created, your users created and enrolled with the Evo Mobile Secure Login App (If not, please reference this article - Evo Mobile App), and you are now ready to install the Evo Credential Provider on your workstation. 

To do so, please follow this guide here - Integrating Evo with Windows Desktop.

Be sure to make note of step 12 in the article, that you MUST append a "_local" to the end of the directory name in order for Evo Cloud to work, as we are referencing the local machine.

Once complete, finish the install, and you're done! You have now finished configuring Evo for Secure Logins on Local Machines with Local Users using Evo Cloud! You can begin authenticating at your earliest convenience. 

Elevated Access Support?

Yes! You do have Elevated Access support when using Evo Cloud. However, there are a couple key differences that you must be aware of in order to correctly implement this:

• The shared account must also be a local account on the machine
• The shared account credentials must match on both the cloud directory and the local machine

The process is the same in the UI for setting up Elevated Access, so please refer to these articles regarding Elevated Access:

• Shared Account Management
• Elevated Access Assignment
• Access Tokens

Still have questions? Let's take a look at some of the frequently asked questions about Evo Cloud.

FAQ

Question: Does Evo Cloud pass my credentials down to my local machine and users?

Answer: No, these two are separate and must be done manually. Whatever changes you make, either locally or on the cloud, do not sync so be sure to make all changes in both places accordingly.

Question: Can an Evo Cloud Credential Provider on Machine A speak to an Evo Cloud Credential Provider on Machine B, so that I can log-in as users that exist on other machines?

Answer: No. You are only able to login with local users that exist on the machine, as these users are not joined by any domains.