[BUG] - Installation over RDP fails with cryptic errors

[dark-penguin]

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

1. Clean Windows 10 Pro installation, with nothing but drivers installed
2. In the Advanced System Properties, "Allow remote connections" - "from any client version"
3. Connect over RDP, launch AME Wizard, install as usual

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

[Ast3risk-ops]

So it finished with errors, did you reboot and check that all was there? Can we have the logs please?

---

to get logs:

1. Press Win + R to open the Run dialog in Windows
2. Type in %temp%\ame\logs\tioutput.txt and press enter (we also want AdminOutput.txt and ErrorLog.txt)
3. Scroll all the way down in the Notepad window, then take a screenshot or photo and send it here Put it on pastebin or something or send it here.

[dark-penguin]

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.
But that failed again, because I was still over RDP. With the same things in the logs. So, after a while, I've figured it out, reran the wizard locally, and then everything was installed properly.
3-09-2024-Atlas-AtlasOS.zip

[Ast3risk-ops]

In case any of you are too lazy to download that, here you go: https://shares.asterisk.lol/share/AI18KUWj

[he3als]

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.

[jonatino]

@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.

[hcocoa]

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.

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!

[he3als]

Please clearly state on the homepage that installation via RDP is not supported!