{"id":44910,"date":"2020-03-12T15:00:00","date_gmt":"2020-03-12T21:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=44910"},"modified":"2024-11-08T16:32:02","modified_gmt":"2024-11-08T21:32:02","slug":"active-directory-migration-utility","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/active-directory-migration-utility","title":{"rendered":"New Feature: Automated Migration from AD to JumpCloud"},"content":{"rendered":"\n

The process of migrating a Windows\u00ae<\/sup> workstation from Active Directory\u00ae<\/sup> (AD) to JumpCloud\u00ae<\/sup> just got easier. Our Solutions Architecture team is excited to announce the Active Directory Migration Utility<\/a> (ADMU), which automates the steps required to non-destructively convert a Windows domain account to a local user account and begin managing that account with JumpCloud.<\/p>\n\n\n\n

For organizations that have been apprehensive about uprooting their existing AD infrastructure, the ADMU presents a new opportunity to complete the transition to the cloud. This new utility minimizes the time commitment, manual labor, and risk involved with implementing JumpCloud as a replacement for AD.<\/p>\n\n\n\n

Using the ADMU, small-to-medium-sized enterprises can complete the transition to JumpCloud in anywhere from a few hours to a couple days. The result is a consolidated user and system management experience for admins, with end users barely noticing the change. Read on for more details about how the ADMU works and the tasks it automates.<\/p>\n\n\n\n

\n
\n \"JumpCloud\"\n <\/div>\n
\n

\n Breaking Up with Active Directory <\/p>\n

\n Don\u2019t let your directory hold you back. Learn why it\u2019s time to break up with AD. <\/p>\n <\/div>\n

\n Read Now<\/a>\n <\/div>\n<\/div>\n\n\n\n\n

Migrating Domain-Bound Systems to JumpCloud <\/h2>\n\n\n\n

JumpCloud achieves its system management capabilities using a lightweight system agent<\/a> that runs in the background and communicates with our core directory service. In order to avoid a situation where JumpCloud would compete with AD for authoritative control over a Windows machine, this agent won\u2019t run on systems that remain bound to an AD domain. Because of this, a full transition to JumpCloud from AD requires that domain accounts be converted to local user accounts, which can then be taken over by the JumpCloud agent. The ADMU automates this entire process: You start with a domain-bound system and end with a JumpCloud-managed system, with the original user account and its attributes intact.<\/p>\n\n\n\n

\"Diagram<\/figure>\n\n\n\n

Once a workstation has been migrated to JumpCloud, the user\u2019s login experience doesn\u2019t change, but the system now contacts your new cloud directory instead of AD as its authoritative source of truth for authentication. As an admin, you can now control the following functions remotely from JumpCloud\u2019s web console:<\/p>\n\n\n\n