BCX v3 to v4 Migration

BCX Client

At the time of writing, BCX Client v3.0.1.4 is compatible with the v4 Server Service to ease migration.

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.

Installation

Deployment for the version 4 client will require you push a new MSI over the previous version 3 client. This must be done via Group Policy and not through BCX. We would recommend you simply unlink your current “Stations – Install BCX Client” policy and create a brand-new policy in its place “Stations – Install BCX Client v4 Base Installer” and link to your Stations OU.

Note if you have multiple BCX server instances in the same domain, you will need to create a MST transform file to tell BCX Client which instance to talk to. By default, BCX Client will look for “bcxmaster” as it did in previous versions. We would suggest you contact support if you need assistance with this, however details are here.

The version 4 MSI will only need to deployed once. Future client upgrades will come down automatically from your local BCX Server as they did before, without the need to redeploy MSI.

File locations

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

C:\Users\%username%\AppData\Local\BC

Custom client settings

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.

All custom configuration for BCX Client must now be completed via BCX Manager using Client Policies.