Exchange 2010 profile issue

[Gardinho]

Hi guys,

 

I have an issue with rolling out Exchange 2010 mailboxes to Outlook 2003. Beforehand, we used Richprofile, which worked a treat. The latest version doesn't work with Exchange 2010.

The main problem I'm having is that the old outlook profiles are needing deleted from the registry, otherwise Outlook won't connect to the exchange server. I think it's stored in the Registry at HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\%username%, but not 100% sure.

Has anyone experienced this? Is there a way in Group policy to delete that registry key? Or will a script do it?

I hope I've explained myself ok!

Many thanks,

[chrisbrown]

GP will let you delete the registry entry:

 

Ned Pyle's way: Deploying Custom Registry Changes through Group Policy - Ask the Directory Services Team - Site Home - TechNet Blogs

 

I would suggest getting rid of OLK 2003 ASAP, Exchange 2010 doesn't support it by default, and you can bet quite safely that support will only become harder and harder to find.

[Gardinho]

Thanks for that. I've been playing around with Office 2010, as we're fully licensed for it. I think it is a bit unstable so I'm starting to roll out Office 2007.

 

I'll look into altering the registry and repost my results.

 

Many thanks.

[chrisbrown]

Thanks for that. I've been playing around with Office 2010, as we're fully licensed for it. I think it is a bit unstable so I'm starting to roll out Office 2007.

..What?

[Gardinho]

We have a license for Office 2010. We have users here that use many advanced features of Office, including editing xml files to be imported using other software. When they try to open certain files, they get the error 'This file is corrupt'. It only happens on 2010, not on 2003 or 2007sp2.

[Gardinho]

The reg key I have created to delete the outlook profile is this:

 

REGEDIT4

-HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\[LogonUser]

 

I just can't get it to work for the user that is logged on! I've also tried it with %username%

[chrisbrown]

We have a license for Office 2010. We have users here that use many advanced features of Office, including editing xml files to be imported using other software. When they try to open certain files, they get the error 'This file is corrupt'. It only happens on 2010, not on 2003 or 2007sp2.

Can you be sure it's not a layer 8 error? Could it possibly be that your xml files don't meet the xml spec and are considered corrupt by office?

[Gardinho]

It could well be possible. I'll have to look into it. It's probably the duff Sims software by Capita that is causing the error with XML, it's so buggy!

 

Anyway, do you know of a way I can delete the registry key above? The more pressing issue is with Outlook.

 

Any advice would be greatly appreciated.

 

Many thanks

[chrisbrown]

How about this?

 

http://i56.tinypic.com/28slfzk.png

 

Most fields within Group Policy preferences allow you to open a list of variables by pressing Shift+F3.

 

Let me know if this helps ...

[Gardinho]

That didn't work, but I don't think it's far off. I'm not totally sure what the path should be to delete the right key. I know which folder it's in (as above), but I'm not sure how to identify the logged on user. I've tried %username% and %LogonUser%.

 

Thanks for your help.

[sukh]

Hi

 

@dgardner - What is the exact issue you are having with Outlook 2003 and Exchange 2010?

Why do you have to delete the profile and then reconfigure again?

 

Sukh

[Gardinho]

 

Hi Sukh,

It also happens with Outlook 2007. We used to use Richprofile, which would configure the mail accounts. Now we use Exchange 2010 and Richprofile is incompatible. When you open Outlook, you get the attached error:

 

If you delete the key in the registry, it resets the profile and Outlook 2007 configures itself for the new Exchange Server when you launch the application.

 

Thanks in advance.

[sukh]

Hi

 

Are you only seeing this issue with migrated users or with a new user set up on Exchange 2010 too? (Using Outlook 2003)

 

Can you also confirm that this issue occurs as above (new user and migrated) using Outlook 2007?

 

Sukh

[Gardinho]

It happens to all users. The error occurs whether you use Outlook 2003, 2007 or 2010. It only occurs on PCs that were once connected to the old exchange server using richprofile. All clean builds don't have an issue.

 

Many thanks

[sukh]

Hi

 

Can you just qucikly explain Richprofile and how it interacts with Outlook/Exchange.

Why was this used?

 

Sukh