Microsoft Windows 7 Deployment in the Enterprise

Microsoft Windows 7 Deployment in the Enterprise

Introduction

• Aaron Slater – Systems Engineer

• Cameron Jameson – Senior Technology Support Officer

1. When was deployment started?

• Initial testing late 2009.

• Selective beta testing early 2010. Expanded throughout 2010.

• Fully operational early 2011.

2. What prompted you to start?

• Didn’t want to make the jump from Windows XP to Windows Vista.

• Windows 7 release date brought forward.

• Windows 7 met our requirements.

3. How many sites did you have to deal with?

• One primary site.

• Five secondary sites.

• Four international campuses.

4. How many workstations do you deal with?

• ~2000 staff workstations.

• ~800 student workstations.

5. What was your general software environment?

• Windows 7 32-bit.

• Core software listings.

• Difference between staff and student software deployment and availability.

6. What tools did you use?

• Initially Altiris Deployment Console.

• Migrated to Microsoft System Centre Configuration Manager 2007 (SCCM).

7. How did you determine the tools?

• Whitepapers and other peoples experiences.

• Economical.

• Met all requirements and had bonus features.

8. How well did the tools work?

• Operating system task sequence creation and alteration.

• Driver segmentation.

• Reporting services.

• Software metering.

9. How many staff were involved?

• One Manager.

• Two Systems Administrators.

• Two Desktop Support.

• One Client Support

10. How long did the deployment process take?

• ~15 months from commencement to completion.

• Continual improvement.

11. How was user impact minimized?

• Educate/train everyone.“The more we all know, the better.”

• Did WellEducated end user – Introduction to Windows 7

• Did Not Do WellDeployment staff not trained in how to use SCCM – didn’t know what to do, couldn’t use it

12. What worked well?

• Two main implementers.

• Communication within the project team.

• Regular meetings, constant communication.

13. What didn’t work so well?

• Problems with long schedules.

• Risks of short schedules.

• Logging can save the day.

14. What would you do differently?

• More documentation.

• Improved communication.

• Application compatibility.

15. What was the user feedback?

• From end user- Big positives due to Introduction to Windows 7

• From Deployment staff- Preferred Altiris’s GUI

- “Training would have been nice”

- Once trained, no problems

- Continue to work closely with Deployment staff and work towards improvements together

16. Conclusion

• Don’t fear the change.

• Manage the change.

• Be prepared.

• User education.