Just after updating to AWS, many of our users are unable to connect with Jive for Office/Jive for Outlook. Just after migration, I was connecting fine. However when I heard some people were experiencing troubles, I manually revoked my own token from the admin console. Now I am unable to create a new token on my Windows 8 laptop.
We tried the latest version of Jive for Office with no luck.
Although we are not live yet with Windows 10, our IT department has confirmed that they can create the token with no issue using Windows 10. However we are not ready to deploy that yet, so we need to solve on current systems.
We are already engaging L2 support and waiting for L3, but if anyone else has experience with this, please let me know.