The Goverlan Management Suite has now been renamed to Goverlan Reach Console.
Scope Actions are now called Automation and Reporting.
The Goverlan Central Server(GCS) has also been renamed, to Goverlan Reach Server(GRS).
External Device Management and 64-bit Architecture Requirement
The Goverlan Reach Console v9 has all the same functionality as the Goverlan v8 Console, now with the added ability to manage devices on an External network across all modules.
The Goverlan Reach Console v9 is now 64-bit only and cannot be installed on a x86 Architecture (32-bit) machine.
v8 and v9 compatibility
All Goverlan v8 components (GCSv2, v8 Agents, v8 Consoles) do not communicate with the new Goverlan Reach Console v9, v9 Client Agents or the Goverlan Reach Server v3. They are designed to be deployed in parallel to each other, to ensure a seamless transition from one infrastructure to another.
Goverlan Reach Server
Previously “Goverlan Central Server”
The Goverlan Reach Server has all the same functionality of the Goverlan Central Server, with the added features of the Reach Gateway, which provides Reach Consoles the ability to manage any device that is on an External Network.
The Goverlan Reach Server can be installed on the same server as the Goverlan Central Server v2, as they will not interfere with each other. (Consider them to be two different applications.) Optional: Feel free to keep the GCSv2 up and running until the new Goverlan Reach infrastructure has been implemented.
The new Goverlan Reach Server must be installed on a Windows Server 2008 OS or higher.
The new Goverlan Reach Server v3 DNS SRV Record name is _goverlanServer, different from the previous Goverlan Central Server v2 DNS SRV Record name _goverlan.
All Goverlan Central Server policies must be recreated within the new Goverlan Reach Server Policy area. There is no migration path.
Will not be migrated to the new Goverlan Reach Server. Optional: For archiving purposes, you can back up all v8 Auditing logs that are set in the GCS data path, which can be found in your Goverlan Central Server Options. (Default path is C:\ProgramData\Goverlan Central Server)
All Internal Goverlan v9 Consoles and Client Agents now communicate to the Goverlan Reach Server via Port 22100. (Previously 21160 for Goverlan Central Server v2)
Goverlan Reach Console
Previously “Goverlan Management Suite”
The Goverlan Reach Console has all the same functionality of the Goverlan Management Suite, with the added ability to manage any device that is on an External Network, with the same toolsets available for Internal Devices.
The Goverlan Reach Console can be installed on the same machine as the Goverlan Management Suite as they will not interfere with each other. (Consider them to be two different applications.)
Database – (Custom Actions, Software Packages, SureDATA Cache, Script Packages, Favorites, Scope/Action Templates)
The Goverlan Reach Console v9 will update the database schema upon first launch when pointed to a Goverlan v8 database, effectively migrating all database contents to the new console. Goverlan v8 consoles will not be able to communicate with the database after the v9 console has updated the schema. It is advised to simply create a copy of the v8 database, rename it to v9 and point the new Reach Console to the renamed database copy.
Scope Actions – Now Process Automation & Reporting
Scope Actions from Goverlan v8 can be migrated to the Goverlan Reach v9 Automation and Reporting by simply right clicking the Scope Action in v8 >Open Definition Directory, then drag and drop the .GSA scope action files directly from Windows Explorer into the Goverlan Reach Console v9 Automation and Reporting User Interface.
Logged-In Workstation Detection(fastConnect) – The Central Data Repository
The Central Data Repository Path has been deprecated. The Goverlan Reach Server is now required for the functionality of this feature. Once the Goverlan Reach Server is implemented, the server will automatically track all live sessions. Refer to Implementing the Goverlan Reach Server for more information.
Credential Manager Credentials
Due to security improvements, all credentials in the Goverlan Credential Manager must be recreated in the Goverlan Reach Console.
Goverlan Client Agents
Goverlan v8 and v9 Client Agents do not interfere with each other and can be installed in parallel. The Goverlan Agent Manager in the new v9 Console can detect and remove legacy v8 agents, which will appear as an added option to the Remove Agents Action.
Goverlan v9 Consoles now communicate to the Goverlan v9 Client Agent via Port 22000 (Previous default port was 21158 for v8 Console to v8 Client communication).
All GPOs must be re-provisioned with the new Goverlan GPO template located in the C:\Program Files\Goverlan Reach Console 9\GPO Templates directory.
As stated above, all Goverlan Central Server v2 policies must be recreated in the new Goverlan Reach Server.
Stealth Mode(No Visual Notification) Policy
If you have configured the Stealth Mode Policy via Direct Registry or GPO, you will need to update your GPO templates as stated above or refer to this KBA on how to manually configure the Stealth mode policy via Registry as the reg keys have changed.