BCX v3 to v4 Migration

Upgrade

Customers with active support and maintenance can complete the upgrade themselves. Alternatively, if you contract support, we can complete an in-place upgrade for you.

Prerequisites

Version 4 client only supports x64 bit machines and requires .NET 4.7.2 or later. This is standard in Windows 10 build 1803 or later. Previous versions of Windows will require this being included in the master image.

Other Considerations

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 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. By default, BCX Client will look for “bcxmaster” as it did in previous versions.

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 to discuss any custom configuration prior to upgrade.

Client Upgrade

Deployment for the version 4 client is via a new MSI over the previous version 3 client. The Installation Assistant will attempt to 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 should upgrade automatically. This will be visible from Station Information.

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

These 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 manage this for you.

In Place Upgrade

The upgrade process involves running the new Network Management Tools installer MSI on your BCX server, over the top of the existing installation. Your existing installation will be detected and upgraded.

BCX Client v3.0.1.4 or later is compatible with the v4 Server Service to ease migration. Legacy 3.0.1.4 or later clients will continue to function without down time, until the v4 upgrade automatically deploys to them.

Moving the BCX Network Management Tools to New Server

To ensure a smooth transition, Burconix can provide this service for you, please contact your account manager, or support@burconix.com for details.

The following provide a walkthrough of the steps. We do however recommend Burconix complete server migrations for you both to minimize any downtime, and to ensure seamless future upgrades and support.

The DNS entry “bcxmaster” is used by the client to find your BCX Server. Any server name change will require you to update the DNS entry manually.

Any file shares you have on this server, such as packages$ will need to be manually migrated with permissions. Your package tasks commands will likely reference these by server name so may also need updating.

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.

Run BCXDBBackup from your old server, and verify the backup files in C:\DBBackup

Copy the C:\DBBackup from the old server to the new one.

Run Installer on new server as a clean install.

On the Group Policy section, note you will likely not need to import the All Users policy, however we would recommend you link BCX Stations – Install BCX Client Base Installer

At end of the install, select, run BCX Database Restore.

Before you run the restore, first open the settings.xml from C:\Program Files\BCX\Server\settings.xml

Note the new SQLDataSource configured by the installer in the new settings xml.

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 for the new server if required.

Update Server settings.xml, verifying new SQL Instance name

Select the Backup to restore from DB Backup.

Ensure Restart BCX is checked.

Restore Database.

Run BCX Update post install both to install any updates and verify communication.

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

Verify Package Task paths

Open Group Policy Management

Verify Group Policy BCX Stations – Install BCX Client Base Installer and Path

Ensure no old client deployment group polices are still linked/remove any duplicates.

Update any custom permissions on ManagerV4 and Tools\BCXChangePassword shares.

Open DNS Management and check dns for bcxmaster

Restart a Station and Confirm Client Comms

Confirm AV Reporting Comms

Confirm Connector Comms

Run DB Backup to create a backup of the upgraded database.

On Old server Disable Services

BCX Server Service

Microsoft SQL

Shutdown if no longer needed.

Return to Installation Guide