SCCM CB Version History

Windows 10 and Windows Server 2016 fails managing DirectAccess clients

What is ISATAP ?
Intrasite Automatic Tunnel Addressing Protocol (ISATAP).

Important Note: There has been much confusion regarding the supportability of DirectAccess in Azure. Historically it has not been supported.

DirectAccess manage out using the Intrasite Automatic Tunnel Addressing Protocol (ISATAP), you may find connecting to remote DirectAccess clients by hostname using Windows 10 or Windows Server 2016 fails. Connections to remote DirectAccess clients using Windows 7, Windows 8.x, Windows Server 2008/2008R2, and Windows Server 2012/2012R2 work without issue.
On a Windows 10 or Windows Server 2016 host configured to use ISATAP for DirectAccess manage out, the remote DirectAccess client resolves to an IPv6 address correctly.
In addition, a route to the DirectAccess client’s IPv6 prefix is also present in the routing table.
Nevertheless, attempts to connect to the remote DirectAccess client by name fail.
The DirectAccess client is reachable by its IPv6 address, however.

Fix:- PowerShell command
New-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters\” -Name AddrConfigControl -PropertyType DWORD -Value 0 -Force

CB with Intune (Hybrid/Stand-Alone) - Architecture

CB with Intune (Hybrid/Stand-Alone) - Architecture

PowerShell Script to Domain Join



Domain Join - PowerShell Script Refer Below

#************************************************************************************************************************
$ErrorActionPreference = "SilentlyContinue"
Set-ExecutionPolicy remotesigned -Force $ErrorActionPreference
Clear-Host
Write-Host "*******************************************************************************"  -foregroundcolor "Green"
Write-Host "File Name : Domain_Join.ps1"                  -foregroundcolor "Green"                                                                                        
Write-Host "Purpose  : Domain_Join"           -foregroundcolor "Green"                       
Write-Host "Version  : 1.0"                    -foregroundcolor "Green"
Write-Host "Date  : 30/13/2017"                  -foregroundcolor "Green"
Write-Host "Author  : Ganapathy Natarajan"           -foregroundcolor "Green"
Write-Host "Requires : PowerShell V2"                  -foregroundcolor "Green"   
Write-Host "*******************************************************************************"  -foregroundcolor "Green"
$DomainName = "LAB"
$JoinDomainUserName = "Administrator"
$Password = "Password@123" | ConvertTo-SecureString -asPlainText -Force
#************************************************************************************************************************
$DomainUserName = "$DomainName\$JoinDomainUserName"
$Credential = New-Object System.Management.Automation.PSCredential($DomainUserName,$Password)
Try
{
 Add-Computer -DomainName $DomainName -Credential $Credential
 Write-Host "Successfully machine joined to $DomainName Domain Network"      -foregroundcolor "Green"
 Write-Host "System is going to reboot now....."           -foregroundcolor "Green"   
 Restart-Computer
}
catch
{
 Write-Host "Failed to joined $DomainName Domain Network"    -foregroundcolor "Green"
 Write-Host "Try next time again....."      -foregroundcolor "Green"
}
#************************************************************************************************************************

Click-to-Run and Windows Installer on same computer isn't supported

What is Click-to-Run ?
Click-to-Run is the technology used to install Office 365 subscription.

What is Windows Installer ?
Windows Installer technology (MSI) is used to install the volume license editions of Office, like Microsoft Office Professional Plus and Microsoft Office Standard.

Note: Unfortunately, you can't have Office products of the same version (like 2013 or 2016) that use two different installation technologies installed on the same computer.