Hello and Happy Monday! Yes, I know and I’m sorry that I’d left my blog “in the cold” as life-work and business has took away most of my time since I’ve started my own (Woo-Hoo!). In this article, I’m about to share about another Cloud platform which involves integration with Microsoft Office 365.

As the industry “all” moves to the cloud, the dependencies of deploying and configuring Cloud platforms gradually increases as well.

Recently, I was involved with an Office 365 with Symantec.Cloud integrated (Mail & Web) and we’d to setup a Schemus Server (similar to Microsoft’s Azure AD Connect) which synchronizes the Active Directory’s Users and Objects to Symantec.Cloud platform. Activating the tenant was pretty straight forward as we already had the tenant ready during the evaluation stage (Proof-of-Concept), next thing is to configure Schemus.

While trying to establish the relationship between the Symantec.Cloud with Schemus, the following error message was presented on the setup window:

Symantec.Cloud_SchemusError

 

 

 

 

 

Can’t access the Symantec.Cloud service. There was a problem communicating with the Symantec.Cloud service server: WS Security The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired)

To resolve this issue, make sure the following entries are in-place:

  1. If you’ve recently changes your password for Symantec.Cloud service, update your most recent password at Schemus Configuration OR at the Schemus Windows, click on Edit > Settings > Symantec.Cloud and modify password field
  2. Make sure that the specified URL is accessible and not filtered/blocked by the Firewall
  3. System Time is the same as the Internet time

Symantec_SchemusUpdate

 

 

 

 

 

We ran into the issue on item #3 and what we’d to do was just simply modify the system clock and click on Apply. Close the Schemus and re-launch the settings window and Walla! the problem went away. Based on Symantec Technical Support, updating the system clock to establish the communication with Symantec.Cloud is only one-time off, so for those organizations whom aren’t following the Internet time, the Schemus server would be able to resync its time with either the Active Directory or NTP Server.