1. NDS / OU design question
I've read a few texts on NDS design, but none seem to deal with the fact
that many (well, mine anyway) offices only have one server per office,
or as in my case, multiple servers, but all are used by all users (ie a
main file server, and small ones for faxserve, groupwise messaging).
I'm unsure as to wheter i should be using OU's in my tree underneath the
actual branch unit. ie i have ho.nsw.coname.tree_name (not real names
Should I make OU's under .HO.??? like travel.ho.nsw...,
freight.ho.nsw....finance.ho.nsw, and i would have deptments splits
under travel again (all because different apps, mappings, printers &
access are required). In all deps, they use the same servers...which are
So, should i be using OU's to represent these departments, or should all
users & resources v=be directly under HO??? and then use profiles,
groups etc to allocate different access to users??? the NDS books
assume every dept of 3 peopl has its own servers , printers etc
etc...not the case for me.
2. IBM C Set++ for OS/2: what's the latest version
3. NDS Design Question in MSWord format...
4. Shopper Letters Column
5. Questions on Designing a 4.1 NDS Tree
6. I am trying to post...
7. CNE Design & Implem. test question?
8. Question about BibTeX
9. NDS and NDS for NT Questions
10. LARGE NDS design
11. NDPS? and NDS Design?
12. NDS Design
13. NDS design ideas?