ADAM (Active Directory Application Mode) Topology, Replication etc

Dear Colleagues,

I have some rather fundamental questions when it comes to setting up ADAM
instances as they appertain to sites.

My understanding is that ADAM has its own replication mechanisms, so one
needs to consider the speed of inter site connectors when designing an ADAM
infrastructure. I am looking for authoritative documentation, ideally from
Microsoft, that will not only shed light on my questions, but also assist my
colleagues and I in terms of proposing designs for ADAM.

If I understand the concepts correctly, a single ADAM “server� with a single
instance will assume that bandwidth is not an option. In the case where you
have a domain controller in one location (lets say NY) and another domain
controller in California. You configure Active Directory to do its
replication thing according to schedules, link speeds, costs, etc.

Now, my understanding is that if you just drop an adam instance in NY and
another one in California, you are going to have issues because the adam
servers themselves need to be told that they are in different sites and need
to have replication configured for them.

The question here is, when you have child domains, how do you set up adam so
that it talks to the higher up domains and, when you don’t have children
domains, you need to configure adam for multiple sites?

Any advise or papers, diagrams, instructions, etc., that comes from
authoritative sources would be helpful.

Regards,

Walt Ellena

--
The Dumbest Question is the one that is never asked.

In news:4F143981-4A41-457E-9AB7-(E-Mail Removed),
Walter Ellena <(E-Mail Removed)> stated, which I
commented on below:
> Dear Colleagues,
>
> I have some rather fundamental questions when it comes to setting up
> ADAM instances as they appertain to sites.
>
> My understanding is that ADAM has its own replication mechanisms, so
> one needs to consider the speed of inter site connectors when
> designing an ADAM infrastructure. I am looking for authoritative
> documentation, ideally from Microsoft, that will not only shed light
> on my questions, but also assist my colleagues and I in terms of
> proposing designs for ADAM.
>
> If I understand the concepts correctly, a single ADAM "server" with a
> single instance will assume that bandwidth is not an option. In the
> case where you have a domain controller in one location (lets say NY)
> and another domain controller in California. You configure Active
> Directory to do its replication thing according to schedules, link
> speeds, costs, etc.
>
> Now, my understanding is that if you just drop an adam instance in NY
> and another one in California, you are going to have issues because
> the adam servers themselves need to be told that they are in
> different sites and need to have replication configured for them.
>
> The question here is, when you have child domains, how do you set up
> adam so that it talks to the higher up domains and, when you don't
> have children domains, you need to configure adam for multiple sites?
>
> Any advise or papers, diagrams, instructions, etc., that comes from
> authoritative sources would be helpful.
>
> Regards,
>
> Walt Ellena

ADAM is a flat model. No child domains, doesn't use DNS, etc. It's more like
Netscape LDAP, or Cold Fusion LDAP, etc. without the overhead and complexity
of AD.

Step-by-Step Guide to Deploying ADAM:
http://technet2.microsoft.com/Window....mspx?mfr=true

More links from a Google search for "active directory configuring adam":
http://www.google.com/search?sourcei...nfiguring+adam

I hope that helps.

--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

Ace,

Thanks for those links.

I have a baseline understanding of ADAM as it appertains to smaller
environments. My question is, what about ADAM as used for a global
enterprise. I mean, what about replication accross slow links? I see some
chatter about ADAM needing to be told what site its in, if applicable.

Its a question of bandwidth and design. Do you know of any microsoft
resources, or other resources for that matter, that get into the nuts and
bolts of designing an ADAM infrastructure as it appertains to a global
enterprise.

Regards,

Walt Ellena
--
The Dumbest Question is the one that is never asked.


"Ace Fekay [MVP]" wrote:

> In news:4F143981-4A41-457E-9AB7-(E-Mail Removed),
> Walter Ellena <(E-Mail Removed)> stated, which I
> commented on below:
> > Dear Colleagues,
> >
> > I have some rather fundamental questions when it comes to setting up
> > ADAM instances as they appertain to sites.
> >
> > My understanding is that ADAM has its own replication mechanisms, so
> > one needs to consider the speed of inter site connectors when
> > designing an ADAM infrastructure. I am looking for authoritative
> > documentation, ideally from Microsoft, that will not only shed light
> > on my questions, but also assist my colleagues and I in terms of
> > proposing designs for ADAM.
> >
> > If I understand the concepts correctly, a single ADAM "server" with a
> > single instance will assume that bandwidth is not an option. In the
> > case where you have a domain controller in one location (lets say NY)
> > and another domain controller in California. You configure Active
> > Directory to do its replication thing according to schedules, link
> > speeds, costs, etc.
> >
> > Now, my understanding is that if you just drop an adam instance in NY
> > and another one in California, you are going to have issues because
> > the adam servers themselves need to be told that they are in
> > different sites and need to have replication configured for them.
> >
> > The question here is, when you have child domains, how do you set up
> > adam so that it talks to the higher up domains and, when you don't
> > have children domains, you need to configure adam for multiple sites?
> >
> > Any advise or papers, diagrams, instructions, etc., that comes from
> > authoritative sources would be helpful.
> >
> > Regards,
> >
> > Walt Ellena
>
> ADAM is a flat model. No child domains, doesn't use DNS, etc. It's more like
> Netscape LDAP, or Cold Fusion LDAP, etc. without the overhead and complexity
> of AD.
>
> Step-by-Step Guide to Deploying ADAM:
> http://technet2.microsoft.com/Window....mspx?mfr=true
>
> More links from a Google search for "active directory configuring adam":
> http://www.google.com/search?sourcei...nfiguring+adam
>
> I hope that helps.
>
> --
> Ace
> Innovative IT Concepts, Inc
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...
>
>
>

In news:626EF3DC-27A3-4970-A357-(E-Mail Removed),
Walter Ellena <(E-Mail Removed)> stated, which I
commented on below:
> Ace,
>
> Thanks for those links.
>
> I have a baseline understanding of ADAM as it appertains to smaller
> environments. My question is, what about ADAM as used for a global
> enterprise. I mean, what about replication accross slow links? I
> see some chatter about ADAM needing to be told what site its in, if
> applicable.
>
> Its a question of bandwidth and design. Do you know of any microsoft
> resources, or other resources for that matter, that get into the nuts
> and bolts of designing an ADAM infrastructure as it appertains to a
> global enterprise.
>
> Regards,
>
> Walt Ellena

I'm not sure what you mean by "Enterprise". Does that mean you want to run a
directory service based soley on ADAM, such as with authentication,
sercurity, delegation, with objects like computers, users, groups,
distribution lists, etc? That's not really it's intention. One example is
that it can be used for an LDAP directory, used for a web app, etc. It's the
toned down version of AD, like Netscape LDAP. I wouldn't use Netscape's LDAP
service for a directory service.

Active Directory is what would be required for an enterprise
directory/authentication service.

Ace