Step-by-step guide
The administrator documentation provides information on how to set up oneclick™, which Windows configurations might be useful for you, troubleshooting for accessing oneclick™, and what to consider in connection with third-party software.
Follow the step-by-step instructions for setting up oneclick™ for the first time:
Setting up oneclick™
How to give users access to resources in oneclick™
1. Request user licenses
2. Create users
3. Create and connect resources in oneclick™
In oneclick™ you can integrate different types of resources. You decide whether to use on-premises systems from your own infrastructure, configure cloud resources from an existing subscription, or provide external websites and portals.
Select the resource type that fits your environment and follow the corresponding setup steps in the respective section.
- On-premises resources: local servers or workstations within your own infrastructure
- Cloud resources: systems from an existing cloud subscription
- Web resources: websites or portals provided as applications
3.1 Connect on-premises resources
Integrate local servers or workstations from your infrastructure as on-premises resources.
3.1.1 Request app licenses.
3.1.2 Connect your on-premises resources as a destination.
3.1.3 Create a destination pool.
3.1.4 If you would like to access the destinations via the oneclick™ streaming, create an app configuration.
3.1.5 Create app instances for the users who should have access.
3.2 Create cloud resources
Set up systems from an existing cloud subscription as cloud resources.
3.2.1 Request app licenses.
3.2.2 Connect cloud resources as destination.
3.2.3 Create a destination pool.
3.2.4 If you would like to access the destinations via the oneclick™ streaming, create an app configuration.
3.2.5 Create app instances for the users who should have access.
3.3 Connect a web resources
Include websites or portals, either internal pages from your infrastructure or public web applications.
3.3.1 Request app licenses.
3.3.2 Connect your on-premises resources where your internal website is located. This step is not necessary for public web apps.
3.3.3 Create an app configuration.
3.3.4 Create app instances for the users who should have access.
Additional settings
- Creating and assigning roles
- Creating and assigning groups
- Set up policies e.g. for an 2 factor authentication 3.1 Create polic for 2 factor