user pref file

Question

Hi, 
 how to make my personal.ucf is written in the same directory as my personal...UPF (on the network) 
 I've created: 
 _USTN_HOMEROOT = $(_USTN_ORGANIZATION)USERS/$(USERNAME)/$(computername)/ 
 _USTN_LocalUserAppDataPath = $(_USTN_HOMEROOT)/ 
 
 but still the personal.ucf is written to: 
 C:\.....\AppData\Local\Bentley\OpenBuildingsDesigner\10.0.0\prefs (on the computer where OBD is installed) 
 what other variable do I have to change too 
 
 regards, 
 Rik

Duncan Gammie · Answer

Currently, you can't. this is restricted. Even setting the _USTN_USERCFG = variable has no effect. It's annopying

Marc Thomas · Answer

You should find that it is possible to relocate the UCF in Update 5 (this was a platform change first available in MicroStation). I have not checked this in OpenBuildings Designer yet but will do so soon. Previously every file other than the UCF could be relocated. 
 Note that we continue to recommend that user preferences are always stored on the local drive, using IT system functions to enable roaming.

Marc Thomas · Answer

Hi Rik, 
 To change the location of all user preferences files including the UCF try the following: 
 
 Create prefs folder in desired location containing a .UCF file, it can be empty or pre-populated. For example: "D:\OBD_User\prefs\personal.ucf" 
 Add the following configuration statements to WorkSpaceSetup.cfg: %undef _USTN_USERCFG _USTN_USERCFG = $(_USTN_HOMEPREFS)/Personal.ucf _USTN_HOMEROOT = D:/OBD_User/ 
 
 The reason for using WorkSpaceSetup.cfg is that file is in the Custom Configuration so Bentley's system files are not modified. The %undef _USTN_USERCFG statement is essential to clear the default value. 
 Obviously choose your own paths. 
 As previously mentioned we strongly recommend that user preferences are stored on the local drive and that relocation of preferences files is carried out with the support of IT systems that synchronize the local instance with a server copy, Windows Virtual Profiles for instance.

Marc Thomas · Answer

HI Sean, 
 Yes, I can confirm that. There is some concern internally that we may see problems caused by UPFs being messed up by slow networks or other causes hence our continuing recommendation. 
 Please could you share more details about your solution with us?

Marc Thomas · Answer

Rik, 
 It looks like OneDrive has potential to be a solution for roaming user prefs, this works in my initial teat at least, needs some more research to check for unforeseen consequences before firming up on it though: 
 _USTN_HOMEROOT = $(OneDriveCommercial)/OBD_User/ 
 OneDriveCommercial is a Windows environment variable that points to the OneDrive for Business root folder; OneDriveConsumer points to the consumer root folder. 
 There may be a 'gotcha' if OneDrive file sync clashes with MicroStation file locking so slightly wary of this at the moment. 
 Credit to Kevin van Haaren for pointing out these variables over in the Product Administration Forum .

Marc Thomas · Answer

Sean, 
 The configuration sequence is such that _USTN_USERCFG is defined early on in the system configuration files. We have been maximising the separation between system and user editable CFGs so that all user configuration takes place after "C:\ProgramData\Bentley\OpenBuildings CONNECT Edition\Configuration\ConfigurationSetup.cfg", this is why the %undef is required. 
 There are ongoing discussions on this topic but I doubt if we will see significant change in the immediate future. Any changes that we make to the initial start up system CFGs, msconfig.cfg for instance, have to work with all of the other applications based on the (MicroStation) Power Platform so cannot be made lightly.

Marc Thomas · Answer

Sean, I'm completely with you on this. 
 The previous situation was that this config could be redefined by modifying mslocal.cfg or other files in the system folders. This required good understanding of the configuration syntax and often complex use of that syntax. A large portion of our user base lacks that understanding or has not interest in learning it so we are working towards user-friendly solutions while doing our best to ensure that the more complex environments and knowledgeable people like you are still able to tune and protect their systems. 
 One of the objectives of the CE configuration changes is to have a clear distinction between what is installed with the application which should be left alone and the user's configuration that can be customised as required and protected appropriately. In terms of your approach essentially what has changed is the point at which your hta files start to take effect.