1 How to Design Task 2 Author: Rodger Burgess 27th October 2008 © Copyright reserved

2

3 Introduction Author: Rodger Burgess 27th October 2008 © Copyright reserved

4 Deliverables Author: Rodger Burgess 27th October 2008 © Copyright reserved

5 Write Down the Deliverables What are you to DO and Document; 1.AD Structure 2.DNS 3.DHCP 4.Folder Structure 5.Global Groups 6.DomainLocal Groups with Full and Restrictive Rights 7.Each User’s Drive Mapping 8.Design the Network 9.Quote of ALL components of the Network 10.No Office Furniture is to be supplied within this project Author: Rodger Burgess 27th October 2008 © Copyright reserved

6

7 Users One could assume there are the following Users; 1 x Owner 1 x Personal Secretary 6 x Accounts 5 x Secretaries 1 x Office Manager Based on this, there are a total of 14 staff within this business Author: Rodger Burgess 27th October 2008 © Copyright reserved

8

9 Information Gathered All User have access to these OU’s and Folders User here ONLY have access to these OU’s and Folders Author: Rodger Burgess 27th October 2008 © Copyright reserved

10 Departments Lets Assume for this Tasks the Departments are as follows 1.Audit 2.Public_Comp 3.Group_Tax 4.Super Author: Rodger Burgess 27th October 2008 © Copyright reserved

11 OU & Folders Audit Public_Comp Group_Tax Super User_Home Groups - Global - DomainLocal OU StructurePossible Folders AdminAudit AccountsPublic_Comp PayrollGroup_Tax HRSuper OHSUsers_Home Policies Author: Rodger Burgess 27th October 2008 © Copyright reserved

12 Folder Structure AdminAudit AccountsPublic_Comp PayrollGroup_Tax HRSuper OHSUsers_Home Policies C:\DataAudit Public Group_Tax Super Users_Home Admin Accounts Payroll HR OHS Policies Author: Rodger Burgess 27th October 2008 © Copyright reserved

13 Folder Structure C:\DataAudit Public Group_Tax Super Users_Home Admin Accounts Payroll HR OHS Policies Lets assume that the current Folder Structure is adequate. Lets now look at 2 Users and see what possible Drive Mappings they will require. User 1: Owner The Owner could be allocated a total of 6 Drive Mappings User 2: Secretary The Secretary could be allocated a total of 7 Drive Mappings In both cases this is an excessive mount of Drive Mappings Author: Rodger Burgess 27th October 2008 © Copyright reserved

14 Folder Structure It would be very difficult for users to navigate through 6 to 7 Drive Mappings. Our task here is to restructure our Folder Structure so Users have no more than 4 Drive Mappings. Have a go and see what you can come up with. TIP By adding a Department and Staff folder could help. Author: Rodger Burgess 27th October 2008 © Copyright reserved

15 Folder Structure Have any luck. Here is what I think could achieve our goal. C:\ DataAdminAccounts Payroll StaffHR Policies OHS DepartmentsPublic_Tax Group_Tax Super Audit Users_Home Author: Rodger Burgess 27th October 2008 © Copyright reserved

16 Folder Structure New Folder Structure. Owner If we Share Admin, Departments, Audit and Users_Home and allow Inheritance that should achieve our goal. Secretary If we share Staff, Departments and Users_Home and allow Inheritance that should achieve our goal. Author: Rodger Burgess 27th October 2008 © Copyright reserved

17 Recapping To this point we have designed the AD and Folder Structure. We could design our Groups and Drive Mappings to suit. At this stage we are still uncertain as to the configuration of our Network. How many Workstations and what Server configuration will we implement. For us to develop our Drive Mappings we will need to know the names of our server/s I would suggest at this stage we design at least our Server/s. If this is the case then why not design the Network completely. Author: Rodger Burgess 27th October 2008 © Copyright reserved

18 Author: Rodger Burgess 27th October 2008 © Copyright reserved

19 Designing a Network Lets start at the beginning, we know there are 2 main types of Computer Networks. 1.Peer-to-Peer 2.Server There are also many configurations of these; Bus Star Mess Ring Author: Rodger Burgess 27th October 2008 © Copyright reserved

20 Designing a Network Lets look at the differences between these networks Peer-to-Peer Files are stored on each computer. Security can be limited. Duplication of resources such as printer, scanners can be difficult. Backups can be difficult to perform and schedule. Less costly to setup. Server Files are stored on the server/s. Security is by way of Unique Username and Password. Sharing of resources easier. Backups can be run and maintained from a central location. Expensive to setup and maintain. Author: Rodger Burgess 27th October 2008 © Copyright reserved

21 Designing the Network What type of Network do we require As a network Administrator, Engineer or Consultant ask yourself 3 real questions regarding installing a peer-to- peer or server centric network. That is; 1.Do you require Data sharing 2.Do you require Security 3.Number of staff using the network. If you require either 1 or 2, then a server centric system MUST be designed and installed If there are more then say 12 staff using the network then a server centric network should be installed due to its cost effectiveness. Author: Rodger Burgess 27th October 2008 © Copyright reserved

22 Designing the Network Remember our Network and Server Bottlenecks Your servers should be a powerful computer/s capable of handling all the work your network will throw at them. Don't cut corners by using a bottom-of-the-line computer that you bought at a discount computer store. No substitute for quality. Remember these: 1. Processor 2. Memory 3. Disk 4. Network card Author: Rodger Burgess 27th October 2008 © Copyright reserved

23 Designing the Network The Server's Configuration Options All network operating systems have options that you can configure. Unfortunately, no hard-and-fast rules exist for setting these options. Otherwise, you wouldn't have options. The following are some of the more important tuning options available for most servers: Virtual memory options, Disk striping, Network protocols, Free disk space on the server, Servers like to have plenty of breathing room on their disks. Author: Rodger Burgess 27th October 2008 © Copyright reserved

24 Designing the Network As we assessed from the information given there are 14 staff within AAA Accountants. Therefore a Server Centric system MUST be implemented. Based on this information we now need at least 14 Workstations. Lets assume that the architecture of these workstation are as follows. A good starting point. P4 2.6HzSoftware 1 GB of RamWindows XP 256 Meg Video Card Office HDD MYOB 10/100/1000 Nic In house Access Database Author: Rodger Burgess 27th October 2008 © Copyright reserved

25 Designing the Network A General Network Rule Workstations do 95% of there processing Server do 5% of the processing If this is the case then 20 workstation can be located on a network segment, if the server has the same architecture as the workstations. If we change the specification on the server to have more RAM, Faster HDD and CPU or a better motherboard then in theory we can have more workstations on that network segment. Author: Rodger Burgess 27th October 2008 © Copyright reserved

26 Designing the Network Other Factors to Consider RAID Amount of Storages space Amount of RAM Network distance (100m) Type of NIC Router or Switch Or just general network traffic Do the users do more right or read request of the servers Possible Server 1 Spec A starting point Quad Core 2.8mHZ 8Gb Ram 1050Mhz 2 x 500Gb HDD (RAID 1) 10/100/1000 Possible Server 2 Spec Quad Core 2.8mHZ 8Gb Ram 1050Mhz 2 x 1TB HDD (Files) 10/100/1000 Author: Rodger Burgess 27th October 2008 © Copyright reserved

27 Designing the Network We can split the work load of the 2 Servers into the following configuration; Server 1DNS, AD, DHCP and Exchange Server(All s and Permission are handled by this server) Server 2File Server (All files are stored on this server) The following slide will demonstrate how this can be achieved Author: Rodger Burgess 27th October 2008 © Copyright reserved

28 Designing the Network Author: Rodger Burgess 27th October 2008 © Copyright reserved

29 Author: Rodger Burgess 27th October 2008 © Copyright reserved

30 AAA Accountant Network Layout Media Cable required 1500m Wall Sockets 18 Author: Rodger Burgess 27th October 2008 © Copyright reserved

31 Author: Rodger Burgess 27th October 2008 © Copyright reserved

32 Setting Naming Convention Domain Name:………………task2.com Server 1:………………………exchange Server 2:………………………data Workstations:………………..WS-? Printers:………………………prtPrinterName Organisation Units:…………………………ouOrganistionUnitName Groups:………………………grpGroupName Global Groups:……………..grpGroupNameGlobal Domain Local Groups:………………………grpGroupNameDom User:………………………….useUsername Network Address:………… Custom Subnet Mask:………………………… Default Gateway:………… DHCP Scope Name:………..Task2 Scope DHCP Scope:……………… Default Gateway:…………… Author: Rodger Burgess 27th October 2008 © Copyright reserved

33 Author: Rodger Burgess 27th October 2008 © Copyright reserved

34 Group Structure Global Groups grpOwnerGlobal grpPerSecGlobal grpManagerGlobal grpAuditAccGlobal grpAuditSecGlobal grpGeneralAccGlobal grpGeneralSecGlobal DomainLocal grpAdminDomFull grpDepartmentsDomFull grpDepartmentsDomRestrict grpAuditDomFull grpUsers_HomeDomFull grpStaffDomFull grpStaffDomRestrict Rights (NTFS) Full = R&E, LFC, R Res = W, R&E, LFC, R, M Sharing Delete Everyone All DomainLocal groups have Full Rights here. Author: Rodger Burgess 27th October 2008 © Copyright reserved

35 Author: Rodger Burgess 27th October 2008 © Copyright reserved

36 Drive Mappings Data Server Drive Mappings default.bat \\data\netlogon\%username% A Users Drive Mappings net use z: \\data\Department net use y: \\data\Staff net use x: \\data\Users_Home Owners Drive Mappings net use z: \\data\Admin net use y: \\data\Departments net use x: \\data\Audit net use w: \\exchange\User_Home Author: Rodger Burgess 27th October 2008 © Copyright reserved

37 Author: Rodger Burgess 27th October 2008 © Copyright reserved

38 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 Author: Rodger Burgess 27th October 2008 © Copyright reserved

39 Designing the Network Exchange Data (Alterative) Switch 16 Port WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 Author: Rodger Burgess 27th October 2008 © Copyright reserved

40 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 Gateway Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

41 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 Gateway Printer 1 Printer 2 Printer 3 Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

42 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Printer 1 Printer 2 Printer 3 Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

43 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Exchange Server DNS AD DHCP Data Server All Business Data is to be stored here Printer 1 Printer 2 Printer 3 Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

44 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Exchange Server DNS AD DHCP Data Server All Business Data is to be stored here Printer 1 Printer 2 Printer 3 Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

45 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Exchange Server DNS AD DHCP Data Server All Business Data is to be stored here Printer 1 Printer 2 Printer 3 Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

46 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Exchange Server DNS AD DHCP Data Server All Business Data is to be stored here Printer 1 Printer 2 Printer Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

47 Designing the Network Exchange Data (Alterative) WS 1 WS 2 WS 3 WS 6 WS 4 WS 5 WS 7 WS 8 WS 9 WS 10 WS 13 WS 11 WS 12 WS 14 aaa.com Servers Names Gateway Exchange Server DNS AD DHCP Data Server All Business Data is to be stored here DHCP Scope: : 75 Printer 1 Printer 2 Printer Switch 16 Port Author: Rodger Burgess 27th October 2008 © Copyright reserved

48 Author: Rodger Burgess 27th October 2008 © Copyright reserved

49 What have we Designed Author: Rodger Burgess 27th October 2008 © Copyright reserved

50 What have we Designed Author: Rodger Burgess 27th October 2008 © Copyright reserved

51 What have we Designed Author: Rodger Burgess 27th October 2008 © Copyright reserved

52 Author: Rodger Burgess 27th October 2008 © Copyright reserved

53 Author: Rodger Burgess 27th October 2008 © Copyright reserved

54 Author: Rodger Burgess 27th October 2008 © Copyright reserved

55 What do we Need Author: Rodger Burgess 27th October 2008 © Copyright reserved

56 What do we Need Author: Rodger Burgess 27th October 2008 © Copyright reserved

57 Quote Author: Rodger Burgess 27th October 2008 © Copyright reserved

58 Quote Author: Rodger Burgess 27th October 2008 © Copyright reserved

59 Quote Author: Rodger Burgess 27th October 2008 © Copyright reserved

60 Author: Rodger Burgess 27th October 2008 © Copyright reserved

61 Author: Rodger Burgess 27th October 2008 © Copyright reserved

62 Author: Rodger Burgess 27th October 2008 © Copyright reserved

63 Author: Rodger Burgess 27th October 2008 © Copyright reserved

64 Author: Rodger Burgess 27th October 2008 © Copyright reserved

65 Author: Rodger Burgess 27th October 2008 © Copyright reserved

66 Author: Rodger Burgess 27th October 2008 © Copyright reserved Our Network Drawing

67 Author: Rodger Burgess 27th October 2008 © Copyright reserved

68 Network Structures Author: Rodger Burgess 27th October 2008 © Copyright reserved New Scenario The goal in the exercise is to delete, move or change accounts.sydney.rodger.com and create a child domain of rodger.com that will cater for 3 other servers. These servers have to be on a different Network Address from the 3 servers currently in place. These 3 servers will deal with; 1. Accounts Payable 2. Accounts Receivable 3. Wages What would you come up with !!!!

69 Network Structures rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer Author: Rodger Burgess 27th October 2008 © Copyright reserved accounts.sydney.rodger.com Managed Switch Accounts.SydneyServer:

70 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com Author: Rodger Burgess 27th October 2008 © Copyright reserved Router Move accounts.sydney.rodger.com to here and rename it to admin.rodger.com

71 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable. admin.rodger.com accpayable.admin.rodger.com wages. admin.rodger.com Author: Rodger Burgess 27th October 2008 © Copyright reserved Router Now add 3 Child Domains Server of admin.rodger.com.

72 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router Author: Rodger Burgess 27th October 2008 © Copyright reserved Router

73 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer DNS: admin.rodger.com IP: DHCP: Scope accrecivable: to Scope accpayable: to Scope wages: to Subnet Mask: Author: Rodger Burgess 27th October 2008 © Copyright reserved

74 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer Author: Rodger Burgess 27th October 2008 © Copyright reserved Router DNS: admin.rodger.com IP: DHCP: Scope accrecivable: to Scope accpayable: to Scope wages: to Subnet Mask:

75 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer Author: Rodger Burgess 27th October 2008 © Copyright reserved Router DNS: admin.rodger.com IP: DHCP: Scope accrecivable: to Scope accpayable: to Scope wages: to Subnet Mask:

76 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer Author: Rodger Burgess 27th October 2008 © Copyright reserved DNS: admin.rodger.com IP: DHCP: Scope accrecivable: to Scope accpayable: to Scope wages: to Subnet Mask: to to to Router

77 Network Structures rodger.com admin.rodger.com sales.rodger.com sydney.rodger.com melbourne.rodger.com accreceivable.admin.rodger.comaccpayable.admin.rodger.comwages.admin.rodger.com Router DNS: rodger.com IP: DHCP: Scope Sales: to Scope sydney: to Scope melbourne: to Subnet Mask: to to to SalesServer: SydneyServer: MelbourneServer to to to ReceivableServer: WagesServer: PayableServer: Author: Rodger Burgess 27th October 2008 © Copyright reserved Router DNS: admin.rodger.com IP: DHCP: Scope accrecivable: to Scope accpayable: to Scope wages: to Subnet Mask:

78 Author: Rodger Burgess 27th October 2008 © Copyright reserved