Forefront Server Security TechCenter >
Forefront Server Security Forums
>
Forefront Security for Office Communications Server
>
FSOCS (Beta 2) Possible Bugs
FSOCS (Beta 2) Possible Bugs
- 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
Answers
- Keenan,
1. IM Notification Display Name:
FSOCS does not explicitly configure the display name that is used by the Forefront Notification Agent. The display name should reflect that which is set in Active Directory for the notification agent user account. Since display names are typically cached, the name change may not take effect until the Notification Agent logs out and back in. This would occur any time the Forefront services are restarted.
The "NotificationDisplayName" registry key is used to configure the display name for E-Mail notifications and does not affect the behavior of IM notifications.
2. Links:
What is the behavior you are seeing (sender/recipient)? Does Forefront report any incidents for messages containing links?
3. Two Notifications:
What is the filter action for the filter list that is being triggered? If the action is configured to Skip-Detect, it is normal for multiple IM notifications to be generated if the offensive word is the first word in an IM conversation. In this case, this would occur since MOC generates 2 messages to initiate the conversation; the first being the "toast" (i.e. the pop-up message from the system tray) and subsequently the actual message content itself.
Regards,
ShreyS
Forefront Server Security (DEV)- Marked As Answer byJim MoliniMSFT, OwnerFriday, December 26, 2008 6:20 PM
All Replies
- Keenan,
1. IM Notification Display Name:
FSOCS does not explicitly configure the display name that is used by the Forefront Notification Agent. The display name should reflect that which is set in Active Directory for the notification agent user account. Since display names are typically cached, the name change may not take effect until the Notification Agent logs out and back in. This would occur any time the Forefront services are restarted.
The "NotificationDisplayName" registry key is used to configure the display name for E-Mail notifications and does not affect the behavior of IM notifications.
2. Links:
What is the behavior you are seeing (sender/recipient)? Does Forefront report any incidents for messages containing links?
3. Two Notifications:
What is the filter action for the filter list that is being triggered? If the action is configured to Skip-Detect, it is normal for multiple IM notifications to be generated if the offensive word is the first word in an IM conversation. In this case, this would occur since MOC generates 2 messages to initiate the conversation; the first being the "toast" (i.e. the pop-up message from the system tray) and subsequently the actual message content itself.
Regards,
ShreyS
Forefront Server Security (DEV)- Marked As Answer byJim MoliniMSFT, OwnerFriday, December 26, 2008 6:20 PM
- Version: 10.2.0308.0
Product ID:
Office Communications Server Version: 3.0.6362.0
I have the same issue for #2. Links. I installed the latest Forefront that is out free trial 120 days. After installation, no links would be sent. If forefront services are stopped hyperlinks will be sent again. It appears that forefront has incompatibility w/ the IMfilter for OCS services. When I send a link such as www.link or http://link the message appears in the popup of the recipient for a second and when the chat window is opened the message disappears. The sender gets the following msg:but it's unclear how to resolve.
The following message was not delivered to ocs user.
More details (ID:400)
Product: Office Communicator 2007 Version: 2.0 Source: Office Communicator Server ID: 400 Message: Bad Request Explanation
The server returns a 400 error when it receives an erroneous request.
Cause
Possible causes of Error Message 400 are:
- The Location Profile has been mis-configured on the Office Communicator client or on the Office Communications Server.
Resolution
Check with your system administrator to ensure that your Location Profile has been configured correctly.
Another thread may address issue #2.
