Apparently, just including this directory at the network level is not enough. Not surprising, because I haven't seen anything to redirect to it...
I would like to include some organizational standards (at the network level because I don't plan on doing anything more on the local level than I have to) but I'm not certain how to accomplish that without jumping ahead of system files or redirecting incorrectly.
What would be the best way to do this? I could add an %include somewhere, but at what level would I do that? Before Workspace? During Workspace? Add something to ConfigurationSetup.cfg or WorkSpaceSetup.cfg?
If you're setting and using the _USTN_CUSTOM_CONFIGURATION variable for your networked configuration, MicroStation will use the Organization folder there as the _USTN_ORGANIZATION folder. I've never had any issue with that.
Rod WingSenior Systems Analyst
I didn't even remember that since one of the first things I did was rename Organization folder to our company name which forced me to set _USTN_ORGANIZATION independently. I also rename workspaces and worksets folders which is why i set all the other variables too. whoops.
interesting twist.
so you have all the same configurationsetup.cfgs on all machines pointing to the same workspacesetup,cfg. on the local machine.
But inside the workspacesetup.cfg varies from machine to machine depending on where you need to direct that machine for its organization, workspace and workset.
and since the workspacesetup.cfg can only look at one place at a time, you change this on the fly based on a prechoice from the user ? where are they making this choice (office server they want to use) ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
if my above statement is correct and this is how you are processing your configurations, I did have another question come to mind.
how do you handle the different versions (on one machine) all looking at the same workspacesetup.cfg - which would be pointing them all to the same organization, workspaces and worksets ?
I am currently in discussions (internally) on how to manage the various versions of client data as well as software being used.
# 10.11 R1 %if $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CE - 2022 Release 1" %error You are using $(_USTN_PRODUCT_FULLMARKETINGNAME) # 10.10 R2 %elif $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CE - 2021 Release 2" %echo You are using $(_USTN_PRODUCT_FULLMARKETINGNAME) # 10.10 R1 %elif $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CE - 2021 Release 1" %echo You are using $(_USTN_PRODUCT_FULLMARKETINGNAME) # 10.09 %elif $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer - 2020 Release 3" %error You are using $(_USTN_PRODUCT_FULLMARKETINGNAME) # 10.08 %elif $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer - 2020 Release 2" %error You are using $(_USTN_PRODUCT_FULLMARKETINGNAME) %endif
Tim Hickman said:how do you handle the different versions (on one machine) all looking at the same workspacesetup.cfg - which would be pointing them all to the same organization, workspaces and worksets ?
This shouldn't be too much of a problem any more with ORD. Since ORD 10.9, 10.10, and 10.11 are in different locations. We keep different configurations for each release then point each version to its respective location.
Even for the WorkSets. We separate WorkSet cfg's by version so that only the projects for that version are available for selection.
Throwing MicroStation into the mix, the U17 release with the Configuration Manager helps resolve launching different WorkSpace locations from a single version of MicroStation.
@svancleave - yes I have looked at those variables along with the "version" ones (version ones not reliable)
@Rod - yes I have looked at doing this as well
was just curious on how Kevin was doing it ?
we have some clients with different versions of standards as well as different versions of the software (different projects of course) - so I cant neccessarily base things on client.
maybe I am just over thinking....