National Extension

1
National Extension Technology Conference - May
2002 - Purdue University Agriculture Information
Technology
2
Introduction

• Outline
• Setting up the situation
• Deployment preparations
• Deployment process
• Processes
• Issues
• Summary

3
Setting Up the Situation

• Remote locations to support
• 92 Counties
• 2 Satellite County Offices
• 5 District Offices
• 2 Ag Centers (Research Farms)
• Number of users
• 300 Educators/Admin
• 300 County staff

4
Setting Up the Situation

• Previous Environment
• Sun
• Servers
• X terminals
• postscript printers
• Dial on demand connections
• 10 MB LAN in office

5
Setting Up the Situation

• Drivers for change
• End user demands
• Software
• Peripherals
• Flexibility

6
Setting Up the Situation

• Current hardware count
• Hardware
• 683 computers (desktop laptops)
• 99 Servers
• 200 Printers

7
Setting Up the Situation

• Current Environment
• Standard Hardware (5 configurations)
• Standard Software
• Microsoft Active Directory
• Microsoft XP
• Local Area Network (LAN)
• State Backbone (WAN)
• Fulltime Connectivity / Leased Lines
• 21 T1Lines
• 78 56K Lines
• 1 DSL Line

8
Setting Up the Situation

• Why consider remote deployment?
• Total cost of ownership
• Return on Investment
• User demand

9
Setting Up the Situation

• Deployment History
• Desktops/Laptops (October 1999-April 2000)
• Connectivity (June-August 2000)
• Servers (March 2001-April 2001)
• XP Operating System (January-March 2002)

10
Setting Up the Situation

• Objectives
• To provide and discuss items that AgIT found
  critical in preparing for a successful remote
  deployment
• To provide and discuss issues that AgIT had to
  overcome before, during and after a remote
  deployment
• To provide best practice experiences

11
Desktop Deployment (October 1999 - April 2000)
12
Deployment Preparations (Desktops)

• Funding Investigation Phase
• Funding - Purdue University and local county
  government teamed
• First Year 85 counties 5 district offices on
  board
• Second Year all 92 counties on board
• Philosophy
• Standard supported equipment
• Corporate vs. consumer grade
• Reduce total cost of ownership/management
• Refresh of technology every 3 years
• Budget considerations

13
Deployment Preparations (Desktops)

• Funding Investigation Phase, cont.
• Tools
• What is available to make a deployment possible
  and successful?
• Ghost
• VNC
• Picture Taker
• ePolicy Orchestrator
• MS SMS
• Script programming

14
Deployment Preparations (Desktops)

• Establish / Create .
• Local Technical Coordinator (TC)
• Backup resources
• University root domain
• Training schedules
• Documentation

15
Deployment Preparations (Desktops)

• Develop technical procedures for .
• Automations
• Site specific configuration
• Agreement between TCs and AgIT
• Develop applications for .
• Web-based order/leasing
• Web-based tracking system

16
Deployment Preparations (Desktops)

• Develop training resources .
• Video (scanners server connections)
• Documentation
• Reference materials
• Provide needed items to vendor .
• Imaging process
• Configuration
• Delivery process
• Return information (MAC address, Serial )

17
Deployment Preparations (Desktops)

• Develop internal policies on .
• Hardware support
• Software support
• Disposing of old equipment (x-terms)
• End of lease equipment transition

18
Deployment Process - Desktops

• Desktop Deployment
• Product order, imaging and shipping
• Product ordered for each county
• Product information entered into tracking system
• Product prepped at vendor
• Product shipped from vendor to county

19
Deployment Process - Desktops

• Desktop Deployment, cont.
• Technical Coordinators (TC) perform local tasks
• Connection
• Power
• Video
• DVD
• Keyboard
• Mouse
• Plugged each desktop into network
• Follow a set of detailed procedures

20
Deployment Process - Desktops

• Desktop Deployment, cont.
• AgIT provides remote configuration
• Connect peripherals
• Set up Sun Servers
• DNS
• DHCP
• Samba
• IMAP mail
• Follow a set of procedures
• Machine name
• Join Windows domain

21
Deployment Process - Desktops

• Desktop Deployment Issues
• Password Synchronization
• SAMBA
• Unix
• Window
• LDAP
• Print drivers for legacy printers in UNIX
  environment
• Printer problems with specific applications
• Access rights on Unix file system from windows
  machines

22
Connectivity Deployment (June - August 2000)
23
Deployment Preparations (Connectivity)

• Funding Investigation Phase
• Funding Purdue University
• 500,000 (plus) in recurring funds
• Philosophy
• Standard supported equipment
• Services in addition to circuit
• Multi-cast
• Guaranteed quality of service
• IP video conferencing
• Etc.
• Reduce total cost of management
• Budget considerations

24
Deployment Preparations (Connectivity)

• Funding Investigation Phase, cont.
• Tools
• What is available to make a deployment possible
  and successful?
• UNIX Script programming

25
Deployment Preparations (Connectivity)

• Establish / Create .
• Relationships with IHETS
• Schedules
• Local Technical Coordinator (TC)
• Site surveys
• Documentation
• Develop technical procedures for .
• IP Address cut over
• Site specific configuration
• Agreement between TCs, AgIT, and IHETS

26
Deployment Preparations (Connectivity)

• Develop internal policies on .
• Troubleshooting techniques
• Big Brother
• Etc.
• Testing
• Sniffing
• Multicast
• Help desk procedures

27
Deployment Process - Connectivity

• Connectivity Deployment
• Negotiate pricing with vendor (IHETS)
• County completes site survey
• Local telephone company install circuit at all
  remote locations (demark)
• Local telephone company completes demark
  extension inside each office
• IHETS test each line
• IHETS provides installs network equipment

28
Deployment Process - Connectivity

• Connectivity Deployment, cont.
• Technical coordinator installs cable from IHETS
  switch to local area network (LAN)
• AgIT assigns address space
• DNS
• IP Address
• Reboot each client machine to grab IP address
• Connectivity Deployment Issues
• Scheduling delays

29
Server Deployment (March April 2001)
30
Deployment Preparations (Servers)

• Funding Investigation Phase
• Funding - Purdue University
• 250,000
• One time rollover monies for initial purchase
• Reoccurring funds from AgIT Supplies and Expenses
• Philosophy
• Standard supported equipment
• Corporate vs. consumer grade
• Reduce total cost of ownership/management
• Popular Windows technology

31
Deployment Preparations (Servers)

• Funding Investigation Phase, cont.
• Tools
• What is available to make a deployment possible
  and successful?
• Ghost
• Script programming
• Terminal Services

32
Deployment Preparations (Servers)

• Establish / Create .
• Local Technical Coordinator (TC)
• Backup resources
• University root domain
• Documentation
• Time zone list
• Schedule

33
Deployment Preparations (Servers)

• Develop technical procedures for .
• Automations
• Site specific configuration
• Agreement between TCs and AgIT
• Backup procedures and tape procurement

34
Deployment Preparations (Servers)

• Develop training resources .
• Video (server connections power supply)
• Documentation
• Reference materials
• Provide needed items to vendor .
• Imaging process
• Hardware configuration
• Delivery process

35
Deployment Preparations (Servers)

• Develop internal policies on .
• Hardware support
• Software support
• Disposing of old equipment (Suns)

36
Deployment Process - Servers

• Server Deployment
• Product order, imaging and shipping
• Product ordered and purchased by AgIT
• AgIT prepares and tests image
• Product prepped at vendor
• Product is shipped from vendor to county

37
Deployment Process - Servers

• Server Deployment, cont.
• Technical Coordinators (TC) perform local tasks
• Connections
• Video
• Keyboard
• Mouse
• Modem
• Plugged servers into network
• Follow a set of procedures
• Product key
• Computer name

38
Deployment Process - Servers

• Server Deployment, cont.
• AgIT provides remote configuration
• Connect peripherals
• Printers
• Modem
• Migrate services off of Sun to Window Servers
• File systems
• Email
• DHCP
• DNS
• Printer
• Logon services authentication

39
Deployment Process - Servers

• Server Deployment Issues
• Purdue University central Windows domain delay
• DNS policies
• ADS Forest design
• Server storage/warehousing
• Power supply failures

40
XP Operating System Deployment (January March
2002)
41
Deployment Preparations (XP)

• Funding Investigation Phase
• Funding - Purdue University MS Licensing
  Agreement
• Mass CD Burner
• Philosophy
• USB support
• Stability
• Usability
• Reduce total cost of ownership/management
• Remote control mechanisms

42
Deployment Preparations (XP)

• Funding Investigation Phase, cont.
• Tools
• What is available to make a deployment possible
  and successful?
• Ghost
• VNC
• ePolicy Orchestrator
• MS SMS
• Script programming

43
Deployment Preparations (XP)

• Establish / Create .
• Local Technical Coordinator (TC)
• File Transfer Utility to save users local data
• Scheduling
• Domain Group Policies
• Documentation

44
Deployment Preparations (XP)

• Develop technical procedures for .
• Automations
• User site specific configuration
• Agreement between TCs and AgIT
• Develop training resources .
• Documentation
• Reference materials

45
Deployment Preparations (XP)

• Develop internal policies on .
• Hardware support
• Software support
• Security

46
Deployment Process - XP

• XP Operating System Deployment
• Prepare image CD
• Test new software
• Test all hardware for dynamic image
• Apply Domain Group Policies
• AgIT shipped counties image on CD

47
Deployment Process - XP

• XP OS Deployment, Cont.
• TC loaded image on each machine
• TC site specific items (computer name, etc)
• AGIT completes site specific - peripherals
• MS SMS (Software Management Services)

48
Deployment Process - XP

• XP OS Deployment Issues
• Skipped Window 2000 upgrade
• Dot Matrix printers
• MS SMS
• Virus Scan / ePolicy Orchestrator Agent
• Support old MS Publisher 2000
• Data migration
• RAM / horsepower issues

49
Summary

• Overall Deployment Issues
• Test sites are extremely critical to success
• Local TC are vital
• Strong Collaboration with vendors, county office
• Not a one man show
• Scheduling adhering to schedule critical
• Upfront testing
• Rev up support/user services
• Continued bandwidth issues
• Communicate!

50
Summary

• Questions
• Contact Information
• Patrick Smoker, Interim Director
• pds_at_purdue.edu
• Brad Clayton, Team Leader Network/Systems
• bac_at_purdue.edu
• AgIT Web site with resources
• http//www.agriculture.purdue.edu/agit