Hello all,
I am an engineer who has been tasked with upgrading our workspace to newer times. With all new computers shipping with Windows 10 and SS2 no longer being supported, out hand has been forced in upgrading...
I have high design skills but only intermediate knowledge of how MicroStation "innards" works.
We have been using SS2 (MicroStation and PowerDraft) for over 10 years. The workspace/cfg was piece mealed to work from a previous companies set up. In short, it is a mess and > 10 years of chaos....
Current products / setup:
We have 30 or so cadd users. all profiles on the server.
MicroStation SS2 (with InRoads), Power Draft SS2, and PowerInRoads SS2.
All run by changing the MSLocal.cfg to point to a workspace on our "F" drive for the workspace and "P" drive for the actual cadd files
EVERYTHING is stored here.
What we need:
What I know (and don't):
I know that the UPF on the server is the likely cause of speed issues.
I've done some research and have come up with a few paths to follow....I know number 1 is "frowned upon" based on my reading of the Bentley community forums but may be "easiest" to do.
Thanks,
Dylan
Marc,
Thanks for the information, I will take a look at the link you provided tonight.
I will have talk to my boss about SS4 vs Connect series...I am sure there is a reason...I assume we wont want to upgrade that far due to compatibility concerns. Our main client is a state agency who is currently still working in SS2 environment. Im not sure of the compatibility issues with DTMs, ALGs, Roadway templates, ect. I will have to do some digging in the AM. Thanks!!
Correct,
The old workspace from SS2 is very poorly set up and is very buggy. We are trying to start from an "out of the box" install and update to fit a new workspace layout.
I also read on this forum that SS4 workspace and SS2 workspaces don't "play nice"...not sure how true that is though...
Hi Dylan,
Take a look at MicroStation - QuickConfig Standard, that might be a route for you to start setting up a clean V8i Workspace. This uses an mslocal.cfg syntax that avoids any need to work in the 'appl' folder; we recommend not modifying files other than mslocal.cfg in the C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation path.
The techniques in Bear's blogs are equally valid when applied to CFG files in the networked Workspace's Standards folder.
If your current Workspace uses UPF files located on the server, we do recommend locating them locally for maximum stability and performance. If your users roam between machines Windows Roaming Profiles is one solution to keeping their preferences consistent.
Futureproofing... have you considered moving to CONNECT Edition? As you are reviewing your whole configuration this would be the optimum time to migrate!
Regards
Marc
Answer Verified By: DshannonNTM
so SS4 is not running the same workspace as the other versions ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Thanks for the response Tim.
Our "workspace" is a hodgepodge of stuff we don't need. There are toolbars missing, buttons that don't work, etc. I believe this is due to having the workspace on the network that is utilizing older system files. In short, it is a mess and I want to clean it up...
We are "being forced" to upgrade to SS4. SS2 is not compatible with Windows 10...I can say SS2/windows 10 is running on most machines in our office...but doesn't appear to like it.. Bentley will not help trouble shoot any future issues with SS2/Windows10.
We also want to upgrade due to sluggishness of the program. I am currently running a "clean" SS4 off the network and it is lightning fast...
If you are thinking of another way that is easier, I am all ears!! I want this to work, and know how its working so we don't run into this issue again down the road with future upgrades...