outlook for office 365

We just purchased office 365 to house Email. We moved from an internal Exchange server. I am trying to configure the outlook to the new office 365 servers, but it keeps trying to connect to the internal exchange server which is offline and not allowing me to even manually enter in the office 365 exchange server to connect. it says server is offline.
please help.

Thanks.
raffie613Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
This is the expected behaviour if you haven't removed Exchange from the old server.
Outlook has no way of knowing the server has gone away, and will always query the local domain first for Autodiscover information.

You need to start that server up, and remove Exchange from it properly, using add/remove programs. Due to the way that Exchange is integrated with Active Directory, you cannot just abandon it.

While you are removing it, using EMS, run the following command:

get-clientaccessserver | set-clientaccessserver -AutodiscoverServiceInternalURI https://host.example.com/Autodiscover/Autodiscover,xml

where host.example.com is the host name that you were told to set for Autodiscover in your EXTERNAL DNS records.

Simon.
0
raffie613Author Commented:
we lost the server completely due to several hardware failures and we have no way of recovering. what else can we do?
0
Simon Butler (Sembee)ConsultantCommented:
Hardware failures is not a barrier to recovery of the server.
Simply RESET the computer account, then build a replacement server with the same name. A VM will do the job.
Install Exchange from the command lines using the recovery options.
Once done you can then remove Exchange correctly.

You will find manual removal instructions elsewhere on the internet, but they will not correct this problem and are also not supported.

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

raffie613Author Commented:
Another issue to that point is that this was exchange 2003 installed several years ago. No one has the exchange 2003 installation disks. Can this be done using exchange 2010? install it name the machine the same thing and then remove it?

Thanks
0
raffie613Author Commented:
also how do i rebuild the exchange using command lines?

Thank you so much again.
0
raffie613Author Commented:
really need help on what to do for this right away please.
0
Vasil Michev (MVP)Commented:
Apart from what Simon suggested above, you can 'instruct' the Outlook clients to bypass the local server discovery by using the reg keys in this article: http://support.microsoft.com/kb/2212902

All you need for O365 is the HTTP redirect method. But that's more of a hack than a solution, you should really do the housekeeping tasks.
0
Simon Butler (Sembee)ConsultantCommented:
If it was Exchange 2003, then Autodiscover doesn't happen as that wasn't a function in that product.

Was this an SBS Server? Or do you have something on the network that is automatically configuring the clients.

To do the recovery it needs to be the same version. Exchange 2010 isn't going to work because it will "see" the Exchange 2003 server (that is dead) and will try to use that information.

Simon.
0
raffie613Author Commented:
It was just 2003 server r2.

So what are my options?
0
raffie613Author Commented:
Vasil Michev (MVP)
I was not able to find any of those registry keys listed in that article in any of the computer registry. Where else can they be?
0
Simon Butler (Sembee)ConsultantCommented:
If it was a regular Exchange 2003 installation then you must have something on your network, either in a login script or group policy that is configuring Outlook for you. It could also be a custom installation of Office that did it. Something must be configuring the client automatically and if you don't have Exchange 2007 or higher on the domain then it is something else.

Simon.
0
raffie613Author Commented:
I don't see anything in GPO. ALSO the few machines we have that are not joined to the domain, are giving the same errors. they too are only looking for the other exchange server.
I checked the DNS settings and didn't notice anything in there but that is the only thing I can think of that would be having any computer sitting on the network point to the old exchange server.

Ideas?
0
raffie613Author Commented:
by the way, I wonder if this has anything to do with it... but the domain was created originally with the same name as the website. in other words, contoso.org is the internal domain name as well as the external office 365 Email and the website.
Would this be contributing to the issue maybe?
0
Simon Butler (Sembee)ConsultantCommented:
Have you created the DNS records in your internal domain for the Office365 implementation?
Whatever you were told to create in your public DNS you need to create internally as well.

Simon.
0
raffie613Author Commented:
so what kind of record do i need to create? an A record with the name Contoso.org pointing to what address?
Office 365 doesn't have an actualy IPaddress I think. When you run test connectivity it just give you an exchange server address something like ghv3-thrc.Contoso.org

Thanks.
If just doing that works, You will be my hero !
0
raffie613Author Commented:
Also, it seems like each user has a different Exchange server so do I need to create multiple records?
0
raffie613Author Commented:
Simon,
So the fact that I lost the previous Exchange server and am not able to recover it, is not causing this. Does it not have something to do with user objects pointing to the old Exchange server?

Thanks again.
0
raffie613Author Commented:
Simon,
Should I manually delete all the host records in DNS for the old exchange server since i can't bring it back up?
0
Simon Butler (Sembee)ConsultantCommented:
When you setup your account with Office365, Microsoft would have told you to create some DNS records for your domain. You need to put those same records in to your internal domain.

If you aren't going to recover the server then you should remove the DNS records. However I would see if you can track down Exchange 2003 installation media so it can be removed correctly. Although there are manual instructions for that process in various places on the internet.

Simon.
0
raffie613Author Commented:
I called Godaddy who is hosting the microsoft office 365. they said they don't have a ip address or server name for me to enter. I can run connectivity test to get the name of the exchange server though. Once i have that, how do i create the record to point to it on the internal DNS? In other words, what host name is pointing to it?
0
raffie613Author Commented:
How do I clean up the MEtadata of the old exchange server in AD DNS using the Active Directory Tool in Sites and services?
0
Simon Butler (Sembee)ConsultantCommented:
You must have a host name to enter in to your domain.
You cannot use Office365 without it.

I have found the current published information, which is here:
https://technet.microsoft.com/en-gb/library/hh852557.aspx?f=255&MSPPError=-2147217396

You need to check your own DNS settings for your domain (if you are with GoDaddy then look in their DNS entries to see what you have been setup with.

Simon.
0
raffie613Author Commented:
first i had to clean up the old exchange server meta data in adsi dns settings. then used autodiscover.office365 as a host record for internal dns. all works now.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
raffie613Author Commented:
everyone else did not have the correct answer. And lazy answers nistead of just showing best way to clean metadata on AD
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.