Hi all,
I already try to deploy Forefront Codename "Stirling" Public Beta, and here's i'll show the first look of FF Stirling.
Actually, this just display the new feature, console from FF codename stirling. I will show the capture from two part of FF Stirling....it's FF Codename Stirling and FF for Exchange Beta (this is the next generation of Forefront Client Security and Forefront for Exchange). I'm not yet test the other part of FF Stirling like FF for Sharepoint Beta and FF Thread Management Gateway (The next generation of FF for Sharepoint & ISA Server), but next time i want to test all feature of FF Stirling.
OK, let's start this....
First, FF for Exchange Beta, i think it's very easy to deploy and setup this one, because the basic feature is same with the current version, only the console have different look, but i think it still easy to maintain. Below is the console from FF for Exchange Beta:

![clip_image002[11]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B11%5D_thumb.jpg)
And the new thing of management in FF for Exchange Beta is FMS (Forefront Management Shell), using Windows PowerShell, i think peoples who like scripting will love this one...;)
![clip_image002[13]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B13%5D_thumb.jpg)
NEXT, FF Stirling Beta, the next generation of Forefront Client Security....hmm...Many pre-requisites, before we install the forefront, and this is the list of pre-requisites (just for FF Stirling Server):
- Windows Installer 3.1
- Microsoft .NET Framework 3.0
- Windows PowerShell 1.0
- Visual C++ 2005 Redistributable Package with SP1
- Microsoft SQL Server 2005 with SP2 (Database Services, Analysis Services, Reporting Services, Integration Services, Workstation Components)
- Windows Server Update Services 3.0
- Microsoft Message Queueing (MSMQ)
- Microsoft Core XML Services (MSXML) 6.0
- Windows Update Agent 3.0
- Microsoft System Center Operations Manager 2007 with SP1
For the operating system, we need Windows Server 2003 SP2 (x86 or x64), because Windows Server 2008 not yet supported now (hope it will supported when release).
OK, after all pre-requisites installed, we can run the FF Stirling Setup from Installer CD media, browse into Server folder and run ServerSetup.exe....follow the instruction in wizard like the screen capture below:
![clip_image002[15]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B15%5D_thumb.jpg)
![clip_image002[17]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B17%5D_thumb.jpg)
Public Beta Version only support for One-Server configuration
![clip_image002[19]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B19%5D_thumb.jpg)
![clip_image002[21]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B21%5D_thumb.jpg)
![clip_image002[23]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B23%5D_thumb.jpg)
If you see the Warning, it's because i'm using 1024MB for RAM (the minimum requirement is 2048MB RAM) :D
![clip_image002[25]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B25%5D_thumb.jpg)
So, because it's just VPC for trial purposes, you can continue the installation
![clip_image002[27]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B27%5D_thumb.jpg)
![clip_image002[29]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B29%5D_thumb.jpg)
![clip_image002[31]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B31%5D_thumb.jpg)
![clip_image002[33]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B33%5D_thumb.jpg)
![clip_image002[35]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B35%5D_thumb.jpg)
After finished, restart the server, and we ready to explore new features from FF Stirling.
First, open the FF Stirling Management Console...one of new feature is Single Management Console. I think we can connect to the other console (example FF for Exchange Beta, in other server) except FF for Sharepoint Beta, and maintain from the same console. Below, is screen capture of Management Console from FF Stirling in my localhost:
![clip_image002[37]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B37%5D_thumb.jpg)
![clip_image002[39]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B39%5D_thumb.jpg)
![clip_image002[41]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B41%5D_thumb.jpg)
The other feature is you can customize the dashboard view by click "Customize Dashboard View" and you will see new panel in right that display some template for dashboard view. To customize, select the template and then click and drag to the center panel. For example, i add one template (Windows Firewall Status) into dashboard:
![clip_image002[43]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B43%5D_thumb.jpg)
Besides Dashboard, there is Policy Management. This is the central of the Forefront Policy that we can deploy to the assets (in Stirling, client computers or servers called assets):
![clip_image002[45]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B45%5D_thumb.jpg)
![clip_image002[47]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B47%5D_thumb.jpg)
For the client side, i only try manual deployment using Command Prompt (deploy agent and FF Client Security). There are two files in CD Media, under folder Client, named FSysAgentPackage.exe and HostProtectionPackage.exe :
![clip_image002[49]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B49%5D_thumb.jpg)
You can see the FF client agent in your system tray:
![clip_image002[51]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B51%5D_thumb.jpg)
If you right click the agent in the system tray, you can start quick scan, check for definition updates, manage quarantined items and view network restriction status (collaboration with NAP?)....
![clip_image002[53]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B53%5D_thumb.jpg)
![clip_image002[55]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B55%5D_thumb.jpg)
Last, this product is Public Beta version, use at your own risk and enjoy the beta version before it release to manufacture (RTM). ;)
![clip_image002[57]](http://wss-id.org/blogs/raymond/WindowsLiveWriter/MicrosoftForefrontCodenameStirlingBetaFi_8D81/clip_image002%5B57%5D_thumb.jpg)
Best Regards,
Raymond Engelbert