Get list of Full mailbox, Send As, Send on Behalf of Permissions in Office 365

Problem

You need to list all full, send as and send on behalf of mailbox permissions for a user in Office 365

Solution
$user = "username"
$Mailboxes = Get-Mailbox
#List mailboxes with full access
$Mailboxes | Get-MailboxPermission -User $user
#List mailboxes with Send As right
$Mailboxes | Get-RecipientPermission -Trustee $user
#List mailboxes with Send On Behalf Permission
$Mailboxes | ? {$_.GrantSendOnBehalfTo -match $user }
Reference, Links and Imges

 https://www.michev.info/Blog/Post/1516/quickly-list-all-mailboxes-to-which-a-particular-user-has-access

Restore deleted AD object if recycle bin is not enabled

If you delete a user account and recycle bin is not enabled then download ADrestore from https://docs.microsoft.com/en-us/sysinternals/downloads/adrestore 
Open up command prompt and change the directory to were you extracted AD restore.

Run the following command and you will be prompted to say yes or no to restore the user account


ADRestore -r 

 

 https://blogs.technet.microsoft.com/asiasupp/2006/12/14/using-adrestore-tool-to-restore-deleted-objects/ 


NOTE

 

When this restores it restores the AD account as disabled so you need to reset the password first the enable the account.

Install Sage V26 Data Service On SBS Server or Server Essentials

Running Sage on a Small Business Server is NOT supported by Sage, but if you need to run it like this for some reason, here's how. 

  1. Attempt the installation using the setup file provided by Sage as normal, when you receive the error message about the operating system being incompatible, click close. This step is necessary as it extracts the files we need to a temporary path on the server.
  2. Log out of Sage from all computers.
  3. browse to C:\Users\<your-username>\AppData\Local\Temp and find the ‘Sage Accounts’ folder with the newest date.
  4. Go into the ‘Sage Accounts’ folder, then into ‘Packages’
  5. You must now run the following msi installer files in this order 1) Sage50Accounts_DataAccess.msi 2) Sage50Accounts_Client.msi 3) Sage50Accounts_ODBC_x64.msi 4) Sage50Accounts_ReportPack.msi
  6. If you get an error complaining about the need for C++ runtimes when you try and install the Sage50Accounts_DataAccess.msi – simply install the runtime library from this link on your server.
  7. Reboot the Microsoft Server 2016 Essentials server and run the Sage Accounts icon on the desktop. Select the company you want to login as and allow Sage Software to do the data conversion from the old version to new. This can take anywhere from a few minutes to an hour depending on the size of your company data.
  8. Once the data conversion is done, that should be it, simply install the regular sage installation file you downloaded from Sage on all the other PCs on the network that need access to Sage and you should now be able to log in and use Sage on the latest version from PCs and Server.

Convert a Dynamic Districution Group to a Standard Distribution Group in Office 365

As far as my research has taken me, I cannot see a way to convert a Dynamic group to a static one in office 365. To make the process easier, we can use PowerShell to duplicate the group then delete the old one.

$DynGroup = Get-DynamicDistributionGroup "All Staff"
$DynGroupMembers = Get-Recipient -RecipientPreviewFilter $DynGroup.RecipientFilter
New-DistributionGroup "All Staff"
$DynGroupMembers | foreach {Add-DistributionGroupMember "All Staff" –Member $_.Name}

How to RDP to an AzureAD Joined Client PC

Connecting to an AzureAD Joined machine is a little different than a normal Active Directory Joined / Workgroup machine. Here is how you can configure RDP

1. On the target PC, ensure that Network-level authentication is disabled.

2. On the source PC, create an RDP file to connect to the computer and save it. Once saved, open it with notepad and add the following two lines of configuration.

enablecredsspsupport:i:0
authentication level:i:2

Finally, enter the username in this format:

AzureAD\<full UPN in Azure AD>

Connect to the RDP session. You will be prompted with a Login screen. SSO will not work when connecting in this way.