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

How to apply a TeamSite group on deployed directories and files in reverse deployment

Surender

Hi,

I am using TeamSite 6.7.1 SP1,OD Base 6.2.1.0.0 and OD Receiver 6.0.2.1.0

I am doing a reverse deployment and got the following error

ERROR: Unknown group .
is a TeamSite group.

Please let me know if someone has already come across the same situation and resolved it

OD Config file:
[html]

[/html]

Find more posts tagged with

Comments

Adam Stoller

Are the Base Server (reverseTarget) and the Receiver (reverseSender) Unix or Windows based? (it looks like Unix - but I it's best to verify)

Assuming Unix based - is group "groupid" (

) a valid OS or LDAP group on both servers?

Are both Base Server and Receiver running as 'root' or are they running as 'non-root'?

Surender

Hi Ghoti,

Thanks for your reply. Answers to your questions
The both base and receiver on unix platform.
"groupid" is a valid TeamSite group, but not a OS level group.
Both servers are running as 'root'.

Thanks

ISCBorisB

Hi Ghoti,

Thanks for your reply. Answers to your questions
The both base and receiver on unix platform.
"groupid" is a valid TeamSite group, but not a OS level group.
Both servers are running as 'root'.

Thanks

As far as I know Permission Rules Group Attribute should indicate valid Unix Group name, not TS Group.

Check what Unix User/Group assets really have for the desired TS Group and assign them.
Then take care of TS Groupinfg sepatrately, perhaps as added WF step or Deployment script
calls

Surender

Hi All,

What I found was the reverse deployment is not applying the group even though I mentioned a valid OS group in Permission rules, instead it is by default applying "nobody" group on all files and directories.

Can some one tell me what's wrong here..
Thanks

Migrateduser

Quick update: Changing the reverse target to a filesystem group from a TeamSite group solved this. Thanks for looking!

Hi All -
This never got resolved and we've run into it again. We'll probably open a Support ticket but, meanwhile, has anyone got an idea succesfully applying user and group info on reverse deployments?

Thanks,
Wally Box
Nike, Inc.

Sarang

Did you check with "iwgloabal" as the group value?