Installing SQL 2005 and applying SP3 - Forefront Client Security (FCS) 4

This post is pertaining to how to install SQL server 2005 for FCS. I will keep on updated this post later with additional information on fine tuning the SQL instance like moving the log files to a different drive and other parameters but for sake of time I will just go with the installation and basic configuration first. Make sure you have SQL and SP 3 downloaded to the server. Start the installer -

Select the below options as shown below -

I name my instance as SQLSEC01. You can choose to install the "Default instance". This will name the instance "MSSQLSERVER"

Enter the domain user id/password that was created for FCS specific install. We will use this id to create the db and other rights for SQL, reporting services etc. Make sure that this id has local admin rights.

This concludes the installation of SQL 2005 server. Now apply SQL 2005 SP3.

This concludes "Applying SP3 to the existing SQL 2005 installation."

Install and Configure Windows Server Update Services (WSUS) - Forefront Client Security (FCS) 3

Before we go ahead I am assuming that following activities are done.

1. Install IIS6.0
2. .NET framework 2.0 or higher
3. MMC 3.0
4. GPMC with SP1
5. The server has the latest and greatest patches.

As part of prerequisites to deploy FCS, WSUS SP1 or higher is required. In this blog I will cover installation and basic configuration of WSUS. WSUS should be installed on the "Distribution Server" component. Since I am using a One topology scenario, my FCS servers has all the 4 roles - Management, Collection, Reporting and Distribution. The previous post has the link to download WSUS. The WSUS installer come in clubbed with the SP so don't get confused when the initial installer screen says SP1 or SP2 setup wizard. If it detects an existing install it will apply the SP or do the install from scratch. Run the installer as admin or DAS service account with local admin privileges.

Choose the first option - "Full Server installation including Admin Console"

I installed MS Report Viewer 2005 but since I am using WSUS SP2 it gave me the above prompt. So after the install I installed 2008 viewer and had no issues.

Here you can use "Windows internal db" if you want to. I wanted to keep in nice and tidy not having multiple SQL servers running on my server, easy backup and restore ETC... so I am using SQL 2005 instance that I already set up for Reporting Services, SQL instance is "SQLSEC01". I covered the SQL DB instance install in the next blog.

Pause here and make sure you get the above select right. We need to choose the send option for WSUS to use port 8530 not the first option because the SQL Reporting will use the port. Also make note of the URL. We will be using this URL later to set up the GPO. http://YourServerName:8530

The above step completes your WSUS install. Open the WSUS configuration wizard.

I suggest check the above option. Most of the people I come across like to use MS products but don't like to give feedback or data back to MS. Help MS help you :-). If you are not comfortable you need not select the option. I did.

If you have proxy set up configure it here...

I forgot to collect the screenshot but in the above option scroll to the MS FCS option and select the appropriate updates for FCS. I will add the updated SS later.

This concludes the installation and configuration of WSUS. Not bad right.

Update to Check for update was not available at this time. Try again later.

This is an update post to the issue I was having yesterday not being able to update my Droid X to 2.2.
Steps to resolve this are as below -

• Go to Settings -- Data Delivery -- Social Applications
• Disable "Sync over WiFi only" option.
• Dial *228
• Select option 1
• Power down Droid X.
• Remove the battery and after 30 sec put the battery and power it back on.
• Go to "About Phone" and check for "System Updates"

The above method worked for me. The upgrade happened next and then the phone powered down and was back up again.

Note - 2.2 update switches you phone "Battery Mode" to "Nighttime Saver" mode. So no sync will happen between 22:00 - 05:00 when not connect to charger. Is this how 2.2 saves battery? Does anyone know?