msconfig.cfg/PCF files for OneDrive

One drive creates an environment variable that points to the one drive location. MicroStation inherits the environment variables as configuration variables.

$(OneDrive) should point to the path and update for each user. (Double check the variable name, it may be different for onedrive for business.

Alternately $(UserProfile) points to the c:\Users\USERNAME path so: $(UserProfile)/Documents/OneDrive should get it too,

Kevin van Haaren said:

it may be different for onedrive for business.

For OneDrive Business its $(OneDriveCommercial)

All,

We'd be interested in any feedback on how well OneDrive works for you in this context.

All,

We'd be interested in any feedback on how well OneDrive works for you in this context.

It worked correctly now. Thanks!

Is it just config files that you are using OneDrive store? I would caution against storing working design files in this environment as we have had issues with users reporting corruption issues.

cfg files are commonly accessed so simultaneous access by multiple users is unlikely but caution should be taken so as to avoid this. 

Could an organization SHARE a workspace environment i.e. Configuration and/or Workspace to a staff members OneDrive?  Will it update automagically when any changes are made to the originating version?

I tentatively suggest the following:

• use OneDrive for Business
• share a configuration to all users as read-only, retaining edit permission only for the admins who maintain it (no exceptions!).
• ensure the users have the OneDrive 'Always keep on this device' option turned on.
• set _USTN_CUSTOM_CONFIGURATION to look at the local OneDrive folder, e.g.: 
  _USTN_CUSTOM_CONFIGURATION = $(OneDriveCommercial)/MyConfig/
• Follow configuration advice elsewhere on communities) to separate projects data locations (including teh DGNWS file y=that needs to be user writable) outside OneDrive.

Any changes made to the source by the admins will be sync'd to the users provided they don't pause OneDrive sync.

As the configs do not change frequently and are generally only edited by one person at at time I would not expect to run into problems.

The compelling advantages are that the config is always accessed from the local OneDrive folders, the updates are automatic and the technology is already present in most cases.

I would be far more cautious about sharing design data. DGN based applications write to file constantly which could clash with OneDrive continuous sync. I imagine this could be the source of the problems mentioned above by David.

As previously mentioned, OneDrive has not been formally tested as a configuration hosting solution so is not formally supported.