Monday, 26 April 2010

I’ve received a number of emails this morning complimenting me on a YouTube video showing a new app that syncs with iTunes via the WiFi connection. The only problem is, I’m not the same Greg Hughes that wrote the app.

To see what all the geeky excitement is about, watch the video below.

The Greg Hughes in question is actually a guy in the United Kingdom. He tells me he’s a 2nd-year Computer Science student at the University of Birmingham. What he’s built looks pretty cool. I hope that when my namesake submits his app to the Apple Store, they accept it and let all of us get at it (I’m wondering if they won’t approve based on past decisions, and if they’ll say it performs an action already provided by an Apple product -- but I’d sure love to be proven wrong on this one).

The app is set to be submitted at the Apple App Store soon according to the author, and it looks like we can check for the latest information at (there’s not much there as of the time of this writing, but that will almost certainly change) and there’s a Twitter account at to check out.

Add/Read: Comments [2]
Apple | Tech
Monday, 26 April 2010 07:19:43 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Friday, 23 April 2010

image I’ve been fighting a bit with my installation of Outlook 2010 (beta) for the past several days. Don’t get me wrong, now: I love Outlook 2010, it’s by far the best version of Outlook ever. The ability to have multiple Exchange account visible at one time is a killer new feature, and there are a lot of other great improvements.

But Outlook can be challenging sometimes. It’s a complicated program, especially when used with Exchange. So. now was just one of those times. Consistently the program would hang and I’d have to wait for what seemed like an eternity for it to come back to a responsive state. I did a lot of analysis and narroowing down the behavior by disabling a lot of account and feature settings, and decided that it seemed to be related to a hosted Exchange account I use for my email service. The more account features I enabled and accessed in Outlook, the more it would hang. For example, if I accessed the calendar associated with that account and then tried to open something, or if I switched from the calendar back to the mail view, or if I tried to look up a contact, Outlook would hang. It was to the point of being ridiculous in terms of getting anything done, since the hangs could last a few minutes or more at times. Outlook actually trained me to walk away and come back in 5 minutes. But that’s better than a busted up laptop, I suppose!

I started troubleshooting this and a couple other issues I was seeing that were affecting performance. One of the problems with trying to resolve Outlook issues is that the error messages the program provides are often very generic in nature and don’t point to a root cause. If I had a dime for every time it told me I didn’t have permission to do something , or for every time Outlook told me it’s trying to connect to an Exchange server and failing, I’d be rich. There are a zillion things that can cause these generic, simple errors. And the funny thing is, sometimes it’s not even an Exchange server it’s connecting to, even though it says it is. It might be connecting to a domain controller name instead to try to go a GC lookup, for example. You have to know what to look for, and how Exchange and Outlook work, in order to solve most Outlook behavior issues. Luckily I have a lot of past experience in that department.

At any rate, I eventually got to the point where I was spending my time looking at the Exchange Server’s connection status window. To see that, you locate the Outlook status icon down in the task bar near the clock, hold down the CTRL key, and click on the icon. Then you can choose the menu option for Connection Status. You only see that option if you CTRL-click the icon, though.

         (Server names omitted where appropriate to protect the innocent)

One of the first things I noticed was the fact that there were communication failures to my hosted Exchange server see the red-outlined numbers above), and that the connections were taking a long time to establish themselves. The status would stay at “connecting” frequently, and that was always the same time when Outlook was hanging. So, I figured was getting somewhere. At least I had a likely correlation. The other Exchange server, which is domain-authenticated and available on the local network, wasn’t hanging. Connections were quick and reliable (as you can see from the numbers above) on that one.

That made me think some more. Every time I start Outlook, I am prompted to enter my credentials for the Exchange Server. Despite the fact that I click the “save password” box when I log in, I am always prompted when starting Outlook. I had planned to see if there was a certificate mismatch problem of some sort, but with the connecting communication failures happening, I wondered if there might be a problem with the credential being passed to the server. As you can see in the connection status windows picture, the connection is an Outlook RPC over HTTPS type, and so I went investigating in the account settings for the account:



Sure enough, I found what I suspected I might: Outlook was prompting me to enter a username and password – behavior that’s associated with basic authentication – but Outlook was configured to use NTLM authentication when connecting. So, logic says that it was trying for a NTLM auth, waiting around for it to time out, and then reverting to the lower-security username and password over HTTPS. That would probably explain the communication hangs, and why Outlook wasn’t saving the plain text credentials when I asked it to.

I changed the proxy authentication setting to use basic authentication, and restarted Outlook. I was prompted to enter my credentials once, and haven’t been asked since. And, the connection to the server is much more snappy and reliable.

I don’t really know why the communication hangs started up a few days ago. Perhaps something changed settings-wise when my svchost.exe file got eaten by my AV software. I have been running Outlook 10 beta for a couple months and it was a new issue (although the credentials pop-up was consistent since installation).

But, regardless it looks like at least one or two of the problems I was having are now solved. And that’s a good thing. Now I’m off to troubleshoot some auto-archiving issues.

Add/Read: Comments [3]
Microsoft Office | Tech
Friday, 23 April 2010 17:07:55 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Wednesday, 21 April 2010

Many users of McAfee's virus scanning products are experiencing some real pain today due to a false positive virus alert (for the wecorl.a virus) that is resulting in dcom error reboots and in many cases the removal of the valid Windows svchost.exe from affected systems.

Despite a massive slew of articles and posts made on web sites today saying a new virus is in the wild and infecting computers (typically referring to this is a zero-day vulnerability), this is not in fact a virus outbreak, as anyone who knows how to use Google and has a remotely curious mind can discover in a matter of seconds. It’s an antivirus false-positive. The wecorl.a trojan is a couple years old, and this is not it. Even if it was a virus, it would not be zero-day.

In a nutshell, McAfee made a big mess with their AV update early this morning, and they are working feverishly to fix it. Read on.

First of all, if you're affected by the problem described below, information about a workaround fix and an update is available from McAfee at the McAfee Threat Center web site:

One of my own computers fell victim to this today, and I've been fighting with it since. I just got it back online, restored to normal and fully operational. My problem started at about 7am today and so I was figuring it out on my own, but the instructions McAfee has provided for the workaround/fix (linked above) are basically the same thing.

wecorl A DAT (virus definition 5958) file that appears was released earlier today has an issue that causes the valid Microsoft svchost.exe critical system file to be flagged as infected. It's not infected, though. This appears to impact primarily Windows XP SP3 computers, but it could be broader than that. As a result of the false flagging of the file, the McAfee AV software takes action, which can include doing nothing, quarantining the file, or in some cases removing it completely (that's what happened to mine).

If the file is quarantined or deleted, Windows stops working normally and a lot of the typical Windows functionality just isn't there anymore. Things like start menus, drag and drop capabilities, copy and paste in Explorer, and a whole lot more. You can still open Task Manager and launch new tasks manually, and the CMD window interface (command line shell) works just like always, so it's possible to get around to fix it up.

If you are running McAfee Virus Scan and have a signature file version 5958 (open the "about" dialog and look for the DAT version), then it appears you are affected. Rolling back to 5957.0000 (which was issued 4/20) will resolve the issue. There is also an "extra.dat" file available that can be dropped into the McAfee AV scanner's DAT directory while in safe mode, and then the computer should be restarted. Or if you're a business using EPO to centrally manage your AV system, you can push it out with that.

But if your svchost.exe file has been quarantined or deleted, you'll have to do some hands-on repair (at east for now, until a better solution is put together). The link at the top of this article walks you through what's needed.

This is a serious challenge today for McAfee. Their web sites appear to be badly overloaded and I have friends in the business who are waiting on hold with McAfee for extended periods on time. In speaking with people working at other (huge) companies, it's apparent the impact is huge and widespread. Thousands of people who should be working are dead in the water now, so to speak, with no computer to do their work on.

I hate to think what the financial impact of this is. It's got to be huge. Follow the link above and check it for updates from McAfee as time goes on.

Add/Read: Comments [1]
IT Security | Tech
Wednesday, 21 April 2010 12:07:18 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Thursday, 08 April 2010

image Apple today announced a technical preview (for registered developers) of iPhone OS v4, which will be released to the public this summer.

It adds a whole slew of new features and capabilities, one of few of which will apply only to the latest models of the iPhone due to computing power requirements:

iPhone OS 4 will work with iPhone 3G, iPhone 3GS, and the second- and third-generation iPod touch this summer, and with iPad in the fall. Not all features are compatible with all devices. For example, multitasking is available only with iPhone 3GS and the third-generation iPod touch (32GB and 64GB models from late 2009).

The mail and multitasking capabilities will be big, so will the addition of eBooks (using the same store as the iPad) and the ability to organize apps on the screen into folders. Today you have to page through screen after screen, all on one “level,” but with the new OS that story changes.

At the enterprise level, there are some other substantial changes and improvements in areas such as app distribution (wireless app distribution for the enterprise is here) as well as security and device management – and all of these are important if Apple wants to make the iPhone something a secure and well-managed enterprise can leverage. Cisco and Juniper are working on SSL VPN apps to allow secure access to the enterprise, as well.

Oh, and they are adding their own advertising network to the iPhone app story, with a service called – shockingly – iAd. Go figure.

The iPad will get OS v4 this fall, according to Steve Jobs during a press Q&A session.

Too bad I don’t have a 3GS, so no multitasking for me until i replace this iPhone (which now sports a badly-cracked glass screen, but still works great).

Add/Read: Comments [2]
Thursday, 08 April 2010 10:48:32 (Pacific Standard Time, UTC-08:00)
#  Trackback
 Wednesday, 07 April 2010

TechCrunch reports today that Google is dog-fooding (using and testing internally) a desktop app that lets you make Google Voice calls.

Google announced the acquisition of Gizmo5 last year, a company with an app that provides Internet based calling software for mobile phones and land lines. At that time they pointed out the Gizmo5 folks would be joining the Google Voice team and working to enhance Google Voice for the future: “Gizmo5's engineers will be joining the Google Voice team to continue improving the Google Voice and Gizmo5 experience.”

This is something to look forward to. Google Voice is a great service, and filling in some of the gaps in the current offering would round it out quite well.

UPDATE: At Download Squad, their sources inside Google indicate that something is coming, as well: “…Google sources have confirmed this as well, saying "We're looking at a full, free, VOIP/SMS desktop client...It's amazing.”

Add/Read: Comments [1]
Wednesday, 07 April 2010 21:06:55 (Pacific Standard Time, UTC-08:00)
#  Trackback

image Richard and I recently interviewed Nick Simons, a program manager at Microsoft who works on the Office Web Apps. He’s been there quite a while, and can say (with pride) that he killed Clippy, that annoying little character that thought he knew what you were trying to do, but often got it wrong and ultimately got removed from the office suite.

In our interview on RunAs Radio this week, Nick discusses Microsoft’s Office Web Apps and how people can use Office 2010 and the Web Apps to share and collaborate, and how it all integrates with SharePoint 2010 and Windows Live Skydrive.

He also briefly describes how they killed Clippy back in the day, and why.

Nick Simons Puts Office on the Web
RunAs Radio Show #155 -- 4/7/2010 (36 minutes)

  • This week’s show page on (with RSS feeds and various available file formats)
  • Direct link to the MP3
  • RSS feed to subscribe to the MP3 format

Add/Read: Comments [2]
Microsoft Office | SharePoint | Tech
Wednesday, 07 April 2010 14:46:26 (Pacific Standard Time, UTC-08:00)
#  Trackback