The first thing you should do is create a test lab in a virtual environment so that you can make mistakes without damaging your production environment. To complete the scripts described in this chapter, you need a domain controller and an ISA Server 2004 machine configured with two network adapters. Remember to isolate the test lab from your production environment before running any scripts.
See Chapter 19, "Configuring Microsoft ISA Server with Microsoft Virtual Server 2005," for more information about how to use Microsoft Virtual Server to configure a test environment. You can also use Virtual PC to configure a test environment. See the Microsoft Virtual PC site at http://www.microsoft.com/windows/virtualpc/default.mspx for more information. In addition, you can download a 45-day trial version from there.
Once you have downloaded the ISA Server 2004 SDK from http://go.microsoft.com/?linkid=2392254, you can install it by following these steps:
On the ISA Server 2004 computer, log on as an administrator.
Run ISA2004SDK.exe, and install with the default settings.
The updated version of the ISA Server 2004 SDK will be located in C:\Program Files\Microsoft ISA 2004 SDK\HHelp\Isasdk.chm.
Open a script editor.
You can download all of the sample scripts from this chapter at http://www.isamvp.com/apc.
You can use the Microsoft Script Editor (MSE), which comes with Microsoft Office 2000 and later versions. To open the MSE, from the Tools menu of any Office application, select Macros, and then select Microsoft Script Editor. One other very useful editor that makes creating and working with scripts easy is PrimalScript, by Sapien Technology. You can download a trial version at http://www.sapien.com. If you don't have either of these tools, you can use Notepad.
|Best Practices|| |
Create and test your scripts in a test environment—such as a test workstation, or a Virtual PC image—not on the ISA server itself.