Thank you for your upgrade request.
If you are an existing licensed customer, OR if you are a current evaluator of our software with a previous version of Remote Desktop Reporter or the Remote Desktop Commander Suite already installed:
Important Version 4.8 Upgrade Notes
NOTE 1: Version 4.5 and later now collects relevant RDP login and RDP logon failure events from the event logs running on your RDS session host(s), virtual desktop(s), and Remote Desktop Gateway server(s) (if you use the RD Gateway role). In order for Version 4.5 or later of our software to poll property, if the Windows Firewall is enabled on your server(s) and/or virtual desktop(s), make sure to add a Firewall Exception for Remote Event Log Management on these systems via Group Policy. If you would like to request additional server license(s) to monitor your Remote Desktop Gateway servers, please request a quote from our sales team here.
NOTE 2: Version 4.5 and later now includes a new IP Geolocation feature that shows you where RDP logon failures and logins originate from. If you are upgrading from Version 4 or earlier, and the Remote Desktop Commander database is running on an on-premise SQL Server, it will load this information into your database automatically, and will use approximately 750MBs of storage for the data and the indexes. This process may take 5 minutes or more to complete. If you use Azure SQL for your database, our software will use on-demand, web-based IP geolocation techniques instead.
NOTE 3: In some rare instances, our installation software, Advanced Installer, may not preserve registry values during in place upgrades on 64-bit operating systems. Therefore, as a precaution, please make a note of your global settings in the program before starting the upgrade process.
1.) Open your current version of Remote Desktop Reporter (e.g. the Remote Desktop Reporter Admin Client). Make a note of any global Application Settings you have modified from their defaults, such as polling interval, database maintenance schedule, email settings, etc. Then stop the Remote Desktop Reporter service and close the Remote Desktop Reporter Admin Client.
2.) If the Remote Desktop Reporter Service is currently running, stop it, and also close the Remote Desktop Reporter program before proceeding.
3.) Start the new install package (rdcommandersuitenoprereq.exe)
4.) When the installation finishes, it will automatically launch the Remote Desktop Reporter Admin Client.
5.) If you are taken back into the Initial Setup wizard (NOTE: this is rare), reenter your domain/workgroup, service account information, and simply select the appropriate “Use the existing Remote Desktop Reporter database…” option in the Configure Database area, depending on whether or not you previously were using a local SQL Server Express instance, or a dedicated (remote) full SQL Server installation. Then click Check and Finalize Configuration. In the main program, complete the upgrade by changing back any of the Application Settings you made a note of in Step 1 above. All of your previous scheduled reports, filters, and monitored computers will remain as they were prior to the upgrade.
6.) If you are not taken into the Initial Setup wizard, your prior application settings were preserved automatically during the upgrade. To finish the upgrade process, reconfigure your service account to use the account you had been using prior. Reenter that account name, reenter the account password, and then stop/restart the service.
7.) After upgrading, you can also upgrade any installations of the Remote Desktop Commander Client that other users are running on their workstations or as a published RemoteApp. The latest version of the Remote Desktop Commander Client installer will be located under \Program Files (x86)\RDPSoft\Remote Desktop Commander\ClientInstaller\rdcommanderlite.exe … To upgrade clients, run this installer on top of the previous version of our client on any machines that need the upgrade.
If you are installing the latest version of our software on a new system:
If you need to migrate licensing, or other configuration parameters, please start a new support ticket here.