Permissions Migration: Intralink 3.4. to 10.0

[ScottPearson]

For all you battle-scarred Intralink Migration Veterans out there....

When migrating from Intralink 3.4 to 10.0, the list of Users comes across but not the Permissions those users had enjoyed in 3.4.

So how did youquickly restore the same Permissions (Access Control) to the same Users to the same Products/Folders when shutting down 3.4 on a Friday and "going live" with 10.0 on a Monday?

There seems to be two major things that would have to happen:

1. A list of Users vs Folders vs Permissions would have be generated somehow in 3.4 to determine which users had which permissions in which folders, and

2. Somehow that info would have to be fed to 10.0 in order to generate the necessary Domain-based ACLs, assign those Domains to their respective (migrated) Products/Folders, then assign Users to the Roles in those Products which have the corresponding permissions (i.e. governed by the Domains).

I am at a lost for how a guy makes that happen across the board...,and "quickly" seems nearly impossible short of some custom scripts written by a high-powered migration implementation consultant.

Note: I realize that Groups can help this effort, but Groups doesn't fill the bill here because the members who have access to any given Product/Folder is seldom comprised of the same set of Users. Such is the nature of our design work.

TIA for sharing your experience!

[MikeLockwood]

You've entered one of the world's greatest puzzles 🙂


- Put everyone in one Windchill group, then assign that group all needed permissions to everything.

- Warn everyone to be careful until you get things figured out.

- Make a test Product from PTC template, then delete ALL of the ACL's from it. Log on a second session as regular user, then put the ACL's back one by one and see their effect. Focus first on: Cabinet, subfolder, EPMDocument, then maybe Promotion Requests if you are using them. Can ignore pretty much everything else until these are set. See attached.

- Study the terminology VERY carefully. It's really different vs. Intralink 3.x.

Address for EPM Documents:

- Create

- Read

- Modify

- Modify content

- Revise

Possibly address for Promotion Requests:

- Create

- Read

Note that "Cabinet" access is needed to see the Products and Libraries where data is stored (which are essentially top level folders). The subfolder object type is one below.

Don't create a bunch of Product and Library contexts from template - all will have zillions of ACL's in them from the template. If they will have common permissions, you are best off creating all of them one level up and creating all from a template that is gutted.

Need to carefully consider your groups also - and whether they are nested. Nesting allow for far less ACL's - each group gets what the parent group gets + more.

[jnelson]

All of that....to manage CAD DATA. UNFREAKING Believable!

From: Lockwood,Mike,IRVINE,R&D [