The RuDesktop 3.1 platform automates the transition from Windows to Linux by managing data migration, OS deployment, software installation, and domain integration. The process involves creating TAR archives and manifest.json files, which are stored on an SMB server and verified using SHA-256 checksums.
Successful migration requires a defined target configuration, including the specific OS release, architecture, and application set. RuDesktop supports Astra Linux, ALT Linux, and RED OS. Administrators must conduct pilot tests on hardware with diverse network adapters, storage, and peripherals to ensure compatibility.
Data migration does not include Windows registry or application settings. While RuDesktop can restore user folders, browser profiles may not function correctly in the new environment. Local Windows passwords are not preserved, and Cyrillic usernames are transliterated on ALT Linux and RED OS.
Network deployment relies on PXE and DHCP. Administrators must configure UEFI/BIOS settings, such as enabling IPv4 PXE support and disabling Fast Boot. The system requires specific credentials to join a domain, and common failure points include incorrect DNS settings, time synchronization issues, or hostname conflicts.
The platform tracks migration status via logs, allowing administrators to resume failed tasks or reset the process entirely. However, the software does not provide an automated rollback mechanism to Windows. Organizations must develop a separate recovery plan for critical roles and verify backups before starting the migration.
