File System Project Conversion from Netware to Windows December 2010

1. File System Project Conversion from Netware to Windows December 2010

2. File System Upgrade • So many questions to answer: What about Mac users? Will the server names change? Why are we doing this project? What do I need to do? What is going to be different for me? When will changes happen? How will I login? How will I access my shared folders? What will I get out of it? What drive mapping will I use? Will I get more space? What is DFS? Will my data be backed up? What about wireless and VPN access? Will I do things differently? Will I still have all my files?

3. Agenda • Project Drivers • Benefits • File System Environment • DFS Namespaces • Changes & Impacts • Timeline • Questions & Feedback

4. Project Drivers • Mission Critical System • Five years since last file system upgrade • Aging server hardware • Disk space is full • Requires high availability

5. Benefits • Updated architecture • New server hardware • SAN connectivity • Built on Microsoft platform • Designed for high availability • Microsoft clustering • SAN data replication

6. Benefits • Quota increase • Approximately doubling capacity for each college or administrative division • Additional 5 GB quota for individual departments • Users get 3 GB quota separate from the departments

7. Benefits • Desktop client reduction • No extra client on the desktop • No licensing fees for Novell products • Drive mapping consolidation • Single drive letter for all data (Windows desktops) • Ability to add additional servers without adding additional drive letters

8. Benefits • Anti-virus scanning • New servers will have virus scanning running • Provides protection where desktop anti-virus is out of date.

9. Benefits • Accessibility • The new environment will be available using the same methods as currently used. • On campus wired & wireless • Off campus – using the VPN client

10. File Server Environment

11. File Server Environment

12. DFS Namespaces • Sample servers and folders

13. DFS Namespaces • DFS provides an abstraction of the server layer and displays all folders under a single drive mapping. • Users only see information under the folders where they have access • Drive mappings are relevant only to Windows desktops

14. DFS Namespaces • Ability to add additional servers and reference them under the same drive letter

15. Changes & Impacts Change Impact Anything using J, K, L, or M Desktop shortcuts MS Office Suite Default file locations Recently used list Desktop applications Scripts Databases Embedded links Documentation • Mapped data drive letter • Single drive for all data ( N:\) • J:\, K:\, L:\, M:\ go away

16. Changes & Impacts Change Impact Users will need to establish connections to the new server for their folders One time process Works the same as before after re-establishing connection • Current Macintosh folder connections • Mac users connect to a server\volume • There is no drive letter assigned • Shows up as a folder

17. Changes & Impacts Change Impact Universal Naming Convention (UNC) mapping Mapping to a file location based on server name Desktop drive mapping (Windows desktop) Desktop folder connections (Mac desktop) Documentation referencing the NWDATA or NWLAB servers • File Server Name

18. Changes & Impacts Change Impact Anything referencing a file in your current user directory Desktop shortcuts MS Office Suite Default file locations Recently used list Desktop applications Scripts Databases Embedded links Documentation • Introduction of user “Home” folders • N:\UserA-F\e-id • N:\UserG-L\e-id • N:\UserM-R\e-id • N:\UserS-Z\e-id

19. Changes & Impacts Change Impact All administrative department and college folder names will be visible. Users will not be able to access folders unless they have appropriate permission Extra visibility will be removed when we no longer need to support 2003 Active Directory services. • Visibility of top level folders • DFS only (Windows desktop)

20. Changes & Impacts Change Impact Departmental Increase Direct increase of space Indirect increase by moving user folders to new home directories User specific quotas Filling up personal space will not affect departmental space • Quota Increase for departments • Separate department and user quotas

21. Changes & Impacts Change Impact Users are notified when saving an infected file Infected files are quarantined Login screen will change If Novell is your current primary login Single login to desktop & files If you currently login to Windows and then start the Novell client separately • Server-side virus scanning • Removal of Netware client (Windows desktops)

22. Timeline • Begin migrations in late January or early February • Three migrations • One for each of our data servers • Each migration will take place over a weekend • Lab services migrations after graduation

23. Questions and Feedback Questions Feedback What other impacts can you identify? What will help you prepare for this migration? • What else would you like to know about this?