190 likes | 345 Views
ITS Windows 7 Desktop. ITS project consultation Feb - Mar 2011 V1.2. Malcolm Days Mark Miners James Farnhill. Agenda. Project Overview Demonstration Discuss Implications Document Additional Requirements. Current Windows XP Desktop. Windows XP desktop
E N D
ITS Windows 7 Desktop ITS project consultation Feb - Mar 2011 V1.2 Malcolm Days Mark Miners James Farnhill
Agenda • Project Overview • Demonstration • Discuss Implications • Document Additional Requirements
Current Windows XP Desktop • Windows XP desktop • Pre-installed apps ( http://bit.ly/haEfjQ ) • Novell ZenWorks 7 to deliver additional apps • ITS desktop not used by some departments
Why change ? • Microsoft development for Windows XP has ended • Support for Windows XP security patches will end in 2014 • Hardware and software vendors are moving to support Windows 7 DOING NOTHING OR WAITING IS NOT AN OPTION.
Windows 7 Desktop • Windows 7 desktop (64-bit) • Pre-installed apps (MS Office 2010, etc.) • Microsoft App-V to deliver additional apps
Project Benefits • Students are arriving with Windows 7 installed on their PCs – having Windows 7 in work areas will improve the student experience • Using Windows 7 would help us get the most out of newer hardware (support for more memory) and applications (support for 64-bit) • App-V will mean most new applications can be packaged more easily and available more quickly than currently • Desktops should be more reliable as App-V reduces application conflicts • Improved security / Reduced support costs • Smaller number of different Windows desktop configurations • Improved ability to centrally manage Windows configuration
Project Outline • In Scope: • Creation of a standard Windows 7 desktop; • Gather more information about application usage across campus; • Identify any needs not met by the proposed standard desktop; • Creation of an App-V infrastructure to deliver applications; • Testing applications to establish which work and do not work; • Creation of a migration plan; • Rollout to student work areas; • [Optional] Rollout to one department. • Out of scope: • Complete rollout to the University (likely to be a separate project); • Software auditing; • Off campus access to applications.
Academic Staff *MyFiles can be used to access files through a web browser interface. • **Windows 7 offline folders will provide increased roaming functionality for files and folders. • % By default, users will not have the rights to install applications, but academic staff could request rights to do so. # Anyone can print to a network printer if they install the iPrint client and print to an ITS supported printer. + A laptop can be used if additional software is needed in a lecture theatre. $ Additional teaching software can be installed onto work area PCs by exception only.
Students *MyFiles can be used to access files through a web browser interface. # Anyone can print to a network printer if they install the iPrint client and print to an ITS supported printer.
Admin Staff *MyFiles can be used to access files through a web browser interface. • **Windows 7 offline folders will provide increased roaming functionality for files and folders. # Anyone can print to a network printer if they install the iPrint client and print to an ITS supported printer.
What will the Windows 7 technical proposals mean for Staff? • A laptop will work the same way on and off campus • A user could work locally on a PC if the network is unavailable • A user could run different versions of the same application delivered by ITS • Application settings will stop roaming. Cannot get ‘universal’ access to ‘my PC’ • The standard Windows desktop is not designed to support long running computation tasks (say > 18 hrs) • Windows applications can only access the ‘computing power’ available on the local PC • PC hardware older than 4 years is very likely to need replacing
What will the technical proposals mean for application deployment? • ITS will not be able to deliver Windows apps to non-windows PCs (Mac, Linux, tablets, smartphones, etc.) • ITS will not be able to deliver apps to thin client devices • ITS will not be able to tailor work area PCs to deliver specific courses • Some interaction between apps may be restricted by App-V • ITS may only deliver apps to UoW standard PCs or laptops • Apps which do not package with App-V (maybe 5%?) will need to be manually installed onto each PC Any additional requirements will need to be backed by a business case to the University
What are the service options for application deployment? • Apps not compatible with App-V will need to be locally installed. • If PC is re-imaged, local apps will need to be re-installed. The greater the instalation rights given to staff, the greater the support costs from malware and user mistakes Proposed option
Any additional implications for Students? • A student cannot access delivered applications from their own PC or other devices • A student cannot access delivered applications from off campus • Not designed to support long running computation tasks (need to stay at a work area PC) Any additional requirements will need to be backed by a business case to the University
Additional Questions • Would any staff like to be involved in user testing in June/July? • What applications are used and by how many users for each one? • What applications are a priority?
Final Questions • Any other questions?