RD Web Access Migration: Post-Migration Tasks
Updated: July 19, 2010
Applies To: Windows Server 2008, Windows Server 2008 R2
This topic describes steps that can be taken after the migration is complete:
Run a pilot program.
Retire the source server after migration.
Restore the RD Web Access or TS Web Access server.
For more information, see Run a pilot program in the Remote Desktop Services Migration Overview: Post-Migration Tasks topic.
After you complete and verify the migration, the source server can be shut down or disconnected from the network.
The following sections describe how to restore the RD Web Access or TS Web Access server in the event of a migration failure.
An RD Web Access server can be returned to service by removing the destination server from the domain and joining the original source server to the domain if it is still available in the state it was in before the migration was completed.
A TS Web Access server can be returned to service in the same way if it is still available in the state it was in before the migration was completed. However, Forms authentication is a new feature in RD Web Access, and many RD Web Access features are dependent on it.
As a result, when you roll back a TS Web Access server, none of the RD Web Access features that rely on Forms authentication will work. The server will no longer be able to make connections to the Internet, or connect to digitally signed RemoteApp programs or virtual desktops. In addition, after the rollback, although RemoteApp programs will work, single sign-on will not.
The TS Web Access server uses Windows authentication. Therefore, it cannot be changed to Forms authentication after rollback.
|If you have installed a customized solution to provide access to the Internet through TS Web Access, you should design a customized migration and rollback plan.|