Figure 10: The installer is verifying if everything is ready to install Client Security with the selected components.
Note the warning sign in Figure 10, “Verifying hardware requirements." Although our host computer is equipped with a quad-core processor, the warning tells us that “having two or more processors is recommended." The reason is simple: Microsoft Virtual PC can recognize only one processor. You can safely ignore this message and proceed with installation.
Figure 11: Installation completed.
After installing everything, I strongly recommend you to reboot your virtual machine. After that, to increase performance of your server, go to All Programs » Accessories » System Tools » Disk Defragmenter and defragment your virtual hard disk. Reboot.
When you log on to your virtual machine, you will see Microsoft Forefront under All Programs. Following this path, open Microsoft Forefront Client Security Console. You will be greeted by a wizard, which will ask you to configure
- the location of the collection server,
- the location of the collection database,
- the management group name,
- the location of the reporting database,
- the user name and the password of the reporting account,
- the location of the reporting server, and
- the URLs for the reporting server.
If you have followed the default values during the installation, you can proceed with the wizard by clicking “Next." In the “Reporting Database" window, you will supply the credentials of the reporting account. For the sake of simplicity, we will proceed with the Administrator account and we enter Contoso\Administrator as the user name and the password of the Administrator account. Proceed by clicking “Next."
In the next window, you can safely click “Next" if you have come so far with the default values. The next two screens will perform relevant checks and configurations. Wait until everything is complete. Finished.
 I strongly recommend you to reboot your virtual machine after making system-wide configuration changes, such as installing new server roles or installing programs such as Update Agents, IIS, FrontPage extensions etc.. The installer may not ask you to restart your computer, but despite this go on with a reboot. Sometimes virtual machines may act weirdly and you may experience some unexpected behavior. Reboot will probably be the first thing you will try. To save yourself from this unexpected acts, reboot at the first place.