Skip to main content
M
msteffke15-Moonstone
15-Moonstone
January 10, 2012
Question

Moving WC9.1 workspaces from an XP to Win7

  • January 10, 2012
  • 15 replies
  • 14056 views
I need to move several XP users over to Win764. Is it safe move the
users local windchill cache from XP to Win7?
Do you just grab the PTC folder from Application data folder, and paste
in into the users appdata folder?
Is there a best practice to follow?



These are the workstations I started the discussion about last month
over the Solid State drives. So I have not forgotten about a report, I
will let you know if there is a perceptal speed increase. Just
unpacking the first one.


    15 replies

    Show previous replies
    D
    DonSenchuk12-Amethyst
    12-Amethyst
    January 11, 2012

    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.

    Mark Steffke
    Engineering System Administrator
    The Delfield Company
    Manitowoc Foodservice
    T 989.775.9215 or 989.773.7981, ext 12484
    Integrity, Commitment to Stakeholders, and Passion for Excellence

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    January 11, 2012
    After reading the other responses, I think the upload to the server on all saves will do what you want automatically.
    Nice tip about separating the CACHE from the ROOT folder. Have to try that.
    The only time you need to move the .settings folder is if your users have local searches or view configurations set. If all Windchill settings are OOTB (or system administrated) then you don't need this folder.

    I agree that all Pro/E config.pro files should have the upload on save set on. Saves a lot of time.

    PTC's method would ONLY be needed IF you had a lot of new content that had never been checked in and the files had not been uploaded. An admin cannot run the command on someone else's workstation unless they log in as that user to the OS and Windchill.

    Large workspaces will always be a problem. Keeping configurations in workspaces, doesn't seem like intended functionality. As I mentioned the system has to check all those workspaces and files. Cleaning up workspaces is a pet peeve of mine. I have seen too many corrupt workspaces where data was lost due to some user action. Keeping the number of workspaces down and minimal files in the workspaces will improve system performance.

    Always good to have discussions to confirm/question pending actions.

    Thank you,

    Ben H. Loosli
    USEC, INC.
    L
    Lohbauer1-Visitor
    1-Visitor
    January 11, 2012
    This has been a very interesting thread. We recently migrated from IntraLink 3.4 to PDMLink 9.1 and we had users check everything in and delete the workspaces. Or for those who had issues that couldn’t be remedied in time, or just waited til the last second to address it export to their data to hard drives for post-migration re-import.

    I’m down with Ben on the auto upload on save. It requires more frequent vault maintenance, but it’s worth it to make sure things end up in the server-side of the workspace.

    BTW the config.pro option is: dm_uploaded_objects = YES

    Best of luck,

    Bob Lohbauer
    D
    davehaigh13-Aquamarine
    13-Aquamarine
    January 11, 2012
    Actually there are two options depending on how your system is set up. And at least for WF4 the setting isn’t YES, it’s automatic.

    dm_secondary_upload AUTOMATIC
    dm_upload_objects AUTOMATIC

    [cid:image005.jpg@01CCD049.A59AAFF0]


    David Haigh
    L
    Lohbauer1-Visitor
    1-Visitor
    January 11, 2012
    David is right, we use automatic, ,my bad.
    Terms & ConditionsAccessibility statement