Incorrect time on a Domain Controller running inside Hyper-V VM

Computer clocks withing whole domain run 5-6 minutes behind. Normally, authoritative time source for the whole domain is a Domain Controller (DC) that holds PDC Emulator FSMO role in the forest root domain. You can find which DC holds this role by running: netdom /query fsmo. Fixing time issues on this machine normally fixes it for the rest of the domain.

The DC in question was configured to receive time from an Internet NTP time source. However, running w32tm /query /source was returning: VM IC Time Synchronization Provider. This means the DC was receiving time from its Hyper-V Host instead of NTP Internet Time source. To resolve this, I went to Hyper-V VM Settings > Integration Services and disabled Time Synchronisation. 

Symantec DLO - can't add storage location - specified path is invalid

Issue

Cannot create a new Storage Location in Symantec Backup Exec Desktop and Laptop Option. When trying to add an existing local or remote folder following error is displayed:

Warning htlps://www.veritas.com/support/en_US.html
The specified palh is invalid.
Unable lo create the directory 'D:\Backups\DLO' on computer '<Server-Name>'. Please check the path does not reside on a read-only device such as a CD-ROM drive and that the DLO database service logon account has sufficient permissions to create the directory. You can change the logon account via the Services control panel. Service returned error code 0xb03b018.

.NET Framework 3.5 Feature Installation Fails - Source Files Could Not Be Found

Issue

Installing .NET Framework 3.5 Feature (via Roles and Features Wizard) on Windows Server 2012 fails with error:

Installation of one or more roles, role services, or features failed.
The source files could not be found. Try installing the roles, role services, or features again in a new Add Roles and Features Wizard session, and on the Confirmation page of the wizard, click "Specify an alternate source path" to specify a valid location of the source files that are required for the installation. The location must be accessible by the computer account of the destination server.

Send emails are not saved to Office 365 / Exchange shared mailbox sent items

Issue

Emails sent from a shared mailbox (users have full access and send as permissions) are saved only in user's sent items folder, but not in shared mailbox sent items.

Resolution

Connect of Office 365 via PowerShell and run following command:

set-mailbox <mailbox name> -MessageCopyForSentAsEnabled $True

To check status of the MessageCopyForSentAsEnabled property:

Get-Mailbox Sharedmailbox1 | select MessageCopyForSentAsEnabled