IIS

Autoconfigure Scripts for Proxy Settings

PROXY.PAC Files

Several of my clients have asked for a way to have browsers automatically pick up proxy settings if the PC (usually a laptop) is on the local LAN, but not use a proxy server if the PC is not on the local LAN. For instance, moving a laptop from a home network with no proxy server to the office LAN, with a BorderManager server.

The browser can be configured with a simple PROXY.PAC file. The PROXY.PAC file can be quite complex, providing for load-balancing, fault tolerance, or other uses. I would be happy to produce a custom proxy.pac file for you (as a paid consulting project). The examples here are pretty basic.

I have tested this PROXY.PAC file on Netscape, Mozilla, Firefox, Opera and Internet Explorer on Windows XP Professional and Windows 2000 Professional.

Note: This is not a method for remotely or permanently setting the proxy settings, which can be done in a number of ways (ZENworks, login script, proxy configuration files from Netscape or Microsoft, etc.) I will assume that you will visit the workstations and enter the proxy settings as necessary to point to the PROXY.PAC file. If the PC is to be moved off the local LAN, you will also need to copy the file to the PC.

Full Article

Backing up your IIS 6.0 Metabase

In previous versions of Internet Information Services (IIS) configurations were stored in the registry.  Part of IIS 6.0's rebuilding was changing where the configuration is stored, which is now a file named MetaBase.xml in your \WINDOWS\system32\inetsrv directory.  Sure, you can copy that file (and possibly MBSchema.bin.00000000h) to a separate directory, but a smarter way to do this is to use IIS 6.0's built-in back-up mechanism.  There are 2 ways to do this, but I'll only be showing you the graphical one at the moment.

Full Article

How can I configure an IIS computer to be a Smart Host for my Exchange Server?

It may be necessary to configure a Windows 2000 server to relay or act as a smart host for security reasons, such as in a perimeter network scenario (also known as DMZ, demilitarized zone, and screened subnet) when you do not want to have a server that participates in domain security available on the Internet or you do not need the full functionality that an Exchange server provides to do e-mail for CDO and list serve-type applications.

Full Article