Export (0) Print
Expand All

Testing Your Remote Access Solution

Updated: March 28, 2003

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

When testing your solution in a lab, recreate the actual user experience as closely as possible. It is likely that the client will be deployed on computers not directly under the control of your organization, such as a user’s home computer. For this reason, it is necessary to test your service profile(s) using a standard set of applications and test on the same types of hardware that you will deploy to.


  • Test both the server and client portions of your remote access design.

Use the following guidelines to test your deployment:

  • Load and run the client on each operating system you are supporting for remote access. If you are supporting both dial-up and VPN connections, test both of these types of connections on your test clients.

  • Test custom actions in detail, using a standard set of application that users might have on their computers. Be sure your test is representative of the end-user experience.

  • Make sure your phone books are updating. If phone books are not updating, check the URL that is pointing to the phone book server, check for firewall conflicts, and ensure that IIS is correctly configured on PBS server.

  • Test your distribution method before announcing and rolling it out. For information about establishing a distribution method, see "Distributing Your Connection Manager Service Profiles" later in this chapter.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft