extending ADAM schema guidelines

[enrico sabbadin @ infinito]

Hi all,
I've read through ADAM schema documentation and I can't find explananions
for things like applicationSettings , applicationSiteSettings ,
configuration and so on ..

Where do I find documentation about such classes, so that I know I f I need
to extended the schema for my needs or I can use the existing classes ?

thank in advance ..

--
Enrico Sabbadin
(e-mail address removed)
MTS - COM+ - VBCOM - Enterprise Services - Security FAQ
..NET & COM+ books selected list
http://www.sabbasoft.com

 

[Dmitri Gavrilov [MSFT]]

Most of ADAM classes are the same as in AD. See AD schema site on MSDN.

The basic rule of thumb is never to reuse existing classes. If you need a
class, create it. WRT attributes -- you may reuse existing ones, but use
caution. There are some additional hardcoded constraints that apply to some
attributes. The safest way is to create your own attributes and classes.

--
Dmitri Gavrilov
SDE, Active Directory Core

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

 

[Eric Fleischman [MSFT]]

And when you do create your own, ensure you are using unique OID's. There is
a place up on MSDN (don't have the link handy, but if you can't find it let
me know and I'll hunt it down again) where you can get an OID space from
MSFT on the fly. The idea here is to ensure you don't overlap with the rest
of the OID-consuming world. It's free, quick, easy and will save you mucho
troubleshooting time down the road when you go to apply further schema
extensions.

~Eric

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

 

[Laura A. Robinson [MVP]]

And when you do create your own, ensure you are using unique OID's. There is
a place up on MSDN (don't have the link handy, but if you can't find it let
me know and I'll hunt it down again) where you can get an OID space from
MSFT on the fly. The idea here is to ensure you don't overlap with the rest
of the OID-consuming world. It's free, quick, easy and will save you mucho
troubleshooting time down the road when you go to apply further schema
extensions.

Are you referring to oidgen.exe from the reskit?

If so:

http://support.microsoft.com/support/win2000dev/ldap white paper.doc

Laura

 

[Eric Fleischman [MSFT]]

No I am not, I am refering to the section of MSDN that lets you get an OID
space for your personal use.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

 

[enrico sabbadin @ infinito]

thank you all for you feedback ! ..

a couple of questions ..

1) Why didn't AD go with GUID, so no central authority was needed ?

2) When I asked for guidelines I was thinking about something like the rules
of database design .. or the definition of a schema for an XML document ..
is there anything like that ?

I'm basically a programmer so you must understand my point of view .. as far
as I've have seen, the coverage of AD stuff adopts an approach that fits
well for network administrators (to let them configure domains and forests
at bests) .. still no particular care about someone who wants use AD for
"application development" pourpouses (there are quite few posts about
extending the schema) ..

basically, what I'm try to understand is when it's better to store
application and user info in AD/AM instead of (for example) xml files
published on an UNC share

comments anyone ?

best regards

No I am not, I am refering to the section of MSDN that lets you get an OID
space for your personal use.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


it

let
Are you referring to oidgen.exe from the reskit?

If so:

http://support.microsoft.com/support/win2000dev/ldap white paper.doc

Laura

 

[Eric Fleischman [MSFT]]

1) Why didn't AD go with GUID, so no central authority was needed ?

GUID's are something we use all over AD. Every object has a GUID.
OID's are an RFC compliance thing. That keeps us in compliance with LDAP
among other RFC's.
We need to use both to keep everyone happy.
Read up on what OID's do. They are handy for cross-platform compatability of
LDAP-enabled applications.

2) When I asked for guidelines I was thinking about something like the rules
of database design .. or the definition of a schema for an XML document ..
is there anything like that ?

Hmm....I'm not aware of anything like this. The docs I know of talk about
the features of the different constructs allowed. Is anyone else?

~Eric


--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

thank you all for you feedback ! ..

a couple of questions ..

1) Why didn't AD go with GUID, so no central authority was needed ?

2) When I asked for guidelines I was thinking about something like the rules
of database design .. or the definition of a schema for an XML document ..
is there anything like that ?

I'm basically a programmer so you must understand my point of view .. as far
as I've have seen, the coverage of AD stuff adopts an approach that fits
well for network administrators (to let them configure domains and forests
at bests) .. still no particular care about someone who wants use AD for
"application development" pourpouses (there are quite few posts about
extending the schema) ..

basically, what I'm try to understand is when it's better to store
application and user info in AD/AM instead of (for example) xml files
published on an UNC share

comments anyone ?

best regards

No I am not, I am refering to the section of MSDN that lets you get an OID
space for your personal use.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

And when you do create your own, ensure you are using unique OID's. There is
a place up on MSDN (don't have the link handy, but if you can't find

it

let
me know and I'll hunt it down again) where you can get an OID space from
MSFT on the fly. The idea here is to ensure you don't overlap with

the
rest

of the OID-consuming world. It's free, quick, easy and will save you mucho
troubleshooting time down the road when you go to apply further schema
extensions.

Are you referring to oidgen.exe from the reskit?

If so:

http://support.microsoft.com/support/win2000dev/ldap white paper.doc

Laura

 

[enrico sabbadin @ infinito]

I think you mean this
http://msdn.microsoft.com/library/d...ining_an_object_identifier_from_microsoft.asp

No I am not, I am refering to the section of MSDN that lets you get an OID
space for your personal use.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


it

let
Are you referring to oidgen.exe from the reskit?

If so:

http://support.microsoft.com/support/win2000dev/ldap white paper.doc

Laura

 

[Eric Fleischman [MSFT]]

Yes, that's what I'm talking about. The section where you can get OID's from
Microsoft.

~Eric

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

I think you mean this
http://msdn.microsoft.com/library/d...ining_an_object_identifier_from_microsoft.asp

No I am not, I am refering to the section of MSDN that lets you get an OID
space for your personal use.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

And when you do create your own, ensure you are using unique OID's. There is
a place up on MSDN (don't have the link handy, but if you can't find

it

let
me know and I'll hunt it down again) where you can get an OID space from
MSFT on the fly. The idea here is to ensure you don't overlap with

the
rest

of the OID-consuming world. It's free, quick, easy and will save you mucho
troubleshooting time down the road when you go to apply further schema
extensions.

Are you referring to oidgen.exe from the reskit?

If so:

http://support.microsoft.com/support/win2000dev/ldap white paper.doc

Laura