Honestly, I'm a bit baffled by all this back and forth concerning moving the folders from one workstation to another. Even the PTC Tech support answer is a head-scratcher.
There is already built in method for moving a user from one machine to another, allowing him to keep the current workspaces and their contents. It's the Upload command. It was already covered in this thread by Ben and it takes almost no effort at all -- no jumping through hoops; no exporting/importing workspaces; no moving a (sometimes huge) cache folder over the network; no sacrificing a chicken. 😉
User uploads all objects from all workspaces. (Honestly, automatic upload should already be set in your config.pro anyway, IMO.)
User logs into new workstationand launches Pro/E.
User activate appropriate workspace and sees all the work he just saw on the old workstation.
That's the purpose of Upload. Upload exists to allow users to move to different workstations and still see the most up to date contents of their workspaces. I urge everyone to try it out. Amazingly, it really does work as advertised.
Though Ben mentions the settings file, that part is optional. The upload method works with or without copying the settings file.
Keep It Simple Sir!
Good point about workspace size and download. I must admit that the users I've had in the past with 8-10k objects in their workspace simply checked everything in when they where scheduled for a workstation upgrade. On the new workstation they would simply download the objects needed and wait for the system/network to get it done.
I wonder if download would be faster or slower than copying those folders to the new workstation manually, as is being discussed in this thread.
In Reply to Mark Steffke:
I agree Don. But apparently this is a topic with interest that most
admins have or will face. Im suprised to see so many opinions. Our
workspaces are HUGE. Like 20,000 objects in them, and there could be
several that size in the users cache. Configure to order and complete
automation from configure to manufacture brings that situation on. A
re-download can be a little painstaking for the user. So far on any OS
conversions I have not moved the local cache, but I was wondering if I
could help out the users here as well. For a normal user who has a few
hundred abjects and is using pro/E in the typical interactive way to
model objects and assemblies, I wouldn't mess with moving anything.
Engineering System Administrator
The Delfield Company
T 989.775.9215 or 989.773.7981, ext 12484
Integrity, Commitment to Stakeholders, and Passion for Excellence