By understanding my previous posts:
Hybrid Azure AD Join – How a computer device is recognized as Hybrid device ?
Azure AD Connect: How to manually synchronize using import, syncronize, export?
Now it is easy to find out how to make hybrid join happen immediately:
Setup the hybrid AAD auto join infrastructure, i.e. AAD, SC... [阅读全文]
You may have noticed that:
if you remove a hybrid domain joined device from AAD, it comes up again.
if you revert the machine or shut it down, then remove the hybrid device from AAD again, still it comes up again.
Why the hybrid domain joined device comes up again?
When the device auto join the hybrid domain to AAD, it writ... [阅读全文]
In short, the recommended steps to manually do the syncronization is:
(Full/Delta) Import from on-premises directories, such as Active Directory
(Full/Delta) Import from Azure AD
(Full/Delta) Synchronization from on-premises directories, such as Active Directory
(Full/Delta) Synchronization from Azure AD
lesca | Azure
You have setup the SCCM Hybrid MDM with Microsoft Intune by following this guide:
But you cannot have your Hybrid MDM polices to be deployed on mobile devices. You checked the Cloudusersync.log log, it says
“Starting user delta sync, raise failu... [阅读全文]
I use OpenWRT as a VPN client connecting to another site as illustrated below:
The OpenWRT can initiate the VPN connection, but I can only reach site A from within OpenWRT shell.
Ping to remote site A from my PC, phone, or other devices connected to OpenWRT is not possible.
Locate the cause
When pinging... [阅读全文]
Dockerfile for wplesca image
FROM wordpress:lat... [阅读全文]
Win10 1709的 Get-WindowsUpdateLog 不再需要联网获取符号库
Win10 1703默认全新安装时不含SMB v1服务器端和客户端：
You are deploying AD RMS with Mobile Device Extension, and thus you also need to deploy AD FS infrastructure.
The AD FS server is on Windows Server 2016, i.e. AD FS version 4.
You are following steps or using PowerShell scripts from the link below to setup ADFS Relying Party Trust for ADRMS Mobile Device Extension
This is an example of .screenrc configuration file. Just for your reference.
# Bind F11 and F12 (NOT F1 and F2) to previous and next screen window
bindkey -k F1 prev
bindkey -k F2 next
screen -t Init
screen -t Work
screen -t OpenWRT ssh -i /root/key 192.168.1.1