Using the same configuration for the IIS server but upgrading the RAM to 16GB on the SQL server MBAM will support an upper limit client load of about 55,000 clients. A two-computer installation or at times called a three-computer installation is supported by Microsoft in production (IIS on one box, SQL on another, and of course the DC is separate). According to the MBAM scalability and high-availability guide ( ) a single server(not supported in production but can be used for testing) that has two dual core XEON 2.4 GHz chips and 12GB of RAM will support an upper limit of about 21,000 clients. I mean it really doesn’t use much processing power, memory, or even disk space. The hardware requirements for MBAM are pretty low if you ask me. As for the clients they need to be Microsoft Windows 7 Enterprise or Ultimate with a Trusted Platform Module (TPM) v1.2 chip turned on and resettable from the OS. Most organizations will combine the database servers so I recommend just using Microsoft SQL Server 2008 R2 Enterprise, Datacenter, or Developer. There is one database that will run on SQL 2008 R2 Standard and that’s the compliance status database server. This is because the compliance/audit reports server and the recovery/hardware database servers needs Enterprise, Datacenter, or Developer. Notice how I didn’t say Microsoft SQL Server 2008 R2 Standard. Keep in mind the other piece of software you need is Microsoft SQL Server 2008 R2 Enterprise, Datacenter, or Developer edition. At the time of this blog Windows Server 2008 R2 64-bit is higher and currently supported. The minimum operating system for the servers is Windows Server 2008 SP2 (x86 and 64-bit) or higher. If you can run the correct OS and SQL versions on your physical and/or virtual machines then you can run MBAM. I’m going to start with the software requirements. Today I’ll discuss hardware and software requirements. Welcome to part two of my multi-part blog regarding MBAM.
0 kommentar(er)
