Office 365 Azure AD Connect assigning .onmicrosoft.com to synced users

When Azure AD Connect it configure to sync ad account to Azure AD/Office 365 it assigns the login name as the AD UPN (as expected), but it won’t assign that same UPN as the default email address – instead it assign a @mydomain.onmicrosoft.com as the primary email address.

to correct this we can use the Synchronization rules editor, which is installed together with the Azure AD Connect (Download Link)

In Synchronization rules editor, switch the direction tabs to outbound rules.
select the rule called “Out to ADD – UserExchangeOnline”, click edit and accept the option to disable and clone the rule (this will create a rule called ““Out to ADD – UserExchangeOnline – Cloned” that can be modified.

Change the precedence to 50

go to transformations, and Scroll down till you find the “Target Attribute” of “ProxyAddresses”
Change the FlowType to “Expressions” and enter the following in the source:

Now resync the users and the primary email address should be changed

Sources: https://rscc.co.uk/solution-office-365-assigning-onmicrosoft-com-addresses-used-aad-connect/

Apple iCloud Add-in Keeps Disabling Itself in Outlook

iCloud Add-in Keeps Disabling Itself in Outlook

you can force outlook not to disable a plugin by change loadbehavior and add it to outlook resiliency list.
It is both done by windows registry (regedit)

open regedit and look for

If you can’t find it try to look for

and set the value for the LoadBehavior to 3 (always load)

Even with this key set, Outlook can some times disable the plugin anyway, you can prevent it by adding another key:

Sources: https://www.slipstick.com/outlook/icloud-sync-failure/

STOP 0x0000007B

When changing storage adaptor or change for IDE to ACHI Mode, you may see the 0x0000007b error code

you can fix it by changing “start” key to 0 the 2 the regedit

Sources:
https://support.microsoft.com/en-us/help/922976/error-message-occurs-after-you-change-the-sata-mode-of-the-boot-drive

Exchange 2010 AutoReply/Forwarding rules not working

Recently I try to setup a Auto reply rule on one of our outlook clients, and noticed that all rules are working except for the ones that requires
forwarding and auto reply, I found out that default a exchange 2010 don’t allow both forwarding and autoreplying. you can enable it here

Source:
http://blog.garraux.net/2010/11/exchange-20072010-forwarding-rules-not-working/

Powershell: List current values of get-commands

Powershell: List current values of get-commands

List all current values of get-command

Get-AutodiscoverVirtualDirectory-fl

List all specific values of get-command

Get-AutodiscoverVirtualDirectory-fl-specific

Exchange 2010 – Single Common Name SSL Certificate

Exchange 2010 – Single Common Name SSL Certificate

Create SRV record:
Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: mail.example.net

 

Run get-exchangecertificate and note the thumbprint on the new certificate (watch out for dublets!)

Run Enable-exchangecertificate -thumbprint <TUMBPRINT> -services SMTP,IIS,POP,IMAP

Run iisreset

Restart the Microsoft Exchange services

Restart Clients Pc’s

source: http://www.cohesivelogic.com/exchange-2010-single-name-ssl-certificates/

Remove password expiration Office 365

Remove password expiration Office 365

I wrote this powershell script to remove password expiration for all users, so that the users password not expires

Password_expiration.ps1

Change Retention Policy – Office 365

Change Retention Policy – Office 365

I wrote this powershell script to remove the Retention Policy that delete all emails in Users Deleted Items folder that are older then 30 days

Retention_Policy.ps1

Live migration of ‘Virtual Machine’ failed. Event 21502

Live migration of ‘Virtual Machine1’ failed.

Virtual machine migration operation for ‘Virtual Machine1’ failed at migration destination ‘NodeX’. (Virtual machine ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

The virtual machine ‘Virtual Machine1’ is using processor-specific features not supported on physical computer ‘NODEX’. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

fix:
stop VM
Set-VMProcessor “Virtual Machine1” -CompatibilityForMigrationEnabled $true