This latest version of the client encrypts all communications
between the client and the server and is highly recommended. In certain cases,
downlevel support for ISA 2004 or earlier clients is needed. If this is the case, the setting
for toggling on or off support for downlevel clients can be found by clicking on the
Define Firewall Client Settings link in the General node of the ISA Management Console.
The checkbox shown in Figure 11.3 controls this setting.
FIGURE 11.3 Changing global Firewall client settings.
302
Using DHCP to Configure ISA Server for Auto Detection
Creating the ISA Client Installation Share is only one step in the automation and distribution
of the ISA client. To fully automate deployment, the network must be configured to
know which server is the ISA server. This process is accomplished through the publishing
of a record in either the Dynamic Host Configuration Protocol (DHCP) environment or
the Domain Name System (DNS) environment, or both, depending on the needs of the
environment.
This information is published in either DHCP or DNS via a Web Proxy auto discovery
(Wpad) file. With this file published on the server, and with auto discovery enabled on
the ISA server (described in the next section of this chapter), the Firewall clients, when
installed, automatically detect which IP address is associated with the ISA server, which
can be used to automate the way that the ISA client configures the proxy server settings
for the system.
Pages:
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513