Network Support Encyclopedia 96-1

home *** CD-ROM | disk | FTP | other *** search

/ Network Support Encyclopedia 96-1 / novell-nsepro-1996-1-cd2.iso / cbt / course7 / less7312.tbk (.txt) < prev next >

Wrap

Asymetrix ToolBook File | 1993-02-01 | 474KB | 4,212 lines

destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 22 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 377 ffield Designating Leaf Objects Some leaf objects are created for you at installation and some you must plan and create yourself.. Computerrrr Computerrrr ADMIN ADMIN Printer: Printer: o 3 A Group Group VG.GSG Server lKDKiK Server destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 5 of 31I estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 390 ffield Strategies for Planning the Top Levels of Your Directory Tree Think strategically as you plan your Directory tree. No one strategy is correct for all companies, and most strategies have advantages and disadvantages. Think strategically. EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 10 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 " gTextID group id 11 of page id 406 ffield Directory tree navigation is much easier and faster if you place resources close to those who use them most. For example, if your company has an artist in the Marketing department that works mostly on projects for the Sales department, then place the User object for the artist in the Sales Organizational Unit. This will enable the artist to access Sales department resources. Sales Sales Printer 2 Printer 2 Artist Artist \#4#Y# Sales Sales EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 30 of 31 N AAA Summary estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 3030,1470,9285,6277 gTextID group id 378 of page id 382 ffield Think strategically when planning your Directory tree, especially the critical top levels. Use a global strategy that allows for effective information flow. After you determine the Directory tree structure, you must designate container and leaf objects, following the rules of placement. The outcome is a highly flexible Directory tree structure that will add to your company's effectiveness. PLast EnterPage leavePage EnterPage DoPage ESetComp 0,100,0 0,0,0 leavePage 0,0,0 0,0,0 0,100,0 0,0,0 leavePage 0,0,0 0,0,0 pTextPort ptemplate plast Page 31 of 31 AAAAAA" ` ` L o t ~ t Q ` ` L o t ~ t Q 3 $ ~ Lesson estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds fGLGppBounds 3030,1470,9285,6277 vGgTextID group id 543 of page id 197 ffield You have now completed this lesson. To select another lesson, click Menu or Map. To search for information on a specific topic, click Options, and then click Topic Search. For more information on these topics, refer to the following: - NetWare v4.0 Concepts - NetWare v4.0 Supervising the Network )8Zc LeavePage EnterPage buttonup whatRevAmI EnterPage vblueback BlueBack background blueback foreground BlueBack vComback pback2 vComback ComBack ComBack DoPage pTest pTest set wr _fb to it vScript wr1_fb wr2_fb wr3_fb LeavePage 3|finverts a,b,c,d clickyes }bHidegoto buttonup 3|finverts a,b,c clickyes wr1_fb wr2_fb wr3_fb fill_h stroke_h whatRevAmI ptemplate :Rev 1.00 bookname terPage leavepage EnterPage buttonUp EnterPage DoPage vBlueBack pback1 vblueback BlueBack background blueback foreground BlueBack vComback pback2 vComback ComBack ComBack leavepage buttonUp phwordscount get textlinecount(my pf set vtemp2 to textlinecount(my pf get textline of my pf set vtemp5 to textline of my pf get my pf set vtemp to my pf vtemp vtemp5 j:to1 vtemp2 vscript vname buttonUp buttonUp dlgInit dlgInit Cancel setValue dlgBox dialog bCancel getValue bSearch getValue tindex.tbK tindex.tbk pCaller bGoto getValue pptotno pptotno Go to Page (1 - Page number is not within this component bTopMenu getValue pTopmenu bGlossary getValue glossary.tbK glossary.tbk pCaller vTopMenu vPage vStartPage vTotalPages vCaller vResult vTempInit vInit coursefile component EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 16 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 374 ffield Placing Objects in the Directory Tree After you determine the Directory tree structure you feel best suits your company, you must designate which objects to use. To make these decisions, you need to understand concepts related to: - Designating container objects - Designating leaf objects - Following rules of object placement ontainer objects - Designating leaf objects - Following rules of object placement Designate Container Objects Follow Rules of Object Placementt Follow Rules of Object Placementt Designate Container Objects Designate Leaf Objectssjects Designate Leaf Objectssjects EnterPage whatRevAmI EnterPage popUp DoPage whatRevAmI ptemplate :Rev 1.00 bookname DoPage whatRevAmI ptemplate :Rev 1.00 bookname pPopup POPUP pTemplate concept pTextPort Page 23 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 361 ffield Default Leaf Objects If you are installing NetWare v4.0 on a new server, the following leaf objects are created for you and placed in the same Organization or Organizational Unit in which you have placed the server: - NetWare Server object - Volume object SYS: - Volume objects for any other volumes on the server's disk besides SYS: - User object ADMIN (This object is created so you can log in for the first time and begin creating other objects.) NetWare Server NetWare Server ADMIN ADMIN popup fpopup (borderstype rectangle No definition for NetWare Server buttonup buttonup popup *@*p/5 vComback vBlueBack pTemplate graphicPick pBack1 pBack2 Country Leaf objects: - Alias Container objects: - Organization Organization Leaf objects: - AFP Server - Alias - Computer - Directory Map - Group - NetWare Server - Organizational Role - Print Queue - Print Server Container objects: - Organizational Unit Organizational Unit Leaf objects: - Printer - Profile - User - Volume Container objects: - Organizational Unit text4 text5 text6 text7 text8 text9 text10 text11 text12 text13 text14 phwordscount Page 25 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds gTextID group id 14 of page id 405 ppBounds 4665,1470,9285,6270 ffield Rules of Object Placement To correctly plan your Directory tree, you must follow certain rules of object placement. These rules allow information to smoothly flow from your top level container objects down to your leaf objects (resources). Click on each container object to see which leaf and container objects can be created there. hows Country, Organization, and Organizational Unit.] estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 315,3279,4515,6255 gTextID group id 21 of page id 405 Country Country Organization: Organization: Organiza- tional Unitt Organiza- tional Unitt EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 4 of 31g estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 349 ffield Planning the Directory Tree Structure Initial planning of the Directory tree structure logically divides into two parts: - Planning the "top levels" These levels comprise container objects that help you manage and organize other objects (both other container objects and leaf objects). - Placing objects in the Directory tree You must create container and leaf objects to fill in the tree. l in the tree. [Is this correct?] Top Levels Top Levels Place Objects in the Directory Treee Place Objects in the Directory Treee EnterPage whatRevAmI EnterPage popUp DoPage whatRevAmI ptemplate :Rev 1.00 bookname DoPage whatRevAmI ptemplate :Rev 1.00 bookname pPopup POPUP pTextPort pTemplate concept Page 8 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 300,3750,9290,6270 gTextID group id 8 of page id 371 ffield Strategy: Follow the Organizational Hierarchy One way to set up your Directory tree is to follow the organizational hierarchy of your company and designate departments as the Organizational Units. An advantage of using the organizational structure of the company as a model for a Directory tree is that it is a familiar representation of how your company functions. A disadvantage is that it might not reflect the actual flow of information within the company. Sales Sales R and D Company Company Manufacturing Manufacturing Organizational Units Organizational Units Finance Finance R and D popup fpopup borderstype rectangle No definition for Organizational UnitsW buttonup buttonup popup pScenario pFeedbackPort pTemplate select1 ptest A is the best answer. Each division is independent from the next, and has its own Manufacturing and R and D departments. Headquarters is also independent. This is represented in the Directory tree structure. B is not the best answer. This structure does not reflect the independent nature of Headquarters (Provo). Page 28 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pFeedbackPort destroy pFeedbackPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pFeedbackPort destroy pFeedbackPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 300,5115,9285,6270 gTextID group id 7 of page id 398 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds Click on the selection of your choice. ffield Based on the scenario, which plan for the top levels of the Directory tree would be best for Toyco? Toyco Dolls Cars and Trucks Sales R and D Toyco Dolls Sales Q ~ Q n R and D R and D R and D Toyco Dolls Cars and Trucks Provo R and D Provo R and D Sales Sales Sales Toyco Dolls Provo R and D Provo R and D Sales Cars and Trucks Cars and Trucks 5v5ppBounds 7912,4380,9127,4755 5pscen Scenario destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds _change destroy adjustBounds scenarioButton_change buttonUp buttonDown buttonStillDown pEnabled pEnabled scenarioButton_change theSelf pScenario ppBounds destroy pScenario adjustBounds pNoAdjust ppBounds buttonUp ppEnabled scenarioButton_change theLocation buttonDown ppEnabled theLocation buttonStillDown ppEnabled theLocation pEnabled 0,0,0 ppEnabled theEnabled pEnabled ppEnabled destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds 77Hc LeavePage EnterPage buttonup whatRevAmI EnterPage vblueback BlueBack background blueback foreground BlueBack vComback pback2 vComback ComBack ComBack DoPage pTest pTest set wr _fb to it vScript wr1_fb wr2_fb wr3_fb LeavePage 3|finverts a,b,c,d clickyes }bHidegoto buttonup 3|finverts a,b,c clickyes wr1_fb wr2_fb wr3_fb fill_h stroke_h whatRevAmI ptemplate :Rev 1.00 bookname EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 14 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 407 ffield For example, in an Engineering department, an engineer may be assigned to several projects during a short period of time. If Organizational Units represent each project, an engineer User object may need to be moved each time an engineer changes projects. If one Organizational Unit encompasses all of Engineering, then the administration of Directory Services is not affected if the engineer is transferred to other projects. I am on Project Z. I am on Project X. User 2 User 3 User 1 User 4 User 5 User 6 User 2 User 3 User 1 User 4 User 5 User 6 Engineering Engineering I am on Project X. Project X.......... Y.oject X.......... EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 18 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 375 ffield Using the Country Container Object The Country container object usually designates site locations. It is placed between the Root object and your Organization container objects. Normally, you need to create a Country container object only when you have a global network that spans multiple countries and the country designation fits your network needs. If you prefer not to use Country, you can still use an Organization or Organizational Unit container object to designate sites in other countries. Used for different sites, if you have a global network. Used for different sites, if you have a global network. Country Country Organizationtion Organizationtion EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTemplate concept Page 19 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds gTextID group id 21 of page id 408 ppBounds 300,3735,9290,6255 ffield Country objects are named with a 2-letter country code based on x.500 standards. One disadvantage of using the Country object is that you are then required to include name types when working with contexts. If you prefer not to use the Country object, you can still use an Organization or Organizational Unit container object to designate sites in other countries. CN=Boardk.OU=R and D.OU=Action Toys.O=Toys.C=US CN=Boardk.OU=R and D.OU=Action Toys.O=Toys.C=US PopUpBig PopUp Big EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pPopup POPUP pTextPort pTemplate concept Page 13 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 373 ffield Strategy: Organize for Stability Choose a structure that is not likely to change frequently. This reduces administration tasks on your Directory tree. r example, in an Engineering department, an engineer may be assigned to several projects during a short period of time. If Organizational Units represent each project, an engineer User object may need to be moved each time an engineer changes projects. If one Organizational Unit encompasses all of Engineering, then the administration of Directory Services is not affected if the engineer is transferred to other projects. ojects. popup fpopup borderstype rectangle buttonup buttonup popup I am on Project X. I am on Project Y. I am on Project Z. User 2 User 3 User 1 User 4 User 5 User 6 User 2 \ 4 Y User 3 User 1 T!,!Q! User 4 User 5 L"$"I" User 6 Engineering ~#V#{# Engineering Project X.......... p$H$m$ X.oject X.......... destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds title PLast EnterPage whatRevAmI EnterPage popUp DoPage whatRevAmI ptemplate :Rev 1.00 bookname DoPage whatRevAmI ptemplate :Rev 1.00 bookname pPopup POPUP pTemplate concept pTextPort Page 15 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 300,3750,9290,6270 gTextID group id 8 of page id 324 ffield Strategy: Create Minimal Levels It is recommended that you use as few levels in your Directory tree as possible. For example, as you create more levels, object contexts become longer and, therefore, more difficult to use. ome longer and, therefore, more difficult to use. his does not sound correct to me.]]]]]]]]]]]] Administrators Finance Manufacturing Electronic Accts Payable Division 2 Division 1 Accts Receivable Administrators Finance Manufacturing Electronic Accts Payable Division 2 Division 1 Accts Receivable popup fpopup borderstype rectangle No definition for contexts/ buttonup buttonup popup nel: Right Half terpage leavePage enterpage menuButton_change enterpage ppTotNo DoPage 0,100,0 0,0,0 INDEX 0,100,0 seqno totno component StartZ leavePage INDEX 0,0,0 0,0,0 0,0,0 menuButton_change pHotTopics vPage vTopic vName theSelf X4@EXT 0,0,0 INDEX 0,100,0 seqno totno component StartZ leavePage INDEX 0,0,0 0,0,0 0,0,0 menuButton_change pHotTopics vPage vTopic vName theSelf r N ptopic10 group id 2563 of page id 304 ptopic9 group id 2559 of page id 304 ptopic8 group id 2555 of page id 304 ptopic7 group id 2551 of page id 304 ptopic6 group id 2547 of page id 304 ptopic5 group id 2543 of page id 304 ptopic3 group id 2538 of page id 304 ptopic2 group id 2534 of page id 304 ptopic1 group id 2530 of page id 304 pColdTopics1 pColdTopics Installation defaults,2 Plan top levels only,6 Think globally,7 Follow organizational hierarchy,8 Information flow,9 Plan for consistency,11 Centralization and autonomy,12 Organize for stability,13 Create minimal levels,15 Country container object,18 Organization container object,20 Organizational Units,21 Leaf objects - Designating,22 Leaf objects - Default,23 Leaf objects - Planning,24 Modification,26 pHotTopics Overview,2 Objectives,3 Planning the Directory Tree Structure,4 Strategies for Planning the Top Levels of Your Directory Tree,5 Placing Objects in the Directory Tree,16 Designating Container Objects,17 Designating Leaf Objects,22 Rules of Object Placement,25 Planning Scenario,27 Summary,30 pTextPort pptotno pTemplate Page 1 of 31 R,Q I 40Q u !!!!!! AAAAAA AAAAAA Index estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds AtAppBounds 3030,1470,9285,6277 AgTextID group id 1943 of page id 304 ffield Lesson Index Click Next to begin this lesson or click an Index button to jump to the topic of your choice. anged the word "component" to "lesson" in the initial sentence. Is this the correct standard?] topic4 bButton fField Strategies for Planning the Top Levels of Your Directory Tree topic1 dFXFpEnabled FvFppBounds 3405,2760,6390,3075 FfFieldID field id 2529 of page id 304 FbButtonID button id 2528 of page id 304 bButton fField OverviewgyyzXx topic2 GpEnabled HppBounds 3405,3495,6390,3810 lHHHfFieldID field id 2533 of page id 304 ~HbButtonID button id 2532 of page id 304 bButton fField Objectives topic3 IpEnabled IppBounds 3405,4065,6390,4590 IfFieldID field id 2537 of page id 304 $JbButtonID button id 2536 of page id 304 bButton fField Planning the Directory Tree Structure topic5 KjKfFieldID field id 2542 of page id 304 KppEnabled KppLines KppLineHeight KppOffset LbButtonID button id 2541 of page id 304 NLFLpLines lL`LpEnabled L|LfTextID field id 64 of page id 154 LppBounds 3405,5445,6390,5970 bButton fField Placing Objects in the Directory Tree topic6 MfFieldID field id 2546 of page id 304 .N"NppEnabled FN>NppLines fN\NppLineHeight NxNppOffset NbButtonID button id 2545 of page id 304 NpLines NpEnabled NfTextID field id 64 of page id 154 2OppBounds 6285,2670,9270,3195 bButton fField Designating Container Objects topic7 rPNPfFieldID field id 2550 of page id 304 PppEnabled PppLines PppLineHeight PppOffset PbButtonID button id 2549 of page id 304 2Q*QpLines PQDQpEnabled Q`QfTextID field id 64 of page id 154 QppBounds 6285,3375,9270,3900 bButton fField Designating Leaf Objects topic8 RfFieldID field id 2554 of page id 304 RppEnabled SppLines *S SppLineHeight FS<SppOffset |SXSbButtonID button id 2553 of page id 304 SpLines SpEnabled SfTextID field id 64 of page id 154 SppBounds 6285,4065,9270,4590 bButton fField Rules of Object Placement topic9 UfFieldID field id 2558 of page id 304 TUHUppEnabled lUdUppLines UppLineHeight UppOffset UbButtonID button id 2557 of page id 304 UpLines VpEnabled FV$VfTextID field id 64 of page id 154 XVppBounds 6285,4845,9270,5160 bButton fField Planning Scenario topic10 WtWpEnabled WppBounds 6285,5535,9270,5850 WfFieldID field id 2562 of page id 304 WbButtonID button id 2561 of page id 304 bButton fField Summary000000000000000 keyUp whatRevAmI keyUp 0,0,0 0,0,0 Do you want to exit the course? Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName totno bmarkfile result revnum atmpt popup seqno isCntrl isShift whatRevAmI Background Title Rev 1.00 bookname EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 24 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 396 ffield Planning Your Leaf Objects As discussed earlier in the lesson, container objects and their contents should be defined by work groups, shared resources, and information usage. Therefore, leaf objects representing resources used by a single group should be placed in the same container. Computer Computer Group Group Printer: Printer: B n2x EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 6 of 319 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 391 ffield Strategy: Plan Only the Top Levels To accommodate special needs at individual worksites or in specific departments, you may want to plan only the top levels of your Directory tree. Then, assign individual sites or departments the responsibility for creating and administering their portion of the Directory tree. Manufacturing's Portion of the Directory Tree Accounting's Portion of the Directory Tree Marketing's Portion of the Directory Tree Manufacturing's Portion of the Directory Tree Accounting's Portion of the Directory Tree Marketing's Portion of the Directory Tree EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 20 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 376 ffield Using Organization Container Objects Like Country objects, Organization container objects can designate different site locations. You can also use the Organization container object to designate a part of your company that is separate, such as a subsidiary.y..... Caps Inc. Caps Inc. Hong Kong Hong Kong Organization V'.'S' Organization '&]K EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 26 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 379 ffield A Final Reminder The Directory tree structure remains highly flexible, even after installation. Remember that you can always add, delete, or move objects after you have installed your Directory tree. Delete Delete title buttonup buttonup Do you want to exit the course? Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName seqno totno bmarkfile result revnum atmpt Do you want to exit the course? Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName seqno totno bmarkfile result revnum atmpt buttonup buttonup Find_Menu coursefile place buttonup buttonup Find_Menu coursefile place Index Index buttonup buttonup 0,0,0 seqno buttonup buttonup 0,0,0 seqno buttonup buttonup \help pCaller vCaller place \help pCaller vCaller place Dialog buttonUp buttonUp dlgInit dlgInit Cancel setValue dlgBox dialog bCancel getValue bSearch getValue tindex.tbK tindex.tbk pCaller bTopMenu getValue pTopmenu bGlossary getValue glossary.tbK glossary.tbk pCaller vTopMenu vCaller vResult vTempInit vInit coursefile , "bGlossary") tbk" buttonUp buttonUp dlgInit dlgInit Cancel setValue dlgBox dialog bCancel getValue bSearch getValue tindex.tbK tindex.tbk pCaller bTopMenu getValue pTopmenu bGlossary getValue glossary.tbK glossary.tbk pCaller vTopMenu vCaller vResult vTempInit vInit coursefile dlgInit button bSearch,b19,TRUE button bGlossary,b21,TRUE button bTopMenu,b25,TRUE button bCancel,b20,FALSE dlgBox 524480,4,30,20,111,114,,,Options,8,Helv,bSearch,3.70,6.61,50.86,32.16,19,1342242816,128,Topic Search,0,bGlossary,57.87,6.61,50.86,32.16,21,1342242816,128,Glossary,0,bTopMenu,29.68,41.93,50.86,32.16,25,1342242816,128,Main Menu,0,bCancel,29.68,84.14,50.86,12.31,20,1342242817,128,Cancel,0 ctrlID Options buttonup buttonup pCaller vCaller place buttonup buttonup pCaller vCaller place title Title Screen EnterPage LeavePage EnterPage initialize 0,0,0 0,0,0 0,0,0 component LeavePage tialize 0,0,0 0,0,0 0,0,0 component LeavePage pptotno pTemplate title Manufacturing's Portion of the Directory Tree Marketing's Portion of the Directory Tree Accounting's Portion of the Directory Planning the Directory Tree Structure Planning the Directory Tree Structure pFeedbackPort pTemplate select1 ptest A is the best answer. Resources are in the same container as those who use them. B is not the best answer. Users should be in the same container as the resources they use. Page 29 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pFeedbackPort destroy pFeedbackPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pFeedbackPort destroy pFeedbackPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 300,5115,9285,6270 gTextID group id 7 of page id 380 & v)A .;+ k estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds Click on the selection of your choice. ffield At Toyco, each division's Manufacturing and R and D departments use separate printers and computers. Which placement of objects is best for the Dolls division? Paris???s? O=Dolls OU=Mfgs OU=R and D User 1 User 2 Computer Printer User 1 User 2 Computer Printer O=Dolls OU=Mfgs User 1 User 2 Computer Printer User 1 User 2 Computer Printer OU=R and D O=Dolls OU=Mfgs OU=R and D OU=Equip Computer Printer OU=Users User1 User2 OU=Equip Computer Printer OU=Users User1 User2 O=Dolls OU=Mfgs OU=Equip Computer Printer OU=Users User1 User2 OU=Equip Computer Printer OU=Users User1 User2 OU=R and D destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 27 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 389 ffield Planning Scenario Toyco has divisions located at sites throughout the world. Two of these divisions are Cars and Trucks (Detroit) and Dolls (Paris). Each division is independently managed and has its own Manufacturing and R and D departments. Sales and Accounting departments for the entire company are located at Headquarters in Provo, which is managed as if it were an independent division. Answer the questions on the following pages based on this information. Click the scenario button if you need to review this information. nformation. questions x.6.U. EnterPage whatRevAmI EnterPage popUp DoPage whatRevAmI ptemplate :Rev 1.00 bookname DoPage whatRevAmI ptemplate :Rev 1.00 bookname pPopup POPUP pTemplate concept pTextPort Page 21 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds n T ppBounds 300,3735,9290,6255 ~ gTextID group id 8 of page id 333 ffield Using Organizational Units Organizational Units do just what their name implies: they divide your Directory tree into branches based on whatever organizational component (unit) makes sense. Typical examples of Organizational Units include geographic locations, projects, or products. Organizational Units do not all have to be the same type. That is, you can designate a workgroup as an Organizational Unit and also designate a project as another Organizational Unit.ional unit. Root Root Company Company Pacific Region Pacific Region Projects Region Projects Region Products Products Organizational Unit Organizational Unit Organizational Unit Organizational Unit Organizational Unit Organizational Unit Organization Organization popup fpopup V-borderstype rectangle No definition for branches buttonup buttonup popup C:\TOOLBOOK\COURSE7.TBK :REPORTDATA 09 +09 FromGoTo FromGoTo curfocus altyes false InCor ActButton FromGoTo System `D|D| System `D|D| pIndex page id 232 ActButton 22.TBK" tno,bancont 4result,revnum,numrev,revdes,atmpt,component,level,bmarkfile Xuser showwindow( gsetwindowword( 9792,7200 8,-14,1024 +512) -- ** Prog. banner content here "Public Switched Telephone Network" -- ** J -- o4 digit no ( ,unit,sec,lesson) c"yes" PMark SMark TotNo TMark c"I" c"C" \ LeaveBook EnterBook LeaveBook EnterBook showwindow setwindowword setwindowword showwindow reader Public Switched Telephone Network PMark SMark TotNo TMark result revnum numrev revdes atmpt component normal result revnum numrev revdes atmpt component level bmarkfile coursefile place bookname seqno totno bancont LeaveBook normal normal normal bmarkfile stoploop LessComp(3,2,3) System gD|D| ActButton ActButton ActButton LessComp(1,1,1) LessComp(2,2,1) curfocus false scrollx field id 0 of page id 148 IdNumber of this Background = 19 field id 43 of page id 198 curfocus fD|D| FromGoTo FromGoTo FromGoTo curfocus gD|D| ActButton fD|D| FromGoTo FromGoTo field id 89 of page id 181 false gD|D| gD|D| gD|D| LessComp(2,2,2) pplaceLastDate p7000LastDate 73874 ActButton pptottry 8 ppbancont "ppPlace ppLevel !0!`! !F"F"@ ActButton 8 of page id 232 :PRINTLAYOUT 09 +09 Title stname PrintReview `D|D| s Rmn `D|D| id 1124 of page id 261 button id 408 of page id 232 `D|D| ActButton 8 of page id 232 8 of page id 232 recordField id 1124 of page id 303 ActButton 8 of page id 232 ActButton :CONDITIONDATA IdNumber of this Background = 19 IdNumber of this Background = 19 this Background = 19 AltKey DoubleEntry DoubleEntry DoubleEntry DoubleEntry FromGoTo ActButton >mhu$ 5 of page id 185 field id 51 of page id 155 omGoTo fD|D| fD|D| DoubleEntry pplaceTime 2 02:58:25 PM p5000LastDate 08:36:21 PM p5000Time (!d vTemp1 Nov 18 1992 03:06:26 PM Jan 20 1993 04:10:47 PM !11893 10:12:01 AM ("p7000Time System `D|D| ActButton Tms Rmn `D|D| Planning the Directory Tree Structure Tms Rmn fD|D| !11326 System System "LessComp(0,0,0) r"30428 !r"~"32976 "35462 "p7312LastDate System `D|D| "36974 43250 !03:21:23 PM !31469 !true "37151 03:07:46 PM #11:38:16 AM "p7312Time Jan 27 1993 02:29:36 PM "07:14:35 PM "--------------------------------- --- Template Name: TextPick --- LATER --------------------------------------------------------------------------- --------------------------------------------------------------------------- send DoPage set syslockscreen to true set vBlueBack of this page to my pback1 if vblueback of this page is "show" show rectangle "BlueBack" of this background send background select rectangle "blueback" of this background set layer of selection to 1 send foreground else hide rectangle "BlueBack" of this background end if set vComback of this page to my pback2 if vComback of this page is "show" show group "ComBack" of this background else hide group "ComBack" of this background end if to handle leavepage hide group "txt1" set text of field "txt1" to null to handle buttonUp set vname to name of target set QT to """" set text of field "txt1" to null step i from 1 to my phwordscount if vname = i set vscript to "get textlinecount(my pf"&i&")" execute vscript set vscript to "set vtemp2 to textlinecount(my pf"&i&")" execute vscript if vtemp2 > 1 step j from 1 to vtemp2 set vscript to "get textline "&j&" of my pf"&i execute vscript set vscript to "set vtemp3 to textline "&j&" of my pf"&i execute vscript set vscript to "put "&QT&vtemp3&QT&" after text of field ""txt1""" execute vscript put crlf after text of field "txt1" show group "txt1" end else set vscript to "get my pf"&i execute vscript set vscript to "set vtemp to my pf"&i execute vscript set vscript to "set text of field ""txt1"""&" to "&QT&vtemp&QT execute vscript show group "txt1" end end if !z"graphicPick normal nner and Pagination L-L-L- Df4f4f4f4f4 BlueBack comback Banner Planning the Directory Tree Structure buttonup buttonup Do you want to exit the course? Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName seqno totno bmarkfile result revnum atmpt Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName seqno totno bmarkfile result revnum atmpt buttonup buttonup Find_Menu coursefile place Find_Menu coursefile place Index ButtonUp ButtonUp 0,100,0 component ponent ButtonUp ButtonUp 0,100,0 component Index buttonup buttonup 0,0,0 seqno buttonup buttonup 0,0,0 seqno buttonup buttonup 0,0,0 seqno buttonup buttonup 0,0,0 seqno buttonup buttonup \help pCaller vCaller place \help pCaller vCaller place Dialog dlgInit button bSearch,b19,TRUE button bGlossary,b21,TRUE button bGoTo,b22,TRUE button bTopMenu,b25,TRUE button bCancel,b20,FALSE dlgBox 524480,5,30,20,111,116,,,Options,8,Helv,bSearch,3.70,6.07,50.86,32.16,19,1342242816,128,Topic Search,0,bGlossary,57.87,6.07,50.86,32.16,21,1342242816,128,Glossary,0,bGoTo,3.70,42.26,50.86,32.16,22,1342242816,128,Go To Page,0,bTopMenu,57.68,42.17,50.86,32.16,25,1342242816,128,Main Menu,0,bCancel,31.54,83.61,50.90,12.31,20,1342242817,128,Cancel,0 ctrlID Options buttonup buttonup pCaller vCaller place buttonup buttonup pCaller vCaller place NE6:>E5 group id 247 of page id 317 pTemplate concept EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname Overview Street estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds gTextID 3030,1470,9285,6277 d;t;ppBounds EpTextPort ffield The Directory tree structure in NetWare v4.0 acts as a powerful tool to organize your resources. Proper planning ensures that your network fully utilizes the capabilities of NetWare v4.0. If you have a small network, you can set up a simple Directory tree using the defaults created during installation; but, if you have a large network, your Directory tree requires more planning. This lesson discusses the strategies you can employ to create an effective Directory tree structure for a large network. Q> Page 2 of 31 ry Tree Structure group id 460 of page id 318 pTemplate concept EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname ` ` ` ` ` x%q L o t ~ t Q L o t ~ t Q AAA!!!" ` ` ` ` L o t ~ t Q c AAA ` 8nq L o t ~ t Q 0po < Objectives estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds gTextID 3030,1470,9285,6277 ppBounds pTextPort ffield At the end of this lesson, you will be able to do the following: - Identify strategies for planning the top levels of your Directory tree. - Identify the best plan for the top level of a specified Directory tree. - Describe the placement of objects in a Directory tree. - Identify the best placement of objects in a specified Directory tree. Page 3 of 31 ry Tree Structure EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 7 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 392 ffield Strategy: Think Globally Design your Directory tree so that the company has shared access to resources -- think of a global database instead of individual databases on separate servers. To take full advantage of the global features of NetWare Directory Services (NDS), Novell recommends that you use only one Directory tree for your company. Database Database normal EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTextPort pTemplate concept Page 9 of 31% estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 393 ffield Strategy: Plan for Effective Information Flow The best Directory tree structures recognize the natural flow of information and shared resources within a company. Configure the tree to conform to the way people actually work and the resources they use, rather than just by their location on the organizational chart. Directory tree navigation is much easier and faster if you place resources close to those who use them most.se them most. I need a... I need a... I need a... *"a # r"i + & K P& % & K 4' EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname %P&l' pTextPort pTemplate concept Page 12 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 394 ffield Strategy: Provide Appropriate Centralization and Autonomy If you plan to use a centralized group as administrators for the Directory tree, use a flatter structure. To give more autonomy to groups in different parts of the Directory tree, consider increasing the number of levels of Organizational Units. j ` # n#F#k# Administrators Administrators Z$2$W$ Finance Admin. Sales Admin. R and D Admin. Finance Admin. Sales Admin. 2)` Y ~)` Y 4,` Y 6/` Y R and D Admin. mouseEnter buttonDown indexButton_change keyUp leavePage keyUp ptemplate 0,0,0 0,0,0 Do you want to exit the course? Would you like to leave a bookmark? bmark bookname pmark smark tmark result review revnum numrev revdes atmpt component tbkfile.dll review numrev revdes component BookName totno bmarkfile result revnum atmpt popup vTemplate seqno isCntrl isShift buttonDown hotword popup displayHotword vtext No definition for fpopup System vtext fPopup fPopup fPopup popup vLines fpopup popup vText mouseEnter hotword indexButton_change pHotTopics vGpage vGPage vPage vItem vTopic theSelf leavePage popup EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname H$r.r. pTextPort pTemplate concept Page 17 of 31 estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 4665,1470,9285,6270 gTextID group id 11 of page id 395 ffield Designating Container Objects The three types of container objects are Country, Organization, and Organizational Unit. You must include at least one Organization object in your Directory tree (other container objects are optional). You can create as many peer Organization objects as you need, and each can contain as many Organizational Units as you need. Organizational Unitttt Organizational Unitttt Organization: Organization: Country Country destroy buttonUp menuButton_change buttonDown buttonStillDown adjustBounds erted within pText pInverted pExcludeTab nverted pText pInverted pExcludeTab menuButton_change theSelf bButton bButtonID fField fFieldID fFieldID bButtonID fFieldID ppBounds pEnabled fFieldID set p of this page to my uniquename vBounds vText destroy set p of this page to null buttonUp ppEnabled within menuButton_change theLocation buttonDown ppEnabled pInverted buttonStillDown ppEnabled within pInverted pInverted theLocation within theObject theLocation pInverted bButtonID bButtonID theInverted pInverted ppInverted pText fTextID theText pText fTextID pExcludeTab bButtonID bButtonID theExcludeTab pExcludeTab bButtonID adjustBounds pNoAdjust ppBounds hatRevAmI EnterBook whatRevAmI LeaveBook whatRevAmI :Lesson Book Rev 1.19 bookname EnterBook seconds altkey sizetopage reader setSysBooks ppTotTry ppBancont ppLevel ppPlace PMark SMark TotNo TMark result revnum numrev revdes atmpt component normal svEnterTime svTotalIdle svStartIdle result revnum numrev revdes atmpt component level bmarkfile StartZ coursefile place bookname seqno totno bancont tottry LeaveBook MMM dd y hh:min:sec AMPM set vLastTime to p time of book bmarkfile set p LastDate of book bmarkfile to vLastDate set p Time of book bmarkfile to vDiff FromGoTo vLastTime vCommand vLastDate vDiff vTotal svEnterTime svLeaveTime svTotalIdle bmarkfile place title EnterPage whatRevAmI EnterPage DoPage whatRevAmI ptemplate :Rev 1.00 bookname whatRevAmI ptemplate :Rev 1.00 bookname pTemplate concept pTextPort Page 11 of 31 OU=R and D Printer Userr Userr Printer L $ I Userr Userr OU=R and D OU=R and D Printer Userr Userr Printer Userr Userr OU=R and D OU=R and D Printer Userr Userr Printer Userr Userr OU=R and D estroy destroy adjustBounds pText pText gTextID ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds pTextPort destroy pTextPort gTextID pText fText pText fText theText adjustBounds pNoAdjust ppBounds ppBounds 300,3750,9290,6270 gTextID group id 8 of page id 323 ffield Strategy: Plan for Consistency Consistency in structure and naming makes it easier for you to manage the network and troubleshoot network problems. If you plan to have network administrators at each site create their own portion of the Directory tree, consider providing standards for structure and names. Japan U. S.atesates France Japan z#R#w# U. S.atesates France Japan Japan