The document outlines guidelines for managing a real-world virtualization project, emphasizing the importance of a solid Statement of Work (SOW) and clear communication between client and technical teams. It highlights a sample project involving a 70,000 user XenApp setup, discussing project goals, constraints, assumptions, and configurations needed to achieve optimal performance. Additionally, it addresses advantages and disadvantages of using different Windows server versions within the project context.

1. Robert Morris – rmorris@agsi.usConsultantAdvantec Global Services IncLife In The Virtual TrenchesЗдравствуйте!

2. General Project GuidelinesAgendaReview real-world XenApp 70K user projectReview real-world “VDI” projectQuestions & (hopefully) Answer Session

3. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating of the SOWHave client write the SOWEnsure technical resources on both sides have reviewed the SOWOpen up the SOW first day on-siteEnsure both sides have firm understanding of project goals and success criteriaDiscuss terminology and different interpretations of same termsEnsure both sides have proper contacts in place for escalation

4. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating of the SOWHave client write the SOWEnsure technical resources on both sides have reviewed the SOWOpen up the SOW first day on-siteEnsure both sides have firm understanding of project goals and success criteriaDiscuss terminology and different interpretations of same termsEnsure both sides have proper contacts in place for escalation

5. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating the SOW

6. End-to-End VirtualizationArchitectureDomain ControllerXS1Web InterfaceData StoreXS2Desktop Delivery ControllerLicense ServerStorageSecure Remote AccessEdgeSightVirtual Machine InfrastructureDesktopReceiverProfile StoreXenAppVirtual DesktopAgentProvisioning Services

7. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating the SOW

8. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating the SOW

9. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating of the SOWHave client write the SOW

10. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating of the SOWHave client write the SOWEnsure technical resources on both sides have reviewed the SOW

11. General Project GuidelinesHold Executive Technical Briefing PRIOR to creating of the SOWHave client write the SOWEnsure technical resources on both sides have reviewed the SOWOpen up the SOW first day on-siteEnsure both sides have firm understanding of project goals and success criteriaDiscuss terminology and different interpretations of same termsEnsure both sides have proper contacts in place for escalation

12. Sample 70K user XA projectProject goalsDetermine the maximum user density per square foot attainable for a large Siebel roll-outProject constraintsTimelineInternal resource assignments from other groups (Siebel team, proj mgmt group, nw team)Hardware provided(1) DL580(2) DL380

13. AssumptionsA solid Siebel back-end platform for high interactive would be readily available throughout, using the Call Center HI QA environment for testingNetwork connectivity would remain solid throughoutWritten scripts existed for the high interactive platform, defining different user types and mix of types in a typical dayNumber of total users expected would be made availableNumber of users connecting at any one time would be made availableUnique user ids would be made available on the back-endAD user ids would be made available on the front-end

14. AssumptionsA solid Siebel back-end platform for high interactive would be readily available throughout, using the Call Center HI QA environment for testingNetwork connectivity would remain solid throughoutWritten scripts existed for the high interactive platform, defining different user types and mix of types in a typical dayNumber of total users expected would be made availableNumber of users connecting at any one time would be made availableUnique user ids would be made available on the back-endAD user ids would be made available on the front-end

17. Config ADL380 36GB MSTCTXAPP10 – Citrix PVS 5.6DL380 36GB MSTCTXAPP11 - W2K8 R2, XA6, 32GB PVS imageDL580 80GB MSTCTXAPP12 – XS 5.6 host running utility images 271 users can be achieved, and performance remains solid throughout. Memory appears to be the bottleneck, with the cpus showing very little stress, even during the mass logins.

18. Config B DL380 36GB MSCTXAPP10 – Citrix PVS DL380 36GB MSTCTXAPP11 – XS 5.6 host MSVTCTXAPP17,18,19,20,21,22,23,24– W2K8, XA5, 4GB PVS image guestDL580 80GB MSTCTXAPP12 – XS 5.6 host running utility images 342 users can be achieved, and performance remains solid throughout. Memory appears to be the bottleneck within a vm – 50 users appear to be a max number for reasonable performance of each vm. The cpus show no stress, even during the rapid logins.

19. AdvantagesWindows 2008 32-bitWindows 2008R2 64-bitTakes advantage of current hardware. Standard to 4 proc/32GB RAM, Enterprise to 8 proc/2TB RAM

20. Fewer images to manage

21. Fewer server lisc, both MS & 3rd party

22. Compatibility with most workstation applications

23. Staff more familiar with 32-bit OS

24. Staff more familiar with 32-bit applications