If this results in essential changes in the users’ work routines, there will be acceptance difficulties for some time. In the beginning, the service provider will offer on-site assistance. Production phase In this phase, the end users start to work with the system productively. The last part of this phase sees the composition of approval protocols, project documentation, and, if applicable, complete operational concepts. Test users and approval procedures ensure that the installation is qualified. Sometimes, complete strategic corporate processes for network, user, and server administration are questioned during this phase. Furthermore, it is often necessary to adapt logon scripts, profiles, and policies. The focus lies on establishing connections to existing user accounts, backend servers, and legacy systems. As a result of this phase, there will be documented tests in line with the specifications, which will help determine reference parameters.įield-test phase This project section deals with transitioning and integrating the clean room installation into the existing production environment. Only if very extensive third systems (for example, mainframe computers or comprehensive databases) need to be connected should compromises to the clean room installation be made. It could even require separate network components and individual domain controllers, file servers, print servers, database servers, and so on. This procedure helps prove the basic functionality of the project concept. Pilot phase In this phase, there will be a so-called “clean room installation” with no direct connection to the existing production target network environment. During the planning phase, the customer will receive some initial training, if this has not been done before, to establish a common basis for know-how and terminology. Therefore, changes to the technical concept or specifications during the project should always be checked and approved by all project partners involved. Both documents are absolutely essential for the successful conclusion of the entire project. The specifications explain the formal processes during the project, for example, decision making, time schedules, measurable results and milestones, approval procedures and criteria, exit scenarios, and escalation mechanisms.
WINDOWS TERMINAL SERVER PROJECT HOW TO
The technical concept describes the technical procedures, such as selecting hardware and operating system components, how to integrate the terminal servers in the existing infrastructure, and installing all required applications. Planning phase After the successful pre-study, a complete technical concept and set of specifications are drawn up. If desired, a corporate concept can be drawn up during the pre-studies for a future production environment based on terminal servers. Do not forget that the results of the pre-study might lead to the conclusion that terminal servers are not recommended for a particular implementation. After all pre-study activities have been completed, you will have an analysis document describing the actual situation, a rough concept describing the target situation, an estimate of all costs, and presentation material for all business units involved. The test environment outlines the basic feasibility of any future project. Pre-study, including test In this phase, the service provider analyzes the target environment, the IT terminal server strategy is defined, required core applications are defined, the total cost of ownership (calculating the total costs) is determined for different operation models, and the test environment is installed. Either an internal or an external service provider normally handles the implementation of such a project. Terminal server projects are typically divided into five phases. Finding out which areas of a company terminal servers can be effectively used and implementing successfully, from a technical point of view is the objective of a terminal server project. They are better suited for some tasks than for others. A four-wheel-drive truck would be a lot better for these tasks, although their basic structure (a vehicle with four tires and a steering wheel) doesn’t differ much from a sports car. No one expects a sports car to be perfectly suited to all tasks in construction or manufacturing. So what is the difference between a successful and a failed terminal server project? The technology itself works, as has been proved, just not under all circumstances.