Rollingback Autodiscover implementation by removing DNS entry
Hi All,
I had enough problem with the Exchange Autodiscover issue and now I have decided to roll back the changes in my internal and external DNS, I didn't make any changes in the IIS server at all and just wondering what else that I should need to know to roll back the changes ?
previously we are happy and got no problem with the Pop up message in random times with Autodiscover until this week that few random people got it. The reason I put Autodiscover is to simplify things but it doesn't work as it should.
I had enough problem with the Exchange Autodiscover issue and now I have decided to roll back the changes in my internal and external DNS, I didn't make any changes in the IIS server at all and just wondering what else that I should need to know to roll back the changes ?
previously we are happy and got no problem with the Pop up message in random times with Autodiscover until this week that few random people got it. The reason I put Autodiscover is to simplify things but it doesn't work as it should.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
MegaNuk3
On the people that get the error, when Outlook is popping up, get them to hold down CTRL and right click on the Outlook icon in the bottom right hand side of the screen (near the time) and then select the "Connection Status" option. Then verify if Outlook is connecting over HTTP or TCP/IP and check the servernames it is connecting to and verify those servers are functional.
ASKER
The people who got affected with this problem are random, from the CIO down to the office admin people. We were trying to publish outlook anywhere but failed, therefore we had to cancel it anyway.
I didn't make anychanges on the IIS virtual directory at all but just want to play safe here since most people who got autodiacover problem risking loosing the OOF, calendar assistance and some other features :-|
I didn't make anychanges on the IIS virtual directory at all but just want to play safe here since most people who got autodiacover problem risking loosing the OOF, calendar assistance and some other features :-|
What version of Exchange and what service pack level? Also what version of Outlook and do you have a 3rd party cert or self signed?
ASKER
Exchange Server 2007 SP1 - Deployed as CCR mailbox with 2x (CAS&HT combined)
Outlook 2007 SP2 installed for the client.
Yes I do have 3rd party self signed certificate in my both CAS from Thawte.
Outlook 2007 SP2 installed for the client.
Yes I do have 3rd party self signed certificate in my both CAS from Thawte.
Time to upgrade to Exchange 2007 SP3 as that fixes loads of popup issues
Also look at applying this to your Outlook clients:
http://support.microsoft.com/kb/983316
But to be honest the install of E2k7 SP3 should fix your issue.
http://support.microsoft.com/kb/983316
But to be honest the install of E2k7 SP3 should fix your issue.
OK, so SP1 seems to be the issue I would guess. As suguested upgrade to SP3 and you will probably have addressed the issue and STILL have autodiscovery working.
ASKER
thanks All, as I work in the a big banking company we have to wait until the mid year upgrades which is way too long.
Well reseting autodiscover is not going to help with your popup issue. The business has a good reason to upgrade to SP3 = supportability
ASKER
hm.. I suppose yes it should since there was no pop up until I add the AUTODISCOVER as CNAME in my internal DNS which points into the CAS Exchange.
But you have removed that now and are still getting popups?
ASKER
yes i have, but just wondering if it pops up randomly again ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
oh ? so do you guess that is the cause of the issue ?
my DNS is AD integrated as well and the CNAME was ping-able though.
my DNS is AD integrated as well and the CNAME was ping-able though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for the points. Has SP3 fixed your problem?
ASKER
Not yet applied mate, but pretty sure that it will.
I just need to delete the dns entry and that's it all went fine since then.
I just need to delete the dns entry and that's it all went fine since then.