[CE/ORD] Username and other user files

I am trying to figure out how best to streamline ORD resources on the network.

Installing client standards is relatively simple so far - most are following the default ORD directory basics.

I'm concerned about how those clients might try to control user files - configurations, preferences, data files, etc.

My preference is to store as much of the user data as possible on the network - CFG, button menus, accudraw shortcuts, function key menus, GUI-DGNLIBS, everything else I can get away with. This minimizes disruption when someone gets a new computer or we have to uninstall/reinstall software.

I understand that different entities will have different standards and suggest different preferences for their users, but at the end of the day, I want MY function key menu and MY button assignments whether I'm working on Ohio, Indiana or Kentucky.

I imagine it is possible to define those user-file-type variables at our "organization" level and %lock them so that the "organization-civil" standards can't overwrite them.
Can you think of any reasons I SHOULDN'T do that?
Are there any other workarounds to this?

Parents
  • Yes Mary, that should work.

    Are you adding your own company resources (templates, cells, sheets, etc.) to the DOT provided resources? 
    Are they different for the different DOT's?

    An alternative may be to create your own WorkSpace.cfg files, that include the provided DOT cfg files. This way you can include the DOT settings first, then overwrite/append the settings you need to after their definitions. This keeps the DOT provided cfg files in tact so you don't have to re-modify them with every update.

    Another question...
    Are you storing the .upf files on the network too? We've found with one client that this severely affects the performance of MicroStation/ORD. They had to revert back to the default, local location of the .upf file.

    Rod Wing
    Senior Systems Analyst

    Answer Verified By: MaryB 

  • I'm not opposed to keeping the UPF itself local, but I'd prefer to keep as many other user files as possible on our network.

    I was planning to use the "Organization" level for our company standards (which would primarily be add-ons) and use the "Organization-Civil" structure for clients. That's the way it appears that most of our client standards are set up to begin with. But it appears that most of these client setups already have defined "user data" locations, and that is what I want to override with my company CFG. If I can override choice variables in my Organization CFG, I don't have to bother changing the client files.

    I can understand why a client standard might include their standard definition/location for user files, but I'd prefer for people to have their personal settings the same (as much as possible) even while working on projects for different clients.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Reply
  • I'm not opposed to keeping the UPF itself local, but I'd prefer to keep as many other user files as possible on our network.

    I was planning to use the "Organization" level for our company standards (which would primarily be add-ons) and use the "Organization-Civil" structure for clients. That's the way it appears that most of our client standards are set up to begin with. But it appears that most of these client setups already have defined "user data" locations, and that is what I want to override with my company CFG. If I can override choice variables in my Organization CFG, I don't have to bother changing the client files.

    I can understand why a client standard might include their standard definition/location for user files, but I'd prefer for people to have their personal settings the same (as much as possible) even while working on projects for different clients.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Children
No Data