I don’t think this problem/solution is much different in older versions.
Problem: when you send a link from Communicator client to another, the link isn’t clickable, has a _ (underbar) in front of it, or both. Results may be different on different computers. It’ll look like this
_http://www.google.com
Solution: Two things are happening here that are not related. The first is the OCS Server (and Edge Server) have the URL Filter enabled, which are adding the _ underbar to all links. Also called “Intelligent IM Filter”. You need to tone that filter down or disable all together to your liking. If users are coming in through an Edge Server, they will follow the Filter settings of the Edge Server they are using, which seams to supersede the Front End Server (my guess is the most restrictive wins). So be sure to set it on both servers separately. Results were instant in new IM’s.
The other issue is the lack of a clickable hyperlink. If you disable the URL Filters above, the underbar goes away but links are still not blue and underlined. To fix this you need to apply a GPO or set a local registry setting to allow Communicator to make hyperlinks clickable:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
new DWORD EnableURL=1
After that exit and restart Communicator.
In both of these cases they are secure by default, which is great; but even years after this features release over several versions their use and configuration are still a mystery to most starting out.
Published on
Oct 1, 2009 in
Microsoft, Networking and Security, Solution Writeups and Tech.
Tags: activesync, email, exchange, firewall, isa, Microsoft, timeout, windows mobile.
They were getting random prompts for passwords in ActiveSync on Windows Mobile 6.0 and 6.1. They had Exchange 2007, and ISA Server 2006, but this problem showed up months after Exchange was migrated to 2007. It seemed random. The error on ActiveSync was the generic:
please log in access was denied 0×85010002
In the ISA Monitoring you would see a denied connection on your ActiveSync rule with this status:
12239 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator.
I tested with Windows Mobile Emulator from outside the firewall and was able to reproduce the error within hours (just letting it sit there).
I first thought this was the HTTP session timeout that changed with a Exchange 2003 service pack when Direct Push came out back in 2005. I remembered that setting and looked under the ISA Web Listener for ActiveSync on the Connections tab>Advanced>“connection timeout”. The wizard had correctly set it to 1800 seconds (30 minutes). No dice.
I poked around the web listener settings some more and noticed the timeout settings for forms authentication were set (this same web listener was used for OWA). ISA is supposed to be smart enough to not apply any of the forms auth settings to clients that don’t support it (falling back to basic auth as with ActiveSync).
Tom and the forums at isaserver.org confirmed my suspicion. The forms auth timeout was indeed affecting ActiveSync. To find it, look for the web listener of your ActiveSync rule, go to properties>Forms tab>Advanced> and make sure “apply session timeout to non-browser clients” is unchecked.
On trying to remove a old server from the directory (2003 server in a 2003 forest) I received this error
Failed to configure the service NETLOGON as requested “the wait operation timed out.”
The root problem was that this domain controller had a DNS entry to another domain controller that no longer existed. It was trying to contact it but couldn’t. Removing that entry and running dcpromo.exe again solved it.
Published on
May 27, 2009 in
Microsoft and Tech.
Tags: error, front-end, hotfix, kb967831, Microsoft, microsoft update, ocs, ocs 2007 r2, ocs r2, rtcqmaagent.
Update 6/22/09: KB972041 is out with a hotfix that resolves this issue. I guess you install it before, or in lieu of KB967831.
OK so this blog post explains it well but it has gotten worse since that post a month ago. Here’s an update and shorter version of what’s going on:
There’s a optional monitoring feature of OCS that many small shops likely won’t install. That’s fine, cus it’s optional right? Well turns out it’s now required (actually just part of it, the MSMQ service) for a hotfix to successfully install. That hotfix is now on Microsoft Update and is likely already on your box, WSUS, SCCM, SMS, etc: (KB967831). The patch is not smart enough to either:
- Do pre-check’s and prevent install unless you have MSMQ
- Roll back it’s changes to leave you in a running state
- Or ignore the fact that you don’t have something optional installed in the first place and just keep patching
So it leaves you a nice broke server to repair in the morning. Front-End and Edge Services service stopped, with cryptic misleading Event Log messages. So multiple boxes are down. Crazy thing is this happens in a “default install” scenario as if no one full tested the patch or something. I would give a pass for a hotfix, but a MU patch… fail!
Quick fix: install MSMQ (even though you don’t need it unless you setup RtcQmaAgent for OCS Monitoring) via this script (win2003 servers), then re-run the update either via MU or downloading and running it manually.
Only a handful of software that isn’t a game could end up on the “fun to use” list. I think Windows 7 is on it. I’ve been using it as the main OS on an increasing amount of computers since the pre-release of the public beta (build 7000) since December 08. I’ve now got 5 out of 7 work/home machines using it, most on build 7077 (which isn’t perfect). Waiting on RC build this month. It’s so enjoyable to use (compared to XP and Vista) that I have that “can’t wait” feeling for RTM.
From the responsiveness of the interface, awesome boot and return-from-sleep times, to the overall look, the new “best taskbar eva”, to little things like knowing the difference between a “default audio device” (speakers) and your “default communications device” (headset or webcam/mic)…. it’s got a lot going for it. I’m starting to get more comfortable with the “library” concepts (old 
habits of caring exactly where your file is located on disk die hard). Though, I’m still not a huge IE8 fan compared to Firefox (and now my new fav: Chrome… yes I said it. Just give it’s minimalism a week and you won’t miss the bloat of Firefox’s add-ins).
Just tried the “play to” option in Media Player to push music from my office to the living room PC, which is plugged into the house audio receiver. Couldn’t be easier. Love the simple and effective management window.
Next is to decide how I will implement a HomeGroup, which removes the need for me to manage share permissions, user passwords, etc. on the various home computers.
