Forefront Security for Office Communications Server Forum

Forefront for OCS R2 - problem after latest Windows Updates

Fri, 11 Sep 2009 10:34:11 Z

I had the evaluation version of Forefront installed and working on our OCS R2 Front End Servers with no problems. After installation of the latest round of windows updates (KB956844, KB971961, KB968816 and KB96723 ) I found that the Front End OCS service was unable to start. To resolve this I deactivated the Front End Service and reinstalled it, which solved the problem. However, after this I had an error in Forefront saying "unable to connect to scan job". The services were still running OK, but users were unable to sign into OCS on this server. In an attempt to resolve this I removed and reinstalled Forefront. After doing this I was still getting the "unable to connect to scan job" error and the OCS front end service was unable to restart again. Any ideas on what might be the problem? I don't seem to be able to fully the remove Forefront by Add/Remove programs as configuration settings are still retained from the previous install. At the moment I have removed Forefront from the server again and OCS services are running properly again but obviously don't want to reinstall Forefront again if it's going to break things!

Installation question

Fri, 06 Nov 2009 16:24:59 Z

I have two questions, first, should FSOCS be installed on both the Edge and Pool server? Also, is it supported to have the Forefront client installed on the server along with the Server portion for the Com server?

Forefront for OCS R2 Edge server error

Thu, 03 Sep 2009 03:34:26 Z

Hi,

After install the forefront on my edge server, have the below error and i have no idea what going on. The notification account I have double checked is correct. Any idea?

Event: 10162

Source: ForefrontNotificationAgent

Wed Sep 02 15:20:31 2009 ( 5564- 8), "ERROR: Microsoft.FSO.IMClient.dll.IMClient.RaiseLoginDone("<System.Boolean success><System.String message>") - Error occured logging in to server: 80EE00A6:

Event: 10161

Source:ForefrontNotificationAgent

Wed Sep 02 15:20:31 2009 ( 5564- 8), "ERROR: ForefrontNotificationAgent.exe.NotificationAgent.imClient_LoginDone("<System.Object sender><FSOIMClient.ReportSuccessEventArgs e>") - Failed to login."

Event 9

Source: ForefrontUC

The description for Event ID ( 9 ) in Source ( ForefrontUC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ForefrontUC.

Andy

OCS File Transfers across firewalls

Tue, 21 Apr 2009 12:56:43 Z

Hi
I thought that forefront would facilitate file transfers across firewalls since its not TFTP TCP 6891-6900 peer 2 peer anymore.
But I'm somewhat confused:
Test Setup:
User A at home office connects to OCS 2007 R2 Edge remotely, User B in office is connected to OCS frontend server
B sends file to A -> Forefront on Edge detects it, ok (note: A downloads the file from Edge on TCP 6891)
A sends file to B -> transfer does not work. It seems that the Edge server tries to download the file from the home user A but fails since
A sits behind a NAT router).
So sending out files to remote access users and federated users works, but not sending in files from remote access users or
between such users with NATting firewalls between.
Is this supposed to be so?

Andreas

Forefront for OCS - WebConference/LiveMeeting Scanning?

Thu, 01 Oct 2009 06:52:38 Z

Hi,
we have a simple question, can Forefront for OCS also scan OCS WebConferences? (Uploaded Documents)
Or is the scope only on IM scanning?
If Ff could not scan WConf´s how can we do Virusscans at the OCS Frontendserver?

(We have OCS 2007 R2)

Thanks and Rgds

Stefan Schneider

File Level AV and Forefront for OCS exclusions

Wed, 05 Aug 2009 19:04:26 Z

In reference to the follwoing technet article (http://support.microsoft.com/kb/943620) MS states the the OCS and Forefront installation folders must be excluded before performing a file-level AV scan on the server using a 3rd party product. I would like a little bit more information on this topic.

Does this exclusion recommendation apply to on-access scanning? If so, doesn't this open up the server to the possibilty of contracting a virus should said virus decide to "hide" in one of these two directories?

If a virus does hide in this directory and is "invisible" to the 3rd party AV product, will Forefront for OCS detect and clean the directory?

Thank you...

Forefront installation issues

Thu, 23 Jul 2009 06:07:21 Z

Hi,

Unlucky, I'm facing a problem during the installation of Forefront for office communication server. When i install it, it's seems like very normal, but finally, it show "The installation failed, and the rollback has been performed. --> System error." and have Event ID: 11001 Source: MsiInstaller error shown on Application log.

The event 11001

The description for Event ID ( 11001 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: Microsoft Forefront Security for Office Communications Server -- Error 1001. The installation failed, and the rollback has been performed. --> System error., (NULL), (NULL), (NULL).

any suggestion or idea?

Thanks
Andy

Forefront Server Suite

Mon, 08 Dec 2008 19:08:37 Z

Since the product is replacing the Antigen IM production which is currently included in the Forefront Server Suite CAL. Is it safe to assume that Forefront Security for OCS will be included in this CAL. Also has there been any word on if there will be any integration with Stirling in the release version?

Thanks

FSOCS (Beta 2) Possible Bugs

Thu, 04 Dec 2008 17:01:31 Z

We have FSOCS Beta 2 running on a Standard Edition server. There appears to be three possible bugs with this release:

The display name for the notification agent does not update after the initial service account has been created.

We attempted to update the display name attribute on the service account within AD and after patiently waiting for AD replication to complete, the FSOCS IM Notification display name does not change.
I found a registry key that records the FSOCS IM Notification display name at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Server Security\Office Communications Server\NotificationDisplayName. I attempted to update this field manually, but once again, the IM notification name does not change.
We will be restarting the FSOCS & Front-End services tonight to determine if there is a differnet result.

Users can not send links within the MOC client. Before the install of Beta 2, users could send links.

URL filtering is off within the main OCS console. The only IM scanning that is currently enabled is Virus and Keyword. I've turned off content and file, with no luck.

Two IM notification messages for a single swear word.

If FSOCS detects a single profanity word, the sender may receive two notifications from the IM Notification agent.

Thanks,
Keenan

URL in IM messages after forefront installation

Wed, 13 May 2009 21:37:12 Z

Hi all,

After instaling forefront, URLs in IM messages are being replaced by text. I mean on the other end instead of having a link for a user to click direclty, it appears as simple text.
I allow URLs in the Pool IM filtering, and the clients have the regkey : HKLM\Software\Policies\Microsoft\Communicator\EnableURL = 1

Before forefront hyperlinks were working fine.

Any help is much appreciated

Thank you

FFOCS Install issue on Edge Edge Server

Mon, 11 May 2009 22:29:13 Z

Greetings,

I am running OCS 2007 R2 and I am trying to install FFOCS on my new edge server. However I keep getting this error:

"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2892."

I added the ForefrontRTCProxy to the appropriate groups and gave it "Logon As Service" rights and I continue to get the same error.

Any ideas?

Ian

OCS File Transfers across firewalls

Tue, 21 Apr 2009 12:56:07 Z

microsoft outlok

Mon, 30 Mar 2009 06:50:09 Z

Helló! Nagyon kezdő vagyok és tájékozatlan.

Újratelepítés után mégsem tudtam levelezni, hibaként IIS 4.0 programot kellene telepíteni. Nem tudom hol találhatom meg.

Másik kérdésem a jogosultság érvényesítéséhez nem fogadja el a felhasználó nevemet és a jelszavamat. Mit csináljak és hogyan.

Üdv Buksika

File Transfer Flow with Forefront for OCS

Wed, 18 Mar 2009 17:43:26 Z

Hi All,

I would like to ask if someone knows if a file transfer is done in a peer-to-peer way, even with ForeFront for OCS installed in the OCS pool.

What I was wondering, is that since the FSOCS must filter the files, if this will force that a file transfer would pass through the OCS server, instead of going peer-to-peer.

I ask this because in my environment, not all users are in the same network, and don't have connectivity between then, so they can't use file transfer feature in MOC.

If the FSOCS would force files to pass through the FE server, would solve me a big issue.

Thanks in advance!

Tip: Resetting New Performance Counters

Thu, 11 Dec 2008 16:34:35 Z

For those of you that have installed either the Beta 2 or Beta 2 RF releases of FSOCS, you may be aware of the new set of performance counters that are available for monitoring the status and health of the product. Depending on the type of testing you may be performing with the product, it is sometimes useful to be able to reset these counters to get a baseline set of numbers. By default, most of the new counters are never reset, however the "ResetCountersOnStart" registry key can be set to override this behavior. Upon startup, all of the new counters will be reset.

    1. Create a DWORD named "ResetCountersOnStart" under: HKLM\Software\Microsoft\Forefront Server Security\Office Communications Server   [Software\Wow6432Node on 64-bit systems]
    2. Set the value to 1
    3. Start (or Restart) Forefront services and OCS

NOTE: Once this is done, consider whether this behavior is something that is desired each time the service starts up. If not, be sure to remove the new key or set the DWORD value to 0 to ensure that the behavior does not occur each time the service starts up. This behavior only applied to the new performance categories:
    Microsoft FSOCS Categorizer
    Microsoft FSOCS Health
    Microsoft FSOCS Sip Traffic
    Microsoft FSOCS Scan Filter

ShreyS
Forefront Server Security (DEV)

Forefront for OCS Issues

Thu, 06 Nov 2008 08:45:06 Z

hi ,

i installed Forefront security for OCS , Beta Version: 10.2.0163.0 , and i configured it using : Microsoft® Forefront™ Security for Office communications Server User Guide Version 10.2 Published: August 2008

i have an issue and also a question :

Question : does it support arabic keyword and content filtering ?

Issue : i already configured it to block certain filenames or files with certain sizes or files with certain extensions , also to block some keywords ( english keywords )

but acually it doesn'r block anything and from incidents in the statistics it shows that the scanned or repaired or infected files and also messages are Zero ( 0 )

note that all services are running correctly and i already make updates to it .

so , any one can help me in this ?

ekramy

Long Passwords Cause Beta 2 Install to Fail

Fri, 12 Sep 2008 15:12:49 Z

An issue has been identified in the Beta 2 installer. This issue manifests itself by causing the installation of FSOCS to fail when the length of the "domain\username" is less than the length of the corresponding password field when specifying the service account credentials.

We recommend that customers use a service account with a longer username or a shorter password (taking security related complexity into account where applicable) to avoid hitting the issue noted above. This issue will be fixed and provided to TAP and CAG customers as part of the Beta 2 Refresh release.

Thanks,

ShreyS
MSFT - Forefront Service Security

A Look at FSOCS

Fri, 15 Aug 2008 02:14:16 Z

I've published a new blog entry which covers the beta version and some of the features included. If anyone is looking at test driving the application, go ahead and give it a shot:

http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=35

Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging

Welcome to the Forefront Security for Office Communications Server Beta Forum!

Tue, 10 Jun 2008 18:36:21 Z

Welcome to the Forefront Security for Office Communications Server Beta Forum!

In this space you can post ideas, questions, issues that you encounter, or general feedback for the Forefront Security for Office Communications Server beta release.

A broad range of IT professionals, Microsoft employees, and MVPs will take part in these discussions, which we expect to be interesting and helpful. We look forward to your participation.