No much...unfortunately...we were hoping someone technical could get on a call with us and Cisco, but we were told that wasn't an option.
What I did get was:
For the information in regards to the coding and calls necessary for Sales Insight to install and work properly, the isn't really more information to provide outside the fact the Outlook Add-ing requires HTTPS traffic to be open in order for it be able to talk to Marketo. The only other requirement is that the User who will be accessing the Outlook Add-in needs to be the one who installs the Add-in. If your IT Team tries to install it for them it will not work properly as the installer places some files into the local profile of the User who performs the install. If your IT Team needs the specific source/destination for the HTTPS traffic, the URL is:
Unfortunately, this wasn't enough information.
According to my IT department:
During the install it makes a call to register the plug-in before it finishes, and it is failing the install at that point.
I have been working with Cisco Web Cloud Security (formerly Scan Safe) who is our proxy server provider and so far we have done traces with Fiddler and Wireshark, and that have tried to make adjustments to the configuration for this .msi piece (as we can get to every website that is listed in the traces, with no problem from a browser, it's just when it makes the call from the .msi that it fails).
That's all that I've got. Any ideas?
Thanks!
.png)