-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Installation over RDP fails with cryptic errors #1050
Comments
So it finished with errors, did you reboot and check that all was there? Can we have the logs please? to get logs:
|
I've rebooted, saw that indeed a lot of things have failed, and reran the wizard. The wizard noticed that the previous installation has failed, and did it all again. |
In case any of you are too lazy to download that, here you go: https://shares.asterisk.lol/share/AI18KUWj |
Hi - this is a known AME Wizard issue and will be fixed in the next AME Wizard release. To install Atlas currently, you would have to use an alternative to RDP or do it locally. |
@dark-penguin until this bug is fixed use https://github.com/rustdesk/rustdesk You can set it up to support direct LAN connections and it's as responsive if not more than RDP in my experience. |
Fainting, I've reinstalled it over and over again, only to find out that the issue was caused by RDP. Please clearly state on the homepage that installation via RDP is not supported! |
You can use the latest AME Wizard beta at https://t.me/+BNgSXRsy2-FmN2Qx, which fixes this issue. There should be a new stable AME Wizard release soon as well. Note that feedback is encouraged and that these betas might introduce other issues. |
Fixed in AME Wizard v0.7.5 |
Description
If you run AME Wizard over RDP, then it "Finishes with some errors". The errors say something about the user tokens and directories not existing, but not even I could guess that it means "installation over RDP is not supported".
While it's not a major use case, it may be quite common for some sysadmins like me who often install things remotely. It would be nice to try acquiring that user token before installation, and warning that installation over RDP is not supported if that fails.
To clarify, the problem I see here is not that installation over RDP is not supported - it's that I was confused for quite some time while trying to figure out why did it fail, even though it just worked fine on my test VM.
Steps to reproduce
Expected behavior
Before installation, there should be a warning that installing Atlas OS over RDP will fail.
Actual behavior
"Installation finished with some errors <error log>"
Atlas Edition
Atlas for Windows 10 22H2
Desktop information
i7-3820
32GB RAM
Noname (Vaseky) NVMe SSD, 240 GB
AMD Radeon R9 290
Additional content
No response
The text was updated successfully, but these errors were encountered: