Microsoft’s naming changes for Windows 10 updates can be a little confusing. Here’s a little guide to describe the latest terminology and a mapping between the old and new terms. As you will likely already know, Microsoft has shifted from a new release of Windows every few years to a ‘windows as a service’ model. …
I recently wrote this script that creates an O365 mailbox within a hybrid exchange environment, creating all the necessary attributes etc in exchange and AD Log all output to a local logfile, that is unique each time and won’t get overwritten
|
1 |
[cc lang="powershell"]Start-Transcript -Path $env:LOCALAPPDATA"CloudwyseLogs"$(get-date -Format ddMMyy_HHmmss)".log" -NoClobber[/cc] |
Clear output from the screen to prevent previous command being sent as first…
A script I recently used to add members to an office 365 distribution group using a remote exchange session in a hybrid setup (covered at the end).
|
1 2 3 4 5 |
[cc lang="powershell"]$SourceFile = "" Import-CSV $SourceFile | ForEach ` {Add-DistributionGroupMember -Identity "Group Name" -Member $_.UPN Write-Host -ForegroundColor Green "Processed the record for $($_.UPN)" }[/cc] |
CSV file contains UPNs of all users to be added. I also found it useful to see who had permissions to send to this group using
|
1 |
[cc lang="powershell"](Get-DistributionGroup -Identity "Group Name").AcceptMessagesOnlyFrom | ForEach {Get-User -Identity $_}[/cc] |
…
This only applies to new Active Directory users. To look at how to use SMTP matching to link an on-prem user to an existing O365 mailbox in a hybrid environment follow this guide.1. Log into the Exchange Admin Center: https://mail.contoso.com/ecp2. In the EAC console of your on-premises hybrid server, go to Recipients > Mailboxes and click…
The scenario is that a user account has been created in Office 365 in a hybrid setup. This scenario is actually ok and is supported by Microsoft. However, it causes problems for an Office 365 user when they require access to public folders on the on-premises Exchange server. First make sure you have the correct…
First connect to the remote server with powershell
|
1 |
[cc lang="powershell"]Enter-PSSession -ComputerName contoso\hv01[/cc] |
Next run the command to add the group:
|
1 |
[cc lang="powershell"]Add-LocalGroupMember -Group "Administrators" -Member "CONTOSO\Hyper-V Admins"[/cc] |
If you’re paranoid (like me) and want to check this worked you can use:
|
1 |
[cc lang="powershell"]Get-LocalGroupMember "Administrators"[/cc] |