Forefront Client Security Server - Reinstallation Issues

Tuesday, November 03, 2009 10:35 PMnatfish

0
Sign In to Vote
Hi Folks,

I'm having issues with reinstalling Forefront Client Security for our evaluation of this product. I had everything setup and working, did not like how, by default, the mom agents use netbios names to communicate. I'm implementing a multi domain setup, and don't want to configure the netbios setup nor want the netbios chatter. After much digging, I found that changing any of the sever name bits required a reinstall and here I am. Any comments on this part is appreciated as well.

Setup:
- Windows 2008
- SQL Server 2005 sp3
- IIS with required bits installed
- WSUS installed and verified
- All in one sever topography
- Virtual Server (VMWare)
- FCS CD - FCS_RTM_EVAL_EN-US_1703.0
The installer currently hangs up on the "Installing MOM Reporting Service" task with a generic error of "Exit code: 1603".

ServerSetupXX.log tail end:
```
[11/3/2009 2:53:24 PM] Task(Install MOM Reporting Service)
Process command 'C:\Windows\system32\msiexec.exe'
[11/3/2009 2:53:24 PM] Task(Install MOM Reporting Service)
Process arguments ' /i "d:\Server\MOMReporting.msi" ROSETTA_SERVER="myserver.location.tld.com" SQLSVR_INSTANCE="myserver.location.tld.com" TASK_USER_ACCOUNT="forefront" TASK_USER_PASSWORD="*****" TASK_USER_DOMAIN="location" REPORTING_USER="forefront" REPORTING_PASSWORD="*****" REPORTING_DOMAIN="tld" MOM_DB_SERVER="myserver.location.tld.com" INSTALLDIR="C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting" REPORT_SERVER_VDIR="ReportServer" REPORT_MANAGER_VDIR="Reports" HttpConnectionType="http://" DB_SIZE="1024" AUTOMATICALLY_DETECT_ROSETTA_VDIRS="0" /qn /l*v "C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMReporting.log"'
[11/3/2009 2:53:28 PM] Task(Install MOM Reporting Service)

[11/3/2009 2:53:28 PM] Task(Install MOM Reporting Service)
The following process failed.
Process: C:\Windows\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [11/3/2009 2:53:28 PM]
```
I've scoured the logs and google but have still come up short. There's a few errors in those logs, but nothing that has come out as a smoking gun:

MOMReporting.Log
```
CPreReqVerifier::CheckCurrentUserIsDBAdmin: Reporting registry key not found. Error Code: 0x80070002. 
```
```
CheckForMomExpress: MOM_DB_SERVER:. myserver.location.tld.com
CheckForMomExpress: Unable to format computer name. Error Code: 0x8007007A. 
```
- I've tried running the MOMReporting.MSI package independently, but there are reported bugs with that as well (http://support.microsoft.com/kb/909846). I've never gotten the MOMReporting.MSI package to install manually, either auto detecting settings or specifying the report/reportserver urls. Both urls come up fine in a web browser (ReportServer just shows a directory listing however, while /Reports/ lets me browse through reports, although none exist yet).
- There's 52 gig free the hard drive and i'm showing "Adding OutOfDiskSpace property. Its value is '0'." in the MOMReporting.Log.
- I've also reinstalled SQL Server, IIS, and WSUS to attempt start from the ground up, but it led me to the same error.
- I've cleared out the %windir%\temp and \users\<myserver>\appdata\local\temp folders
- I've cleared out the windows\installer folders of any MOM or Forefront msi's
- I've cleared out the registry of anything referencing 'forefront', 'mom' or 'operations manager'
- I've added the location\forefront AD service account we're using for this product to the local admin group for the machine (as a shotgun security approach)
Any thoughts?
- Reply
- Quote

All Replies

Wednesday, November 04, 2009 2:39 AMNick Gu - MSFTMSFT, Moderator

0
Sign In to Vote
Hi,

Thank you for your post.

Before going any further, I’d like to know the version of Windows Server 2008 and SQL Server 2005. As we know, it is no support install FCS server component on 64 bit servers. For more information, refer to: http://technet.microsoft.com/en-us/library/bb404245.aspx

Regards,
Nick Gu - MSFT
- Reply
- Quote
Wednesday, November 04, 2009 6:00 PMnatfish

0
Sign In to Vote
Windows 2008 Standard,
SQL Server 2005 Stardard,
All 32bit
- Reply
- Quote
Thursday, November 05, 2009 9:22 AMNick Gu - MSFTMSFT, Moderator

0
Sign In to Vote
Hi,

Thank you for your update.

According to your description, this issue is similar with the following post. You may delete all forefront entries and run "serversetup.exe" from the Administrator to see if it works.

http://social.technet.microsoft.com/Forums/en-US/Forefrontclientsetup/thread/63c59290-5e41-4cb2-bfad-e536d117d619

Regards,
Nick Gu - MSFT
- Reply
- Quote
Thursday, November 05, 2009 4:52 PMnatfish

0
Sign In to Vote
I've removed all of the registry entries with ' c:\program files\microsoft forefront' in their data and rerun setup without success. Logs show the same issue.

I tried the manual install of MOM Reporting (using the MOMReporting.MSI installer on the cd). I was able to get the MOMReporting to pass validation this time (following the instructions in http://support.microsoft.com/kb/919954 under the section titled You receive an "Unable to contact the Microsoft SQL Server Reporting Services server via WMI" verification failure, Method 2. I unchecked "Automatically Detect Virtual Directories" and entered only the virtual directory name "(ReportServer" as opposed to http://myserver.location.tld.com/ReportServer). This let it pass the pre-req check and install successfully.

Is it possibly to install the components individually? Doesn't solve the installer issue, but would get me up and running.
- Reply
- Quote