Replication – DFS

23 Feb


Good article


Outlook 2016

22 Feb

Issue: Outlook 2016 (which I am testing) cannot connect to Office 365 Exchange.

It is no longer possible to manually enter Exchange Server details. A valid Autodiscovery record is required. Use this site to find out which autodiscovery mechanism you are using.

Verifies that we do have a valid autodiscovery record and that we use the HTTP Redirect method. It also shows that Outlook tries several other autodiscovery methods before the correct (for my organisation) HTTP redirect method.


What is actually happening is that Outlook 2016 on the PC is hanging when performing the HTTPsAutoDiscoverDomain method. We can force it to use the correct method by the following registry entries.

If Outlook is slow finding the autodiscover records, you may need to tell Outlook to exclude the root domain or other records.

DWORD: ExcludeHttpsRootDomain
Value: 1

The other records you can exclude, also under the Autodiscover key are as follows. Use a value of 1 to enable, delete the key if you no longer want to exclude these checks.

DWORD: ExcludeScpLookup
DWORD: ExcludeHttpsAutoDiscoverDomain
DWORD: ExcludeSrvRecord

Rename UPN – O365 Powershell

16 Jan

Login to Windows Azure Active Directory Module for Windows PowerShell with Office 365 administrator credentials and run the following command:

Set-MsolUserPrincipalName -UserPrincipalName -NewUserPrincipalName


16 Jan

Shadow Copy Overview



Bulk update emails in AD

9 Jan

Numerous ways to do this however perhaps the easiest is open Active Directory Users and Computers, select the users you want to update, get their properties, and Email to the variable field you have already used, %username%@restofaddress. ADUC will flesh out the username for you. You’re not restricted to the domain name AD uses, it’s a free-form field.

Remote Desktop Services

11 Dec


Prepopulate domain field

Key path SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon
Value name DefaultDomainName
Value type REG_SZ

Value Data

Set-MsolUserPrincipalName : Access Denied.

5 Dec

Most of the time, you see the “Access Denied. You do not have permissions to call this cmdlet” error message because of a non-existent UPN name in the “-UserPrincipalName” parameter.

To verify this, you can combine Get-MsolUser and Set-MsolUserPrincipalName cmdlets to include this validation check to get some more meaningful error message.

I suggest you replace “Set-MsolUserPrincipalName -UserPrincipalName $365 -NewUserPrincipalName $email

with “Get-MsolUser -UserPrincipalName $365 | Set-MsolUserPrincipalName -NewUserPrincipalName $email” and let us know the outcome.