Migrating from Proxy Server 2 to ISA Server

Internet Security and Acceleration Server (ISA Server) is Microsoft's secure solution for sharing an Internet connection on a network. It replaces Microsoft Proxy Server 2 and exceeds the capabilities of other Microsoft solutions such as Routing and Remote Access and Internet Connection Sharing (ICS).

Although Microsoft ISA Server isn't simply Proxy Server 3, you can still perform an upgrade from Proxy Server to ISA Server provided you do it on Windows 2000 before upgrading to Windows Server 2003. (Proxy Server 2 doesn't work on Windows Server 2003). Most Proxy Server settings are migrated to ISA Server, and existing Proxy clients continue to function.

Here is a list of some of the prerequisites and actions you need to take to upgrade to ISA Server:

  • To upgrade from Proxy Server to ISA Server 2000, the Proxy Server computer you upgrade must be running Proxy Server 2 on Windows 2000 Service Pack 1 or later.
  • If Proxy Server is still running on Windows NT 4, stop all Proxy Server services, upgrade the server to Windows 2000, and then install ISA Server. (Ignore the warning that ISA Server isn't compatible with these operating systems.)
  • To upgrade to Windows Server 2003, ISA Server must be running Service Pack 1 or newer.
  • If your network uses the IPX/SPX protocol for internal clients, you will need to install

Requires Free Membership to View

  • TCP/IP and configure all clients to use it, because ISA Server doesn't support IPX.
  • If you're migrating a Proxy Server array to a stand-alone ISA Server, most of the settings are migrated. If you're migrating to an ISA Server array, the enterprise policies you create affect how Proxy Server's settings are transferred.
  • To migrate a Proxy Server array, first remove all members from the array. During ISA Server setup, create a new array, and migrate each Proxy Server array member to this new array

About the author: Rahul Shah currently works at a software firm in India, where he is a systems administrator maintaining Windows servers. He has also worked for various software firms in testing and analytics, and also has experiences deploying client/server applications in different Windows configurations.

More information on this topic:

This was first published in October 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.