the concept is similar to that of printer objects in AD: you you don't create printer queues in an OU (or as child-objects of servers) - instead you create a reference to an existing printer queue on a server - this reference is stored in a printer object; basically Active _Directory_ can act as a "central repository" of all printers available in a network, which allows you easy searching for printers (e.g. to find those close to you when you're located in a specific subnet or those that have a specific feature, such as duplex printing or color etc.)
 
Similarly, you don't create shares in an OU - instead you create a shared folder object which contains a reference to an existing share on a server.  AD could again be used as a "central repository" of all shares available on all servers in the network.
 
While the first example (printer objects) has been adapted quite well, I hardly find companies that see much value in using the shared volume objects. 
 
I'd say this is basically due to the fact that AD as a "search engine" for printers is integrated in the printer-install UI on Win2000/XP clients and there is no similar search-engine for shared folder objects (you'd have to use LDAP queries or build you own UI). Also, it's likely due to the nature of the objects they represent: printers are output devices which can and should be used by most people in a company (although you can still restrict printing to expensive devices via permissions on the printer queue and via their object's visibility in AD).  Shares however are used to make data available to a select group of people - you don't really want users "sniffing" for available shares in the network. Instead you want to control which user mounts which share to do their work (often controlled via logon-scripts).
 
hope this clarifies some of the things you're wondering about
 
/Guido


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ
Sent: Montag, 27. Juni 2005 22:39
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Creating share object in an OU

What's the purpose of being able to create shares beneath an OU versus just having a share on a file server?  How will the users see the share in the OU?  Whats the advantages and disadvantages of creating the share in an OU versus just having it exist on a fileserver?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail is confidential, may contain proprietary information
of the Cooper Cameron Corporation and its operating Divisions
and may be confidential or privileged.

This e-mail should be read, copied, disseminated and/or used only
by the addressee. If you have received this message in error please
delete it, together with any attachments, from your system.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to