guideit customer success criteria guide

GuideIT Proprietary and Confidential. © 2014 GuideIT Inc. All Rights Reserved. GuideIT or its affiliates and are registered in the USA and other countries. All other trademarks are the property of their respective owners.

.

GuideIT Customer Success Document

Submitted to:

CUSTOMERA

Submitted by:

Brian Murphy

GuideIT

<DATE>

2 GuideIT Proprietary and Confidential. © 2014 GuideIT Inc. All Rights Reserved. GuideIT or its affiliates and are registered in the USA and other countries. All other trademarks are the property of their respective owners.

Table of Contents

1 Overview ...................................................................................... 3

1.1 Summary ................................................................................ 3

2 Pre-Implementation Requirements ............................................... 3

2.1 Pilot Deployment .................................................................... 3

2.2 Active Directory Integration Requirements ............................. 4

3 Data Center Requirements ......................................................... 11

3.1. Data Center Network Requirements ........................... 12

3.2. Physical Data Center Requirements On-Premises .. 12

3.3. Cabling Requirements .................................................. 13

3.4. Virtual Private Networking Requirements ................. 13

3.5. Onsite Engineer Visitation ........................................... 15

3.6. Remote Access Requirements .................................... 15

3.7. Change Control Requirements .................................... 16

4 Client Applications ...................................................................... 16

5 Virtualization Pilot User Data Migration ...................................... 18

6 Integration Questions ................................................................. 19

7 Success Criteria ......................................................................... 20


1 Overview This GuideIT Customer Success document describes the deployment pre-requisites, implementation, and configuration processes. The intent of this document is to properly convey customer requirements pre-implementation, during implementation, and post implementation. The requirements stated in this document define the criteria for success. The customer requirements (action items) are not optional but in fact are required for successful implementation.

1.1 Summary Over the course of the next few weeks, <CUSTOMERA> plans to implement a pilot Virtualization service to test and validate the Virtualization on-premises virtual desktop solution. As part of this pilot, an infrastructure will be installed at the customer data center located in <LOCATION>. Success of pilot requires integration with the customer network, customer Active Directory, customer DNS, and other stated requirements contained herein. The pre-requisites defined in this document are the minimum requirements necessary to provide a functional pilot. Defining the customer requirements and providing this information prior to implementation provide information that is critical to the pilot success and a window of opportunity for the appropriate subject matter experts to review; thereby, providing all the necessary technical content required to engage change management. In addition, this document is multi-purpose in that it contains requests for information for purposes of understanding the environment, applications, authentication, or other areas of interest or concern that impact our ability to deliver a successful pilot. Completion of the pre-requisites and providing the requested information are critical to our ability to implement a customer on-premises pilot. In addition, the sooner GuideIT receives the requested information and requirements are implemented has a direct impact on our ability to implement a successful and timely pilot.

2 Pre-Implementation Requirements The sections that follow summarize the customer pre-implementation requirements necessary to participate in the “Virtualization Pilot Program”. Please read each section carefully and provide the requested information. Pre-implementation for purposes of this document refers to the customer action items listed in the sections that follow. In summary, the Virtualization implementation team cannot integrate the pilot solution until all pre-implementation requirements are complete. Success criteria for completion are each section is completed and documented per instruction and post-completion this document returned to the “Virtualization Pilot Program” project manager.

2.1 Pilot Deployment Virtualization Pilot Program is more in-depth than a simple proof of concept; our solution provides a scaled down version of production thereby allowing for real world production workloads, application validation and user feedback. A pilot deployment provides a quick and easy way for our customers to preview the features and benefits of the “Virtualization Virtual Desktop Solution” leveraging a subset of customer line-of-business applications.


2.2 Active Directory Integration Requirements

GuideIT Virtualization Architect Resources:

An Active Directory engineering customer resource with full Domain permissions is required to assist with this implementation and represent the customer interests. GuideIT will perform the majority of the changes; however, there are often situations that will require more permissions or additional approvals by the customer Active Directory team. Please provide the required contact information below:

Customer AD Engineering Resource(s):

The GuideIT Virtualization resource requires a dedicated customer Active Directory subject matter expert that has full rights in Active Directory to assist with the initial setup and configuration of the VDI architecture components and afterwards available as needed to assist with additional requirements or issues. If possible, provide two contacts for primary and secondary.

Please provide the required contact(s) information below:

Change Control Representative (can be same as AD resource):

The Virtualization implementer will be required to follow change control procedures during this change. Please provide a resource that will be assisting the Virtualization implementer with the AD change control requirements. If the Active Directory engineering resource can provide change control requests, this would be the preferred approach.


C

OU Dedicated to Virtualization:

GuideIT AD Resource(s) – Required

Name Contact Phone Contact Email

Customer AD SME – Required


Primary

Secondary

Customer Change Control Representative – Required



An Active Directory organizational unit dedicated to Virtualization must be created. This OU should have “Block Policy inheritance” enabled. Please provide the distinguished name for the newly created OU. For example: /Virtualization

Virtualization Architect will require a summary of Group Policies (GPO) that the customer requests to be recreated under the new Virtualization OU. GuideIT will deploy standard Virtualization policy settings and then evaluate the provided policies to determine if they can be recreated at the Virtualization OU level. These should be limited to a small number of specific global settings.

The following policy settings are provided as an example:

Customer Required Information:

Policy Setting

Scope

Path


Policy Setting

Scope

Path


Policy Setting

Scope

Path

Virtualization Implementation Engineers/Administrators:

An account with remote access will be required for the Virtualization implementation engineers, which can potentially include SME resources from Citrix, network, storage, and hardware. Security and audit constraints require the customer issue named accounts – generic accounts are not an option. The assumption is that the issued accounts utilize the customer naming convention but certain accounts do require special rights in Active Directory to install components, configure infrastructure, create GPO’s, et cetera – see below.

Customer Requirement: Virtualization Citrix VDI Administrator

Virtualization Citrix Administrator Brian Murphy

Active Directory User ID

Active Directory Password

Permission Requirements

Remote Access

Full control permissions to the Virtualization OU and all subordinate containers

Permissions to create new GPOs and delegate new GPO permissions

Permissions to create user, group, and computer accounts under the Virtualization OU

Permissions to create service accounts under the Virtualization OU

Customer Requirement:

Virtualization Citrix VDI Administrator

Virtualization Citrix Administrator Rudy Peev

(Example) GPO to be created in Virtualization OU Policy Setting Interactive logon: Message text for users attempting to log on

Scope Machine

Path Computer Configuration\Windows Settings\Local Policies\Security Options

GPO to be created in Virtualization OU







Remote Access

Full control permissions to the Virtualization OU and all subordinate containers

Permissions to create new GPOs and delegate new GPO permissions

Permissions to create user, group, and computer accounts under the Virtualization OU

Permissions to create service accounts under the Virtualization OU

Customer Requirement:

Virtualization Network Engineer

Virtualization Citrix Administrator Sanjay Basu




Remote Access

Active Directory Groups:

For ease of administration, Active Directory Global group(s), which contain the list of users authorized for Virtualization desktop access should be created. For production rollouts, GuideIT recommends role based security model. For example, “CC Lab Tech” or “5W Nurses” would be role groups. These groups will be nested in the appropriate domain local groups which provide access to desktops. The Virtualization implementer will create virtual desktop and resource domain local groups within the Virtualization OU; however, Virtualization will not be responsible for the role based groups or the security access request process. Please provide the name of global group(s) identified for access to the Pilot desktops.

Entitlement Group Name(s):

Role Based Group Name Group Type

Domain Global Group

Domain Global Group

Domain Global Group

Active Directory Naming Standard

Fully Qualified Domain Virtualization virtual desktop infrastructure requires your fully qualified domain name for servers and desktops that are joining the domain. This information is required for proper integration with your Active Directory. This FQDN should match the root DN (Distinguished Name) of the root domain that contains the Virtualization VDI resources. Please provide this information below;

Fully Qualified Active Directory Domain Name

Server Naming Convention Virtualization leverages a custom naming convention for infrastructure roles. If you require a specific naming convention to identify servers on your network, please provide the naming convention. By default, Virtualization will use the following naming convention:


Virtualization Infrastructure Role – Default Naming Convention

Server Name Infrastructure Role

Virtualization-FS01 Virtualization Infrastructure Role

Virtualization-XDC01 Virtualization Infrastructure Role

Virtualization-ZDC01 Virtualization Infrastructure Role

Virtualization-XD-XML01 Virtualization Infrastructure Role

Virtualization-ZDC-XML01 Virtualization Infrastructure Role

Customer Infrastructure Roles – Requested Naming Convention

Server Name Infrastructure Role

Virtualization Infrastructure Role





Virtual Desktop Naming Convention Virtual desktop systems are created and deployed as needed through the use of desktop catalogs and machine pools. The dynamic desktop creation requires a computer name be assigned to each virtual desktop. The computer name prefix will be used, along with a numerical suffix to dynamically generate the virtual desktop computer names. Example: Virtualization generating Virtualization01, 02, 03 ….etc. If you would like to request a specific naming convention to identify desktops on your network please provide the computer name prefix to be used.

Virtual Desktop Naming Convention - Prefix

Desktop Group Naming Prefix

DHCP Requirements: Virtualization will require a dedicated IPv4 DHCP scope that aligns with the virtual desktop subnets requested by the Virtualization network team. In addition, Virtualization may require additional scope options defined at the scope level. This is not always the case but if required the Virtualization Implementer will provide this information to the customer DHCP resource. Following is a summary of Virtualization DHCP requirements:

DHCP Scope Requirements

This scope can be standalone or AD integrated; however it must be authorized in AD

The DHCP assigned segment must allow for dynamic update

DHCP lease is set for 3 days

IPv6 DISABLED on the new Virtualization network

Exclusions for infrastructure role IP4 addresses

2 x /23 networks – <CUSTOMERA> Pilot for 300+ seats

Please provide the new DHCP scope:

DHCP Scope Information

DHCP Client Network Range DHCP Server IP Address


Virtualization implementer will require exclusions within the DHCP scope. Virtualization implementer will work with the DHCP resource to define these exclusions. This resource can be the same as the AD resource.

DNS Requirements:

Virtualization requires that DNS Non-Refresh Interval set to 1 day and Refresh Interval set to 2 days. Non-refresh interval is the period of time where the timestamp set against a DNS record will not be reset due to a standard refresh message being received. Refresh interval is the period of time in which a refresh message from a client will reset the timestamp of a record. Virtualization requires dynamic updates for the virtual machine accounts and a reverse lookup zone configured for the client IP network allocated for the virtual machines. This is required for registration of the virtual desktop with the infrastructure controllers. Following is a summary of Virtualization DNS requirements:

DNS Requirements

Requirement Description

Non-Refresh Interval is set to 1 day

Refresh Interval is set to 2 days

Dynamic Updates Required for virtual desktops

Forward Lookup Zone Required for infrastructure and virtual desktops

Reverse Lookup Zone Required for the allocated client subnet

If these settings are compatible with your environment, please provide the required DNS information for the Virtualization configuration.

Active Directory Functional Levels:

Virtualization requires that all domains containing XenDesktop Controllers and virtual desktop computer accounts must be at "Windows 2000 native" functional level or higher. All forest functional levels are supported. Please provide functional level of the AD domain for Virtualization.

DHCP Resource Contact Information

Name Contact Information

DNS Information

DNS Servers

DNS Zones

Notes / Comments

AD Functional Levels Information

Forest Functional Level

Domain Functional Level

Notes / Comments


Active Directory Trusts:

Virtualization requires forest-to-forest level bidirectional trusts and two-way trusts between all authentication domains. Authentication domains contain user accounts that require access to the virtual desktop solution. Please provide details for the AD trust configuration.

Active Directory Sites:

Virtualization on-premises pilot solutions require an Active Directory site defined in the customer domain that hosts the VDI infrastructure. In addition, a duplicate site matching the name of the original must be defined in each forest/domain where those users are accessing the pilot environment. If the users are located in one domain then a Site should exist with one or more domain controllers that are closest in proximity to the VDI environment. Best case scenario is to have at least two domain controllers defined in the site and the domain controllers reside at the same location on the same physical LAN. If users reside in a different location and require access to the pilot environment we require a Site created with the same name as the VDI hosting domain and domain controllers from the hosting domain that are closest in proximity. In a production scenario the customer should consider at least one domain controller from the hosting domain at each location unless the intent is to utilize a decentralized VDI solution where each location hosts a dedicated VDI solution. Please provide the AD Site information in the section provided below:

S

AD Trust Information

Forest Trusts

Domain Trusts

Notes / Comments

AD Site Information

Site(s) Name

New Domain Controller Names

Notes / Comments


Active Directory GPO Central Store:

Virtualization requires implementation of a Windows 2008 Group Policy Central Store. This requires folders and files to be created or copied to the PDC Emulator. The Virtualization implementer or the customer AD resource can perform this change; however the files and folder structure will be provided by the Virtualization Implementer.

S

Windows User Logon Profiles:

Virtualization will use folder redirection for areas that are accessible to the user accounts. Roaming Profile settings will be stored using Citrix User Profile Management; however, these settings will not roam outside of the Virtualization environment, between XenDesktop and XenApp servers, or between different Operating Systems. (e.g. Windows XP and Windows 7).

AActive Directory Folder Redirection:

Most folders capable of folder redirection are redirected to the user home folders and excluded from the profile. A list of redirected and excluded folders is available upon request. The customer is responsible for any required data migration from the physical PC not covered by Folder Redirection. In addition, the customer is responsible to provide a “Data Migration SME” to assist with data migration tasks. Please provide special/custom folder redirection requirements in the section provided below:

AD GPO Central Store Information

PDC Emulator Server Name

Notes / Comments

User Profile Information

Profile Requirements

Notes / Comments

Folder Redirection Information

Folder Redirection

Folder Exclusion

Notes / Comments


S Please provide the required contact(s) information below:

Service Account Requirements:

The Virtualization implementer will create additional OUs, groups, users, computer accounts within the Virtualization OU. The Virtualization implementer will also create new GPOs and import standard Virtualization settings. These GPOs will be linked to the Virtualization OU or subordinate OUs. The Virtualization implementation team will create required Virtualization service accounts. The service accounts reside in the dedicated subordinate OU. Service accounts have the following attributes:

Active Directory Login Scripts

Virtualization virtual desktop solution requires an isolated environment and utilizes customized group policy configuration to maximize performance and alleviate login scripts or domain policies incompatible with a read only streamed desktop methodology. However, we understand that some users or business units might require access to data located on customer hosted file servers. To meet this requirement we provide support for drive mappings. If required, please provide the information below:

3 Data Center Requirements <CUSTOMERA> is “on-premises” implementation, which requires multiple data center resources from the customer to assure completion of Virtualization requirements; including but not limited to data center

Customer Data Migration Subject Matter Expert (SME)


Primary

Secondary

Complex/Randomized Password

Cannot change password

Password never expires

Login Scripts

Login Script Name Important Notes


space allocated for the physical hardware. This section provides critical information regarding data center requirements. Please review each section and complete applicable sections. Virtualization Administrators will create virtual machines and run these on the pilot servers. The client network will need the same access and restrictions as typically provided to any other client device network. Routing, firewalls, and internet connectivity are examples of items to consider.

3.1. Data Center Network Requirements Virtualization Citrix VDI Administrators and Virtualization Implementation Engineers require information for all networks that access the Pilot environment. Please provide preliminary information below:

S S

3.2. Physical Data Center Requirements On-Premises <CUSTOMERA> is “on-premises” implementation, which requires multiple data center resources from the customer to assure completion of Virtualization requirements; including but not limited to data center space allocated for the physical hardware. Pilot utilizes a VPN tunnel to access the environment remote for purposes of finalizing the customer configuration and resolving technical issues. Production phase utilizes <CUSTOMERA> standard network provider.

The GuideIT Virtualization Architect requires a dedicated customer allocated resource with access to the data center. The “Data Center SME” has full access to the data center and is our primary resource for accessing the data center.


Network TCP/IP Information

Subnet(s)

Subnet Mask

Default Gateway

Primary DNS Server

Secondary DNS Server

Primary DNS Zone (FQDN)

DNS Service Information

WINS Server

Notes / Comments

Customer Data Center Subject Matter Expert (SME)



Following is a list of pre-requisite requirements expected prior to Virtualization implementation team arrival.

3.3. Cabling Requirements <CUSTOMERA> is “on-premises” implementation, which requires multiple data center resources from the customer to assure completion of Virtualization requirements; including but not limited to data center cabling.

The GuideIT Virtualization Architect requires a dedicated customer allocated cabling resource with access to the data center and full knowledge of the data center cabling requirements. The “Data Center Cabling SME” has full access to the data center and is our primary resource for cabling questions or issues.


3.4. Virtual Private Networking Requirements

GuideIT VPN Engineering Resource:

C

Customer VPN Engineering Resource:

A customer VPN engineering resource must be provided to assist with this implementation and represent the customer interests.

Primary

Secondary

Requirements

# Description Status

1 Data center space allocated

2 Rack assignment

3 Power allocated

Customer Data Center Cabling SME


Primary

Secondary

GuideIT VPN SME – Required


Customer VPN SME – Required


C

Virtualization VPN Information:

Please provide the following VPN information:

VPN Information

Preshared Key To be provided over the phone.

Local IP (GuideIT Cloud): GuideIT will provide

Remote IP (DuPont):

Virtualization subnet (GuideIT Cloud):

Remote subnet (DuPont):

Virtualization VPN Encryption Parameters:

Virtualization uses the Vyatta VPN virtual software to establish VPN connectivity. Virtualization VPN will be created with the following parameters:

IKE Phase 1

Encryption algorithm Authentication algorithm Diffie-Hellman group

Proposal 1

AES128 MD5 2

Proposal 2

NA NA NA

IKE Phase 2 (ESP)

Proposal 1

AES128 MD5 NA

Proposal 2

NA NA NA

Additional Settings

Key lifetime 86400

PFS Disabled

Please provide alternate parameters if needed:

IKE Phase 1

Encryption algorithm Authentication algorithm Diffie-Hellman group

Proposal 1

Proposal 2

IKE Phase 2 (ESP)

Proposal 1

Proposal 2

Additional Settings



Key lifetime

PFS

3.5. Onsite Engineer Visitation To alleviate any confusion and expedite access to the <CUSTOMERA> facility requires a contact person at the physical location documented in this section. We recommend a primary and secondary contact to prevent any delay if the primary contact is not available at time of arrival. In addition, please describe any special access requirements that might prevent access such as “driver’s license required for access”. Please provide the listed contacts information pertaining to the visit. Please advise the contact(s) our engineers might contact them. Please provide customer Site Contact information below: Customer Information:

Please provide address and special details such as building description, color of building, number of levels, name of building, et cetera. Anything you can think of that might save time for those who are unfamiliar with the area. Customer Information:

Please provide special access instructions such as anything that might prevent access to the facility. Example: Driver’s license required and retained during visit. Customer Information:

3.6. Remote Access Requirements The Virtualization Implementation engineer can utilize remote access to the <CUSTOMERA> network to implement AD changes prior to availability of the VPN tunnel. If available and permitted, utilization of the customer remote access solution serves two purposes:

1. Enables the Virtualization engineer to start customizing the environment pending setup of the GuideIT VPN Tunnel

2. Provides a secondary backup access option for the Virtualization engineer Customer Information:

Remote Access Access Requirement Description VPN Access:

Citrix Portal URL:

Other:


Site Address Important Details

Building Access Requirements


3.7. Change Control Requirements Virtualization will require access to the Change Control Coordinator(s) for change control planning and approvals. Virtualization leverages <CUSTOMERA> Change Control process for changes that affect systems external to the Virtualization framework. Changes limited to the Virtualization framework mandate the Virtualization Engineer utilize Virtualization Change Control system. Please provide contact information of the assigned Change Control Coordinator. If possible, provide a primary and secondary contact and notify these individuals that someone from Virtualization will contact them. Customer Information:

4 Client Applications Pilot is more in-depth than a simple proof of concept but much smaller in comparison to full production; our solution provides a scaled down version of production thereby allowing for real world production workloads, application validation and user feedback. A pilot deployment provides a quick and easy way for our customers to preview the features and benefits of the “Virtualization Virtual Desktop Solution” leveraging a subset of customer line-of-business applications. Pilot deployment provides our customer(s) an opportunity to preview the Virtualization solution and gain understanding and insight relative to the virtual desktop technology and a first look into the methodology of streaming applications to a virtual desktop and thereby provides our customer(s) the added benefit of using a centralized virtual desktop solution and virtual application deployment. Build of the client virtual machine, requires assistance from the customer “Desktop Support SME” or “Application Support SME” to install and configure the applications into the “gold image”. The number of application selected for testing during Pilot is limited to line of business applications. The customer is responsible to provide Virtualization design team with a list of business applications. With that stated, the Virtualization design team evaluates the list and determines the best option for delivering the application to the virtual desktop. In addition, based on the application requirements certain applications; Adobe Reader, Macromedia Flash, Java or other pre-requisites are installed into the base “gold image”. These pre-requisite applications considered a requirement for proper function of the business application. By default, virtual desktop users are granted “User” access level permissions in the virtual desktop. Most applications function at this level but some applications require “Power User” others might require “Administrator”. Virtualization Citrix VDI administrators make these adjustments as needed but the goal is to maintain the default.

Application Licenses

The Pilot implementation engineer will require Desktop Operating System licenses and can create the “image” from which virtual desktops will be cloned by “clean installation” from licensed media. For purposes of Pilot the list of applications is limited to 12 line-of-business applications.

Coordinator Name(s) Contact Phone Contact Email


Please provide the required Operating System information below:

P

Please provide the required application information below:

Application Dependencies Required for Base Image

Application Required (Yes/No) Version Required

Crystal Reports

Oracle Client

Sybase Client

Java Runtime

.NET Framework 1.1

.NET Framework 2.0

.NET Framework 3.0

.NET Framework 3.5

.NET Framework 4.0

AddNew

AddNew

Application Dependencies Required for Base Image

Application Patching

Do any of the applications require an ongoing update process to select files, patches, service packs, etc?

Notes: Most Citrix applications require some type of ongoing update and/or patching. Updates can be minor releases or complete new versions of an application.

If yes, how frequent are the updates?

Procedure Name Y/N Frequency

Hot Fixes

Service Packs

New Releases

Upgrades

Operating System Customer OS License Key

Application Line-of-Business Installation Key


Notes: The processes relative to patching are as follows: Emergency patches, Hotfixes, Service Packs, Version Upgrades, New Releases. Provide the “Procedure Name” and “Description”. Frequency is Monthly, Daily, Weekly, Hourly, et cetera)

What team controls or owns the update process today?

Process Name Process Owner / Group Owner

Hot Fixes

Service Packs

New Releases

Upgrades

Notes: For example, is the update process performed by Windows Team, Application Team, Development Team, Desktop Support?

Software Agents

Virtualization leverages best practice for optimization of the streamed desktop to provide the best user experience possible. Some of these optimizations include disabling unnecessary agents or processes that are no longer relevant to a read only, streamed desktop. In most cases, third-party agents utilized on a normal desktop become obsolete in the virtual desktop design. Software agents used for inventory, auditing, security compliance, desktop shadowing, application installation, patching, remote management, and others are no longer relevant with read only desktop. This is one of the many cost benefits of leveraging a centralized VDI solution. Third-party software agents can easily consume an entire virtual CPU and 100% of the allocated memory depending on the agent. Our primary concern is the negative impact this can cause to performance and memory which impacts customer perception due to the negative experience. Customer perception is critical to the success of our solution. It is for this reason that we do not include third-party agent software in the base image. With that said, we offer this as an option to our customers with the disclaimer that for every agent we add to the image impacts CPU, memory, and disk performance. In some cases the impact is enough that it requires upgrading to the desktop level. In addition, adding agents to the build requires additional testing, there is not guarantee the agent will function, and the potential exists for impact to project timeline. With that said, please indicate below the required agent(s) required for the base image:

5 Virtualization Pilot User Data Migration

During the Pilot, some user data will need to be migrated to the Virtualization infrastructure. Since the Pilot has a limited scope, this migration is manual processes. On successful completion of the Pilot, no return of the user data will be provided. If the Pilot is not successful, the Virtualization implementer will provide recovery of the user data to a customer designated file system.

<CUSTOMERA> is “on-premises” implementation, which requires multiple data center resources from the customer to assure completion of Virtualization requirements; including but not limited to data center user data migration.

The GuideIT Virtualization Architect requires a dedicated customer allocated data migration resource with access to the file servers and data. The “Data Migration SME” has full access to the file servers and user data and is our primary resource for user data migration questions or issues.

Third-Party Agents required for base image

Agent Vendor Installation Contact



6 Integration Questions

It is important for the resource assisting with the implementation to be aware of any scenarios that may affect the standard Pilot implementation or cause them to alter the implementation specifics.

Listed below are a number of questions of which the answers will help to insure a successful Virtualization Pilot implementation.

Support Dependencies for Pilot and Production

Notes: Some of these questions might not be relevant depending on what phase of the project. Has IT Help desk been engaged to hand-off level 1 support post go-live?

Have the users been trained on accessing and using the system or is this pending?

What team will handle the level 2 support for the application?

Has the customer escalation documentation been updated?

Is there a firewall, or any other access restrictions between the Virtualization client network and server network provided in previous sections? If yes, please provide SME information below.

Is there a firewall, or any other access restrictions between the Virtualization client network and the application server network(s)?

Customer Data Migration SME


Primary

Secondary

Yes or No Firewall SME Contact Info

Yes or No Firewall SME Contact Info


Are there group policies, login scripts, or other management policy that will apply to the servers and administrator accounts defined in previous sections?

What are the organization specific password requirements?

Will the password requirements be the same for Local Administrator Accounts?

Domain – Virtualization Service Account?

Are there requirements to operate (or not) the built-in Windows firewall feature?

Are there customer specific Server or Desktop requirements, which will need to be installed or configured to remain compliant (security, audit, etc…) within the customer network?

Will internet access be allowed from the servers to accommodate Microsoft Security Patches and Updates? If yes, is proxy server used and if so what is the required settings?

7 Success Criteria

It is important for the Virtualization project team to understand the success criteria for the Virtualization Pilot. This section will outline the success criteria as defined by the customer.

The following questions should be answered as part of the pre-pilot questionnaire.

Yes or No Description

Requirement

Password history:

Minimum Password Age:

Maximum Password Age:

Minimum Password Length:

Password Must Be Complex:

Yes or No

Yes or No

Yes or No

Yes or No Required Component Owner and Contact Information

Yes or No Proxy Information Owner and Contact Information

Why is the customer participating in the Virtualization Pilot?


What outcome does the customer hope to see from the Virtualization Pilot? (Example: Financial goals, performance goals, licensing, etc) ?

Are there any show-stoppers? (Example: if a particular application doesn’t work, if certain groups are not candidates for Virtualization, etc)?

guideit customer success criteria guide

Technology