Wider Deployment; Post-Deployment Documentation And Validation - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

If an application is dependent on other applications, review the applications on which the
dependency exists and migrate them as MSI or as actions dependent on the requirements, then
migrate the dependent applications.
If the traditional ZENworks application objects use files that are hosted on the network share,
you should map the network share on the device hosting the migration tool.
By default, the applications are uploaded to the content server during the migration. If the
application files are located on a shared network and you want to continue using the network
files, deselect the Upload to content server option.
If there are too many associations to be listed in the Migration Utility, select the Either eligible
or ineligible for migration (No warning) option to reduce the time taken by the utility in listing
the associations.
Application objects that have the AppFsRights attribute set in eDirectory are not listed in the
Migration Utility. To list such applications for the migration, remove the AppFsRights
attribute. For more information on removing attributes, search for the LDAP Attribute
Remover article at the
communities/coolsolutions/zenworks).

5.6 Wider Deployment

After you have completed the pilot deployments, you can move on to a wider deployment.
Continuing to use the deployment plan that you have documented. You should execute against your
project plan until you have completed the rollout to all remaining workstations on your network. See
Appendix 6, "Deployment and Migration Scenarios," on page 85
this, depending on the type of deployment you are performing.
5.7 Post-Deployment Documentation and
Validation
After you have completed the deployment, you should document all steps you took to deploy across
your entire infrastructure. We recommend that you do this outside of the project plan, and include
this in your documentation repository as either a separate document or as a part of your existing
design document.
In addition, you should validate your success as much as possible. This can be done by doing the
following:
Perform physical spot checks wherever you can. Interview individuals briefly to see if they are
experiencing any issues with the deployment, and more specifically with the addition of the
ZENworks Adaptive Agent.
Review error logs in ZENworks Control Center and investigate further from there. Visit
workstations to find out more details if necessary.
Monitor Service Desk activity throughout the duration of the deployment phase. Service Desk
incidents reveal a lot of information. You are looking for spikes in activity and the details of the
individual Service Desk requests.
84 System Planning, Deployment, and Best Practices Guide
ZENworks Cool Solutions Community (http://www.novell.com/
for further details on how to do