Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exch 2003 on Ent Svr 2003, Outlook 2003 client profiles won't setup 1

Status
Not open for further replies.

libove

MIS
Apr 9, 2002
56
US
My network consists of a Windows 2000 Advanced Server as the Domain Controller, running Exchange 5.5 SP4; and an old NT 4.0 Server which remains as a BDC from before I upgrade the DC to Windows 2000 Advanced Server.

Now I have installed a new machine with Windows 2003 Enterprise edition, joined it to the domain as a member server, and promoted it to also be a DC; and then I installed Exchange Server 2003 Enterprise edition on it.

I did NOT try to join the new Exchange Server 2003 to the existing Exchange 5.5 site. In the past, playing with Exchange Server 2000, I had loaded Active Directory Connector but never quite gotten it to work.

Between my last failed attempt with Exchange 2000 and now, I uninstalled Exchange 2000 from any machine on the network, uninstalled Active Directory Connector, and used ADSIEdit to completely delete the Exchange container from AD. Then I installed Exchange 2003 as above.

Almost everything works fine:
* Mail sends and receives
* Outlook Web Access works (beautiful!)
* IMAP works (PINE on a UNIX box)
* Within OWA, composing a new email and clicking on the To: link and searching through the Global Address List works fine.

What does NOT work is that no heavy Outlook 2003 client is able to set up a profile to point at a user with a mailbox on the Exchange 2003 server. The same mailbox I'm trying to get Outlook 2003 to be able to access WILL work in OWA and via IMAP, just not from Outlook 2003.

The error I get when I right-click on the Outlook 2003 desktop icon and select properties, or go to the user's Mail applet in Control Panel, and type in the Exchange 2003 server name and the user's mailbox alias is:

"The name could not be resolved. The name could not be matched to a name in the address list."

I found this MS KB article:


.. and followed all of its steps. Everything it said to look for, to check permission on, &etc was fine. The only thing that might be an issue is #7 from the article:

7. Verify that Microsoft Exchange Server 5.5 is not installed on the global catalog server.

In fact, the Windows 2000 Advanced server which is the DC, started its life as an NT 4.0 Server, and does have Exchange Server 5.5 SP4 running on it.

Probably making things worse, I then tried to migrate the GC from that Windows 2000 Advanced Server to the new Windows 2003 Server in hopes that it was the simple presence of Exchange 5.5 on the GC that mattered, and not that having had the Exchange 5.5 server on the GC polluted AD (in which case a migration of the GC wouldn't make a difference).

Now when I try to set up an Outlook 2003 profile to point to the new Exchange 2003 server, the error has become:

"The action could not be completed. The bookmark is not valid".

So, what was actually wrong, and what did I make worse by evidently not doing the GC migration properly, and most important of all ... HEEELLLLLLLLP!! How do I fix it? :)

Thanks!
-Jay
 
We had a similar problem - Our old Exchange Server 2000 machine died with disk failure which resulted in the RUS service trying to run on the old server .

You need to check that the RUS has run correctly on the users account. Do they have showInAddressBook attribute set correctly in AD? You can use ADSIEdit /LDP to check this.

If not then troubleshoot the RUS [ REcipient Update Service] via the Exchange Manager. In our case we change the service to run on the new Exchange Server and bingo.

This certainly would be the original problem, but can't say whether the GC migration has made it worse.

In the RUS you can select to rebuild, which may [??] sort out the AD corruption

Good luck

Roger
 
Thanks Roger. I switched the GC back to where it was before, and the error message returned to what it was before. Then I went to Exchange System Manager and found RUS and selected update and then rebuild, and neither made a difference. As there is only one Exchange server in this organization, I don't have any option to "move" RUS - it already shows up as being on the one Exchange server.

Any other ideas please?

Thanks again!
-Jay
 
Jay, did you check that they have 'showInAddressBook' attribute set correctly in AD? You can use ADSIEdit /LDP to check this. [ You'll find this in C:\Program Files\Support Files ]

This still "smells" like an AD problem.

Rog

 
I ran ADSIEdit /LDP, opened the Users container under the domain, pulled up properties for the user I'm trying to add, and verified that it has the attribute 'showInAddressBook' and that the attribute's values were sensible (all address lists, global address list).

I also tried mapping a different user to the Outlook profile just to make sure it wasn't peculiar to this one user, and have the same result, both in the error trying to set up the Outlook profile, and in verifying that they do have the 'showInAddressBook' attribute.

Next? :)

Thanks again.
-Jay
 
Sorry I was out yesterday.

Phew !! Its stumping me! My in-experience with Exchange is beginning to show.

Have you tried deleting the Profile completely from the users PC and then re-creating it ?

I could also suggest trying a post on the Exchange Admin List or others. You need to subscribe with email address
at


This forum and the Sunbelt ones are the only ones which I have ever had any help from.

Slight word of warning - you WILL get loads of traffic from the Exchange Admin List which can be either very useful or very distracting. You just need to be a bit disciplined with your incoming mail. [and quick !!]

Good luck

Rog
 
As the problem has occurred on two possible client systems - on a Windows XP workstation which had a previous Outlook profile on it, and the other the Windows 2003 Server Enterprise Edition itself where Exchange 2003 is running and has never had any Outlook profiles on it, I'm sure it's not the profile itself.

I've subscribed to the Exchange Admin forum from Sunbelt and will see how that does for me. I'm okay with high volumes of mail. I already get a lot of mail...

Thanks again!
-Jay
 
Here's what fixed this:

Migrate all FSMO roles to the new 2003-based DC, including GC.

Demote 2000-based DC to member server.

Rename 2000-now-just-a-member-server to fully comply with the DNS name of the domain (For historical reasons, it was reset4.felines.org instead of reset4.ad.felines.org).

Promote the 2000-member-server back to being a DC.

Optionally, move FSMO roles back to 2000-based DC.

Now profiles set up fine.

Microsoft's warning about getting DNS naming and AD domain naming right sure matters in weird ways...


A side issue noted during this process: My 2000-based CD has Certificate Services on it. You cannot rename or demote such a server. So, I used the backup option built in to Certificate Servers to save the certificates of the Cert Svr itself and the certificate history, then uninstalled Cert Services, demoted, renamed, promoted, and reinstalled and restored Cert Services. No problem.

-Jay
 
Hi Jay,

Thanks for the feedback.

I'm glad you eventually sorted it out.

Rog
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top