Hi All, I hope someone can help me out, I've tried Google, but have had no joy. We've recently installed Exchange 2007 freshly into our orginsation, and have rolled out Outlook 2007 onto client machines. The auto build of the profile works really well from AD on the clinet machines and gets them to their mailboxes nicely without any user interaction - brilliant, love it (for new profiles obviously).However I've installed Outlook 2007 onto our Terminal Servers (2003sp2), but almost always the auto profile builder fails (and therefore shows up) with a "Outlook cannot log on" message. In the server name instead of just "exchange.domain.co.uk" I get the following: /o=OrginsationName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE I've tried various bits and bobs, setting RCP (not that it's in use, but it's the closest thing Google said to do), setting dns up for "autodiscovery" etc, but nothing's helping. I understand that the above line is a ServerDN address, which is correct, but Outlook doesn't like it. As I say, standard XP clients are fine.Has anyone come across this one and know how to fix it? Many thanks, Steve
What if you manually try to configure a profile on the terminal server? Can you connect then?
- Joel
Yep, that works fine, if I remove the ServerDN string from the window and replace it with a standard FQDN then all is well.
Weird!
When you open Outlook does it automatically configure it or does it prompt you for the user and password before it completes?
Automatically configures. Or at least, does on normal clients, but doesn't quite on the TS clients (i.e. pops up a box because the server name is incorrect - i.e. ServerDN instead of Server).
The setting of "Automatically configure profile based on Active Directory Primary SMTP address" is used both within the setup MSP, and within GPO.
To me it doesn't seem to be a configuration setting on the Exchange side. Is the GPO for the Terminal server different than the one for the rest of the clients?
If all other things are the same, I would either try to repair or reinstall Office. When you reinstall try to use the standard setup rather than an a packaged or transformed install.
Did you ever figure this out?