Forefront Client Security Setup and Configuration Forum

Microsoft Forefront Client Security (Managed by a system administrator) on XP. Both left click, right click, and double clicking do nothing.

Tue, 01 Dec 2009 20:30:51 Z

I am having an issue where on computers with a deployed client the system tray icon does not always show. On a fresh boot, sometimes it will show up and other times not or it might show up initially and then disappear later. A bigger issue is when it does show the clients do not have any ability to manage the settings locally. On a Win XP machine logged on as a domain admin and local admin, I mouse over the system tray icon it says, "Microsoft Forefront Client Security (Managed by a system administrator)". Both left click, right click, and double clicking do nothing.

On the Forefront Client Security Management Console, under the Policy Management tab, in the deployed policy, on the Advanced tab, under Client Options, I have set the "Users can view all client security agent settings and messages" and unchecked "Only Administrators can change Client Security agent" and checked "Allow users to add exclusions and overrides".

Policy deployment : "Unable to create a group policy link"

Fri, 20 Nov 2009 17:53:09 Z

This question may have been asked before, but none of the suggested solutions have worked. Maybe this case is different.

The error I am getting occurs when I am deploying a policy to a selected OU:

---

The policy cannot be deployed.

Further details:

Unable to create a Group Policy link.

---

The GPO does get created (I see it in the GPM console), but it is not linked anywhere (as expected, following the error).

The Forefront Client Security Console (with service pack 1 installed) is running on Windows Server 2008 (32-bit); the domain controller runs on another server (Windows Server 2008 64-bit).

Does anyone have any suggestions to resolve this issue?

Thanks!

Forefront Client Security server

Thu, 26 Nov 2009 08:11:59 Z

Hi Experts,

I had a plan to install FCS. & i m going to use small topolozy.
as microsoft recommend that i should have two H/W server one for FCS & other for WSUS& distribution server.

but i have only one hardware serevr.

is it possible to install fcs & wsus on a single server...

Thnaks in Advance.

Balwan Singh

KB971026.adm does not work for me

Fri, 27 Nov 2009 16:51:39 Z

Hi,

I try to make the KB971026.adm file work from the corresponfding KB article to "DisableScanningNetworkFiles". I can see it when loaded as an adm in my policy, i can configure it. I then see it in my group policy management console but the settings is not set on my client. Client is Windows XP SP3, Ad controller is Server 2008 R2. Could it have something to with the 1.0 in the name structure?

KEYNAME "SOFTWARE\Policies\Microsoft\Microsoft Forefront\Client Security\1.0\AM\Scan"

When is use the same template i can put the key in KEYNAME "SOFTWARE\Policies\Microsoft\Microsoft Forefront\Client Security"

Any ideas anybody?

Thanx for helping out.

DJITS.

right-click menu for Forefront Client Security?

Mon, 30 Nov 2009 15:16:28 Z

I have installed FCS using /NOMOM installation.

Everything works fine but I couldn't find the right-click menu for custom scan. (while most anti-virus programs have it)

I checked the option but I couldn't find something related to it.

I know it is doing real-time protection but I am used to double check for virus scan after download.

Should I just trust the real-time protection and run the downloaded(or un-zipped) files(as well as files in USB) without a custom-scan?

I am concerned about running a program before FCS does real-time scan.

Client Policy Settings

Thu, 19 Nov 2009 18:02:27 Z

Hello everyone, thanks in advance for any help on this. I feel like I'm missing something obvious here, but I'm not sure exactly what. We are running Forefront client security 2007 with both admin computers and locked down computers.

I found this document detailing how the policy setup works. http://technet.microsoft.com/en-us/library/bb418862.aspx

I have the following, nondefault settings in the policy...
On the Protection tab, Run a scan every day at 2:00 pm with a quickscan
On the Advanced tab, Check for updates at an interval of 1 hour
On the Advanced tab, Users can view all Client Security...
On the Advanced tab, Only administrators can change Client...
(Adding exclusions and prompting for unclassified software are both unchecked)

Now, this is what I'm seeing, on the Protection tab of the policy, if you only set both Malware protection settings to On, client options will be greyed out but visible to admins. I see the custom settings above. With users, I am not able to view the options or run a manual scan, but the custom settings are in effect. (auto scan ran at the non default time)

In the protection tab, if you set both Malware protection settings to User Controlled, both admins and users can view and change the client options. However, the nondefault settings that I applied earlier had been reset to the default values.

It would be preferable to have users open the client and see the custom settings but not be able to modify them. Also the user ability to run manual scans would be helpful. In addition, administrators should be able able to open the client and have the custom settings but be able to modify them if needed. Is this a possible configuration for a policy file?

Sorry, this seems like a lot of info in this post, hopefully it's clear. If anyone has any questions to clarify the issue please ask. Thanks again for any help on this.
Mike

Forefront client Security on 64bit?

Fri, 23 May 2008 20:53:17 Z

I've tried installing Forefront Client Security on a 64bit computer in the past but the problem was the dependancies because SQL 2005 doesn't come with one of the components for 64 bit that I needed. I forget which one though. Anyways, we've received SQL 2008 in the mail and I was wondering if I were to use the new version of SQL, would I be able to install forefront on Windows Server Standard x64?

Installation Quesitons

Tue, 24 Nov 2009 08:44:03 Z

Dears

I m trying to install the Client Security and I have the following questions:

- In my organization the databases are usually stored and handled by the database Server, I understood that the Client Security management must be installed on the database server, and that will be not applicable .... so did i understand the idea wrong. And i still want to use one Server scenario but i only want to host the databases on the database Server.

- Can I put password to prevent other administratos from logging to the admin console and change configuration?

Forefront detected changes

Tue, 02 Dec 2008 16:39:03 Z

Every time we make a slight change to our firewall rules, all users around the world get "Forefront has detected changes" messages that they have to do something with to get rid of the alert. How do we prevent this from appearing every time we make the slightest changes to the firewall policies?

Thanks

MomService taking high CPU utilization

Thu, 19 Nov 2009 04:21:54 Z

Need help.
I have a 4CPU, 9GB RAM virtual Machine runing on VMWare hardware acting as a Forefront Server running windows 2003 sp2 enterprise ,SQL server 2005 Enterprise and all components except WSUS running on this system.
Initially when i had 300 computers reporting the systems was working great. Now once it reached 2800 clients now i see that MOMservice is consuming most of the CPU and is acting up. Can't open any other applications on it , it even times out on the network ping from someother system.

When i disable Momservice , i can ping and i can run other applications.

Please advice what can i do?

Collection Server Installation Failure

Thu, 17 Apr 2008 19:54:23 Z

Hello!!

I have been working on this for a couple of days trying to get FCS installed, and I'm at the final stages with an installtion error that I can't resolve.

Installation Architecture:

Server A:

Collection Server (Windows 2003 SP2 - Fully Patched)

Management Server (Windows 2003 SP2 - Fully Patched)

Server B:

Reporting Server (Community SQL 2005 Reporting Server)

Server C:

Collection Database (SQL 2005)

Reporting Database (SQL 2005)

Server D:

Distribution Server (WSUS 3.0)

I have the Collection Database and the Reporting Database installed successfully. Additionally, I have the Reporting Server installed successfully as well. Now, I'm trying to install the Collection Server, but I continue to get the same error, and I'm completely out of ideas. When installing the Collection Server, the "Verifying Settings and Requirements" section completes successfully (all green check marks). The following screen ("Completing Setup Wizard") fails on the first step (Install Collection Server Component). The error from the log is listed below:

[4/17/2008 2:23:50 PM] Task(Install Collection Server Component)
Installing from this MSI: 'c:\documents and settings\forefront\desktop\forefront\1.0\Server\MOMServer.msi'
Log file: 'D:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMServer.log'.
[4/17/2008 2:23:50 PM] Task(Install Collection Server Component)
Starting Install Collection Server Component.
[4/17/2008 2:23:50 PM] Task(Install Collection Server Component)
Starting C:\WINDOWS\system32\msiexec.exe.
[4/17/2008 2:23:50 PM] Task(Install Collection Server Component)
Process command 'C:\WINDOWS\system32\msiexec.exe'
[4/17/2008 2:23:50 PM] Task(Install Collection Server Component)
Process arguments '/i "c:\documents and settings\forefront\desktop\forefront\1.0\Server\MOMServer.msi" /norestart /qn /l*v "D:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMServer.log" INSTALLDIR="D:\Program Files\Microsoft Forefront\Client Security\Server\Microsoft Operations Manager 2005" CONFIG_GROUP="ForefrontClientSecurity" ADDLOCAL="MOMXServer,MOMXUI" ACTIONSUSER="forefront" ACTIONSDOMAIN="**********" ACTIONSPASSWORD="*****" MOM_DB_SERVER="SERVER C\S5P01" SQLSVR_INSTANCE="SERVER C\S5P01" MOM_SERVER="SERVER A" DAS_ACCOUNT="forefront" DAS_PASSWORD="*****" DAS_DOMAIN="**********" '
[4/17/2008 2:23:55 PM] Task(Install Collection Server Component)

[4/17/2008 2:23:55 PM] Task(Install Collection Server Component)
The following process failed.
Process: C:\WINDOWS\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [4/17/2008 2:23:55 PM]

Here is the log from the "MOM SERVER" install:

MSI (s) (50:5C) [14:23:55:447]: Note: 1: 1708
MSI (s) (50:5C) [14:23:55:447]: Product: Microsoft Operations Manager 2005 -- Installation failed.

MSI (s) (50:5C) [14:23:55:462]: Cleaning up uninstalled install packages, if any exist
MSI (s) (50:5C) [14:23:55:462]: MainEngineThread is returning 1603
MSI (s) (50:68) [14:23:55:572]: Destroying RemoteAPI object.
MSI (s) (50:EC) [14:23:55:572]: Custom Action Manager thread ending.
=== Logging stopped: 4/17/2008 14:23:55 ===
MSI (c) (98:AC) [14:23:55:572]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (98:AC) [14:23:55:572]: MainEngineThread is returning 1603
=== Verbose logging stopped: 4/17/2008 14:23:55 ===

Here is the Event Log Error:

Source: MsiInstaller

Event ID: 11708

Description: Product: Microsoft Operations Manager 2005 -- Installation failed.

I ran the following command to determine why the MSI was failing:

msiexec.exe /i "c:\documents and settings\forefront\desktop\forefront\1.0\Server\MOMServer.msi" /l* c:\forefront.txt

The installation said that I didn't have all of the prerequsites to complete the MSI install. According to the log, I was missing a SQL Server installation. Since I'm not running SQL Server on the Collection Server (Server A), I deceided to install the Microsoft SQL Server Native Client...hoping that would satisfy the requirements. But no luck with that. I have all of the prerequsites installed on the Collection Server (Server A):

.NET 2.0 +

Network COM+ Access

Windows Update Agent 2.0 +

Link: http://technet.microsoft.com/en-us/library/bb404276.aspx

From what I can gather from the error logs, I have to install a full version of SQL on the Collection Server (Server A) even though it will not be housing the Collection Database. I really don't want to do that if it is not necessary. If anyone has any thoughts to this, I would really appreciate them.

UPDATE: I installed Microsoft SQL (2005) Access Client Tools with no luck either. This is starting to become fustrating.

Thanks!

Huggy Bear

Install ForeFront with SQL Server 2008

Sat, 11 Oct 2008 05:50:01 Z

Is it possible to install forefront with sql server 2008??

If not when is the expected date for this method to be made available?

I am running Windows Server 2008 Enterprise Edition.

Computers not showing up in FCSMC / Clients definition don't install automaticly

Wed, 09 Apr 2008 11:28:41 Z

As stated in the headline I have a couple of problems:

1. NO computers showing up in FCS Management Console (number of managed computers = 0)

2. Client agent definition updates are not Automaticly installed after download from WSUS. FCS agent are in a warning state and the Automatic Update warning icon states that forefront updates are ready to install.

My setup is FCS 2 topolygy:

Server 1: Reporting, management console, databases etc.

Server 2: Distribution (WSUS 3.0 with SP1)

What I have done is:

Follow the deployment guide for a 2 topology line after line.
On the WSUS server:
- Selected the Forefront product category
- Enabled the Automatic approval
- Manually approved the forefront agent for installation (had to accept the license thingy)
I made a WSUS policy for servers and clients with this things, among others:
- Configure Automatic Updates Enabled
  Configure automatic updating: 4 - Auto download and schedule the install
  Scheduled install day: 0 - Every day
  Scheduled install time: 05:00
- Allow Automatic Updates imidiate installation - Enabled
- Changed the update service location to the WSUS server
- Applied it to all relevant computers
- Updates seems to be installed, and the computers restarted when necessary (at night)
I made a FCS policy (in management console) with the following:
- Full scan once a week and quick scan every day
- Check for updates before scanning

I also ran the GPMC modeling tool to check that the policies was applied.

The updates are not installed automatically, except from around 5 am.

Is there something I have forgotten here? You have to do this manually??

Error 0x80240016 downloading definition updates

Fri, 16 Feb 2007 16:10:22 Z

I came in this morning to the nice orange icon in my tray telling me I needed to download definition updates. When I click on "Check for Updates Now" I get "Error found: Code 0x802400016."

What do I need to do to download the updates?

Thanks.

Repeated reinstallation for Forefront Client update after hotfix KB952265

Thu, 24 Jul 2008 16:25:04 Z

I installed KB952265 when it came down from WSUS and it appeared to install successfully. However, my automatic update client now shows the FCS client update (1.0.1703) as a needed update repeatedly. It appears to apply successfully, but automatic updates continues to say it is needed. Anyone else seeing this in the last few days?

Centrally manage the setting "Do not scan files accessed by these processes"

Mon, 23 Jun 2008 08:50:30 Z

Hi all,
Is there a way to centrally manage this setting that is (for the moment) available only in client console??
I've found the solution of copiyng registry keys between PCs but is not so smart.
I think that it may be done via and ADM/ADMX on Active Directory.
I' hope that the FCS team would include this feature in next revision of the product, but the customers are asking me for this feature right now... :)

Thanks,
Marco Lelli

Event Notifications-Any ideas

Mon, 16 Nov 2009 03:05:09 Z

Hi All,

I am getting the following errors in my event viewer from Forefront. Can anyone shed any light on this? Is there someway I can accept these messages across the domain, by adding an exclusion to the policy? Users are convinced these events are causing there machines to run slower.....

Scan ID: {68EE2AB2-54B9-4977-B321-232A9F37AB2D}

Agent: IE Configuration

User: PROD\shanc

Name: Unknown

ID:

Severity: Not Yet Classified

Category: Not Yet Classified

Path Found: iemain:HKCU@S-1-5-21-1606262815-1649469861-2962907493-2295\SOFTWARE\Microsoft\Internet Explorer\Main\\Search Bar

Alert Type: Unclassified software

Process Name:

Detection Type:

Status:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Microsoft Forefront Client Security Real-Time Protection agent has detected changes. Microsoft recommends you analyze the software that made these changes for potential risks. You can use information about how these programs operate to choose whether to allow them to run or remove them from your computer. Allow changes only if you trust the program or the software publisher. Microsoft Forefront Client Security can't undo changes that you allow.

For more information please see the following:

http://go.microsoft.com/fwlink/?linkid=74409

Scan ID: {25BDC744-52B7-4E05-A4FF-0A1C5BB7014C}

Agent: IE Configuration

User: PROD\shanc

Name: Unknown

ID:

Severity: Not Yet Classified

Category: Not Yet Classified

Path Found: iemain:HKCU@S-1-5-21-1606262815-1649469861-2962907493-2295\SOFTWARE\Microsoft\Internet Explorer\Main\\Default_Page_URL

Alert Type: Unclassified software

Process Name:

Detection Type:

Status:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

For more information please see the following:

http://go.microsoft.com/fwlink/?linkid=74409

Scan ID: {FD35BB9C-F216-493D-8351-52AD7E1334C0}

Agent: IE Configuration

User: PROD\shanc

Name: Unknown

ID:

Severity: Not Yet Classified

Category: Not Yet Classified

Path Found: iemain:HKCU@S-1-5-21-1606262815-1649469861-2962907493-2295\SOFTWARE\Microsoft\Internet Explorer\Main\\Start Page

Alert Type: Unclassified software

Process Name:

Detection Type:

Status:

How to delay scan

Mon, 16 Nov 2009 03:08:28 Z

Hi All,

At present I have a policy that says all machines on the network get scanned at 13:00 on a Fri. This is because despite trying to get users to leave pc's on over the weekend some still shut them down. Is there a way I can schedule the policy to run over the weekend? If the pc was shut down over the weekend the scan should run two hours after the pc is switched on so as not to interfere with login scripts, logons etc etc.

Thanks

Forefront installation - Failed to initialize 0x80070424

Sat, 14 Nov 2009 18:27:03 Z

I have the same issue mentioned in another posting, but I already re-installed XP SP2. At first attempt to install Forefront, it failed, apparently because I was not at SP3. I upgraded to SP3 and now I get the "failed to initialize" message. Do I have to re-install again?

Installing one-server topology fails on Windows Server 2008 x86 Standard Edition

Fri, 13 Nov 2009 09:21:43 Z

Hi,
I am trying to install FFCS on a fresh Windows Server 2008 x86 Standard Edition. I have followed http://technet.microsoft.com/da-dk/library/cc901471(en-us).aspx preparing the server for FFCS installation, but when the installation starts, it fails at the very first action (Install the Collection Database).

I have pasted the log below:

Number of verifications started: [13-11-2009 10:16:53]

[13-11-2009 10:16:53] Verification(Verifying operating system requirements)

[13-11-2009 10:16:54] Verification(Verifying hardware requirements)
Warning: Having two or more processors is recommended for the specified component(s). Recommended processor speed (in MHz): 2850
Warning: More RAM is recommended for the specified component(s). Recommended RAM (in MB): 4096
Warning: More disk space is recommended for the specified component(s). Recommended available disk space on drive D (in MB): 107520

[13-11-2009 10:16:54] Verification(Verifying software prerequisites)

[13-11-2009 10:16:55] Verification(Verifying collection database)

[13-11-2009 10:16:55] Verification(Verifying access to collection server)

[13-11-2009 10:16:56] Verification(Verifying DAS account)

[13-11-2009 10:16:56] Verification(Verifying access to reporting server)

[13-11-2009 10:16:56] Verification(Verifying reporting database configuration)

[13-11-2009 10:16:57] Verification(Verifying URLs for reports)

[13-11-2009 10:16:57] Verification(Verifying action account)

[13-11-2009 10:16:58] Verification(Verifying DAS account)

[13-11-2009 10:16:58] Verification(Verifying DTS account)

[13-11-2009 10:16:59] Verification(Verifying reporting database service startup)

Number of verifications completed: [13-11-2009 10:16:59]
Tasks started: [13-11-2009 10:17:01]
Root Directory: E:\SERVER
Current Directory: E:\
[13-11-2009 10:17:01] Task(Install the Collection Database)
Installing from this MSI: 'e:\Server\MOMServer.msi'
Log file: 'C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log'.
[13-11-2009 10:17:01] Task(Install the Collection Database)
Starting Install the Collection Database.
[13-11-2009 10:17:01] Task(Install the Collection Database)
Starting C:\Windows\system32\msiexec.exe.
[13-11-2009 10:17:01] Task(Install the Collection Database)
Process command 'C:\Windows\system32\msiexec.exe'
[13-11-2009 10:17:01] Task(Install the Collection Database)
Process arguments '/i "e:\Server\MOMServer.msi" /norestart /qn /l*v "C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log" INSTALLDIR="C:\Program Files\Microsoft Forefront\Client Security\Server\Microsoft Operations Manager 2005" ADDLOCAL="MOMXDB" MOM_SERVER="server" SQLSVR_INSTANCE="server" DAS_ACCOUNT="das" DAS_PASSWORD="*****" DAS_DOMAIN="domain" DB_SIZE="15360" CONFIG_GROUP="ForefrontClientSecurity" '
[13-11-2009 10:17:07] Task(Install the Collection Database)

[13-11-2009 10:17:07] Task(Install the Collection Database)
The following process failed.
Process: C:\Windows\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [13-11-2009 10:17:07]

Does anyone have an idea, why it is failing?

My SQL-databases are located on D: - is that a problem?

Thanks in advance!

/Michael

Installing Forefront Client Security on server 2008 standard

Tue, 08 Sep 2009 15:44:51 Z

Hi
I am getting these error and have tried what seems to be everything but cannot get past it...
Error: Could not access this address: http://server/Reports Details: The remote server returned an error: (500) Internal Server Error.
Error: Could not access this address: http://TRINBMNP01/ReportServer Details: The remote server returned an error: (500) Internal Server Error.

Can anyone please help me as I seem to have a brick wall on this
many thanks
Shahin

xp forefront client install/uninstall fail manual removal

Wed, 15 Jul 2009 19:50:03 Z

I have an XP client who has a problem with their Forefront Client install. When I attempt to uninstall the Forefront client security antimalware service they are receiving an error "Application failed to initialize: 0x80070424. The specified service does not exist as an installed service".

I have then attempted to install with the /R switch to "force" a reinstall and I receive the same error.

Are there any instructions on MANUALLY REMOVING FOREFRONT so I can then install the client succesfully?

Any help appreciatted.

THANKS

Deploy FCS without MOM agent

Fri, 13 Nov 2009 14:35:05 Z

Is it possible deploy FCS to my domain client without install MOM agent, by using AD-GPO policy?

If yes, how can I do?

Thanks you

FCS /NOMOM fail with wsus

Thu, 12 Nov 2009 17:41:14 Z

Hi, to all and sorry for my poor English

I have installed my FCS on a notebook that is not domain member by doing this tasks.
-Forced Windows Update to point my local Wsus by editing local policy; (Wsus test pass successful)
-CLIENTSETUP /NOMOM
-FCSLOCALPOLICYTOLS /I FCS.REG

In my installed application I can’t initially seen any Microsoft MOM 2005 client Agent, but as soon as client windows update contact my wsus, it want upgrade my FCS (Client) and virus definition to newer version.
-Definition upgrade was ok.
-Client installation start but fail with error!

After the installation failure, I can see in my installed application a new entry: Microsoft MOM 2005 client Agent.
Why the local wsus try to install MOM client when upgrade my FCS on my notebook, even if I have initially installed with /NOMOM And why the upgrade fail?

Thanks

Action: Collection server role Failures

Tue, 09 Jan 2007 16:58:46 Z

Hi, I'm doing a single server test setup and am running into the following error during the installation of "Collection Server Disabling Rules"

[1/9/2007 11:52:36 AM] Task(Collection Server Disabling Rules)

Exception Execution against the runtime failed. See inner exception for more details.

Stacktrace

at Microsoft.EnterpriseManagement.Mom.Internal.RuntimeInterop.CommitConfigurationChange(String momServer, String configurationName)

at Microsoft.EnterpriseManagement.Mom.ManagementServer.CommitConfigurationChange()

at Microsoft.Forefront.ClientSecurity.Configure.MOMDisableMOMRulesTask.CollectionServerTask()

at Microsoft.Forefront.ClientSecurity.Configure.MOMDisableMOMRulesTask.ThreadedWebServiceTask(Object x)

Any thoughts on this issue? Everything else completes successfully (except for the three steps following this error). Thanks!

ForeFont Server Installation, Error at MOM Reporting Service, return code 1603

Thu, 05 Nov 2009 09:28:34 Z

Hi

I am trying to install forefront Server in an office environment.. But i got stuck while it reached Install MOM reporting service.
The Server is installed with SQL Server 2005 and OS with windows Server 2003 with SP 1 ...

I got the following log error in the installation time...
Please help me to solve this as it is a critical situation.

Property(S): Welcome_Title = Welcome to the Microsoft Operations Manager 2005 Reporting Setup Wizard
Property(S): SP1WelcomeDlg_Title = Welcome to the Microsoft Operations Manager 2005 SP1 Software Update Wizard
Property(S): Welcome_Desc = The wizard will install Microsoft Operations Manager 2005 Reporting on your computer. To continue, close all other programs and click Next.
Property(S): PatchWelcomeDlg_Desc = The wizard will Update MOM 2005 Reporting on your computer. To continue, close all other programs and click Next.
Property(S): Maintenance_Text2 = The setup wizard will allow you to reinstall or remove Microsoft Operations Manager 2005 Reporting. To continue, click Next.
Property(S): Resume_ResumeText = The setup wizard will complete the suspended installation of Microsoft Operations Manager 2005 Reporting on your computer. To continue, click Next.
Property(S): Resume_PreselectedText = The setup wizard will complete the installation of Microsoft Operations Manager 2005 Reporting on your computer. To continue, click Next.
Property(S): Resume_Text1 = Resuming the setup wizard for Microsoft Operations Manager 2005 Reporting
Property(S): ProgressDlg_Desc1 = The program components you selected are being installed.
Property(S): ProgressDlg_Desc2 = The program components you selected are being uninstalled.
Property(S): ProgressDlg_Title1 = Installing Microsoft Operations Manager 2005 Reporting
Property(S): ProgressDlg_Title2 = Uninstalling Microsoft Operations Manager 2005 Reporting
Property(S): ProgressDlg_Text1 = Please wait while the setup wizard installs Microsoft Operations Manager 2005 Reporting. This may take several minutes.
Property(S): ProgressDlg_Text2 = Please wait while the setup wizard uninstalls Microsoft Operations Manager 2005 Reporting. This may take several minutes.
Property(S): Progress_lbStatus = Status:
Property(S): InitDlg_Text1 = Welcome to the Microsoft Operations Manager 2005 Reporting Setup Wizard
Property(S): InitDlg_Text2 = Please wait while the setup wizard prepares to guide you through the setup.
Property(S): Exit_DlgTitle = Completing the Microsoft Operations Manager 2005 Reporting Setup Wizard
Property(S): ExitDialog_RunDTSTask = Transfer data from the MOM database now
Property(S): Exit_DlgDesc1 = The setup wizard has successfully installed Microsoft Operations Manager 2005 Reporting. To close this wizard, click Finish.
Property(S): Exit_DlgDesc2 = The setup wizard has successfully uninstalled Microsoft Operations Manager 2005 Reporting. To close this wizard, click Finish.
Property(S): UserExit_FinishText1 = Your system has not been modified. To install this program at a later time, please run the installation again.
Property(S): UserExit_RestContText1 = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
Property(S): UserExit_TextLine = The setup wizard was interrupted before Microsoft Operations Manager 2005 Reporting could be installed.
Property(S): FatalError_FinishText1 = Your system has not been modified. To complete installation at another time, please run setup again.
Property(S): FatalError_RestContText1 = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
Property(S): FatalError_RestContText2 = Click Restore or Continue Later to exit the wizard.
Property(S): FatalError_TextLine = The setup wizard was interrupted before Microsoft Operations Manager 2005 Reporting could be installed.
Property(S): DirectorySelectionDlg_Title = Destination Folder
Property(S): DirectorySelectionDlg_Text = Click Next to install in this folder, or click Change to install in a different folder.
Property(S): DirectorySelectionDlg_Path = Install Microsoft Operations Manager 2005 Reporting to:
Property(S): ReadyToInstallDlg_Desc = The setup wizard is ready to begin installation.
Property(S): ReadyToInstallDlg_Title1 = Ready to Modify the Program
Property(S): ReadyToInstallDlg_Title3 = Ready to Install
Property(S): ReadyToInstallDlg_Text1 = Click Install to begin the installation.
Property(S): ReadyToInstallDlg_Text2 = If you want to review or change any of your installation settings, click Back. Click Cancel to exit the setup wizard.
Property(S): ReadyToRemoveDlg_Text1 = Click Remove to remove Microsoft Operations Manager 2005 Reporting from your computer. After removal, this program will no longer be available for use.
Property(S): ReadyToRemoveDlg_Text2 = If you want to review or change any settings, click Back.
Property(S): ReadyToRemoveDlg_Title = Remove the Program
Property(S): ReadyToRemoveDlg_Desc = You have chosen to remove the program from your system.
Property(S): FileInUse_DlgTitle = Files in Use
Property(S): FileInUse_DlgDesc = Some files that need to be updated are currently in use.
Property(S): FileInUse_DlgText = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
Property(S): RegisterUserDlg_Name = &User Name:
Property(S): RegisterUserDlg_Company = &Organization:
Property(S): RegisterUserDlg_Title = Registration Information
Property(S): RegisterUserDlg_Desc = Enter your name. It is not necessary to enter a company name.
Property(S): LicenseDlg_Desc = Please read the following License Agreement. Press the PAGE DOWN key to see the rest of the agreement.
Property(S): LicenseDlg_Title = End-User License Agreement
Property(S): DiskSpaceDlg_Text = The highlighted volumes do not have enough disk space available for the currently selected components. You can remove files from the highlighted volumes, choose to install less components onto local drives, or select different destination drives.
Property(S): DiskSpaceDlg_Title = Disk Space Requirements
Property(S): DiskSpaceDlg_Desc = The disk space required for the installation of the selected components.
Property(S): MaintenanceDlg_Remove = Remove Microsoft Operations Manager 2005 Reporting from your computer.
Property(S): MaintenanceDlg_Title = Program Maintenance
Property(S): MaintenanceDlg_Desc = Repair, or remove the program.
Property(S): MaintenanceDlg_Repair = Repair Microsoft Operations Manager 2005 Reporting. Use this option to fix missing or corrupt files, shortcuts, and registry entries.
Property(S): BrowseFolderDlg_Combo = &Look in:
Property(S): BrowseFolderDlg_Tail = &Folder name:
Property(S): BrowseFolderDlg_Desc = Browse to the destination folder.
Property(S): BrowseFolderDlg_DescData = Browse to the folder you want to create database data file in.
Property(S): BrowseFolderDlg_DescLog = Browse to the folder you want to create database log file in.
Property(S): BrowseFolderDlg_Title = Change Current Destination Folder
Property(S): BrowseFolderDlg_TitleData = Change Database Data File Folder
Property(S): BrowseFolderDlg_TitleLog = Change Database Log File Folder
Property(S): OutOfSpaceDlg_Title = Out of Disk Space
Property(S): OutOfSpaceDlg_Text = The highlighted volumes do not have enough disk space available for the currently selected components. You can remove files from the highlighted volumes, choose to install less components onto local drives, or select different destination drives.
Property(S): OutOfSpaceDlg_Desc = Disk space required for the installation exceeds available disk space.
Property(S): CancelSetupDlg_Text = Are you sure you want to cancel the Microsoft Operations Manager 2005 Reporting installation?
Property(S): SetupErrorDlg_Error = <error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here>
Property(S): User_Account = &User Name:
Property(S): User_Password = &Password:
Property(S): User_Domain = &Domain or local computer:
Property(S): AccountVerificationErrDlg_Text3 = To continue setup, go back and enter the correct account information.
Property(S): DatabaseOptionsDlg_Title = Database and Log File Information
Property(S): DatabaseOptionsDlg_Desc = Enter the size and location for the database data and log files. For more information about calculating the space required, refer to the product documentation.
Property(S): DatabaseOptionsDlg_Size = Database size:
Property(S): DatabaseOptionsDlg_DataLocation = Data file location:
Property(S): DatabaseOptionsDlg_LogLocation = Log file location:
Property(S): DatabaseOptionsDlg_FilesGroup = Database files
Property(S): AdvancedDBOptionsDlg_Title = Database Files Location
Property(S): AdvancedDBOptionsDlg_Desc = Select the location for the database and log files
Property(S): AdvancedDBOptionsDlg_DataLoc = Database Data File Location:
Property(S): AdvancedDBOptionsDlg_LogLoc = Database log file location:
Property(S): DatabaseOptionsErrDlg_Title1 = Invalid Database Size
Property(S): DatabaseOptionsErrDlg_Title2 = Out of disk space
Property(S): DatabaseOptionsErrDlg_Title3 = Database Or Database Files Already Exists
Property(S): DatabaseOptionsErrDlg_Text11 = The Microsoft Operations Manager 2005 Reporting database requires a minimum of 300MB. To continue setup, go back and change the database size to be greater or equal to 300.
Property(S): DatabaseOptionsErrDlg_Text12 = Setup found that the selected database files locations do not contain sufficent disk space. To continue setup go back and either choose a different drive or reduce the database size.
Property(S): DatabaseOptionsErrDlg_Text13 = Setup found that either the selected database instance already contains the 'Microsoft Operations Manager 2005 Reporting' database or the specified file locations already contain database files RepData.mdf or RepLog.ldf. To continue setup go back and either remove the database, database files, or select a different directory.
Property(S): SQLServerInstanceDlg_Title = SQL Server Database Instance
Property(S): SQLServerInstanceDlg_Desc = Select the name of the SQL Server instance to host the Microsoft Operations Manager 2005 Reporting database.
Property(S): SQLServerInstanceDlg_Note = (Note: Setup will automatically start the Microsoft SQL Server and SQL Server Agent services if they are not running.)
Property(S): SQLServerInstanceDlg_SQLServer = SQL &Server Instance
Property(S): RosettaServerDlg_Title = SQL Server Reporting Services Server
Property(S): RosettaServerDlg_Desc = Select the machine name of the SQL Server Reporting Services Server.
Property(S): RosettaServerDlg_RosettaServer = Enter the SQL Server Reporting Services &Server Name
Property(S): RosettaServerDlg_ManualRosettaVDirs = &Automatically detect virtual directories
Property(S): RosettaServerDlg_ReportServerVDir = Report Server &Virtual Directory (e.g. ReportServer)
Property(S): RosettaServerDlg_ReportManagerVDir = Report Manager Virtual &Directory (e.g. Reports)
Property(S): RosettaServerDlg_Desc2 = For example by specifying "ReportServer", report server can be accessed as: http://<servername>/ReportServer
Property(S): ClusterNode_Text = &Passive node of a Windows Server Cluster
Property(S): OperationalDataReportingSettingsDlg_Title = Operational Data Reports Settings
Property(S): OperationalDataReportingSettingsDlg_Yes = &Yes, I want to send operational reports (Recommended)
Property(S): OperationalDataReportingSettingsDlg_No = N&o, I do not want to send operational reports
Property(S): OperationalDataReportingSettingsDlg_Desc = Enabling this feature requires a MOM Agent to be installed.
Property(S): ReadyToInstall_DlgDesc_UpgradeText = The wizard is ready to begin Operations Manager Reporting Services upgrade.
Property(S): ReadyToInstall_DlgText_UpgradeText = Click Upgrade to begin the upgrade.
Property(S): ButtonText_Upgrade = &Upgrade
Property(S): Upgrade_Welcome_Text1 = Welcome to the Microsoft Operations Manager 2005 Reporting Upgrade Wizard
Property(S): Upgrade_Welcome_Text2 = Select this option to upgrade your Microsoft Operations Manager 2005 Reporting. Setup will remove previous versions, and install the new version based on your current configuration.
Property(S): Upgrade_Welcome_Text3 = It is recommended that you back up your database prior to starting the upgrade.
Property(S): UpgradeVerification_Text = Upgrade MOM 2005 Reporting
Property(S): SQLServerNotFoundDlg_Title = Microsoft SQL Server 2000 Service Pack 3 or Higher Not Found
Property(S): SQLServicesErrDlg_Title = Setup failed to start Microsoft SQL Server services
Property(S): SQLServerNotFoundDlg_Text1 = The Microsoft Operations Manager 2005 Reporting database component requires Microsoft SQL Server 2000 Service Pack 3 or above version. The selected instanace does not have the correct version. To continue setup, go back, choose custom setup, and unselect the database component.
Property(S): SQLServicesErrDlg_Text1 = The Microsoft Operations Manager 2005 Reporting setup failed to start Microsoft SQL Server services. To continue setup, start the SQL Server services for the selected SQL Server instance or go back and choose a different SQL Server instance.
Property(S): LicenseDlg_No = I &do not accept the terms in the license agreement
Property(S): LicenseDlg_Yes = I &accept the terms in the license agreement
Property(S): DatabaseOptionsDlg_MB = MB
Property(S): MOMDBServerDlg_Title = MOM Database Server Instance
Property(S): MOMDBServerDlg_Desc = You have chosen to install a Microsoft Operations Manager 2005 component that requires a MOM database.
Property(S): MOMDBServerDlg_Help = Type the name of the SQL Server instance that hosts the Microsoft Operations Manager database.
Property(S): MOMDBServerDlg_DBInstance = &MOM Database Server (server\instance)
Property(S): MOMDBServerErrDlg_Title1 = MOM Database Server Name cannot be Blank
Property(S): MOMDBServerErrDlg_Title2 = Setup was unable to contact the database server.
Property(S): MOMDBServerErrDlg_Title3 = Invalid Microsoft Operations Manager Database Version
Property(S): MOMDBServerErrDlg_Title4 = Invalid Microsoft Operations Manager Database Version
Property(S): MOMDBServerErrDlg_Title5 = Unable to determine Microsoft Operations Manager Database Version
Property(S): MOMDBServerErrDlg_Text1 = You did not provide a name for the MOM database server name. To provide the MOM database server name, click Back. Click Cancel to exit the installer.
Property(S): MOMDBServerErrDlg_Desc11 = Missing MOM database server name.
Property(S): MOMDBServerErrDlg_Desc12 = To continue setup, go back and provide a database server computer name which hosts the Microsoft Operations Manager database.
Property(S): MOMDBServerErrDlg_Desc21 = Setup was unable to locate a MOM database on the specified database server.
Property(S): MOMDBServerErrDlg_Desc22 = To continue setup, go back and either change the database server name or verify that Microsoft SQL Server is running on the specified computer and that the database is installed.
Property(S): MOMDBServerErrDlg_Desc31 = Setup found that the Microsoft Operations Manager database version on the specified database server is not the same as the current product version.
Property(S): MOMDBServerErrDlg_Desc32 = To continue setup, go back and either change the database server name or upgrade the database on the specified server to the current version.
Property(S): MOMDBServerErrDlg_Desc41 = Reporting cannot be installed against a MOM Express install
Property(S): MOMDBServerErrDlg_Desc42 = To continue setup, go back and change the database server name to a non-express version of Microsoft Operations Manager.
Property(S): MOMDBServerErrDlg_Desc51 = Unable to determine the Microsoft Operations Manager Database Version
Property(S): MOMDBServerErrDlg_Desc52 = To continue setup, go back and change the database server name or validate that MOM is installed peroperly.
Property(S): MOMReportURLDlg_Text1 = You have chosen to install a Microsoft Operations Manager component that requires a Reporting Server.
Property(S): MOMReportURLDlg_Text2 = Type the name of the Report Server that will host the Microsoft Operations Manager Reports.
Property(S): MOMReportURLDlg_Server = &Report Server
Property(S): MOMReportURLDlg_Title = Microsoft Operations Manager Reports Server
Property(S): ReportingNotInstalled = Microsoft SQL Server Reporting Services must be installed prior to installing Microsoft Operations Manager 2005 Reporting.
Property(S): MinimumOSMsg = This product must be installed on Windows 2000 or later.
Property(S): NetFrameworkNotInstalled = The .NET framework is required to install this application.
Property(S): NotAdministrator = This product requires administrator privileges to install.
Property(S): SchedulerTaskAccountDlg_Title = Data Transfer Task Account
Property(S): SchedulerTaskAccountDlg_Desc = Specify a domain account that has access to both the MOM database and the Microsoft Operations Manager 2005 Reporting database.
Property(S): SchedulerTaskAccountDlg_Help = The Data Transfer Task Account will be used to run the scheduled task to transfer data between the MOM database and the MOM reporting database.
Property(S): AccountVerificationErrDlg_Text1 = Setup is unable to confirm the account.
Property(S): AccountVerificationErrDlg_Title = Account Verification Error
Property(S): PreReqResultDlg_PreReq_Recommended_Not_Met = The recommended requirements are not met. You may continue to install MOM, but optimal performance may not be achieved. Click on View Log for more information.
Property(S): PreReqResultDlg_PreReq_Met = Requirements are met for the installation. Click on View Log for more information.
Property(S): PreReqResultDlg_PreReq_Not_Met = The minimum requirements are not met. Click on View Log for more information
Property(S): PreReqResultDlg_PreReq_No_Component_Selected = No Components have been selected for install. Please go back and select one or more components for install.
Property(S): PreReqResultDlg_Title_PreReq_Met = Prerequisite Check Passed
Property(S): PreReqResultDlg_Title_PreReq_Recommended_Not_Met = Prerequisite Check Passed with Warnings
Property(S): PreReqResultDlg_Title_PreReq_Not_Met = Prerequisite Check Failed
Property(S): ButtonText_ViewLog = &View Log
Property(S): ReportingUserDlg_Title = Reporting User Account
Property(S): ReportingUserDlg_Desc = Specify the credentials that should be used by the MOM Reporting Server to connect to the MOM Reporting database.
Property(S): This_Computer = (this Computer)
Property(S): _CreateDatabase.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = REPORTINGDW QIQ-SRR1-SUS1 SystemCenterReporting 1024 C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
Property(S): _RollBack_CreateDatabase.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = REPORTINGDW QIQ-SRR1-SUS1 SystemCenterReporting
Property(S): _ExecuteSqlScripts.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = REPORTINGDW QIQ-SRR1-SUS1 SystemCenterReporting 1 DWBuildReportingSQL C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Database\Build_reporting_db.sql DWMOM2005LocaleSQLInstall C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Database\MOMDW2005LOCALE.sql DWMOM2005SP1 C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Database\MOMXDWSP1Upgrade.sql
Property(S): _ImportSchema.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\SMC.ImportSchema.dll;C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Schema\;QIQ-SRR1-SUS1;SystemCenterReporting;true
Property(S): _GenerateMTViews.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\SMC.MTViewGenerator.dll;QIQ-SRR1-SUS1;SystemCenterReporting;C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\PropertyViews.sql;
Property(S): _ImportReports.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\MOM.Reporting.ReportImportExport.dll;C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\MicrosoftOperationsManager2005Reports.xml;http://QIQ-SRR1-SUS1//ReportServer;QIQ-SRR1-SUS1;SystemCenterReporting
Property(S): _LinkReporting = Write QIQ-SRR1-SUS1 OnePoint http://QIQ-SRR1-SUS1//ReportServer http://QIQ-SRR1-SUS1//Reports/Pages/Folder.aspx?ItemPath=%2fMicrosoft+Operations+Manager+Reporting&IsDetailsView=False QIQ-SRR1-SUS1 SystemCenterReporting
Property(S): _Rollback_LinkReporting = Delete QIQ-SRR1-SUS1 OnePoint http://QIQ-SRR1-SUS1//ReportServer http://QIQ-SRR1-SUS1//Reports/Pages/Folder.aspx?ItemPath=%2fMicrosoft+Operations+Manager+Reporting&IsDetailsView=False QIQ-SRR1-SUS1 SystemCenterReporting
Property(S): _AddSchedulerTask = **********
Property(S): _CreateDataSource.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = **********
Property(S): _RegisterDTSEventSource.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\MOM.Datawarehousing.DTSPackageGenerator.exe
Property(S): _ExecuteStoredProcedures.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = QIQ-SRR1-SUS1 SystemCenterReporting p_SetupLogins N'QIQ-SRR1-SUS1' p_CreateDWGroomJob @ownerLogin=N'qiqatar\fcsadmin',@destCatalog=N'SystemCenterReporting'
Property(S): _SetSCSecurity = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\
Property(S): _CreateLocalGroups = SC DW Reader SC DW Reader can view data in SC DW database SC DW DTS SC DW DTS can view data in MOM DB, can modify data in SC DW database
Property(S): _Rollback_CreateLocalGroups = SC DW Reader
Property(S): _AddUserAccountToLocalGroup = SC DW Reader qiqatar\fcsadmin SC DW DTS qiqatar\fcsadmin SC DW DTS qiqatar\fcsadmin QIQ-SRR1-SUS1
Property(S): VersionNT = 502
Property(S): SecureCustomProperties = MOMX_REPORTING_FOUND
Property(S): Redist.51D569E0_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): MS.51D569E0_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): System.51D569E0_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): Redist.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): MS.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): System.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\WINDOWS\system32\
Property(S): ReportingModuleDir.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\
Property(S): REPORTING_DIR.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\
Property(S): RESOURCE_DIR.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\en\
Property(S): DATABASE_DIR.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Database\
Property(S): SCHEMA_DIR.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Schema\
Property(S): _RollbackDTSEventSource.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\MOM.Datawarehousing.DTSPackageGenerator.exe
Property(S): _SetReportingFolderSecurity.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting
Property(S): SQLSVR_INSTANCE.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = QIQ-SRR1-SUS1
Property(S): DatabaseName.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = SystemCenterReporting
Property(S): MOM_DB_SERVER.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = QIQ-SRR1-SUS1
Property(S): ROSETTA_SERVER.B8A67CEF_63FF_40C5_B79F_68FE309F3E50 = QIQ-SRR1-SUS1
Property(S): ServerReportingCmnModuleDir.0FBCB50B_2336_4A38_9BCC_74F7EB32265C = C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\
Property(S): PackageCode = {F51B3310-5805-4174-86B8-AF0013E818DD}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): HTTPCONNECTIONTYPE = http://
Property(S): CURRENTDIRECTORY = I:\AUTORUN
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 4628
Property(S): CURRENTMEDIAVOLUMELABEL = FCS_RTM_EN-US_1703.0
Property(S): VersionDatabase = 200
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 3790
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\fcsadmin\LOCALS~1\Temp\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\fcsadmin\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\fcsadmin\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\fcsadmin\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\fcsadmin\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\fcsadmin\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\fcsadmin\Recent\
Property(S): SendToFolder = C:\Documents and Settings\fcsadmin\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\fcsadmin\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\fcsadmin\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 4085
Property(S): VirtualMemory = 4848
Property(S): AdminUser = 1
Property(S): LogonUser = fcsadmin
Property(S): UserSID = S-1-5-21-1646942584-1055729856-2927860159-1108
Property(S): UserLanguageID = 1033
Property(S): ComputerName = QIQ-SRR1-SUS1
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1440
Property(S): ScreenY = 900
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 12:18:39
Property(S): Date = 11/5/2009
Property(S): MsiWin32AssemblySupport = 5.2.3790.1830
Property(S): RedirectedDllSupport = 2
Property(S): DATABASE = C:\WINDOWS\Installer\3a1144.msi
Property(S): OriginalDatabase = i:\Server\MOMReporting.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): CLUSTERED = 0
Property(S): SOURCEDIR = i:\Server\
Property(S): SourcedirProduct = {63C847C6-07A0-4A6F-8A78-8A066C9F9773}
Property(S): ProductToBeRegistered = 1
MSI (s) (64:20) [12:18:39:161]: Note: 1: 1708
MSI (s) (64:20) [12:18:39:161]: Product: Microsoft Operations Manager 2005 Reporting -- Installation failed.

MSI (s) (64:20) [12:18:39:161]: Cleaning up uninstalled install packages, if any exist
MSI (s) (64:20) [12:18:39:161]: MainEngineThread is returning 1603
MSI (s) (64:E8) [12:18:39:271]: Destroying RemoteAPI object.
MSI (s) (64:18) [12:18:39:286]: Custom Action Manager thread ending.
=== Logging stopped: 11/5/2009 12:18:39 ===
MSI (c) (14:A0) [12:18:39:286]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (14:A0) [12:18:39:286]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/5/2009 12:18:39 ===

thanks alot
Sameer

Active Directory Security Group

Mon, 09 Nov 2009 00:21:05 Z

I would like to find out, that all the security group of AD, where it is implemented. Like for example I have a security group called GRP Client Access. I would like to kno where i i have used this security group, what are the folders, and files have this security group. Simmilarly, i would like to know all the security groups in my AD where it is using at the moment

FCS & WIn Server 2008 R2

Sun, 08 Nov 2009 13:33:48 Z

بسم الله الرحمن الرحيم
what can i do ?
I have SCCM 2007 SP2 + WSUSSP2 + SQL 2005 SP3 on Windows server 2008 R2
I want install FCS server and FCS server need SQL & WSUS server But FCS not support Windows 2008 R2 and i can't run FCS CD on 2008 R2
I can setup it on another server but how can connect My WSUS and SQL without run FCS CD on 2008 R2

Clients going into unmanaged mode

Mon, 02 Nov 2009 20:55:31 Z

Is there a document that describes the rules that forefront uses to put machines into the pending actions group with a pending action of "uninstall agent". I am trying to figure out the details of what this means.

Help with running Forefront Client Security

Mon, 02 Nov 2009 20:51:29 Z

Hey guys, I'm new to Microsoft Forefront Client Security and I am having a few problems. I have done a one server topology server setup. I installed everything on a VM server (which is my FCS management server) except the distribution server component. I have a external (seperate server) setup for WSUS that we use in our corporate environment. I have installed forefront on my management serverand finally got the 14 day chart to come up. Next I setup a XP workstation as a VM for a test client. I then setup a group policy in the FCS console to point at an OU that has this XP workstation in it. My reason for doing this is to install the agent and the components. BUT I cannot get it to install anything. I have approved forefront on my WSUS server and only told it to install the updates to this computer in a group on the WSUS server. What am I missing to get this to install the agent without me doing it manually? Also, I installed the agent manually and it still won't report in to the dashboard on the FCS console. Do I need the distribution server? I would hate to have to install these manually, I need to do this through GPO, but right now after a manual installation it still won't report it and I don't see the agent in the taskbar. Can you guys help? I have checked everything in the MOM 2005 admin console that is supposed to be there, its all enabled.

Forefront Client Security Server - Reinstallation Issues

Tue, 03 Nov 2009 22:35:11 Z

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?

Extending Microsoft Front Front Security server across AD Forests

Wed, 04 Nov 2009 07:07:08 Z

Hi,

we are planning to implement the Microsoft Forefront security for our organization. Our organization has spread across many sites and has many ActiveDirectory forest..would like to know how to design the forefront security architeture for these multiforest scenario's.

Objective is , Forefront security policy and polling needs to be executed centrally and VDf updates needs to be pushed to the clients from their local AD site and local AD forest.

Could you please assit me to design..

FCS installation Issue

Wed, 04 Nov 2009 16:30:35 Z

Hi all,

       Im trying to instal FSC (FCS_RTM_EVAL_en-us_1703.0) on a server 2008 Standard x64, with only WSUS SP2 (needed) and SQL 2005 (32Bit)

       Im having this error, when setup gets to Collection Server Disabling Rules:

       Starting collection server disabling rules.
[04-11-2009 15:45:01] Task(Collection Server Disabling Rules)
Microsoft.EnterpriseManagement.Mom.MomSdkException: Loading the rule failed. ---> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {31CFCB56-0A22-4176-927E-5EEDD3C252D5} failed due to the following error: 80040154.
   at Microsoft.EnterpriseManagement.Mom.Rule.Intialize()
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Mom.Rule.Intialize()
   at Microsoft.EnterpriseManagement.Mom.Rule..ctor(DasProcessRule dasRule)
   at Microsoft.EnterpriseManagement.Mom.Administration.GetRule(Guid ruleId)
   at Microsoft.Forefront.ClientSecurity.Configure.MOMDisableMOMRulesTask.CollectionServerTask()
   at Microsoft.Forefront.ClientSecurity.Configure.MOMDisableMOMRulesTask.ThreadedWebServiceTask(Object x)Number of tasks completed: [04-11-2009 15:45:02]

    I already seen a post with this error, but the DAS account already belongs to local administrators group, and the problem persist....
    Can you help me solve this problem?

    Thank you very much

Forefront client computers not schedule scanning

Tue, 03 Nov 2009 16:11:02 Z

Hello fellow Forefronters:

I have looked and looked before I made a new post with no results. And I have been going back and forth where to put this post here or in the group policy forum.

My client computers are not scanning when scheduled to. I have several policies created in Forefront Client Security "Policy Management" and I have confirmed that my policies are making it to my Active Directory Organizational Units. Now the problem is that my clients registry entries are broke. HKLM\Software\Policies\Microsoft\Microsoft Forefront\Client Security\1.0. I have over 1000 computers so un-joining and rejoining them one by one isn't an option. GPUPDATE /Force also don’t work. Making a test policy in "Policy Management" and a test Organization Unit in Active Directory and adding a single computer also doesn't work. I know that the problem is that my client registry isn't correct. Is there a place in Start\Run\gpedit.msc on a client where I can find the break down? Is there a way to see the Forefront Policy as you would the Group Policy MMC? Or can someone help me with this? Thank you very much for your time and interest.

Jake

Deploying FCS on Windows 7 32bit

Tue, 03 Nov 2009 21:42:49 Z

I am trying to deploy FCS on Windows 7 32bit. It fails.
The other box is frustrating too. one error is the firewall, which is off and the other is that Task sheduler is not running, but in the services.msc the task scheduler shows that it is running.
here is on log.
p: 172.16.3.150
[03/11/2009 16:15:43] Recconecting
[03/11/2009 16:15:43] Executing Forefront Installations
[03/11/2009 16:15:43] executing proccess: 3724
[03/11/2009 16:16:14] Failed to install Forefront cilent
StackTrace: at Microsoft.FCS.deployment.Wmi.install(Object obj) in C:\projects\Microsoft.FCS.Deployment\Microsoft.FCS.Deployment\classes\Wmi.cs:line 547

Could not find file '\\GVMITDIR03\C$\15c28818-d38c-4618-b6cc-217b7e16ee9a\forefront\clientsetup.log'.
StackTrace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)

at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)

at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)

at System.IO.StreamReader..ctor(String path, Encoding encoding)

at System.IO.File.ReadAllText(String path, Encoding encoding)

at Microsoft.FCS.deployment.Wmi.install(Object obj) in C:\projects\Microsoft.FCS.Deployment\Microsoft.FCS.Deployment\classes\Wmi.cs:line 532

adam Lussier

Forefront Client Security Client on a File Server - Or Not?

Wed, 30 Sep 2009 15:09:22 Z

Does anyone else have the Forefront Client Security client installed on their Windows 2008 file server? We recently ran into an issue where we had to disable the real-time protection of a malware product (CounterSpy) on our file server because it was causing lockups every week or so. We continue to keep the Forefront Client running on the server in real-time mode however.

In talking to my colleages, I've found that many say they do not have AV or Malware protection running on their file server; they say they stay protected at the client-pc level so why put that load on the server? Some have AV and Malware installed but don't run it in real-time mode, they only scan their servers every night. I've never looked at it that way and wonder what others are doing in the same situation.

Orange County District Attorney

Remote Single Server

Thu, 29 Oct 2009 22:24:56 Z

I lease a dedicated Windows 2003 SP2 server from Godaddy.

I would like to use Forefront Client Security to protect it.

Do I need to install all components (remember, the server is "isolated" from my LAN, so I have no desktops or servers to manage or protect).

Is there a way to install only a subset of the components?

Thank you for your help.

Reassigning clients to different MS

Fri, 30 Oct 2009 19:01:19 Z

We have started deploying FCS with our SCCM environment.

Due to acquisitions our number of clients will surpass 10,000.

Would like to know an easier/best practice way to reassign clients and servers to different MS.
i.e. FCSPOD1 to FCSPOD2

Reinstalling Forefront Client Security issue

Thu, 27 Sep 2007 08:28:34 Z

Dear experts,

I have installed Forefront Client Security successfully and clients got installed on the member computers in the security group created on Active Directory. For disk space reasons and crashing problems, I decided to re-format and re-install the client security server. After re-installation (with the same computer name), i was thinking it will still connect to both WSUS and Forefront servers and would report fine since I used the same computer name and same IP address.

It didnt work, no computers connecting to wsus nor to the forefront server. I tried renaming the computer to another name, deploying a new policy to the same security group but still not working.

Would anyone please enlighten me.

Many thanks,

Joel

SQL for 3 server topology

Sun, 25 Oct 2009 14:40:31 Z

Hello.
I'm trying to deploy FFCS in 3 server topology. We have a server with SQL Ent. installed, and another one with WSUS, so I think the 3 server topology is the best choice.
The reporting database server role require SQL Std./Ent. - that's ok. But the Management, collection and reporting server role require one more SQL Std./Ent.
My company is an MS Golden Partner, so we have limited licenses for SQL server. If you buy the FFCS, you get the licence for SQL Ent. included to the FFCS license, but in the case of MS Golden Partner internal use rights it is not the same. Golden Partner should use the licence for SQL Ent. granted for internal use.
And it may be OK for all-in-one topology, but looks bad for 3 and more server topology.
All SQL licenses for internal use are utilised. Do anybody know how to solve this problem without payments. The installation of the FFCS on the server with SQL Ent. thet i'm going to use for the reporting database server role is restricted.

Best regards