Before you start the design phase and workshops, you must complete the assessment phase, in its entirety. This is covered in detail in Section 2.0, Performing Pre-Design Activities.
The first thing you must do during the design phase is to work with the teams across the organization to identify who is responsible for what, and identify how to structure the design teams and schedule the meetings to get everyone with a stake in the project in a room to flesh out the details of the design elements. Plan to break down the design into manageable chunks, then put it all together as you develop the detailed design document and infrastructure architecture diagrams.
Conducting design workshops is the best way to consider each of these individual elements of the overall design. A workshop is an informal gathering of all individuals that have a stake in the success of that particular element, where you use a detailed agenda to direct the discussion.
How is a function currently performed?
How will the function be performed after ZENworks Configuration Management has been fully deployed?
How many locations does the organization have?
How many users work at each location?
How many devices are located at each location?
Do users roam from site to site?
Do devices roam from site to site?
What additional components of ZENworks are required, such as Asset Management, Patch Management, and Security Management?
Is the customer limited to the use of a specific database vendor (Microsoft SQL, Oracle, or Sybase)?
How do devices connect internally and externally?
Which platforms should be used for the ZENworks Configuration Management servers?
Which platforms are used by the organization? This includes both Windows and Linux.
Topics for design activities should include, but are not limited to, the following:
Infrastructure topics, including Management Zone configuration, Locations and Network environments, user sources, role-based administrative accounts, folder structure, and placement of services. The overall infrastructure layout should be developed with the most senior members of the customer's IT departments.
Device discovery and agent deployment.
Migration tactics, if applicable.
Device and user policies.
Inventory gathering and reporting.
OS deployment, including consolidation of existing OS images (for example, Universal Imaging).
Remote management capabilities.
Database design, including maintenance, performance, scalability, fault tolerance, disaster recovery, backup, and restore procedures.
Administrative roles, including individual roles required by the customer, and identifying who is required to have an assigned administrative account with what level of access.
It is important that everyone involved agrees on each of the individual design elements. If you do not have consensus, you will likely face deviation from the design in the future. The objective of this phase is to build a solid design for the overall infrastructure that is based on best practices outlined by Novell. Every intricacy of the design needs to be well documented because this will be a reference during the deployment and long after the deployment is completed.