Highlighted
Anonymous_User Absent Member.
Absent Member.
1428 views

User Context woes

Hi we seem to have come up against the same problem as
http://forums.novell.com/novell-product-support-forums/zenworks/configuration-management/zcm-server-install/355370-user-sources-cant-add-new-context.html
except it's slightly worse. This ought to have been fixed by now one would
have thought.

Running ZCM 10.2.1. 2 Primaries. We have defined an AD user source with a
root context at a top level OU that equates to the entire organisation:
domain: orgad.loc
root context: ORG

We have set up User contexts for those OUs beneath this that have ZCM users.
This has been a gradual migration. Now we have reached 9 contexts, we
cannot add a 10th. I have tried adding this with a ZMAN ucc, but this does
not seem to work either
"Unable to add new context because this container or a parent container has
already been added as a user context"
which of course is not true
We have also tried deleting one that isn't yet used to give room for the one
we have to add now, and we get exactly the same error, which is obviously
not helpful.

There is a nice command there which should let you amalgamate user contexts
with one at a higher level. However, we can't because the parent OU, ORG is
part of the root context.
Nor does it let you change the root context of the user source, if you
attempt to, a Tomcat error is spawned. I imagine you'd have to remove the
existing contexts first, and a) it doesn't seem to let us, and b) we would
lose the assignments

Now of course we could define a new user source and migrate our logins and
assignments to this. However, we cannot create a 2nd user source pointing
at the AD, it doesn't let you, probably because it is named with the AD
domain, and this cannot be changed and the source cannot be disabled.

So our only course of action, unless there is a magic fix for the arbitrary
9 contexts limit (please tell!), is to delete the existing user source and
create a fresh one, with a single user context.

Of course we will lose and have to reload bundle and policy assignments on
300 odd bundles!
So in case this is what we need to contemplate, is there a method say using
ZMAN, to extract all these assignments to a file so that after a bit of
manipulation, we could put them all back in again?

regards,
Martin



Labels (2)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: User Context woes

I would suggest opening an SR, this is a bug.


--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"Martin Farrer" <dddwale@spammenot.yahoo.co.uk> wrote in message
news:20LDm.20339$7G7.18931@kovat.provo.novell.com...
> Hi we seem to have come up against the same problem as
> http://forums.novell.com/novell-product-support-forums/zenworks/configuration-management/zcm-server-install/355370-user-sources-cant-add-new-context.html
> except it's slightly worse. This ought to have been fixed by now one
> would have thought.
>
> Running ZCM 10.2.1. 2 Primaries. We have defined an AD user source with
> a root context at a top level OU that equates to the entire organisation:
> domain: orgad.loc
> root context: ORG
>
> We have set up User contexts for those OUs beneath this that have ZCM
> users. This has been a gradual migration. Now we have reached 9 contexts,
> we cannot add a 10th. I have tried adding this with a ZMAN ucc, but this
> does not seem to work either
> "Unable to add new context because this container or a parent container
> has already been added as a user context"
> which of course is not true
> We have also tried deleting one that isn't yet used to give room for the
> one we have to add now, and we get exactly the same error, which is
> obviously not helpful.
>
> There is a nice command there which should let you amalgamate user
> contexts with one at a higher level. However, we can't because the parent
> OU, ORG is part of the root context.
> Nor does it let you change the root context of the user source, if you
> attempt to, a Tomcat error is spawned. I imagine you'd have to remove the
> existing contexts first, and a) it doesn't seem to let us, and b) we would
> lose the assignments
>
> Now of course we could define a new user source and migrate our logins and
> assignments to this. However, we cannot create a 2nd user source pointing
> at the AD, it doesn't let you, probably because it is named with the AD
> domain, and this cannot be changed and the source cannot be disabled.
>
> So our only course of action, unless there is a magic fix for the
> arbitrary 9 contexts limit (please tell!), is to delete the existing user
> source and create a fresh one, with a single user context.
>
> Of course we will lose and have to reload bundle and policy assignments on
> 300 odd bundles!
> So in case this is what we need to contemplate, is there a method say
> using ZMAN, to extract all these assignments to a file so that after a bit
> of manipulation, we could put them all back in again?
>
> regards,
> Martin
>
>
>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.