Connect products while Work from Home

Would recommend you review the following articles:

https://communities.bentley.com/products/microstation/w/microstation__wiki/47474/working-from-home-with-microstation#Q9

https://communities.bentley.com/products/microstation/w/microstation__wiki/47877/using-microstation-in-azure-windows-virtual-desktop

https://communities.bentley.com/products/microstation/w/microstation__wiki/47983/teamviewer-remote-desktop-with-microstation

Accessing files to a remote server and through a VPN issues are bound to occur if you continue to use this method I would strongly recommend you enable file backup creation.

David,

Thank you for the very useful information.

I was actually inquiring more specifically on what everyone is doing with defining _USTN_CUSTOM_CONFIGURATION when the staff is split between WFH & working in the office.  In the "normal" world, we just push out ConfigurationSetup.cfg and WorkspaceSetup.cfg to each device and everyone is pointed in the right direction.  However, in our scenario, its seems a bit kludgy to have to manually manage those two files for office vs remote environments and to even rely on the staff to manage that.

I have read other posts where admins wrote an IF/ELSE statement that checks for an office network drive and defines _USTN_CUSTOM_CONFIGURATION to be corporate or local depending on the result of the check.  That seems more reasonable to do, except VPN users will be mapped to the network while connected to the VPN too, so when it checks, the result will still be true.

Project file access is another issue and much harder to remedy.  Most of the staff have adequate internet connections that allows them to access the files directly over the VPN, some others do not.

Thanks again

Chuck

David,

Thank you for the very useful information.

I was actually inquiring more specifically on what everyone is doing with defining _USTN_CUSTOM_CONFIGURATION when the staff is split between WFH & working in the office.  In the "normal" world, we just push out ConfigurationSetup.cfg and WorkspaceSetup.cfg to each device and everyone is pointed in the right direction.  However, in our scenario, its seems a bit kludgy to have to manually manage those two files for office vs remote environments and to even rely on the staff to manage that.

I have read other posts where admins wrote an IF/ELSE statement that checks for an office network drive and defines _USTN_CUSTOM_CONFIGURATION to be corporate or local depending on the result of the check.  That seems more reasonable to do, except VPN users will be mapped to the network while connected to the VPN too, so when it checks, the result will still be true.

Project file access is another issue and much harder to remedy.  Most of the staff have adequate internet connections that allows them to access the files directly over the VPN, some others do not.

Thanks again

Chuck

Hi Charles,

You can include an If/Else statement in the [General] section of ConfigurationSetup.cfg. You may also be able to put statements currently in your WorkSpaceSetup.cfg in there too.

Once _USTN_CUSTOM_CONFIGURATION has set _USTN_CONFIGURATION to point to the Custom Configuration I wouldn't expect a WorkspaceSetup.cfg on the local drive to be read unless it was specifically included?

Note that currently we overwrite the ConfigurationSetup.cfg with new installs but are looking at modifying that behaviour (Enhancement 854340).

Currently I am experimenting with Custom Configurations located in OneDrive folders. Windows has system variables that resolve to the user's local OneDrive root folder that handle any managed or individual changes to that location, OneDriveCommercial being most relevant (there is also OneDriveConsumer). This is not something we have formally tested or certified, but looks promising. Use of OneDrive has been discussed in other posts here so there may be other current experiences to share.