IMS Outlook Clients prompting for logon?

[ianbachus]

Hello, we are running VM Pro 4.0 with IMS Pro with an Avaya 406. IMS appears to be working correctly as it drops the voicemail to the appropriate e-mail box BUT when the user opens up Outlook 2003 it prompts them for a user, domain, password every time. I have tried the CORRECT user and password and it does not work. In the mailbox configuration I have added the user so they have permission to access the mailbox and the Primary NT account is the users account but it just will not connect. I can close the message and get outlook to display the inbox and I see the voicemail is there and when I go to play it I get a message from IMS saying it cannot connect to the mailbox ext xxx. VM Pro and IMS are running on a Windows XP machine with SP2. The client machine (a differnt machine) is XP Pro with SP2 running Outlook 2003. Everything seems to be working EXCEPT for logging in on the client side. Also, this is a brand new installation. Anyone have any ideas?

Thanks in advance!

-Ian

 

[tazmgr]

Check out the FAQ for IMS:

IMS Configuration
faq940-4932

Be sure to follow the DCOM Configuration settings.

I have a document produced by MR IPO that gives step by step instructions, but I could not find it online (It was called "IMS 3.1 Test Note".

Also, we found that if you do all of this and IMS still does not show up in Outlook 2003, you need to check (in Outlook) under Help -> About -> Disabled Items
to see if the IMS software is disabled. If it is, enable it and then restart Outlook.

We got our clients working, but now I am having issues with the IMS administartion showing the new voicemailboxes we created. Does anyone have any answers for this?

Hope this helps.

TAZ

 

[ronromano]

I'll bet you set up IMS in your office before you brought it out to the customer. If you did, make your life easy and uninstall IMS and VM Pro and reinstall at the site while it is joined to the domain it will be using. I'm telling you from experience this is the only way to do it.

 

[indyarcher]

Have you changed your decom settings and ran your Avaya fw batch file?

 

[MrIPO]

Dcom Dcom Dcom !!!, refer to the Test note and follow it to the dot, it will resolve your issue.

The link is below

R

http://www.iporesource.com

"Launching late 2006

 

[ianbachus]

Solved!! Thank you for your posts and direction. I solved it by changing the "Edit Limits.." on the "Access Permissions" and the "Launch and Activation Permissions" of the properties of "My Computer" in the "Component Services". You can reach this screen by typing "dcomcnfg" in the run prompt. I ticked the "Allow" box for all options for "everyone" in both places included "Remote Launch" and "Remote Activiation" for launch permissions. As soon as I made the change, it worked like a charm! Hope this helps someone else!

-Ian

 

[ianbachus]

Sorry... this information is found on the "COM Security" tab...

 

[ianbachus]

Actually I just discovered that the user must be a "Domain Administrator" now in order for the IMS client to connect. If you are a domain admin you don't even see the logon window, if you are not a domain admin you will see the window and it doesn't matter what user name and password you enter it will simply not connect. Anyone encounter this?

Thanks!