Difference between revisions of "BCX v3 to v4 Migration"
| (10 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
Version 4 client only supports x64 bit machines and requires .NET 4.7.2 or later which is standard in Windows 10 build 1803 or later. Previous versions of Windows will require .NET 4.7.2 being included in the master image. | Version 4 client only supports x64 bit machines and requires .NET 4.7.2 or later which is standard in Windows 10 build 1803 or later. Previous versions of Windows will require .NET 4.7.2 being included in the master image. | ||
| + | |||
| + | We recommend adding a path exclusion in your AV solution for "C:\Program Files\BCX", as some products may falsely report/quarantine BCX components. | ||
====Client Upgrade==== | ====Client Upgrade==== | ||
| Line 23: | Line 25: | ||
C:\ProgramData\BCX | C:\ProgramData\BCX | ||
| + | <font color=red> | ||
====Custom Client Settings==== | ====Custom Client Settings==== | ||
| Line 28: | Line 31: | ||
If you are using custom client settings.xml, this will not be honored in the v4 client, you should set the desired features using BCX Manager, Client Policy, before you deploy the v4 Client MSI. | If you are using custom client settings.xml, this will not be honored in the v4 client, you should set the desired features using BCX Manager, Client Policy, before you deploy the v4 Client MSI. | ||
| + | </font> | ||
====Other Server Connectors and AV Information Client==== | ====Other Server Connectors and AV Information Client==== | ||
| Line 47: | Line 51: | ||
==In Place Upgrade (recommended)== | ==In Place Upgrade (recommended)== | ||
| − | The upgrade process involves downloading and running the new Network Management Tools installer MSI | + | The upgrade process involves downloading and running the new Network Management Tools installer MSI on your exiting BCX server. |
| + | |||
| + | Any stations with BCX Client v3.0.1.4 or later will continue to function without down time, until the v4 upgrade automatically deploys to them, usually on a station reboot. | ||
Your existing installation will be detected and upgraded as you walk through the upgrade wizard. | Your existing installation will be detected and upgraded as you walk through the upgrade wizard. | ||
| − | + | The latest upgrade for your BCX server is located at https://secureupdate.burconix.com/pub/BCXNMTServerSetup/ | |
| − | + | On completion of your upgrade, we recommend you complete the following checks. | |
| + | |||
| + | ===== Post Update Checks ===== | ||
| − | + | * Open BCX Update from your server Desktop and confirm connectivity/complete pending updates | |
| + | * Open Start - BCX Database Backup, Create Backup and confirm a database backup is taken to C:\DBBackup | ||
| + | * Open BCX Manager v4 and Check/Update Shortcut paths if required for BCX Manager and BCX Change Password under Shortcut Management tab (search "BCX") | ||
| + | * Configure any required Client Policies for custom settings from File - Client Policies | ||
| + | * Check Group Policy Management for the new "BCX Stations – Install BCX Client Base Installer v4", and that any older v2/v3 BCX Client MSI's are no longer linked to any OUs. | ||
| + | * Reboot some stations, and confirm they upgrade to v4, this will be visible from Station Information - Choose Filter, Client Latest | ||
| + | * Confirm connector services are updating from File - Settings - Connectors (it may take up to an hour before the auto update is triggered). | ||
| + | * Confirm a path exception is added to AV solution for "C:\Program Files\BCX". | ||
| + | Contact support if you have any queries. | ||
==Moving the BCX Network Management Tools to New Server== | ==Moving the BCX Network Management Tools to New Server== | ||
| − | We recommend a Burconix Engineer completes any server migrations, both to minimize any downtime, and to ensure seamless future upgrades and support | + | We recommend a Burconix Engineer completes any server migrations, both to minimize any downtime, and to ensure seamless future upgrades and support. There will likely be other services and shares running from your server, as well as paths to consider if the server name is to be changed. Please contact your account manager to discuss further. |
<!-- | <!-- | ||
Latest revision as of 13:22, 6 May 2022
Contents
Upgrading the BCX Network Management Tools
Please contact support to arrange for us to remote in and complete an in-place upgrade for you. We can discuss any specific configurations you have as required prior to the upgrade.
Alternatively, customers can complete an in-place upgrade themselves by downloading the Installation Assistant and running it on your exiting BCX Server.
Prerequisites
Version 4 client only supports x64 bit machines and requires .NET 4.7.2 or later which is standard in Windows 10 build 1803 or later. Previous versions of Windows will require .NET 4.7.2 being included in the master image.
We recommend adding a path exclusion in your AV solution for "C:\Program Files\BCX", as some products may falsely report/quarantine BCX components.
Client Upgrade
Deployment for the version 4 client is via a new MSI over the previous version 3 client. The Installation Assistant will unlink your current “Stations – Install BCX Client v3” policy and create a new policy in its place “BCX Stations – Install BCX Client v4 Base Installer” and link to your Stations OU.
Existing version 3 clients will upgrade automatically. This will be visible from Station Information using the Filter - Client Latest.
The new client components will now be deployed to:
C:\Program Files\BCX
Settings, configurational data and logs are now stored under:
C:\ProgramData\BCX
Custom Client Settings
All custom configuration for BCX Client must now be completed via BCX Manager using Client Policies.
If you are using custom client settings.xml, this will not be honored in the v4 client, you should set the desired features using BCX Manager, Client Policy, before you deploy the v4 Client MSI.
Other Server Connectors and AV Information Client
Connectors will update automatically as required. Some legacy connectors will continue to function without updates, such as those for customers running older versions of Exchange server. The Installation Assistant will automatically upgrade connectors as required.
The legacy tool BCXMISExtractor is not currently part of version v4, however the legacy v3 tool can still be used with BCX MIS Compare. Please contact support prior to upgrade if you are using this.
Other Considerations
If running BCX Client on RDS servers, you may need will likely need create a custom client policy prior to upgrading the client to ensure the correct features/client behavior is enabled/disabled as required.
If you have any custom permissions on your ManagerV3 or Tools\BCXChangePassword folder share, these will need to be manually added to the new folders post upgrade.
If you have multiple BCX server instances in the same domain, you will need to create client policies to tell BCX Client which instance to talk to and assign these to the correct Organizational Units. By default, BCX Client will look for DNS entry “bcxmaster” as it did in previous versions.
Please contact support prior to upgrade to discuss any custom configuration prior to upgrade.
In Place Upgrade (recommended)
The upgrade process involves downloading and running the new Network Management Tools installer MSI on your exiting BCX server.
Any stations with BCX Client v3.0.1.4 or later will continue to function without down time, until the v4 upgrade automatically deploys to them, usually on a station reboot.
Your existing installation will be detected and upgraded as you walk through the upgrade wizard.
The latest upgrade for your BCX server is located at https://secureupdate.burconix.com/pub/BCXNMTServerSetup/
On completion of your upgrade, we recommend you complete the following checks.
Post Update Checks
- Open BCX Update from your server Desktop and confirm connectivity/complete pending updates
- Open Start - BCX Database Backup, Create Backup and confirm a database backup is taken to C:\DBBackup
- Open BCX Manager v4 and Check/Update Shortcut paths if required for BCX Manager and BCX Change Password under Shortcut Management tab (search "BCX")
- Configure any required Client Policies for custom settings from File - Client Policies
- Check Group Policy Management for the new "BCX Stations – Install BCX Client Base Installer v4", and that any older v2/v3 BCX Client MSI's are no longer linked to any OUs.
- Reboot some stations, and confirm they upgrade to v4, this will be visible from Station Information - Choose Filter, Client Latest
- Confirm connector services are updating from File - Settings - Connectors (it may take up to an hour before the auto update is triggered).
- Confirm a path exception is added to AV solution for "C:\Program Files\BCX".
Contact support if you have any queries.
Moving the BCX Network Management Tools to New Server
We recommend a Burconix Engineer completes any server migrations, both to minimize any downtime, and to ensure seamless future upgrades and support. There will likely be other services and shares running from your server, as well as paths to consider if the server name is to be changed. Please contact your account manager to discuss further.
Return to Installation Guide