Home → Questions →

Accessing Windows build worker via Remote Desktop

• Edit

servoz

21 Jun, 2023 01:26 PM

Hello,
When I access Windows build worker via Remote Desktop Protocol, I don't get the feeling that I'm in the right initialization state.

I put:

ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))

just at the end of the install part, so I should access the build with everything installed?

For example, we can see in the report Python 3.7.9, but in the RDP build, it is Python 3.11 ...
and we do pip install psutil before accessing the build, but if I do pip show psutil in the build, psutil doesn't seem to be installed ...
I must be missing something obvious ... ?
Thanks for your help.
Best.
Eric

1. 1 Posted by servoz on 23 Jun, 2023 04:14 PM

   

   Any idea ?

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 23 Jun, 2023 04:41 PM

   

   It's because when you RDP you don't have the same environment variables as inside your build. You could, theoretically, export all env variables before starting RDP and then import them when in RDP.

   • Edit

3. 3 Posted by servoz on 23 Jun, 2023 04:53 PM

   

   Thanks for the response.
   do you have any example on how to achieve this? I'm not sure I understand everything...

   • Edit

4. 4 Posted by servoz on 23 Jun, 2023 06:27 PM

   

   you've given me the way , thank you!

   i added in appveyor.yml:
   - cmd: SET >> allvariables.txt

   in RDP i done in Command Prompt:
   for /F %A in (allvariables.txt) do SET %A

   source

   This is working only on Command Prompt, not on PowerShell but it do the job (maybe a need to add this in the documentation ?)

   thanks again

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 23 Jun, 2023 06:49 PM

   

   Nice, we could suggest your approach to other users. Thanks for sharing it!

   • Edit

6. servoz closed this discussion on 26 Jun, 2023 12:34 PM.