Recently we had an issue where a Office 365 Hybrid Environment where a local user would reset their expired Local Password and the ADDconnect service would disconnect the user and delete the Mailbox and User account. We could restore the Mailbox from deleted Users in the Admin Panel however it was only restoring “In Cloud” rather than “Synced with Active Directory”

I checked the ImmutableId for the User in 365

Get-MSOLUser -UserPrincipalName user@domain.com |flGet-ADUser -Filter {UserPrincipalName -like user@domain.com } -Properties ObjectGUID | select ObjectGUID

which is the unique value AADconnect uses to sync between on-premise and 365 and it was the same.

Running through the ADDconnect “Customize Synchronisation Options” showed the AD group created for selective Users to be Synced had been moved to a different OU and it could not reference this anymore.

Fixing the OU location of the Group resolving this fixed the accounts back to 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a user with a new Office 365 account receive the above error during downloading new email. Testing the connection it looks like the Wireless connection she was connecting to the internet with was intermittently slow.

Changing the Wifi to a hotspot or cable connection resolved this

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

I logged into https://h41111.www4.hpe.com/storage/msafirmware.html

To download the latest firmware for my 2040 , however, I needed to link my Device warranty to my HP Passport account

With only remote access to the Unit, I needed the Chasis Serial and Product Number

To get this on an MSA if you SSH into the device and do a “SHOW CONFIG”

Press Enter until you hit the SKU

Product Number for MSA 2040 is : K2R80A

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Mimecast Guide

Azure Microsoft Guide

Create a Distribution Group in Office 365, this will be to Add the users to you want enable SSO on , add Users 

Make sure Mimecast is Synced with Office365 AD – Services -> Directory Synchronization ( Connect to 365 ) 

Perform manual sync in Mimecast to download user and group

Azure

On Azure – Got o Azure Active Directory, All Application find:  Mimecast Personal Portal

Next Single Sign-On

Sign on URL : https://au-api.mimecast.com/login/saml

Identifier : https://au-api.mimecast.com/sso/%Customer ID% per Mimecase User Guide

Reply URL : https://au-api.mimecast.com/login/saml

User Identifier : user.mail

Azure AD Properterties : User assignment  required No 

Mimecast

Configuring Mimecast-Personal-Portal for single sign-on

1.In a different web browser window, log into your Mimecast Personal Portal as an administrator.

2.Go to Services > Applications.

3.Click Authentication Profiles.

4.Click New Authentication Profile.

5.In the Authentication Profile section, perform the following steps:

a. In the Description textbox, type a name for your configuration.

b. Select Enforce SAML Authentication for Mimecast Personal

c. As Provider, select Azure Active Directory.

d. In Issuer URL textbox, paste the value of Azure AD SAML Entity ID : https://sts.windows.net/434324324342343242323442/ which you have copied from Azure portal.

e. In Login URL textbox, paste the value of Azure AD Single Sign-On Service URL : https://login.microsoftonline.com/434324324342343242323442/saml2 which you have copied from Azure portal.

f. In Logout URL textbox, paste the value of Sign-Out URL which you have copied from Azure portal.

g. Open your Downloaded Azure AD Signing Certificate (Base64 encoded) in notepad downloaded from Azure portal, copy the content of it into your clipboard, and then paste it to the Identity Provider Certificate (Metadata) textbox.

h. Select Allow Single Sign On.

i. Click Save.

Now Add a New Application Settings to Application and Link the Group you created in the first step to use this New Authentication Profile

Issues

reply address ‘https://au-api.mimecast.com/login/saml’ does not match the reply addresses configured for the application: ‘https://au-api.mimecast.com/sso/’.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I tried to boot an hp elite 8200 Compaq desktop from USB, however, pressing the f9 key on bootup was not showing me any USB key. 

Upgrading the BIOS did not fix the issue

I have to Reset the BIOS to factory defaults which then showed the USB Key

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you are using products such as Cofense PhishMe , FriendlyPhishing or Knowbe4 as Phish testing software in your organisation then these test’s will get blocked in Mimecast. These organisations will give you a list of IP Addresses e.g for Cofense PhishMe ( 52.1.96.230, 52.5.119.169, 52.20.155.14 and 52.20.128.29 ) which you will need to whitelist through Mimecast 

Login to the portal and choose Policies then Permitted Senders

Create a new policy with the below options :

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)