UCA outlook contact import does not work

[mswanink]

Hi,

I have a problem with importing outlook contacts to UCA.

Situation
Customer has a Remote Desktop server 2008 R2 SP1 with Office 2010 32-bit and UCA 5.1.

We can not import any contacts from outlook to UCA.  Importing from UCA i cannot select outlook. Drag and drop outlook to UCA does not work.

Admin user can import contacts.

Normal user can not import contacts.
We have GPO's in place for the users.
Removed the Office 2010 GPO, but that did not help.

In  my opinion, its is not a Office 2010 issue.

Big question, what is then the issue.

I haven't got a clue. All input is welcome.

Kind regards,

Martijn Swanink
Netherlands

[garyr]

Martijn

Did you manage to resolve this issue?

Gary

[chourdeau]

Hi,

I have exactly the same problem !
It ok for Microsoft Windows 7 and Microsoft Office 2010.

I still have not found the solution. Probably access rights somewhere.

[Chaos77]

The outlook contacts once imported by UCA client go to this folder, C:\Users\Username\AppData\Roaming\Mitel\UC\contacts.dat

If i put a new user in outlook and then manually import data I can find the new contact in the contact.dat file

[ajsmith9870]

Same issue here, Windows Server 2008 R2 running XenApp 6.5, folder redirection of %appdata%.  I have been able to intially setup the Outlook PIM integration and import contacts, I can see the contacts.dat in the \\%appdata%\Mitel\UC folder and have appropriate permissions, but the Microsoft Outlook check box is greyed out now.  Anyone found a solution?

Anthony

[markyb73]

I don't know if its the same issue as i had an issue with UCA 6.0 where the import outlook checkbox couldn't be selected. Mitel gave me a new dll file with updated code which fixed it.

[akuhn]

this might be an issue with x64 versions of windows.  It worked for me on my Windows 7 x86 machine, but now I'm running x64 and I can't drag and drop.  I think others have commented about this on these forums.

Windows 2008 is x64 as well.  Perhaps the newer UCA versions will address this.

[ajsmith9870]

Mitel have sent me a new Mitel.Communicator.PIM.dll repalced 6.0.30.0 with 6.0.103.1

This appears to have resolved the problem :-)