Search the Community

My company is going through an exercise to retire all of the SHA-1 certificates in the environment due to its upcoming EOL date by MSFT. One of the larger pools of devices using a SHA-1 cert are the end user devices, which use a self-signed SHA-1 certificate when using RDP. Most of the info i've found online so far only discuss how to force this cert to use SHA-1 with registry edits, but nothing about SHA-2. Has anyone gone through this exercise yet? If not you may need to soon. Looking for some technical pointers on how to accomplish this. Also, we currently use the self-signed cert that each device generates when connecting. If i force a new certificate from a domain CA, wouldn't I lose the ability to RDP from non-domain computers?

Hi My first post, and I have to say, I should visit the site more often for many reasons! Anyweb - Its been a while, you may remember me from Clan -DwD-, WasTed here! and prior to that HTAS! Anyway nice site plenty of good stuff going on here. My issue is this, I have a number of users connecting to virtual PC's from site G, this is over a BT Etherlink! The response time from this site is 180ms, but for the most part RDP to the machines is fine and usable. Connecting to site D for the Virtual PC's that connect to a SQL database at Site F, either Via a Web application Server hosted from Site F, or from the the Virtual PC site D. The two methods of connectivity to the application are different and the Fat client on the VM is the preferred method. The issue is that that a process that the process takes 3 minutes when connecting from site W, but up to 12 minutes when performing the same task from site G. Site G has a latency of 24ms to site D. Does the number of transactions multiplied by the latency have an impact on SQL transactions over RDP? My assumption was that only IO was communicated to and from the remote site to the VM. Any assistance would be appreciated. The VM's don't have local mapped drives, links or printers. I have taken Wireshark, can't make head nor tale of it! Regards Ted, AKA -DwD-WasTed, AKA Lee Barnes

I've seen a few blogs which have guides to add Remote Control support to Boot Images which I found would be quite useful. Especially if it's in the Boot Image rather than the Task Sequence so I would be able to RDP/VNC/DameWare etc to the client in WinPE. My main goal is for troubleshooting and for support during the build stage. I've seen the following posts but didn't have too much luck with getting it to work: http://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx http://blog.danovich.com.au/2011/12/27/dameware-remote-control-in-winpe/ http://depsharee.blogspot.com.au/2010/06/integrate-vnc-to-windows-pe.html Anyweb - it would be awesome if you could add a Step-by-Step for this topic as I'm sure a lot of admins would benefit from it. Thanks!