- Make sure you have a Send Connector in O365 so that I route all emails from your subdomain e.g. imanage.domain.com back to the Public IP where your Communication Server is , use the Router to NAT port 25 from this IP to the communication server and make sure SMTP is allowed through the local firewall
- Update the ‘Email Domain’ on the ‘WorkSite Server’ properties to ‘imanage.domain.com’ stop and start the ‘WorkSite Server’ service.
- Then update the ‘Domain’ in the communication server ‘Exchange Online’ properties to ‘imanage.domain.com’ stop and start the ‘Exchange Online’ service.
- The above will allow internal recipients to Send and File , if wanting external recipients to be able to file emails to this server, make sure you create an MX Record for imanage.domain.com externally to route to your communications server ( preferably via your Spam Filter)
Azure Single Sign-On
Identifier (Entity ID): https://imanage.domain.com
Reply URL (Assertion Consumer Service URL): https://imanage.domain.com/api/v1/session/saml-login
Download Certificate file (.cer) and store on iManage server e.g. C:\SSL\
SAML Attribute: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
SAML Endpoint: https://myapps.microsoft.com/signin/iManage%20SAML/xxxxxxx-xxxxxx-xxxx
SAML Key File: C:\SSL\iManageSAML.cer
SAML Logout Endpoint: https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0
SAML Web RP: https://imanage.domain.com
Recently we had a DC Power supply ( with external Transformer ) fail at a Site using a rebranded Overture NTU with Vocus. This NTU actually has an internal AC Power Supply in the unit with a IEC Connector. These can be run in parallel ( ACTIVE – ACTIVE ) incase failure of the replacement DC Powersupply fails again
On the Fortigate
Import Following Service Templates for Fortigate
Add a new Device via IP Address ( Category Router )
Add Service templates to device
A client had to roll out 100+ laptops and choose Intune for this. It wasn’t certain who was getting what laptop so the choice was made to use an admin account to enroll the devices before giving them to the user.
Intune has a Enroll Limit of 15 so after 15 you start having issues
In Intune you can actually setup Device Enrollment Managers who can actually Enroll 1000+ machines
In Intune in the Azure portal, choose Device enrollment > Device enrollment managers.
On the Add User blade, enter a user principal name for the DEM user, and select Add. The DEM user is added to the list of DEM users.
Clicking on any website links in Outlook 2010 in Windows 10/2016 would cause this prompt to appear:
Ticking Always use this app doesn’t help as clicking on the link again causes the prompt to re-appear. After doing some digging, I initially thought it was due to this documented issue with Citrix and Microsoft Server 2016 – https://support.citrix.com/article/CTX228597
However after spending more time than I care to admit looking at the above, the fix was something completely unrelated to the above article. Implementing a few simple missing registry keys outlined in this article resolves the problem: https://support.microsoft.com/en-us/help/3094186
TLDR the below keys are missing from Windows 10 which are present in earlier versions of Windows, which is what causes this prompt to constantly re-appear. To address it, create the below two registry keys:
Modify the value of the (Default) registry setting:
Change value of (Default) to rundll32.exe url.dll,FileProtocolHandler %1 to open links in a new tab
Change value of (Default) to “C:\Program Files\Internet Explorer\IEXPLORE.EXE” %1 to open links in a new window
For a new deployment we needed for Outlook to show the Task’s ToDo List on the Outlook Home Screen
I couldn’t find this documented anywhere so I have to monitor the Outlook.exe during the change to find out what Registry Key it changed
Item : PinMail
Type : Dword
Value : 4