Recently I added a new Email Account ( Office 365 ) to Mac Mail , however, when trying to compose a new mail with

Preferences > Composing > Send new messages from: Account Selected

It would send the email from another account altogether , the accounts setup where not receiving email , in the end I have to go through and check all the other accounts were OK before readding the Exchange account again twice it finally worked


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

Install-Module : The term ‘Install-Module’ is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is corre
ct and try again.

Install Either of these : 

$x86 = ‘’
$x64 = ‘’

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

On setting up a new surface for a user , which was enabled for modern authentication MFA 2fa in 365 , when asked in Outlook for Need Password the login prompt would come up blank and disappear.

  • Signing out and back in to Outlook did not fix this
  • Proxy Configuration was checked

**** Update ***** Make sure you have the following Reg Keys

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\DisableADALatopWAMOverride] – REG_DWORD “1”

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL] – REG_DWORD “1”

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

We could not access a Gatekeeper certificate. This can occur if:
•no certificates could be found on your system;
•your certificate has expired; or
•you hit “Cancel” when asked to select a certificate.

If you know you hold a current certificate and can see it in your certificate store, contact Support to trouble-shoot. They can assist with other possible causes such as:
•A missing certificate chain (root and intermediate certificates); or
•A proxy server on your company network interferring with SSL/TLS client authentication.


In Internet Explorer go to Internet Options then Content and Certificates

Under your Personal Tab double click on the most Recent Gatekeep Cert

Go to Certification Path and make sure it does not say The issuer of this certificate could not be found.

If it does say this it means your Root Chain is broken and you need to install the Gatekeeper Root 

Navigate to

Scroll to the bottom and download all the Root CA’s

Double Click on the X509 and install these using the Automatic Wizard ( you can select Trusted Route Authority the Second one down if you want to do Manually ) 

Back where you Opened up the Certificate in Internet Explorer , if you go back to the Personal Tab and Click on Import

Choose Browse , change the Input all Files you can import the PKCS#7 Files

Now when you go to Certification Path you should see multiple files there

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

The Antivirus N-able Technologies installs as part of its agent is called

Security manager AV defender

This is just rebranded Bitfender , you are supposed to contact N-able to get the un-installer however you can get it from the BitFender site here

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

Installing N-able on a windows machine is as simple as running an MSI with the customer ID and creates an activation key for you 

On a Mac you would think this would be the same however not! 

  1. Add the Device Manually on the N-able server under your client

Enter the Device Name and IP Address ( address should be fully qualified domain pc.domain.local ) , change the machine Workstation OSX and class to correct

Set Local Agent Tab to Manual Click Save Button

Navigate to the nearly created device and go to Settings and sub Tab Local Agent

Download the  agent-macosx.tar.gz file from the link it gives you and copy the Activation Key

Extract the  agent-macosx.tar.gz on the Mac after downloading 

Open “agent-macos.pkg”

If you getcan’t be open because the identity of the developer cannot be confirmed”, please change Security and Privacy settings as follow ?nd try again:

1. Open “System Preferences”
2. Select “Security & Privacy”
3. Go to General tab
4. Click the Lock (bottom-left corner) to unlock it (administrative password is required)
5. Set “Allow apps downloaded from” to Anywhere
6. Close the dialog
7. Repeat agent installation
8. Change “Security & Privacy” to the initial setting if needed

Once running it might fail to generate an Activation Key , if you go back you can choose to authenticate with a key , use the Key you copied from previous step and this should activate

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 using roaming profiles at your company via GPO or in the profile Tab in Active Directory, Roaming Users visiting remote sites on the same network as the office might have issues logging in due to the speed at which the profile is downloaded over the site to site VPN

Use the IP range of the Remote Site to make a new AD Site

Create a GPO 

Open up Group Policy Management and add this GPO to that site


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

To Recreate SysVol Share

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following subkey in Registry Editor:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
  3. In the details pane, right-click the SysvolReady flag, and then click Modify.
  4. In the Value data box, type 0, and then click OK.
  5. Again in the details pane, right-click the SysvolReady flag, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

The NetLogon Share is actually the Scripts folder that sits in this Folder , so is this Sysvol folder is still blank if means your replication is not working

In the Event Log : Applications and Services Logs/DFS Replication in Event Viewer:

Check for Event ID’s 2010 or 4114 ,


set msDFSR-Enabled to FALSE


set msDFSR-Enabled to TRUE

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


UEFI requires USB media to be in FAT32 format, which has a 4GB file size limitation. The install.wim file for Server 2012R2 is about 4.5GB, so needs to be split up as follows:


Step 1. Split install.wim image

  • Extract ISO contents, go to the Sources folder and locate the install.wim file
  • Copy the file to a separate folder (e.g. C:\Temp)
  • Open a Powershell window with admin rights and browse to this newly created folder
  • Run the following command:

Dism /Split-Image /ImageFile:install.wim /SWMFile:install.swm /FileSize:4000

This will create two files: install.swm and install2.swm

  • Copy these two files to the Sources folder and delete the install.wim file


Step 2. Format USB key

  • Run cmd



> SELECT DISK (pick appropriate disk)








  • Copy all the folders from extracted ISO into the USB stick. Now you should be able to boot and install Windows from it
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Login to Fortigate WebUI

Go to System , then Administrators, Enable Trusted Hosts for the user account and add the IP/Subnet to the allow lists ( remember to do internal as well ) 

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