Search results
We're excited to announce that our old student portal, TheLoop, has been replaced by our new and improved portal, MyRDP. The new portal is now live and offers enhanced features and a better user experience. For Current Students. You will log in with your RDP email address. For New Students.
- What is MyRDP (formerly The Loop)?
Effective July 2, 2024, MyRDP is the new RDP student portal,...
- What is MyRDP (formerly The Loop)?
12 cze 2020 · After setting a sign in frequency for conditional access users using the remote desktop client are having issues once their session times out. When the login screen pops up if they click their account it starts a loop of trying to login but it never allows them to input their credentials.
15 mar 2024 · The RDP connection logs allow RDS terminal server administrators to get information about which users logged on to the server when a specific RDP user logged on and ended up the session, and from which device (DNS name or IP address) the user logged on.
Effective July 2, 2024, MyRDP is the new RDP student portal, replacing The Loop. Log in to MyRDP. MyRDP is Red Deer Polytechnic's secure student portal. Access MyRDP at https://rdpolytech.ca/MyRDP. Red Deer Polytechnic students can use MyRDP to: Access Blackboard. Access RDP email. Register for classes.
26 sie 2015 · If you first do a Ctrl-Alt-Delete and choose "Switch user", after that you can remote access that computer. So, if we can do that remotely (get a Win 10 into that "Swtich user mode"), then we can also remote access it.
10 kwi 2022 · Logout and login with password (not PIN) at least once before RDP access. Once you login with a password once, you can re-enable the Hello sign-in if you want and still use the password with RDP. The fix is logging in once with the password.
12 cze 2022 · Every so often it gets into a state where client RDP connections hang after successful (NLA) authentication and just show the "Please Wait" with the indefinite looping dots UI forever. Once this happens, it will never resolve itself. Restarting Terminal Services does not fix it.
