nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OS group for Workarea level permissions in TS 6.7.2

dazzlad

All:

I am using TeamSite 6.7.2 SP2 on Windows Server 2003 R2 (SP2).

I am migrating a TeamSite server from one physical machine to another.
The OS and software versions match.

When I add an OS group to the Workarea permissions - Using the "Add permissions" Button in the GUI I can't manipulate files in the backing store (via the mount - Y:\) despite the fact the OS group has been given full control. I am granting "Full control" to the group - I am able to navigate to the Workarea but not into sub folders, nor am i able to create new files or folders.

When I add a user (rather than a group) to the permissions writing files to Y:\ works as expected. Additionally if I place the OS group inside a TeamSite group and give the TeamSite group permissions to the area it works too.

The old server works with OS groups granted permission over the Workareas - so it is possible.

Is there a configuration I need to set somewhere?

I'm not able to migrate away from OS groups at this time as the custom codebase reads from these OS groups.

I've already identified that a workaround exists where I can wrap my OS groups in TeamSite groups but this isn't ideal.

Any suggestions would be much appreciated.

Thanks.

Find more posts tagged with

Comments

nipper

What are the settings for workarea_security and branch_security in iw.cfg ?

So you have group darrens_friends on oldserver that owns a WA and copied the backingstore to newserver and made the same group (which being DOS has a different SID and is a different group).This is why domain groups are suggested.

Have you run iwidmap to remap the old group to new group ?

dazzlad

What are the settings for workarea_security and branch_security in iw.cfg ?

So you have group darrens_friends on oldserver that owns a WA and copied the backingstore to newserver and made the same group (which being DOS has a different SID and is a different group).This is why domain groups are suggested.

Have you run iwidmap to remap the old group to new group ?

Thanks for the reply:

I haven't migrated the backing store - I've created all branches, areas and groups manually on the new server.

Can you point me at the docs for workarea_security and branch_security?

nipper

in the [iwserver] section of iw.cfg

# Do you want to prevent users from seeing the names of branches or workareas
# for which they have no read permissions? ("on" means don't let them see.)
branch_security=off
workarea_security=off

Is this the group that shares the workarea in the workarea properties ?

PaulW

Are the OS groups, local groups or domain groups?

Are you saying that everything is working through the web interface? If youve got TeamSite configured the same, I would think it's some difference in how the boxes are configured.

Do they both have the same group policies applied? is the new box a member of the domain yet?

Are the services running as the same user on both boxes?

Frederik

check for any differences in the iw.cfg of both systems.

I remember reading (edit: in 7.2 docs) about several settings in iw.cfg that determines what type of group will be sync'd (universal, domain. ...) and other settings related to coexisting with a Windows Active Directory.

HTH