PowerShell Basics: How to Force AzureAD Connect to Sync
In every organization, the possibility of role changes or change of contact information can occur quite frequently. AzureAD Connect is a great tool that allows administrators to make said updates either on-premises or in cloud and will sync all changes accordingly. It can take up to 30 minutes for Azure Active Directory to update these changes when these changes are applied on the on-premises Active Directory instance and vice-versa via AzureAD Connect. It can also take up to an additional 30 minutes to then sync changes with Office 365. This post will detail steps to force AzureAD Connect to sync on command when required via PowerShell to combat the delay.Step-By-Step: Manually Removing A Domain Controller Server
Use of DCPROMO is still the proper way to remove a DC server in an Active Directory infrastructure. Certain situations, such as server crash or failure of the DCPROMO option, require manual removal of the DC from the system by cleaning up the servers metadata. This blog post will help you accomplish this.Step-By-Step: Enabling Hyper-V for use on Windows 10
Virtualization provides a plethora of solutions from making the most of an organization’s hardware investment to running specific applications in other OS offerings. Using the same technology found in Windows Server, the Windows 10 embedded Hyper-V client allows IT professionals to move VMs from server to client without the requirement to re-learn the use of Hyper-V features and tools.AzUpdate: Post Ignite recap, Responsible AI, Azure Automanage, Azure Resource Mover and more
Well Microsoft Ignite 2020 is over and while our step counters may not have captured as many steps as last year... it doesn't mean that there wasn't a plethora of Azure news shared. Here are the headlines we are covering this week: The IT Professional's role in the Responsible use of AI, Azure Automanage for VMs, Move resources to another region with Azure Resource Mover, New Windows Virtual Desktop Capabilities, Hybrid Cloud announcements surrounding Azure Arc and Azure Stack as well as the Microsoft Learn module of the week.How to In-Place Upgrade Windows Server 2008 R2 to Windows Server 2019
As you know the Windows Server 2008 and Windows Server 2008 R2 are out of support on January 14th, 2020. Customer will need to upgrade their Windows Server 2008 and Windows Server 2008 R2 to a newer version of Windows Server or migrate these servers to Microsoft Azure.Step-By-Step: Migrating The Active Directory Certificate Service From Windows Server 2008 R2 to 2019
End of support for Windows Server 2008 R2 has been slated by Microsoft for January 14th 2020. Said announcement increased interest in a previous post detailing steps on Active Directory Certificate Service migration from server versions older than 2008 R2. Many subscribers of ITOpsTalk.com have reached out asking for an update of the steps to reflect Active Directory Certificate Service migration from 2008 R2 to 2016 / 2019 and of course our team is happy to oblige.
Idle time out GPO for Remote Desktop Services sessions not working in Windows 2019 servers
I have configured GPO to Set time limit for active but idle Remote Desktop Services sessions. Policy has been set to disconnect sessions which are idle for more than 3 hours. But I am getting warning after 30 minutes itself. This GPO has been applied at OU level. Issue occurs only with Windows 2019 servers. Session time limits on Windows 2016 servers which are in the same OU works well. I ran gpresult /h on the affected servers. I could see session time limit policy is applied properly still sessions are getting disconnected after 30 minutes. Anyone came across this issue? Please assist me
