v8 to v9 Migration
Already a client migrating from v8 to v9? Take a look at our Goverlan v8 to v9 Migration Guide.
Goverlan features a sign-on based licensing system that can be managed through the myGoverlan Portal to assist with allocating Goverlan licenses across your team. The myGoverlan portal also has a downloads area to access all Goverlan builds. For more information, please refer to the myGoverlan Portal User Guide
Goverlan Reach Console
Download the latest Goverlan Reach Console from the myGoverlan portal. After installation, the console is designed to be ready for immediate use. However, there are some advanced features that may need further configuration.
- Windows 7 64 bit or Windows Server 2008 and above.
When you launch the Goverlan Console, you will be prompted to log in using your my.goverlan.com ID and password:
- Enter your login ID and password to sign in
- Select free the license when I close the program to acquire a floating license (See Floating vs Fixed in the myGoverlan User Guide.).
NOTE: If you are using Goverlan within a Citrix or TS farm environment, you must select free the license when I close the program to avoid duplicates in license consumption.
Once you have authenticated, Goverlan will allocate a license for your assigned product version. If multiple licenses are available, Goverlan will prompt you to select a license:
By default, license admins are authorized to use all available licenses owned by the account. A standard user will only see the licenses that have been assigned to the user’s account.
NOTE: The name of each license owned can be customized by an account administrator (see Renaming Licenses).
Once you have selected a license, the sign-on process is completed. You will no longer be prompted to sign-in upon starting the software.
Goverlan Reach Client
The Goverlan Reach Client gives Goverlan Consoles the ability to manage any device regardless of its network location.
For Internal Devices, the Goverlan Clients are automatically installed and maintained on a per-needed basis by the Goverlan Consoles. Prerequisites for deploying the Goverlan Client through the Goverlan Console are:
- Port 445 & C$\ADMIN$(Windows Print & File Sharing) for Goverlan Client installation.
- Port 22000 for Goverlan Console to Client communication.
Refer to Configuring Windows Firewall for Goverlan for more information.
For management of External Devices, the Goverlan Reach Server is required with all of the Reach Gateway Services configured. The Goverlan Reach Server contains the Reach Gateway that will proxy all External Device connections to your Goverlan Consoles within your Internal network. For more in-depth information on deploying the client to External Devices refer to Deploying the Goverlan Reach Client.
For devices that have never been on your internal network and are external on a public internet connection, you can utilize the On-Demand feature, which also requires the Reach Gateway Services configured.
Logged-In Workstation Detection(fastConnect)
The Goverlan Console can detect the device that any Active Directory User is currently logged into by username. This feature requires the Goverlan Reach Server to be configured, which logs all live sessions on all devices that have the Goverlan Client installed. The Goverlan Reach Server can be downloaded from the my.goverlan.com portal.
The Goverlan Console and Goverlan Reach Server use two separate SQL databases that have their own functons. Upon installation, both the Console and Server default to their own local file-based SQL databases, with the option to select a Microsoft SQL Server instance. SQL Server 2008 or higher is supported.
- The Govelran Console Database (default name GoverlanV9_DB) – Stores SureDATA, all Goverlan Packages & enables Team Collaboration
- The Govelran Reach Server Database (default name GoverlanGCS) – Stores Global Goverlan Policies, Reach Gateway Service & Auditing
There are several objects in the Goverlan Console that can be shared with other Goverlan operators in your network.
Shareable objects include:
- All objects within the Goverlan Object Manager
- Software Packages
- Script Packages
- External Controls
- Custom Actions
- Action Modules (within Scope Actions or Custom Actions)
- Scope Modules (within Scope Actions)
- Shared Favorites
- Custom Commands in the Goverlan Remote Command Line
With Goverlan Team Collaboration, these objects are stored in the database used by SureDATA and retrieved by anyone on the team. Objects can also be enforced on the team.
Team collaboration has two prerequisites:
- A configured Goverlan SureDATA database(See Understanding SureDATA)
- All Goverlan Consoles set to point to the same SureDATA database (See Applying SureDATA Database Configurations)
Goverlan Reach Server
The Goverlan Reach Server (GRS) is a central authority for all Goverlan services. The Goverlan Reach Server is not required for the Goverlan solution to function. You can donwload the Reach Server from the my.goverlan.com portal, Reach server tab.
The GRS is used as the authoritative source for:
- Policy Distribution – Centrally control Goverlan settings and behavior for all Goverlan Consoles and Clients on your network.
- Reach Gateway Services – The proxy between your External Devices and your internal Goverlan Consoles.
- Auditing – Central store of all user log-on/off events and remote control sessions on devices that have the Goverlan Client installed.
- Logged-In Workstation Detection(fastConnect) – Detect live Windows user login sessions by Active Directory user name.
For your Goverlan Consoles and Clients to be aware of the Goverlan Reach Server a DNS record or GPO must be configured. Additionally, Consoles and Clients communicate directly to the GRS internally via port 22100. For more information refer to Advertising the Goverlan Reach Server.