Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
50 2 Best Practices at Planning, Prototyping, Migrating, and Deploying Windows Ser ver 2008 Hyper-V input about areas of concern related to the application (known “quirks” of the application relative to specific service packs not supported, or hard-coded IP addresses in the application, or the like). Key end users can reveal needs that their managers or directors aren’t aware of, especially in organizations with less-effective IT management or unstable infrastructures. Special attention should be paid to ferreting out the problem areas and technologies that never worked right or have proven to be unstable. After all, they likely won’t mysteriously be fixed when migrating. | 50 2 Best Practices at Planning Prototyping Migrating and Deploying Windows Server 2008 Hyper-V input about areas of concern related to the application known quirks of the application relative to specific service packs not supported or hard-coded IP addresses in the application or the like . Key end users can reveal needs that their managers or directors aren t aware of especially in organizations with less-effective IT management or unstable infrastructures. Special attention should be paid to ferreting out the problem areas and technologies that never worked right or have proven to be unstable. After all they likely won t mysteriously be fixed when migrating them from physical to virtual configurations. For the most part the bigger the project the more thorough the discovery should be. For projects involving a complete upgrade or system replacement every affected device and application should to be reviewed and evaluated to help determine its role in the new environment. If network diagrams exist they should be reviewed to make sure they are current and contain enough information such as server names roles applications managed switches routers firewalls and so on to fully define the location and function of each infrastructure device. If additional documentation exists on the detailed configuration of key infrastructure devices such as as-built server documents with details about the server hardware and software configurations or details about router configurations or firewalls they should be dusted off and reviewed. Information such as whether patches and fixes have been applied to servers and software applications becomes important in the design process. In some cases the desktop configurations need to be inventoried if client changes are required by an application upgrade. Software inventory tools can save many hours of work in these cases. Certain documented company policies and procedures that are in place need to be reviewed. Some such as disaster-recovery
