Musings, Findings and Tech
I added a script to my personal github – Gives permission to a mailbox on Office 365. I find myself needing to do this somewhat regularly, and the rule is if you’re something over and over again, automate it as much as you can.
https://github.com/brandons-zz/Powershell/blob/master/Set-UserMailboxHiddenUnHidden.ps1
Continue reading “Git: Give access to an O365 Mailbox to single user”
I added a script to my personal github – Hides or unhides a mailbox on Office 365. I find myself needing to do this somewhat regularly, and the rule is if you’re something over and over again, automate it as much as you can.
https://github.com/brandons-zz/Powershell/blob/master/Set-UserMailboxHiddenUnHidden.ps1
Continue reading “Git: Hide or Unhide a User Mailbox on Office365”
I needed to do this today because I had setup a pair of servers and it turns out they needed to be Datacenter edition instead of Standard edition. What used to mean you would need to rebuild, is really now just another command to run.
dism /online /Set-Edition:ServerDatacenter /ProductKey:CB7KF-BWN84-R7R2Y-793K2-8XDDG /AcceptEula
It took about 20 minutes or so but Before you tell me I posted my keys … sorry but it’s the KMS client key from Microsoft.
I found this command from ITechLounge.
Longest title in history?
A while back we were doing some troubleshooting and we added an administrator’s account to have read permissions on all of our mailboxes. Mailboxes permissions came up as a topic yesterday in a conversation I was having and I remembered I had meant to clean this up. I could have gone about this a bunch of different ways, but ultimately I wanted to create a script in case I ever needed it again. Continue reading “Remove a single user’s permissions from all mailboxes in Office 365”
As an admin occasionally you’ll give yourself permissions to a mailbox. And then you’ll remember Outlook conveniently auto-maps that mailbox for you. Easy fix.
Close Outlook. Open Powershell.
Add-MailboxPermission -Identity targetuser@foo -User youradmin@foo -AccessRights FullAccess -AutoMapping:$false
Open Outlook. Enjoy the emptiness of the side bar.
You can/should also (once the mailbox disappears from Outlook) remove the permissions completely.
Remove-MailboxPermission -Identity targetuser@foo -User youradmin@foo -AccessRights FullAccess -InheritanceType All
Shamelessly borrowed from:
Spiceworks
# Get login credentials $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session -AllowClobber -DisableNameChecking $Host.UI.RawUI.WindowTitle = $UserCredential.UserName + " (Office 365 Security & Compliance Center):" # search for the email in all mailboxes New-ComplianceSearch -Name "Easy-To-Identify-Name" -ExchangeLocation all -ContentMatchQuery 'sent>=12/01/2017 AND sent<=12/30/2017 AND subject:"announcement" AND from:"username@domain.org"' Start-ComplianceSearch -Identity "Easy-To-Identify-Name" # wait a minute and view the results Get-ComplianceSearch -Identity "Easy-To-Identify-Name" Get-ComplianceSearch -Identity "Easy-To-Identify-Name" | Format-List # delete the messages if the results look right New-ComplianceSearchAction -SearchName "Easy-To-Identify-Name" -Purge -PurgeType SoftDelete # check when it is completed Get-ComplianceSearchAction -Identity "Easy-To-Identify-Name_Purge"
I forget this every time I reset my password…
(Get-Credential).Password | ConvertFrom-SecureString | Out-File "C:\Scripts\365SecureString.txt"
Using it:
$pass = cat "C:\Scripts\365securestring.txt" | convertto-securestring $mycred_online = new-object -typename System.Management.Automation.PSCredential -argumentlist "UserAccount@contoso.com",$pass $mycred = new-object -typename System.Management.Automation.PSCredential -argumentlist "UserAccount",$pass
Storing this one for later…
$cred = Get-Credential
Enter-PSSession -Credential $cred -Computername <hostname>
Get-NetAdapter -Physical
Get-DNSClientServerAddress –interfaceIndex XX (Just making sure this is the interface I want to change).
Set-DNSClientServerAddress –interfaceIndex XX –ServerAddresses (“x.x.x.x”,”x.x.x.x”)
Exit-PSSession
I was provided a list of email addresses of employees in a system that doesn’t interface with AD/Exchange and asked to validate those email addresses exist within our Exchange server. I figured the easiest way was to just script it (the list was close to 1000 people). Total run time to compare the list was just a few seconds.
Here’s the (quite simplistic) script to accomplish the task.
$logFile = 'c:\scripts\IsAccountValid.log'
# Uncomment the entry below if not running from the EMS
# Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin
# Import the email addresses from text file
$Import=Get-Content "c:\Scripts\emailaddresses.txt"
ForEach ($address in $import) {
$valid = get-mailbox -an $address
If ($valid) {
"$address is Valid" >> $logFile
} else {
"$address is Not Valid" >> $logFile
}
}
This summer I’m decommissioning an old file server that is no longer under warranty, and we have plans for it along with the iSCSI SAN it’s connected to. Slight problem though – even though I’ve configured our user shares to replicate around using DFS, for years the user creation script that was used for creating accounts hard coded the user home directory to this file server. With thousands of accounts – I’m not about to go and do all this by hand.
Enter Quest ActiveRoles Management Shell (free). Sure I could have used other tools – but I’ve got this one and I like it. Anyway, here’s the script I wrote to do this. Note: It is likely not perfect, maybe not the most efficient way to handle this (definitely a bit slow), but it works and was ran against a few thousand user accounts.
Continue reading “Bulk Migrate User Home Directory in Active Directory”