Windows 7 with mutiple RDP sessions

[paristotle]

I just signed a new client. Their last tech has them using a Windows 7 pro desktop as a file server. I thought this was bad enough, but then I noticed that there were concurrent RDP sessions going on this 'server'. Obviously this is hacked... so now I need to figure out what to do with this.
Until I get them to replace it I have to support it. Does anyone know if updates will break this?

 

[Moltuae]

Does anyone know if updates will break this?

I can confirm they don't.

I'm presently maintaining a similar setup, until the customer's budget allows me to migrate them away from it. Been like that for a while now and the computer in question is maintained no differently from any other, in that all updates are installed as they become available.

 

[cyabro]

There is software available, that you can buy, that will do this for you.
One used to be called XPUnlimited but as since changed to AADS and there are others as well.
Have a look under Administrator Tools in the Control Panel and see if you can see anything in there as that was where the above two programs put their shortcuts.

 

[YeOldeStonecat]

. Does anyone know if updates will break this?

It depends on what was done to give this feature. Back a few years ago (Win2K or XP days)...there was some "hack" to replace a certain DLL file, like termsrv.dll or something like that, with one from Windows server. Installing service packs would replace that...and you'd have to do that "hack" again.

I'm not sure about if that's still true with Windows 7....and I know there are 3rd party software packages which also turn a desktop OS into a "terminal server"...so I'd wager updates won't break them. I don't know how "legit" those 3rd party software packages are. Microsoft licenses a desktop operating system for just 1x console session at a time...either local, or remote...not both, and not multiple. As to how legit 3rd party software is to change that...doesn't interest me, it's a pizza tech el cheapo approach IMO.

So to answer your question...need more info, like how was this change done?

 

[doubleohalex]

It depends on what was done to give this feature. Back a few years ago (Win2K or XP days)...there was some "hack" to replace a certain DLL file, like termsrv.dll or something like that, with one from Windows server. Installing service packs would replace that...and you'd have to do that "hack" again.

I'm not sure about if that's still true with Windows 7....and I know there are 3rd party software packages which also turn a desktop OS into a "terminal server"...so I'd wager updates won't break them. I don't know how "legit" those 3rd party software packages are. Microsoft licenses a desktop operating system for just 1x console session at a time...either local, or remote...not both, and not multiple. As to how legit 3rd party software is to change that...doesn't interest me, it's a pizza tech el cheapo approach IMO.

So to answer your question...need more info, like how was this change done?

If I remember correctly, its pretty similar to the XP "hack". Replace the DLL and modify some registry keys. Updates won't break it and it can be maintained as normal without any real risk of harming the system.

They do have an executable to automate the process now too.

 

[paristotle]

I remembered hearing about the XP hack, but that was some time ago. I googled a little and found that the same approach is available in 7. Anyway I can't wait to get rid of it. It's not made for that is it responds in bizarre ways. For example when I installed AV on it file sharing slowed to a crawl. Not sure why CPU, RAM resources we not taxed but it was painfully slow until I removed the AV....thanks for your input, everyone.

 

[YeOldeStonecat]

For example when I installed AV on it file sharing slowed to a crawl. Not sure why CPU, RAM resources we not taxed but it was painfully slow until I removed the AV....thanks for your input, everyone.

Yeah Windows desktop OS is not designed to handle concurrent console sessions....and of course antivirus should not be desktop grade antivirus for a terminal server....and there are certain ways programs are correctly installed on terminal server. So when you get outside of a supported environment..."anything goes"...

 

[paristotle]

Yeah Windows desktop OS is not designed to handle concurrent console sessions....and of course antivirus should not be desktop grade antivirus for a terminal server....and there are certain ways programs are correctly installed on terminal server. So when you get outside of a supported environment..."anything goes"...

Yup. I always files these customer "options" in the category "save a nickle to spend a dollar".

 

[YeOldeStonecat]

Yup. I always files these customer "options" in the category "save a nickle to spend a dollar".

LOL...well said!