Pre-Deployment Documentation; Pre-Deployment Testing; Pilots; Migration - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

Change Management.
Security services groups, they need to be well informed that this is a planned
organizational initiative.

5.2 Pre-Deployment Documentation

Documentation is key to the success of every aspect of the project, including how you plan to deploy
the services and agents. Everyone directly involved in the actual deployment, should have
documentation that they can reference at all times, eliminating the chance of error.
Documentation regarding the deployment processes needs to be completed during the design phase,
and while you are testing the deployment in your test lab facilities. After you have proven the
concept and included deployment activities in the design document, you should create a Deployment
Assistance Guide that can be used by the individuals who are involved. You might not need to share
the entire design document with everyone involved in the deployment of the product. Use your best
judgment here.

5.3 Pre-Deployment Testing

We recommend that you set aside some time before you perform your pilots to further prove your
deployment by running some last-minute tests. Allow enough time so that any adjustments can be
made and documented prior to deployment.
Perform the test in your lab facilities, using three or four sample workstations with a sample of line-
of-business applications installed. This can be a replica of tests done during your full testing phase.

5.4 Pilots

The first phase of the actual deployment is the pilots. This is where you deploy the ZENworks
Adaptive Agent to those members that you identified and notified as part of the pilot phase. You are
looking for feedback from these individuals, and this can be done through a feedback form, e-mail,
or face-to-face meetings.
Do not perform the pilots all at once. Use a rolling approach to this phase. If something goes wrong
with the deployment, you want to limit the number of people that are impacted. After you are
confident that the deployment is going as planned, you can increase the number of devices you
deploy to.

5.5 Migration

If your deployment involves a migration from an existing ZENworks infrastructure, you should have
gone through a pre-staging process (see Section
Scenarios," on page 85
communities should not be different. You still need to pilot and deploy in the same way as if this is a
new deployment of ZENworks Configuration Management.
You should use the ZENworks Migration Wizard to perform the pre-staging activities. This includes
a migration of the following resources:
Application objects and source content. This includes all AOT/AXT-based objects and content,
MSI-based objects and content, and Simple objects.
82 System Planning, Deployment, and Best Practices Guide
Appendix 6, "Deployment and Migration
for further details), but your actual process for deploying to the end-user