Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
How to set up Autodiscovery for Outlook 2007? - 8.Aug.2006 3:39:22 PM
I've just once touched a topic about configuring DNS for autodiscover but haven't found anything anymore.
I tried creating a new AutodiscoverVirtualDirectory (New-AutodiscoverVirtualDirectory -server %servername%) but it has failed.
The reason for it will be probably because Virtual Directory (Autodiscovery) is automatically in place right after instalation. A have SSL certificate in place and it is trusted by computer. RPC over HTTP, OWA or Active Sync works fine, but Autodiscover not :(
Does anybody know correct command for MSH and Autodiscovery?
The article on this server (msexchange.org) is related to E12 beta 1 and it is not functional anymore in E2007 beta 2.
In order to get AutoDiscover working you need to do the following:
Create the AutoDiscover DNS Record
- Open the DNS Manager. - Expand Forward Lookup Zones then expand domain.com - Now right-click domain.com then select New Host(A) - Type autodiscover and the IP Address of the E2K7 server, then click Add - Click OK to close the dialog box then click Done. - Close the DNS Manager.
Configure Exchange 2007 Server
- Switch to the e2k7 server. - Open the Exchange Management Shell - At the command prompt, type Set-OutlookProvider id exch ssl:$true then press Enter. - Now type Set-OutlookProvider id exch server:servername and then press Enter.
That should do it!
_____________________________
HTH Henrik Walther Exchange MVP | MCM: Exchange 2007 MCITP: EMA, MCITP: EA, MCSE: M+S
Thanks a lot for your quick answer. Itīs working fine for me now, but I donīt know why :) The problem is in MSH command. It still returns me errors... but, as I said, itīs working now.
In order to get AutoDiscover working you need to do the following:
Create the AutoDiscover DNS Record
- Open the DNS Manager. - Expand Forward Lookup Zones then expand domain.com - Now right-click domain.com then select New Host(A) - Type autodiscover and the IP Address of the E2K7 server, then click Add - Click OK to close the dialog box then click Done. - Close the DNS Manager.
Configure Exchange 2007 Server
- Switch to the e2k7 server. - Open the Exchange Management Shell - At the command prompt, type Set-OutlookProvider id exch ssl:$true then press Enter. - Now type Set-OutlookProvider id exch server:servername and then press Enter.
That should do it!
ACK!
Not even this simple feature was included in the UI?
Hello Thomas. Itīs nice to see you here... (Iīm MVP for ISA Server)
Henrik I see this:
[MSH] C:\>Set-OutlookProvider -id exch -ssl:$true Set-OutlookProvider : A parameter cannot be found that matches parameter name ' -ssl:'. At line:1 char:35 + Set-OutlookProvider -id exch -ssl:$ <<<< true
[MSH] C:\>Set-OutlookProvider -id exch -server:MAIL Set-OutlookProvider : A parameter cannot be found that matches parameter name ' -server:'. At line:1 char:38 + Set-OutlookProvider -id exch -server:M <<<< AIL
Maybe is a problem on my side, but Iīm still newbie in MSH, so I have no idea, where the problem is...
Well since pretty much every MS product will be based on or at least support Windows PowerShell (formerly known as Monad), my guess is it will be implemented in the ISA Server product in the future. And that would actually be a good thing if you ask me, let's just hope they don't miss so many GUI features as is the case with E2K7.
Why not have a CLI in ISA Server?
_____________________________
HTH Henrik Walther Exchange MVP | MCM: Exchange 2007 MCITP: EMA, MCITP: EA, MCSE: M+S
From my point of view, I hope that next version of ISA Server Will support Powershell. Itīs very good for administrators and administration at all - everybody knows why... but many people working with Windows because of "Windows" - I mean, that GUI is still very important for everybody.
Because Iīm member of Exchange Beta test, I think, that GUI will support more and more configuration options. In beta 1, in GUI you canīt do anything. In DF4 it was better and in beta 2 is acceptable for many administrator.
Because Iīm member of Exchange Beta test, I think, that GUI will support more and more configuration options. In beta 1, in GUI you canīt do anything. In DF4 it was better and in beta 2 is acceptable for many administrator.
We will see in RC and in RTM...
Unfortunately I don't think you'll see any changes (except very minor) when we reach RCs or even the RTM, since MS said Beta 2 is more or less feature complete. From now on they focus on fixing bugs etc.
So any changes to the GUI will be post-RTM.
_____________________________
HTH Henrik Walther Exchange MVP | MCM: Exchange 2007 MCITP: EMA, MCITP: EA, MCSE: M+S
As Thomas mentioned - what about configuration of POP3 and IMAP4? Itīs very hard to configure from PowerShell... I know, that there are many plans for SP1 in Exchange 2007 - for example S/MIME in OWA... but these basic thinks (POP3, etc.) must be implemented to GUI.
I too think there should be many more features included in the GUI, but the Exchange product group didn't have the resources or time for eveything, so these things will come post-RTM.
_____________________________
HTH Henrik Walther Exchange MVP | MCM: Exchange 2007 MCITP: EMA, MCITP: EA, MCSE: M+S
As Thomas mentioned - what about configuration of POP3 and IMAP4? Itīs very hard to configure from PowerShell... I know, that there are many plans for SP1 in Exchange 2007 - for example S/MIME in OWA... but these basic thinks (POP3, etc.) must be implemented to GUI.
Donīt you think?
Hi Martin,
Thank you! I was thinking I was crazy or something, because I was shocked that very basic functionality that almost all Exchange admins I know use, such as SMTP cert config, POP3/S, IMAP4/S and much more were left out of the Exchange Managmenet console. Seems like they might as well delay release until that have a reasonably viable user interface.
Posts: 895
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline
I created a blog entry that might help you guys. It has some information on how to publishg Autodiscover in ISA 2006, how to configure the Autodiscover service, and how you would configure Internal URLs vs External URLs depending on whether you are using a UC certificate vs splitting up IIS into multiple websites and assigning different certificates to each website. It doesn't talk about the set-OutlookProvider cmdlet, but hope the blog entry might still be of help help: http://www.shudnow.net/2007/07/15/publishing-exchange-2007-autodisover-in-isa-2006/
Q: Running Get-OutlookProvider in the EMC shows that neither the EXCH, EXPR nor WEB entries have any content in the "SSL" column. I want to set this SSL property to "true". but running the set-outlookprovider -id exch -ssl:true' command returns an error saying that the parameter -ssl is invalid. Checking with "help get-outlookprovider" shows that the switch is unlisted. I know from other posts that it was there in Beta, but has it been removed in the final release? If yes, how do I set the parameter to "true"? A: Outlook requires SSL and Exchange 2007 always preconfigures with a self-signed SSL cert. It's not something that can be turned on/off anymore (this is why the switch is gone since the earlier beta).
The Outlook client needs to trust the self-signed cert if accessing the Exchange server from the open internet (through ISA 2006 of course), that's why you wouldn't want to use the self-signed cert but get one from a trusted CA. I think the point from MS is to get a cert up and running so you can configure and test the functionality of the set-up. Before you go in production you are recommended even by MS to get a trusted cert. If the client is logged in directly on the LAN as member of the same domain as the CAS computer, however, I think the client does not need to trust the self-signed cert.
The common name used is (if I remember right), the same as the machine name of the Client Access Server, without any domain suffix.
I am not sure what you mean by "SAN" in this context, Tom
Here are a couple of useful links on Autodiscovery:
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> General >> How to set up Autodiscovery for Outlook 2007? 
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
How to set up Autodiscovery for Outlook 2007? - 
RE: How to set up Autodiscovery for Outlook 2007? - 
RE: How to set up Autodiscovery for Outlook 2007? - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
