The Envision SMF creates the framework for the Windows 7 deployment

an article added by: Antonio d at 12132009


Windows XP :: The Envision SMF creates the framework for the Windows 7 deployment ::

 French | Spanish | Portuguese | Italian | German | Japanese | Chinese | Korean | Russian | Arabic Bookmark and Share

>The Project Planning SMF serves as a transition between vision and implementation, laying the groundwork for the actual deployment. The Project Planning SMF uses the documents and processes created in the Envision SMF to add structure and content to the deployment plan. Key steps in this phase include the following tasks:

 

Create the development and testing environment Build a testing lab that adequately embodies the target deployment environment, using virtualization to reduce the cost of creating labs. In addition to resources such as servers and sample target systems used to develop and test the deployment, the labs should also include the resources that the project team will use to prepare and accomplish the final deployment.

Develop the solution design The solution design builds on the solution concept, project structure, and other documents created by the Envision SMF to define the conceptual, logical, and physical solution designs for the planned deployment. This document serves as a road map for the project team to begin building the deployment.

Create the functional specification The functional specification defines the requirements of all stakeholders targeted by the deployment and serves as a contract between the customer and the project team. It should clearly define the goals, scope, and outcomes of the deployment.

Develop the project plan The project plan is actually a collection of plans that address the tasks the project team will perform to carry out the project, as defined by the functional specification. Each plan in this document covers a particular area, such as facilities and hardware, testing, training, and communication.

Create the project schedule The project schedule compiles individual schedules created by team members for the purpose of planning deployment activities.

Complete a computer inventory In the Project Planning SMF, a complete computer inventory must be made to identify existing systems and applications that the deployment will affect. In addition, the server resources to be used for deployment must also be identified and evaluated for suitability. Perform a networkBuild

The Build SMF is the period during which the team builds and unit-tests the solution. The Build SMF includes six key tasks:

Start the development cycle In this initial step, the team creates a lab server for development work and begins the process of creating images, installation scripts, and application packages. The team should also create an issue-tracking system so that team members can communicate about and coordinate solutions to issues.

Prepare the computing environment In this key task, the teams build a deployment environment with facilities such as servers, networking, system backup, and data repositories (such as Microsoft Visual SourceSafe) with separate workspaces (that is, computers and network shares) for each team role.

This environment provides the infrastructure for teams to work both independently and jointly as necessary to complete their development tasks.

Develop the solution scripts In this step, the teams begin the process of packaging applications, creating computer images, and developing remediation steps for application-compatibility issues.

The teams also plan how and what user data will be retained and migrated during the deployment and validate that network infrastructure (that is, shares, credentials, and other components) is in place and functioning properly prior to deployment.

Develop deployment procedures Using the documents, processes, and other resources created up to this point, begin creating the documents that the teams will use to accomplish the deployment and post-deployment tasks.

These documents include training materials for users, administrators, and others who will maintain systems and applications after deployment; a plan for communicating with users about the upcomingchanges; and site-deployment procedures to simplify and standardize the deployment of solutions across sites.

Develop operations procedures Create a document that describes the operations procedures to support, maintain, and carry out the solution following deployment. Key processes to describe include maintenance, disaster recovery, new-site installation, performance and fault monitoring, and support and troubleshooting.

Test the solution Perform test deployments and remedy any issues that arise using the issue-tracking framework created by the Project Planning SMF to monitor and address these issues.

The Stabilize SMF addresses the testing of a solution that is feature-complete. This phase usually occurs when pilots are conducted, with an emphasis on real-world testing and with the goal of identifying, prioritizing, and fixing bugs.

Key tasks in this phase include the following: Conducting the pilot At this stage, the teams use a small pilot deployment to test the deployment and identify any remaining issues.

Procedures, resources, and personnel should be in place to assist in addressing any user issues that arise during the pilot deployment. This key task should also include obtaining user feedback as well as review and remediation of issues identified during the pilot.

Operational-readiness review All teams at this stage perform a complete operational- readiness review to determine that the deployment plan is ready to move forward to full-scale deployment. The solution is frozen at this stage, and any remaining issues are addressed.

Final release This task incorporates all fixes and issue resolutions to create the final release of the solution, which should now be ready for full deployment.

Deploy

In the Deploy SMF, the team implements the solution and ensures that it is stable and usable. The key tasks involved in the Deploy SMF include the following: Deploying core technology Based on the plans and procedures developed in the Project Planning SMF, install, configure, and test deployment servers at each site. Also train administration staff in preparation for deployment.

Deploying sites Teams perform the deployment of Windows 7 at each site using the procedures and resources developed by the Project Planning and Build SMFs. Team members remain on site to stabilize each site deployment, ensuring that users can move forward with reliable systems and applications and that the goals of the deployment plan for the site have been met. Stabilizing the deployment In this key step, the project team ensures stabilization across all sites and addresses any remaining deployment issues.

Completing the deployment This step marks the transition from deployment to operations and support. Ongoing operations are transferred from the project team to permanent staff. Reporting systems are activated, and support processes are fully operational.

legal disclaimer

Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.

related articles

1. How to setup a local network in Windows XP
LOCAL NETWORK PROBLEMS Any time two or more computers and their related devices are under the same roof, they should probably connect to one another through a etwork. Networking allows users to share files and printers and to share access to the Internet through a common modem or broadband connection. Windows XP includes tools and wizards that make it relatively simple to set up a network, but a network is always more complicated than an isolated, stand-alone computer. Network problems don’t oft...

2. Windows XP activation and hardware problems
Not every computer failure is caused by a software issue. Many problems that appear to be related to Windows are actually caused by some kind of hardware malfunction or by a conflict between two or more incompatible hardware components inside the computer. This article describes many of the most common problems that you might encounter when you try to add, move, or change a component inside your computer. Most of these problems have relatively easy solutions if you know where to look. Finding and fixing hardware problems requ...

3. Installing a New Hard Drive on Windows XP Professional
Hard drives are a special case. On a cost- per-bit basis, drives are cheap and getting cheaper all the time. When a drive fails, the cost of replacing the physical device is relatively small, but the data stored on the old drive is often irreplaceable. So you shouldn’t throw away an apparently broken drive until you have done everything possible to recover the data, and you shouldn’t do anything to the drive that might erase or damage any more data. When your boot drive (almost always the C: dri...

4. How to recover data from a corrupted hard drive using Windows XP Pro
Recovering Your Data Unless the physical platters inside the drive are severely damaged, it’s probably possible to recover the data from a bad drive. In extreme cases, you might need to send the drive to a very expensive recovery service that will take the drive apart in a clean room environment and replace the damaged parts, but it can be done. Before you spend that money, try the techniques in this section to read your files with special recovery software. The most important thing to ...

5. How to move a hard drive to a new computer under Windows XP
Moving a Hard Drive to a New Computer Moving an old drive to a new computer is often the best way to continue using the same data after you start using the new machine. However, it’s often not possible to use the old drive as the boot drive (the C: drive) on your new computer. You can’t just drop the old drive into the new box and use the Windows software that you installed on the old computer. Unless the old and new computers are exactly the same make and model or they use exactly the same m...

6. Adding more RAM under Windows XP
Hard drives aren’t the only parts of a computer that can fail. Memory modules, the central processor, the motherboard, the power supply, and all of the peripheral devices that allow the computer to exchange data with the rest of the world can stop working properly. Obviously, troubleshooting a memory module is very different from trying to fix a mouse or a keyboard, so this article contains specific advice about fixing many of the most common devices and components in and around your computer. Memory ...

7. Mouse, Keyboard, Motherboard and Power Supply Problems
Replacing the Motherboard Installing a new motherboard is the computer equivalent of a brain trans- plant. It’s major surgery that replaces the central components that control everything the computer does. Obviously, you won’t perform a motherboard swap very often, but if you are a truly dedicated hardware geek and you’re not afraid to tear the whole computer apart, it can be done. Just follow the instructions that come with motherboard, take your time, and double-check all the li...