I needed to RDP into my desktop at work to complete a couple of tasks while at home but didn’t have RDP enabled on it. I connected to our VPN and RDP’d into one of the servers. I then connected to my desktops registry via regedit’s “Connect Network Registry” feature.
The key I needed, fDenyTSConnection, was in HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server.
I changed the REG_DWORD value from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled), then remotely rebooted my PC, shutdown -m \\%PCNAME% -r.
After the reboot I was able to log in via the domain admin account. Once logged in I added my domain account to the users allowed to utilize remote desktop.
Last night I moved my PRTG virtual machine to my newly installed ESXi server. The move went well, but when I went to boot up the PRTG VM the service wouldn’t start. PRTG was nice enough to tell me that I had another copy of the service running on the network and even gave me the command to find the PC it was running on.
Turns out it was running on an old monitoring PC I had used years before that was still powered on. Since I still use it for a couple of other monitoring apps I couldn’t just turn it off. As a temp fix I stopped the service and set it to disabled. Now the PRTG VM started up and began collecting data once again.
As the PRTG uninstaller did not remove the PRTG service from the old monitoring PC I still needed a way to pitch it even though I had disabled it. A quick search turned up a couple of options, the easy way and the slightly more difficult way.
The Easy Way:
sc delete “service_name”
In my case the command was:
sc delete PRTGService
The Slightly More Difficult Way:
**Dislaimer: This process involves working in the Windows Registry. Before deleting any file please make a backup in case of borking your system.
Find the registry entry “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services”
Look for the service there and delete it.
We are in the process of installing a policy and procedure management application at the hospital. It has been setup so that users are not required to enter their user name and password to access the site, it is done via LDAP. To get the single-sign-on benefits of the LDAP look ups we needed to add the domain name to the list of trusted sites in IE. This can be done via Group Policy, but, my experiences with this group policy setting has been mixed. Each time I configured this Group Policy Object setting it turned off the option for the user to add sites. Each new site needed to be added by me in to the GPO. While I limit what my users can change and access I do not like getting calls for simple stuff like this. What was I to do?
We just got in a batch of HP desktops and so far they look to be a good investment. There isn’t much crap/bloat ware installed on it, so we can get them out the door to our users quite quickly. We have had only 1 minor issue with them. For each new user who logs in, the system sets the IE homepage to an HP/AOL site, not our corporate intranet. Instead of emailing our users instructing them on how to set the homepage back to our intranet site I logged into our Desktop Authority server and added a new option under the registry settings.