Working with many Office365 clients, I receive queries on how to go about provisioning users and mailboxes for an Exchange hybrid deployment. To begin with, let’s assume a couple things. We have a Windows 2012 R2 member server with Azure AD Connect (AAD Connect) version 1.1.105.00 (or newer) and the Azure AD Module for PowerShell installed; […]
Having a local administrator of your workstations can come in handy. Sometimes you might need to logon locally to troubleshoot or rejoin a computer to your domain. You can create a group policy that creates a local admin users and sets the local password. Admins make a common mistake when they want to add a […]
Let me start by saying that I don’t recommend doing this at all. Password Never Expires is bad security practice, but there are situations that might require it. I had a similar request on how this could be done. Setting it for multiple users:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
#Connect of Office365 Import-Module MSOnline $O365Cred = Get-Credential $O365Session = New-PSSession –ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection Import-PSSession $O365Session Connect-MsolService –Credential $O365Cred #Get a List of user that belong to the second domain $SDusers = Get-MsolUser -All -DomainName "yourseconddomain.com" #Setting the password never to expire ForEach($SDuser in $SDusers) { Set-MsolUser -UserPrincipalName $SDuser -PasswordNeverExpires $true } |
Setting it for a single user:
|
1 |
Get-MSOLUser -UserPrincipalName user@domain.com | Select PasswordNeverExpires |
Based on my audit for a client I found that a user mailbox was at sometime converted to a resource mailbox. There is no convert button/ link to switch it back. I still don’t know how, or why this would have happened. Anyways, for someone who may come across this weird issue, here is the […]
So I came across this error while migrating some accounts from On-Premise Exchange 2010 Server to Exchange Online. Error: The subscription for the migration user user@domain.com couldn’t be loaded. The following error was encountered: A subscription wasn’t found for this user. In short, there is an address conflict between the user properties of the exchange […]
The changes that need to be made are: Configure the user attribute targetaddress to contain the remote routing address for the mailbox. This should be in the format user@vanitydomain.mail.onmicrosoft.com. Set the msExchRemoteRecipientType attribute for the user account to equal 4. Set the msExchRecipientDisplayType attribute for the user account to equal-2147483642. (yes, this is a negative value) Set the msExchRecipientTypeDetails attribute for the user account […]
Connect to Office365 via Powershell ISE
|
1 2 3 4 5 |
Import-Module MSOnline $O365Cred = Get-Credential $O365Session = New-PSSession –ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection Import-PSSession $O365Session Connect-MsolService –Credential $O365Cred |
To delete a user:
|
1 |
Remove-MsolUser -UserPrincipalName user@domain.com |
Permanently delete a user or Remove the User from Recycle Bin:
|
1 |
Remove-MsolUser -UserPrincipalName user@domain.com -RemoveFromRecycleBin |
Remove All the Users From the Cloud:
|
1 |
Get-msoluser | remove-msoluser -force |
Remove All the Users From the Recycle Bin:
|
1 |
Get-msoluser –returndeletedusers -maxresults 100000 | remove-msoluser -removefromrecyclebin -force |
Remove All the Users With an Unlimited Count:
|
1 |
Get-msoluser -maxresults unlimited | remove-msoluser –force |
Send As permission is used when you need to give a user permission to use another recipient’s email address in the From address. In order to give Send As permission to a user on Office 365 you need to use Windows PowerShell. To give Send As permission to a user use these cmdlets: 1.Connect Windows PowerShell on your […]
