Internal Exchange 2016 to Novell GroupWise 2012 appointments show as emails with no accept or reject
I have been working extensively with a large GroupWise to Exchange conversion project.Novell GroupWise to Microsoft Exchange 2016 Hybrid Conversion with QWEST co-exsistance and GWAVA for migration tool.
RESOLUTION: What is needed is for Mail Users not Mailboxes, you need to disable RichTextFormat.
I had checked the GroupWise GWIA and noticed that the iCalc was enabled on the SMTP tab, and everything else checked out. However when I looked at the message it was in RichText. When I read the Dell article it lead me to believe that when the communication occurred Exchange says I'll use whatever it wants, and Novell was saying send it to me as Richtext. Exchange now prevents RichText so it will force as HTML or Plain Text, but RichText is no longer an option. Oh Novell.....
Powershell script
.Get-MailUser * -ResultSize Unlimited | % { Set-MailUser $_.alias -UseMapiRichTextFormat Never }
Get-MailUser * -ResultSize Unlimited | % { Set-MailUser $_.alias -UseMapiRichTextFormat Never }
I came across this Dell/Qwest article which had me curious...
https://support.software.dell.com/migrator-for-groupwise/kb/68002
Meeting requests sent from Outlook to GroupWise do not have any content and are received blank. (68002)
Return
Title
Meeting requests sent from Outlook to GroupWise do not have any content and are received blank.Description
In an Exchange Server 2010 to GroupWise 7 SMTP coexistence scenario, meeting requests sent from Outlook to GroupWise do not have any content and are received blank.Cause
This issue is not related to GroupWise Migrator but to Exchange Server 2010, as coexistence is realised via SMTP in this scenario. GroupWise clients may be unable to correctly read the Exchange rich-text format, so that meeting requests sent from Outlook to GroupWise appear as blank.Resolution
SOLUTION 1Change the properties of the remote domain in the Exchange Hub Transport settings
- Go to Organization Configuration -> Hub Transport -> Remote Domains -> Domain properties -> Message Format
- Set the Exchange rich-text format setting to 'Never use' (please see attached MessageFormat.png for screenshot)SOLUTION 2Set the Exchange rich-text format setting to 'Determined by individual user setting'. If this is set, the mAPIRecipient attribute on the AD contact or user object will be used to control whether messages are sent with Exchange rich-text format or not.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.