Difference between revisions of "BCX v3 to v4 Migration"
Jump to navigation
Jump to search
| (38 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | ==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=== | ===Prerequisites=== | ||
| − | Version 4 client only supports x64 bit machines and requires .NET 4.7.2 or later | + | 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 | ||
| − | ===Client | + | <font color=red> |
| + | ====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. | |
| + | </font> | ||
| − | + | ====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== | ==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. | |
| + | <!-- | ||
===Considerations=== | ===Considerations=== | ||
| − | The DNS entry “bcxmaster” is used by the client to find your BCX Server. | + | The DNS entry “bcxmaster” is used by the client to find your BCX Server. If building the new server alongside, any server name change will require you to update the DNS entry manually to switch over. |
| − | Any file shares you have on this server, such as packages$ or Apps will need to be manually migrated with permissions. Your package tasks commands | + | Any file shares you have on this server, such as packages$ or Apps will need to be manually migrated with permissions. Your existing shortcuts and package tasks commands will likely reference by the old server name so may also need updating. |
| − | Check for other connectors installed locally on the old server such as BCX Exchange Connector/File Server Connector/AV Reporting. | + | Check for other connectors installed locally on the old server such as BCX Exchange Connector/File Server Connector/AV Reporting Client. |
| − | Check Add Remove Programs to see if anything else installed on the BCX server that might need consideration. | + | Check Add Remove Programs to see if anything else installed on the BCX server that might need consideration when decommissioning the old server. |
Check and make a note of custom non/standard permissions on ManagerVx, and Tools\BCXChangePassword as these will need to manually set on the new server. | Check and make a note of custom non/standard permissions on ManagerVx, and Tools\BCXChangePassword as these will need to manually set on the new server. | ||
| Line 77: | Line 94: | ||
===Technical Walkthrough=== | ===Technical Walkthrough=== | ||
| − | The following | + | The following provides a walkthrough of the steps for technical users only. |
| + | |||
| + | '''While the following has been made public, we recommend a Burconix Engineer completes any server migrations, both to minimize any downtime, and to ensure seamless future upgrades and support, as there will likely be other services and shares running from your server.''' | ||
Run BCXDBBackup from your old server, and verify the backup files in C:\DBBackup | Run BCXDBBackup from your old server, and verify the backup files in C:\DBBackup | ||
| Line 89: | Line 108: | ||
Install SQL Express 2019, and include Studio Manager to make any manual package path changes easier. | Install SQL Express 2019, and include Studio Manager to make any manual package path changes easier. | ||
| − | + | Browse to Existing Packages Location | |
| − | On the | + | On the DNS pane, you can allow DNS resolution mismatch to continue, as it will be pointing at your old server while you get the new one setup. |
| − | + | On the Group Policy section, note you will likely NOT need to Link the "BCX Users - All Users" policy, however we would recommend you do link "BCX Stations – Install BCX Client Base Installer v4". | |
| − | Before you run the restore, first open the settings.xml from C:\Program Files\BCX\Server\settings.xml | + | At end of the install, uncheck Launch BCX Manager, and instead check Launch BCX Database Restore Tool. |
| + | |||
| + | Before you run the restore, first open the newly installed settings.xml from C:\Program Files\BCX\Server\settings.xml | ||
Note the new SQLDataSource configured by the installer in the new settings xml. | Note the new SQLDataSource configured by the installer in the new settings xml. | ||
| Line 101: | Line 122: | ||
Next copy the latest settings.xml from C:\DBBackup over the top of C:\Program Files\BCX\Server\settings.xml, open in Notepad and update the SQLDataSource using notepad for the new server instance name if required. | Next copy the latest settings.xml from C:\DBBackup over the top of C:\Program Files\BCX\Server\settings.xml, open in Notepad and update the SQLDataSource using notepad for the new server instance name if required. | ||
| − | + | Now using the BCX Database Backup and Restore Tools, Ensure Restart BCX is checked. | |
| − | + | Click Restore Backup, Select the Backup to restore from DB Backup. | |
| − | + | Run BCX Update shortcut from Desktop post install both to install any updates and verify communication. | |
| − | + | Configure Proxy settings as required, settings.xml in ProgramData | |
| + | |||
| + | "C:\Program Files\BCX\SetupWizard\BCXInstallationAssistant.exe" importupdateshortcuts | ||
Run BCX Manager from Desktop Shortcut | Run BCX Manager from Desktop Shortcut | ||
| − | If upgrading from a previous version, update any shortcuts such as BCX Manager V3 to the new location. \\BCXSERVERNAME\ManagerV4$\BCXManagerLauncher.exe | + | If upgrading from a previous version, check and update any shortcuts such as BCX Manager V3 to the new location. \\BCXSERVERNAME\ManagerV4$\BCXManagerLauncher.exe |
Also check BCX Change Password Shortcut | Also check BCX Change Password Shortcut | ||
| − | Verify Other Shortcuts if Apps share was hosted, | + | Verify Other Shortcuts if Apps share was hosted |
| + | |||
| + | Check for list using old server name using follow statement, then update using Shortcuts in BCX Manager. | ||
| + | |||
| + | SELECT Name,Description,TargetPath,Arguments,WorkingDirectory,TargetPath64,Arguments64,WorkingDirectory64 FROM Shortcuts WHERE TargetPath LIKE '\\bcx%' | ||
Verify Package Task paths by exporting as CSV. | Verify Package Task paths by exporting as CSV. | ||
| + | |||
SQL Update | SQL Update | ||
| − | UPDATE Packages | + | |
| + | UPDATE Packages SET PackagePath=REPLACE(PackagePath, 'oldname', 'newname'); | ||
| + | |||
| + | UPDATE PackageTypes SET DefaultLocation=REPLACE(DefaultLocation, 'oldname', 'newname'); | ||
Open Group Policy Management | Open Group Policy Management | ||
| − | Verify Group Policy BCX Stations – Install BCX Client Base Installer | + | Verify Group Policy |
| + | |||
| + | BCX Stations – Install BCX Client Base Installer | ||
Ensure no old client deployment group polices are still linked/remove any duplicates. | Ensure no old client deployment group polices are still linked/remove any duplicates. | ||
Update any custom permissions on ManagerV4 and Tools\BCXChangePassword shares. | Update any custom permissions on ManagerV4 and Tools\BCXChangePassword shares. | ||
| + | |||
| + | Migrate any BCXChangePassword settings.xml from old server. | ||
Open DNS Management and check dns for bcxmaster | Open DNS Management and check dns for bcxmaster | ||
| Line 137: | Line 172: | ||
Confirm Connector Comms | Confirm Connector Comms | ||
| − | Run DB Backup | + | Remove old connectors from File - Settings in Manager. |
| + | |||
| + | Start - BCX Database Backup to Run DB Backup of the upgraded database. | ||
| − | On Old server Disable BCX Services | + | On Old server Stop and Disable BCX Services |
BCX Server Service | BCX Server Service | ||
| + | |||
BCX...Connector | BCX...Connector | ||
| + | |||
SQL Server (BCXSQL) | SQL Server (BCXSQL) | ||
| − | Remove old packages$ shares entry point. | + | Disable BCX Tasks in Task Scheduler |
| + | |||
| + | Computer Management | ||
| + | |||
| + | Remove old packages$ shares entry point and Apps if there. | ||
| − | + | Remove ManagerV3 share and BCXChangePassword and Client Share | |
| + | Shutdown Server if no longer needed. | ||
| + | --> | ||
Return to [[BCX_Network_Management_Tools_Installation_Guide|'''Installation Guide''']] | Return to [[BCX_Network_Management_Tools_Installation_Guide|'''Installation Guide''']] | ||
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