Disable autodiscover on a SBS 2011 Server
up vote
0
down vote
favorite
It is a SBS 2011 domain, single server. They are using Exchange. Whenever a new profile is set up Outlook automatically autodiscovers the Exchange Server and configures Outlook. I am going to be migrating them to Office 365 and don't want this autodiscover to keep automatically configuring Outlook to the Exchange Server. I basically want to disable autodiscover on the SBS 2011 Server.
There are a million different articles about it and each one seems different. Has anyone actually done this on a SBS 2011 Server and can confirm that it works? What are the steps?
exchange-2010
asked Nov 20 at 15:08
Refurb
1
migrated from superuser.com Nov 20 at 20:44
This question came from our site for computer enthusiasts and power users.
add a comment |
up vote
0
down vote
favorite
It is a SBS 2011 domain, single server. They are using Exchange. Whenever a new profile is set up Outlook automatically autodiscovers the Exchange Server and configures Outlook. I am going to be migrating them to Office 365 and don't want this autodiscover to keep automatically configuring Outlook to the Exchange Server. I basically want to disable autodiscover on the SBS 2011 Server.
There are a million different articles about it and each one seems different. Has anyone actually done this on a SBS 2011 Server and can confirm that it works? What are the steps?
exchange-2010
asked Nov 20 at 15:08
Refurb
1
migrated from superuser.com Nov 20 at 20:44
This question came from our site for computer enthusiasts and power users.
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
It is a SBS 2011 domain, single server. They are using Exchange. Whenever a new profile is set up Outlook automatically autodiscovers the Exchange Server and configures Outlook. I am going to be migrating them to Office 365 and don't want this autodiscover to keep automatically configuring Outlook to the Exchange Server. I basically want to disable autodiscover on the SBS 2011 Server.
There are a million different articles about it and each one seems different. Has anyone actually done this on a SBS 2011 Server and can confirm that it works? What are the steps?
exchange-2010
asked Nov 20 at 15:08
Refurb
1
It is a SBS 2011 domain, single server. They are using Exchange. Whenever a new profile is set up Outlook automatically autodiscovers the Exchange Server and configures Outlook. I am going to be migrating them to Office 365 and don't want this autodiscover to keep automatically configuring Outlook to the Exchange Server. I basically want to disable autodiscover on the SBS 2011 Server.
There are a million different articles about it and each one seems different. Has anyone actually done this on a SBS 2011 Server and can confirm that it works? What are the steps?
exchange-2010
exchange-2010
asked Nov 20 at 15:08
Refurb
1
asked Nov 20 at 15:08
Refurb
1
asked Nov 20 at 15:08
Refurb
1
asked Nov 20 at 15:08
Refurb
1
asked Nov 20 at 15:08
Refurb
1
1
migrated from superuser.com Nov 20 at 20:44
This question came from our site for computer enthusiasts and power users.
migrated from superuser.com Nov 20 at 20:44
This question came from our site for computer enthusiasts and power users.
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33
add a comment |
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
The way to do this after the move to Office365 is to change the internal Autodiscover value to point to Office365.
set-clientaccessserver servername -AutodiscoverServiceInternalURI https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml
The clients will still do Autodiscover, but will be pointed straight to the Office365 service. If you remove Exchange from the SBS then the clients continue to go to the correct place.
answered Nov 20 at 21:10
Sembee
2,7421310
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
The way to do this after the move to Office365 is to change the internal Autodiscover value to point to Office365.
set-clientaccessserver servername -AutodiscoverServiceInternalURI https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml
The clients will still do Autodiscover, but will be pointed straight to the Office365 service. If you remove Exchange from the SBS then the clients continue to go to the correct place.
answered Nov 20 at 21:10
Sembee
2,7421310
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
add a comment |
up vote
3
down vote
The way to do this after the move to Office365 is to change the internal Autodiscover value to point to Office365.
set-clientaccessserver servername -AutodiscoverServiceInternalURI https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml
The clients will still do Autodiscover, but will be pointed straight to the Office365 service. If you remove Exchange from the SBS then the clients continue to go to the correct place.
answered Nov 20 at 21:10
Sembee
2,7421310
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
add a comment |
up vote
3
down vote
up vote
3
down vote
The way to do this after the move to Office365 is to change the internal Autodiscover value to point to Office365.
set-clientaccessserver servername -AutodiscoverServiceInternalURI https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml
The clients will still do Autodiscover, but will be pointed straight to the Office365 service. If you remove Exchange from the SBS then the clients continue to go to the correct place.
answered Nov 20 at 21:10
Sembee
2,7421310
The way to do this after the move to Office365 is to change the internal Autodiscover value to point to Office365.
set-clientaccessserver servername -AutodiscoverServiceInternalURI https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml
The clients will still do Autodiscover, but will be pointed straight to the Office365 service. If you remove Exchange from the SBS then the clients continue to go to the correct place.
answered Nov 20 at 21:10
Sembee
2,7421310
answered Nov 20 at 21:10
Sembee
2,7421310
answered Nov 20 at 21:10
Sembee
2,7421310
answered Nov 20 at 21:10
Sembee
2,7421310
2,7421310
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
add a comment |
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
If that link worked :) that would be the cats meow. That is exactly what I would like to do. How about a working link? BWT why would you want to wait until after the migration? I am doing a cutover and would think I would want to change the autodiscover to Office 365 pretty much right away.....
– Refurb
Nov 21 at 13:44
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
That link does work. You cannot browse to it though because your browser isn't Outlook. The information returned is dynamic. You wait until after the migration is complete because you may need clients to connect to the old server. I mainly do hybrid deployments, so Outlook and Exchange sort themselves out.
– Sembee
Nov 21 at 17:10
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f940947%2fdisable-autodiscover-on-a-sbs-2011-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
We always migrate them with autodiscover on, then disable the exchange server after the migration. Autodiscover on a domain with exchange server will always catch it, so you just have to be careful when you create the account. Optionally, give everyone a faux email address in their AD so outlook will try to resolve that email address, fail and then present you with an input field.
– LPChip
Nov 20 at 15:35
I am missing something. I have seen Outlook reconfigure itself mid stream back to the Exchange server because autodiscover is still pointing to the Exchange Server. What do you mean "you have to be careful when you create an account"? The accounts on the Exchange Server are already created...... can you elaborate a little?
– Refurb
Nov 20 at 15:55
Exactly that, that it reverts back to the exchange server. You don't want that. If you set the AD to a fake email address, it should not happen.
– LPChip
Nov 20 at 15:56
Still not clear. You are suggesting changing their existing email addresses in the AD? That would be difficult for a couple reasons. 1) it is doing a cutover migration and 2) it would merely re-associate the changed email address with the same user wouldn't it? any idea how to simply disable the autodiscover feature on the Exchange Server?
– Refurb
Nov 20 at 16:02
You can safely change/set the email property in general tab in AD without altering email functionality. But In the organisation, outlook will then check and try to automatically configure using that email address. It will fail and that allows you to configure it manually without disabling exchange. I'm not saying you must alter the email address in exchange management console, only AD. From M.Name@example.com to M.name@example2.com for example
– LPChip
Nov 20 at 16:33