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; } } }

TeamSite Install directory permissions

phd

Hello All,

What should be the file permissions of the iw-home directory on Windows operating system?

I have seen that we need to give Everyone Read & Execute permission on iw-home directory for TeamSite to work. Is this correct?
Is there a definitive list of who should have what access on iw-home directory?

Thanks for helping.

Cheers
Pawan

Find more posts tagged with

Comments

Migrateduser

In general, default values for file permissions are used on Windows. There are specific areas where ACLS are updated to enable access for the IW users created by the installer.

Are you experiencing difficulties with permissions, or is this a hypothetical question?

Staff Engineer, Installation Development
Interwoven, Inc.
Moving Business to the Web

phd

I am experiencing problems. On our instance we have Local Administrator group and SYSTEM account FULL CONTROL on the iw-home directory. On testing we found out that some TeamSite GUI commands are not functioning properly. e.g. File Properties. So we added Everyone with Read & Execute permission on iw-home. After that all issues were resolved.

It is somewhat strange to give Everyone rights on iw-home. So I was trying to confirm with others.

BTW we are running TeamSite 5.0.1 on Windows 2000.

Thanks for all the help
Regards
Pawan

Adam Stoller

If memory serves me correctly - I believe you need to ensure that the users of the system (or Everyone) has read/execute permission up through IWHOME in order for operations like File Properties to work within the GUI (there were other functions too). Failure to do so resulted in strange messages in one of the log files (I think it was one of the IWHOME/local/logs/iwui/ logs) stating something like: "...path-to-IWHOME ... IWHOME not found" which seemed strange because it knew the path and the path was there - the problem was that the user logged into TeamSite did not have access to the IWHOME directory and the process was being run "as" them.

--fish
(Interwoven Senior Technical Consultant)