There is no connection made to your personal device itself and hence no remote access is possible to any of the content displayed or held on your personal device. The use of CRD does not create a risk of exposure of any content on your personal device - the CRD connection is made directly to your remote DICE desktop session, and your DICE account.

Bear in mind that holding any content other than specifically work related content in your DICE account is against the Computing Regulations that you will have agreed to on registration. The use of CRD creates a potential risk of exposure of any personal content you hold within your DICE account. Discuss this with your demonstrator or course organiser. Microsoft Teams for example supports screen sharing, and sometimes offers remote control. If, as a student, you are working jointly and you do not wish to use CRD, then the group should look for an alternative. While clearly advantageous, the use of CRD is entirely a personal choice for any student. Use on anything other than a remote DICE desktop session is not a permitted use of CRD.

Use for anything other than described here is not a permitted use. Only DICE remote desktopĪccess and control of your remote DICE desktop session is the only permitted use of CRD.Īccess and control of your personal device is not a permitted use of CRD. (Don't confuse it with our similarly named ⇒ remote desktop service.) We're using it to help facilitate group lab work, to help give participants some interaction and support when we can't provide these sessions face to face on campus.ĬRD will allow a demonstrator or another student to access and control your remote DICE desktop session, in order to provide instructional support or to allow joint working. Google's Chrome Remote Desktop (or 'CRD') is a way of sharing control of your remote DICE desktop session with somebody else.

Chrome remote desktop