Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1026
  • Last Modified:

Outlook changes proxy settings and keeps prompting for username and password

Our server environment has been SBS2003 with Windows 7 clients. We had an old server so we are using a Hosted Exchange service that we are very happy with. We recently upgraded to SBS2008 and I am moving everyone over to it as we speak. My problem is that when I move the clients to the new server, my proxy settings in Outlook change to connect to the local server even though I set them to connect to our hosted exchange. I change them back and close Outlook and when I reopen Outlook, they are pointed to remote.(mydomain).com again.

Is this a GP or something else? We would like to continue to use our hosted Exchange solution for now.

Thanks.
0
TcAnthony
Asked:
TcAnthony
  • 5
  • 3
1 Solution
 
viveksahuCommented:
hi,

Iinto IIS Manager, opened SBS Web Applications, Select Autodiscover, double click SSL settings (you have to scroll down to see it), check Accept instead of ignore or require, and Apply. Also repeat it for owa, remote, Rpc, RpcWithCert (possibly don't have to do all these). Restarted Web Publishing and Joy Joy Joy!!!
0
 
TcAnthonyAuthor Commented:
Thanks for the reply. Unfortunately, no joy. Still getting the prompting from the local server.
0
 
Cliff GaliherCommented:
autodiscover is still kicking in and thus resetting Outlook for the local machine. SBS *really* was designed to keep Exchange in-house and running it with hosted Exchange is a ver difficult proposition. You'll have to uninstall Exchange and then work through a series of post-uninstall issues.

Have backups!!!

http://technet.microsoft.com/en-us/library/dd728003(WS.10).aspx
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
TcAnthonyAuthor Commented:
I was really hoping to not have to do something so drastic. SBS can have some MAJOR issues when you start taking things away like that. Can there be any other option?
0
 
Cliff GaliherCommented:
Sadly you are already down that road by trying to run SBS with hosted Exchange services. Yes, SBS can have complaints when you take stuff away, but you've *already* taken away in-house mail which is why you are having the issues you are having. At least going down this path is completing that process and is putting you in a truly supported (albeit unorthodox) state as that documentation is provided by MS and includes a supported topology. Any workarounds you try to do is actually going to be unsupported from an MS standpoint, so this really is one of the better options.

-Cliff
0
 
TcAnthonyAuthor Commented:
JoyJoy! My Dell Support guy fixed me up in a jiffy. He made a quick change in the Exchange Management Shell.
Set-ClientAccessServer -Identity dc1 -AutoDiscoverServiceInternalUri
https://(hostedexchange.com)/Autodiscover/Autodiscover.xml

Works great!! They have great software support, even on a Sunday afternoon.

Thanks.
0
 
Cliff GaliherCommented:
Just be aware that the SBS wizards are unaware of that change and unexpected results will now occur regularly when doing maintenance-type work within Exchange using the wizards. That is one of those unsupported scenarios I was referencing.

-Cliff
0
 
TcAnthonyAuthor Commented:
1
0
 
TcAnthonyAuthor Commented:
My own solution
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now