Just a short note on Google Chrome. I downloaded it today to try it out. I had not idea how hard that would be. The download was easy but it doesn't seem to work with a lot of webpages. Most importantly for me if you try to visit Outlook Web Access the Exchange 2007 CAS server will force you into downlevel "OWA Light". Any browser I use absolutely must support the full functionality of OWA. Maybe I shouldn't have had such high expectations from a beta product but I expected more from Google given all the hype.
My opinion is Chrome will have a somewhat limited use scenario once the novelty wears off. There's a lot of potential with google app integration, but the web is full of unrealized potential (see Google, youTube, monetization).
The Leader in Network Knowledge
Google Chrome and Plaxo
I like the appearance and the functions of Google Chrome but it caused Plaxo to stop functioning. I had to reinstall plaxo...
Google Chrome Outlook Web Access and Citrix.
Chrome was FAST, and I mean really fast when logging in and using OWA. However it seems as is ASP isn't enabled or something of the sort in Chrome. When I right click a mail in IE, I get outlook options (flag, mark as read etc..) when I right click in Chrome, I get Chrome options (back/forward/inspect page). I also couldn't login to the secure login at work which uses a Citrix connection. Other than those two issues it sure is fast and pretty clean. It is still beta so I'm sure the little bugs will be worked out in the next release.
Chrome OWA Letdown...
What a disappointment. Firefox has the same problem. If somebody has a solution to this problem PLEASE SHARE IT WITH US! Thanks.
Firefox + OWA
if you use firefox on windows, IEtab plugin will solve your problem and imitate IE behaviour.
enjoy.
OWA in Firefox
There is an IE tab for Firefox that opens OWA as in IE.
https://addons.mozilla.org/en-US/firefox/addon/1419
It's Outlook Web Access that can't handle Google Chrome.
OWA is designed to detect IE.
if not then it use a downlevel mode.
You might want to check this
You might want to check this out, Microsoft is to blame NOT Google. http://mullac.org/post/google-chrome-owa
Callum, Wow, you make a lot
Callum,
Wow, you make a lot of assumptions in that post. Either that or just a poor attempt at link-baiting. Microsoft doesn't have any special hooks that other browsers can't use. They can either use or license the technology and integrate it into their browser if they choose. That's the key, Google made a choice not to... And for me, like many, that makes it a second tier browser.
Besides, how can you blame MSFT for not supporting "Chrome"? Chrome didn't exist when they launched Exchange 2007 over a year ago. Chrome has got to catch up in terms of basically functionality instead of flashy features if it wants to be taken seriously.
Chrome is Safari, it uses
Chrome is Safari, it uses the Safari rendering engine (WebKit) and even identifies itself as Safari. OWA Full employs Internet Explorer hooks that other browsers don't use because it isn't a standard. Hence why Sharepoint doesn't work well in Firefox, Safari etc
A second tier browser? Google Chrome has been designed to support standards, not random code that Microsoft dreams up instead of employing standard AJAX calls. You are crazy to think this is Google's fault and not Microsoft.
No, seriously, blame Microsoft.
It isn't merely that Microsoft uses its non-standard, proprietary browser extensions in OWA. It also literally checks to see if the browser identification string indicates Internet Explorer, and if it doesn't, it forces the user into "OWA Light". If you hack a proxy or write a program to intercept the request and replace the Firefox or Chrome useragent string with IE's, it will let you log in to the full version (and then break again, because its Javascript also has code that checks to make sure you're running IE.)
This is not merely "your browser doesn't support our technology". This is "you are running someone else's browser and we won't allow that."