registry | KC's Blog https://www.kjctech.net Tue, 24 Jan 2023 18:21:07 +0000 en-US hourly 1 https://i0.wp.com/www.kjctech.net/wp-content/uploads/2016/12/cropped-KC-Logo.png?fit=32%2C32&ssl=1 registry | KC's Blog https://www.kjctech.net 32 32 24634607 How to make an old school SUBST virtual drive persistent https://www.kjctech.net/how-to-make-an-old-school-subst-virtual-drive-persistent/?utm_source=rss&utm_medium=rss&utm_campaign=how-to-make-an-old-school-subst-virtual-drive-persistent https://www.kjctech.net/how-to-make-an-old-school-subst-virtual-drive-persistent/#comments Mon, 19 Apr 2010 06:36:22 +0000 http://www.kjctech.net/2010/04/18/how-to-make-an-old-school-subst-virtual-drive-persistent/ If you have touched DOS before, you might still remember what this old school command subst is all about. It’s a command used for substituting local paths on physical and logical drives, known as virtual drives. For example, if you want to have a logical drive P: mapped to a local folder on your computer, say c:\temp, you can simply […]

The post How to make an old school SUBST virtual drive persistent first appeared on KC's Blog.]]> If you have touched DOS before, you might still remember what this old school command subst is all about. It’s a command used for substituting local paths on physical and logical drives, known as virtual drives. For example, if you want to have a logical drive P: mapped to a local folder on your computer, say c:\temp, you can simply use the following command to make it.

subst p: c:\temp

It’s very useful when you test out the application that uses a network mapped drive so you can have a complete test environment right on your local machine.

However, any subst’d virtual drivers are not persistent. You have to Subst them again once the computer is rebooted. Making a batch file that includes subst commands in it and placing it in startup folder doesn’t seem to be working for something.

If you want to make them like a permanent driver that doesn’t disappear, you can either

Create a new registry entry “string value” in the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices

The name of the entry should be “X:” where X is the drive letter you want to make.

And the value of the entry should be the local path in the form of: \??\c:\path. Make sure reboot once to make the change take effect.

Or, if you are not comfortable with playing around the registry keys, you can also use a tool called psubst with an option /p as well.

The post How to make an old school SUBST virtual drive persistent first appeared on KC's Blog.]]> https://www.kjctech.net/how-to-make-an-old-school-subst-virtual-drive-persistent/feed/ 11 1141 The remote computer disconnected the session because of an error in the licensing protocol https://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/?utm_source=rss&utm_medium=rss&utm_campaign=the-remote-computer-disconnected-the-session-because-of-an-error https://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/#comments Fri, 12 Jun 2009 21:50:02 +0000 http://kjctech.net/blog/archive/2009/06/12/the-remote-computer-disconnected-the-session-because-of-an-error.aspx One remote user from work called me the other day saying her remote desktop client stopped working because of “there are no terminal server client access licenses available for this computer”. Well, that’s easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and happily told her you can try it again now. […]

The post The remote computer disconnected the session because of an error in the licensing protocol first appeared on KC's Blog.]]> image

One remote user from work called me the other day saying her remote desktop client stopped working because of “there are no terminal server client access licenses available for this computer”. Well, that’s easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and happily told her you can try it again now. But surprisingly, she replied a few seconds later saying no, still didn’t work. But this time the error message was different:

The remote computer disconnected the session because of an error in the licensing protocol

It’s surprising because having been using remote desktop client for ages this is the first time I saw the error message like this. Out of luck after a few checking here and there, I went to Google for help. Nothing had worked until I was landed to this Microsoft KB, Removing Terminal Server licenses from an RDP client. At the very bottom of this KB, it mentions:

If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message:

An Error occured in the licensing protocol.

And suggests that to resolve this problem, right-click the Remote Desktop Connection icon, and then click Run as Administrator. 

Bingo!! That was it. Did I mention that this problem was actually occurred on a Vista computer above? And it only happens on Vista or later OSs because:

By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.

Related Posts:

The post The remote computer disconnected the session because of an error in the licensing protocol first appeared on KC's Blog.]]> https://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/feed/ 24 918