Re: Provisioning Accounts in ADAM (Active Directory
Application Mo

Jean-Marc,
               thanks for the info. I had put this on the back burner but 
then came across your reply and have started working on it again. I've 
created a Provisioning Rules Extension for my ADAM connector using the MIIS 
Provisioning Assistant as you suggested and have populated my Metaverse with 
my users from Active Directory however I can't figure out the missing step 
for adding them from the Metaverse into my ADAM instance.

I'm pretty sure I'm missing something simple but can't put my finger on it. 
I don't get any errors, nor does anything get created in my ADAM instance.

If I create a contact object in my ADAM instance with the same "cn" as
that 
in my Active Directory and therefore my metaverse, I get an error saying that 
Object Already Exists, which is what I expected because it does, although it 
would be nice if rather than producing this error, it joined the two objects. 
I have configured the Joins and Provisions for my Active Directory Management 
Agent for Provision only and for my ADAM Management Agent for Join only.

"Jean-Marc Desperrier" wrote:

> Tomasz Onyszko wrote:
> > [...]. However to create new object You need
> > to write a code for provisioning extension.
> 
> I think it's worth to mention it's possible instead to download the 
> Ressource Toolkit and use MIIS Provisioning Assistant :
>
http://www.microsoft.com/downloads/details.aspx?familyid=D3C7BD7A-E8D5-43CF-AD4D
-4F1F0AE00D79
> 
> MIIS Provisioning Assistant will write and compile the rule extension, 
> as well as install it under MIIS. The code will be there, it's created 
> as an intermediate step by the Provisioning Assistant, but it's not 
> required to even look at it.
> 
> Still the GUI of provisioning Assistant is not very intuitive, the cases 
> it can handle are only the rather basic ones, so experienced users will 
> prefer to simply write the code themselves.
> 
> 

Just to clarify, the Object Already Exists error occurs when I synchronise 
the Management Agent and not when I try to create it in the ADAM instance 
i.e. I can create the object in ADAM manually but it isn't joined in the 
metaverse when I synchronise the Management Agent.

"Anonymous" wrote:

> Jean-Marc,
>                thanks for the info. I had put this on the back burner but 
> then came across your reply and have started working on it again. I've 
> created a Provisioning Rules Extension for my ADAM connector using the MIIS

> Provisioning Assistant as you suggested and have populated my Metaverse
with 
> my users from Active Directory however I can't figure out the missing step

> for adding them from the Metaverse into my ADAM instance.
> 
> I'm pretty sure I'm missing something simple but can't put my finger on it.

> I don't get any errors, nor does anything get created in my ADAM instance.
> 
> If I create a contact object in my ADAM instance with the same
"cn" as that 
> in my Active Directory and therefore my metaverse, I get an error saying
that 
> Object Already Exists, which is what I expected because it does, although
it 
> would be nice if rather than producing this error, it joined the two
objects. 
> I have configured the Joins and Provisions for my Active Directory
Management 
> Agent for Provision only and for my ADAM Management Agent for Join only.
> 
> "Jean-Marc Desperrier" wrote:
> 
> > Tomasz Onyszko wrote:
> > > [...]. However to create new object You need
> > > to write a code for provisioning extension.
> > 
> > I think it's worth to mention it's possible instead to download the 
> > Ressource Toolkit and use MIIS Provisioning Assistant :
> >
http://www.microsoft.com/downloads/details.aspx?familyid=D3C7BD7A-E8D5-43CF-AD4D
-4F1F0AE00D79
> > 
> > MIIS Provisioning Assistant will write and compile the rule extension,

> > as well as install it under MIIS. The code will be there, it's created

> > as an intermediate step by the Provisioning Assistant, but it's not 
> > required to even look at it.
> > 
> > Still the GUI of provisioning Assistant is not very intuitive, the
cases 
> > it can handle are only the rather basic ones, so experienced users
will 
> > prefer to simply write the code themselves.
> > 
> >