The BCM agent runs using the "System" account, therefore it won't be able to write in the connected user's registry keys (e.g., HKCU) or in "C:\Documents and settings", "C:\Users" and the user's variables cannot be used (e.g., %USERPROFILE%). To perform any of these changes, the program needs to be executed as the connected user.
In order to set this there are two options:
Option 1:
- Set the option "Run as Current User" in an assignment schedule:
- Assign the device (group) then click on "No" when prompted to use the default schedule.
- Edit the assignment schedule to select "Run as current user".

- Click on ok, then right click on the device/device group assignment and click on "Activate Operational Rule".
The operational rule or the package will then be assigned to the device(s) or device group(s).
Option 2:
- Publish the package to a device or to the user and have the package installed by the current user of the device.
More information on how to publish a package to a user or a device can be found in the documentation or in section 6B of the KA 000121358.
Note:
- User variables and system variables like %USERPROFILE% must be mentioned in the following format in operational rule steps and packages: ${USERPROFILE} , Using "%" will not work.
- A prerequisite is that the user of the device needs to have the write permissions to the folder .../Client/data/CustomInventory.