Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Vincent <vfrissora@xxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Dec 2008 08:11:16 -0800 (PST)
On Dec 16, 12:11 pm, "Rich Matheisen [MVP]"
<richn...@xxxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, 16 Dec 2008 06:51:02 -0800 (PST), Vincent
<vfriss...@xxxxxxxxxxxxxxxxx> wrote:
[ snip ]
I found a workaround for this. I went to a previously setup user on
the server and went to the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion
\Windows
Messaging Subsystem\Profiles\
I selected the profile name (mine was called outlook) and exported
this key.
I then dropped the reg file into the users my documents, logged in as
them, and then doubleclicked to import that key into the new users
profile.
Then I went into mail properties to change the name to the correct
user. The "check name" found the user with no problems (aka no login
box) and I was able to login to the mailbox successfully.
My next question is, based on my workaround above, can anyone think of
a more permanent solution to this problem? or why it may be happening
in the first place?
Sounds more like there's something in the profile that's causing the
problem.
Check the value in the key that starts with dca74....... The value
001f662a should be the fqdn of the global catalog. If it's not, remove
the value from the key.
Is the "Closest GC" value set to 1 in
HKLM\Software\Microsoft\Exchange\Exchange Provider? Set it to 0. That,
together with the missing 001f662a value should force the client to
ask the Exchange server for a referral to a GC.
---
Rich Matheisen
MCSE+I, Exchange MVP- Hide quoted text -
- Show quoted text -
I doubt it is something with the outlook profile, since this setup
happened on another newly created user.
I also tried to manually set that "001f662a" to my GC on a new profile
by copying the binary value on a working account and copying it to a
non working account, and it still continued to ask me for a login.
Also, the "Closest GC" registry entry you're talking about, I assume
that's a DWORD, right? Do I need to restart the exchange services for
this to go into affect?
.
- Follow-Ups:
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Rich Matheisen [MVP]
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- References:
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Andy David {MVP}
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Vincent
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Rich Matheisen [MVP]
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Vincent
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Vincent
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- From: Rich Matheisen [MVP]
- Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- Prev by Date: Re: Remove a certificate from a service
- Next by Date: Re: Exchange 2003 issues... cannot mount public store... and More
- Previous by thread: Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- Next by thread: Re: Exchange 2003 Outlook 2007 on Terminal Services Domain Controller
- Index(es):
Relevant Pages
|