Before deploying your virtual desktops or apps to production, it is a good idea to create and test them using sandbox servers. The Servers screen lets you access servers in the cloud for which you have administrative rights. You can install, configure, and update a selected server. This will become the base image which will be deployed to the production environment.
In some cases, you may want to make changes directly to a production server. The servers screen enables you to do so. Please use extreme caution and coordinate production changes with Apporto.
Server access is an add-on feature in Apporto. The ability to start and launch servers is dependent on your subscription package. Contact Apporto to set up server access and Windows administrative permissions for your Apporto Admins.
This short guide will show you step by step how to:
View Servers Screen
Using your preferred web browser, navigate to the URL for your Apporto system, for example, “mycollege.apporto.com”, and log in to the system using your Admin credentials.
Click the Servers icon in the Navigation Panel.
The ‘Servers’ screen displays.
The Servers screen shows a list of servers to which your Admin account has access, and provides the following information for each server:
LOCAL NAME: User-defined name of the server (editable field)
SERVER NAME: The unique name for the server
LOCATION: The geographic region where the server is located
INSTANCE STATE: The current operational state of the server
To start a server, click Start
Wait about 30 seconds (AWS) to 2 minutes (Azure) for the server to start.
Once started, the INSTANCE STATE will change from stopped to running. Also, the button will change from Start to Launch. Click Launch to launch the desktop.
Once the desktop is launched, you can install software and configure the desktop. Common changes include installing software, adding desktop shortcuts, changing the time zone, and setting the default browser and/or landing page.
When you have completed configuring the desktop, contact Apporto to move the image to the production auto-scaling environment - or create a base image and Schedule Downtime to replicate the base image to the server farm.
IMPORTANT: Extreme caution should be used when configuring a production server. Active sessions on the server will be interrupted. Also, changes made on one server will need to be replicated to all production servers.