Windows 10: What is the tsclient computer in my Network window in Windows 10?

My Hyper-V vms show a tsclient computer in the Network view. I know tsclinet relates to remote desktop, but what can I do with the tsclient computer that appears in the Network window? Is it available for any user activity?





:)

 

Several mapped drives - cann't disconnect

In fact, I did

net use * /delete

then I discovered that an issue I thing with remote connections as follows

You have these remote connections:

\\TSCLIENT\C

\\TSCLIENT\E

\\TSCLIENT\H

\\TSCLIENT\S

\\TSCLIENT\T

\\TSCLIENT\W

Continuing will cancel the connections.

Do you want to continue this operation? (Y/N) [N]: Y

Investigating the tool I use to RDP "MobaXterm", I discovered that 1 option "Redirect Drives" was checked.

However, after the successful delete operation, drives were not removed, I needed to uncheck this option in Moba

Thanks for your help

 

Computer in my network place is not accessible in Windows 10

Lets get the facts straight. It is all Windows 10 which is the problem. Since day one of windows 10, there has been issues with showing computers in the NETWORK folder. These are the icons to access other computers on your network to share PUBLIC files
and folders. Setting up the shared setting as mentioned is what to do. But I would in "PRIVATE", turn on network discovery, turn on file and printer sharing, and allow windows to manage home group. Then in "GUEST OR PUBLIC" select turn on network discovery
and turn on file and printer sharing. Then in "ALL NETWORKS", turn on sharing for anybody, use 128bit, and turn OFF password protected sharing. "THESE SETTING ARE FOR PUBLIC SHARING AND NOT HOME GROUP SETTINGS. HOME GROUP SETTING are after you enter the password
and join home group and then there are settings for sharing out of your personal folders of music, docs, videos, pics and printers. Also Home group is for media device sharing and there is settings for those too in HOME GROUP.

Back to the issue of Public sharing between Computers. Windows 7 and 10 will connect no problem. But since the issue on 10 is NOT showing the computers in the NETWORK folder to connect. Then you can do this. right click on your desktop and select in menu,
"new - shortcut". In the wizard, under "TYPE LOCATION OF THE ITEM" TYPE IN THIS>> \\(Name of the other computer on your network) >>
L: \\Name. Note: Make sure the name of other computer is exact. CLICK NEXT. When it finds the other computer on your network it will ask you to keep or change name.
Keep the same name and click on FINISH. Now click on the icon on your desktop, it should open up other computer and show PUBLIC ICON. click on that and you should be accessing the other computers PUBLIC folder. Do the same for other computer by creating shortcut
to access the other one from other computer.

It pisses me off windows 10 has this missing computer icons in the network folder. I had it fixed twice on my main system but after windows 10 cumulative updates or other updates, it becomes f..ked up again and no icons, so I did this to resolve the issue
until Microsoft pulls their heads out of their "you know what" and fixes this issue. Remember. joining the home group is for sharing your personal folders and personal media devices and not Public folders. Network sharing is for public folders by default in
XP, Vista, 7, 8, and 10

After doing this, it would be a good idea to restart your computer, then reboot your modem and restart again to set the network.

 

Tsclient is an important part of Hyper-V networking. When your VM is in normal mode it's needed although you cannot access it directly:





In enhanced mode when local resources have been enabled it offers access to local drives you have selected:



In this you can access your host drives through Tsclient:





However, this is of course not necessary because Tsclient also displays the enabled host drives (highlighted) directly in VM's This PC:




Whatever you do, do not touch the TSclient! It is needed and required to assure networking between your host and its virtual machines works as expected.