Hi Frederick... I just got an answer on this and was looking for this old thread. After editing or transforming the MSI one should not expect the digital signature to remain valid. 'Real' (read not free or very expensive) packaging software can accomplish this, but orca cannot do this. This came from the manager of our packaging group (a true SME on the subject), I showed him the procedure Cisco is prescribing and he assured me there is no simple way of accomplishing this. Thanks Zack ... View more

Do you know if PEAP was ever added to the 9971 firmware? Thanks Zack ... View more

Hi Jas Thanks for the response. The issue with that method vs. the transform is that it breaks the digital signiture of the .msi. Before ORCA Edit: After ORCA edit: It's my understanding the transforming the MSI vs editing retains the digital signiture. Thanks Zack ... View more

It appears that using the suggested method breaks the digital signature of the .msi. Any suggestions? ... View more

Hi Jasmeet It does not appear that Step 3 and the link in Step 4 apply any longer. I am still getting this issue in the newest version of Jabber. Thanks Zack ... View more

Hi Michael Thanks for the info. Question on the second response (your link is exactly what we were referencing), is that caveat applicable to both EWS and WebDAV integrations? The big problem we see is that there is very little alignment between the CUP and Exchange teams, i.e. the voice team would not have any indication that a user is being moved between mail box servers and if this is being done en masse how could the CUP administrator possible manage resetting the integration? Thanks Zack ... View more

Hi Scott Thanks for posting this very helpful and timely script for integrating CUP to Exchange. In our planning for this integration, we have encountered a few areas of the Integration guide that are a little less than clear: 1) How is the impersonation service account password stored in the CUP database? I'd assume our enterprise is similar to most in that Voice Engineering does not manage Exchange. As such, the service account will be owned by the Exchange team and they would like reassurance that the password cannot be compromised. The integration guide does not provide any details around this concern. 2) Page 68 of the deployment guide calls out a caveat called "Calendaring State Does Not Update if a User Moves between Exchange servers". Does this apply to both WebDAV and EWS? If this does impact EWS, the proposed solution doesn't really scale and will be operationally challenging as there is no alignment of users between CUCM Cluster and Exchange mailbox servers. Thanks for your time Zack ... View more