Exchange Server - Upgrading Outlook 2003 to Outlook 2007 Fails.
Asked By j
06-Sep-08 01:34 PM
Hi.
Has anyone run into trouble upgrading Outlook 2003 to Outlook 2007 in
their environment.
When I deployed Exchange 2007, I basically had to use the Outlook 2003
client as installing or "Upgrading" Outlook 2003 to Outlook 2007
failed to work most of the time.
The main issue I ran into was when Office 2003 was installed.
Upgrading the outlook portion to Outlook 2007 was horrible. The
Outlook 2007 installer would make it part way then "flat line" i.e
freeze the computer.
It appears that Uninstalling Outlook 2003 first, then installing
Outlook 2007 works without issue.
Anyone experience similar ?
Thanks JJ
Outlook
(1)
Environment
(1)
Fails
(1)
Experience
(1)
Installed
(1)
Newsgroup
(1)
Installer
(1)
Computer
(1)
Andy David {MVP} replied...
I would ask in an Outlook newsgroup.

Exchange 2007 & Outlook 2007 autodiscover service Exchange Server Hi, I believe I have a pretty good handle on web services (availability service, OOF, OAB and Unifed Messaging service) and they all work fine. Outlook Anywhere even works correctly (as configured by the autodiscover service). These services are all published of each of the Exchange web services. If I choose the "test autoconfiguration" option in Outlook 2007 I can see that these are all set correctly. My issue is that my these services to the internet using basic authentication. What I do not understand is why Outlook 2007 is ever trying to access the external versions of the various Exchange web service the internal autodiscover service. No credential prompt happens at this stage. Surely the fact that Outlook has successfully found the SCP entry in Active Directory should tell it that it is currently for each of the Exchange web services? However, once Outlook receives the URLs from the autodiscover service it now tries to access the external versions which of course require a credential prompt! Why does Outlook want to access the external versions of the URLs? If Outlook chose only to use the internal versions then everything would work correctly. My question is
issues with Out of Office (Exchange Server 2007 SP1. . . . Outlook 2007 SP1) Exchange Server Good afternoon! Okay, this can possibly be one of the longest short and sweet (which means 20 pages instead of 60!). Exchange Server 2007 SP1 MS Outlook 2003 SP3 / MS Outlook 2007 SP1 WIN2003 SP2 AD Four AD Sites (EXCH2007 - on box, in the HQ site) Issue is that when a user (MS Outlook 2007 SP1) tries to use Out of Office he / she gets the error message "blah blah! Server not available". Yes, OWA works just fine. Yes, MS Outlook 2003 SP3 works just fine. This affects users in all four Sites. Yes, there are not present us with the Cert error. We have about 65 users making use of Outlook Anywhere without any issues. They are all MS Outlook 2003, so no OoO issues with them (Thank, God! These 65 users are the Police Department!). I tested MS Outlook with two users (in different Sites. . .same results) by holding down the Ctrl key and
autodiscover.domain.com - outlook 2007 Exchange Server We have Windows Std Server 2003 and Exchange Server 2003 and all the users are using Outlook 2000. Now we have some users with Outlook 2007 and it works fine from office but when users trying to connect from home using VPN, Outlook 2007 opens(outlook 2000 wrks fine from home for same user)but it does not connect to my certificate is invalid or does not match the name of the site). Last year I installed Standard SSL from GoDaddy for IPHONE setup but our IPHONE did now work so I any settings where I need to look. (I have desktop at home where I have installed Office 2007 before I installed SSL and that works fine but recently new laptop we buy with Outlook 2007 does
SBS 2008, Exchange 2007 & Outlook 2007. . . Exchange Server Sorry for the cross-posting, but I am hoping someone out there the major problems is users at a remote office cannot get their email now using Outlook 2007. It worked fine with Exchange 2003, but not Exchange 2007 - why? I have been any other kind of smart phones have no problems, either. When users try to open Outlook, they are prompted for a username & password. I entered domain \ username & then was prompted, twice what do I need to get this to work?!?!? Exchange Admin Discussions Windows Update (1) Outlook 2007 (1) SBS 2008 Exchange 2007 (1) GetHostAddresses (1) SocketException (1) Rollup (1) Backup (1 are they on a network that is considered to be "the Internet"? Are they using Outlook Anywhere? If they put your autodiscover URL into a browser do they get the expected yes, that is the response they get. As far as the test exchange site, the outlook anywhere failed, autodiscover passed, pretty much like the messages included in my original post. [ snip using a SAN certificate? Is the CN of the certificate the same one that your Outlook clients are trying to connect to? Do you fill in both edit boxes in Outlook's "Exchange proxy settings"? Are they both referencing the same server name? - -- Rich Matheisen MCSE
WHy doesn't Outlook Live sync the calendar like it does in our own Exchange server Exchange Server Good afternoon, We are currently migrating our users from our onsite EX2007 server to hosted Exchange (Outlook Live / Live@Edu). One thing that is different with Exchange Live over Outlook 2007 is that calendars are not synced immediately like they are in the EX2007 server synced with the server immediately. It usually happens when the next time comes around for Outlook to sync with the server, which I think happens every 10 minutes or so. But if you log on to the Outlook Live website and use Outlook Web App to change the calendar, it syncs the changes immediately. This is a fairly big deal in a group environment where people are sharing calendars and they want to be able to see changes straight people working on the same calendar they will not get the same version as what Outlook has locally on the computer until it syncs back with the server. There are commercial