- Shopping Bag ( 0 items )
Ships from: fallbrook, CA
Usually ships in 1-2 business days
Ships from: Chatham, NJ
Usually ships in 1-2 business days
Here’s the book you need to prepare for Exam 70-227, Installing,
Configuring, and Administering Microsoft Internet Security and Acceleration (ISA)
Server 2000, Enterprise Edition:
Preconfigure network interfaces.
For any kind of non-T-carrier connection (ISDN, DSL circuit, cable modem) that runs at less than 10 megabits per second (Mbps) you can safely run any processor above a Pentium II 300 megahertz (MHz)-class CPU. (You can't buy one today, but that's another story.)
For a T1–T3 (E1–E3 in Europe), OC-1, or DS3 connection running anywhere between 10Mbps and 50Mbps, you should consider, at a minimum, a Pentium III 550MHz or higher.
For speeds higher than that (OC-3 running at 155Mbps, for example) you should consider a Pentium III 550 MHz with an additional processor for each bump beyond 50Mbps. So, for a dedicated OC-3 pipe to your ISP, you'd consider a quad-Pentium III 550MHz or greater for your ISA Server. ISA, by virtue of tagging onto Windows 2000 Server, is symmetric multiprocessor (SMP)–aware, so you won't have a problem with it recognizing and working with up to four processors.
You have to look at the number of nodes you're supporting in order to figure out how much disk space you need to allocate for your cache. It's difficult to determine how much cache space to allocate because not all users are created equal. Some will be highly robust in their Internet enjoyment, while others will be basic surfers. For the test, you should remember that Microsoft recommends 2–4GB of disk space for up to 500 users, 10GB for 500–1000 users, and an additional 10GB for every 2000 users you add to the system.
You should consider doubling or tripling these numbers for a real-life production scenario.
For deployments in which you're planning to perform a limited amount of logging (for such things as IP packet filtering and Web Proxy), you should plan on at least 1GB of space dedicated to the logs.
It may not be a bad idea to consider partitioning your ISA computer in such a way that the OS lives on one partition, the ISA program files on another, the cache on another, and the logs on another. Consider putting the cache and logs on completely separate physical disks, not just parti-tions. The cache must be located on an NTFS partition. If you're still putting things on FAT, can we talk?
With ISA Server Enterprise Edition, you can install ISA Server on multiple computers, each of which can become a member of the same ISA array and can fulfill various duties. This will help you facilitate large deployments that have many users and needs within a single array design. The caveat with this is that there's a pretty large jump in price from ISA Standard to ISA Enterprise. In either the Standard or Enterprise pricing scenario, you pay by the CPU. The retail price for ISA Standard is around $1500 per CPU, while ISA Enterprise is $6000 per CPU ($3000 per CPU if you're upgrading from an older firewall product). Keep this in mind as you size your ISA Server and ask the question, "Is this such a large enterprise that I have to go with a full ISA Server array, or can I get by with one reasonably well-engineered server?"
With the above sizing recommendations in mind, you should have a somewhat better understanding of the caliber of computer you'll be using for your foray into enterprise-class firewalling. You should not consider installing ISA Server on a workstation-class computer running a Pentium II 450 with 128MB of RAM. You won't like the performance and neither will your users. Take this box seriously. Buy a good-quality computer from a Tier-1 vendor, and over-engineer the computer with more CPU, RAM, and disk than you think you'll need. You will not be sorry you did....
Chapter 1: Introduction to ISA Server.
Chapter 2: ISA Server 2000 Installation.
Chapter 3: Basic ISA Configuration.
Chapter 4: ISA Server and RRAS Integration.
Chapter 5: Configuring ISA Server for the Enterprise.
Chapter 6: Client Access.
Chapter 7: Performance Tuning and Optimization of ISA Server.
Chapter 8: Troubleshooting ISA Server.