RDP server not works after osdtool

[Sphinx114]

RDP server can't start after removing all drivers. Port 3389 not listening. Advices from the internet for start RDP server do not help. This bug exists in latest versions osdtool (e.g. 4.11). Currently i use version 4.00, because it works fine, RDP properly works. I'm use osdtool in IFL GUI. Target operation system: Win 7 SP1 prof russian 32bit + all updates.

[TeraByte Support]

probably the best this is for you to run osdtool 4.00 - clear drivers - then
use the tbexplo.tbs script to copy the SYSTEM file from the
Windows\System32\Config folder to another location as a new name
(system.400). Then run 4.11 and restore the backup when it asks, then
clear drivers, use tbexplor.tbs again and SYSTEM file from the
Windows\System32\Config folder to another location as a new name
(system.411).

Zip up both those files and email them to support directly indicating the
issue.



"Sphinx114" wrote in message news:8724@public.tbosdt...

RDP server can't start after removing all drivers. Port 3389 not listening.
Advices from the internet for start RDP server do not help. This bug exists
in latest versions osdtool (e.g. 4.11). Currently i use version 4.00,
because it works fine, RDP properly works. I'm use osdtool in IFL GUI.
Target operation system: Win 7 SP1 prof russian 32bit + all updates.

[Sphinx114]

files sent

[Sphinx114]

Problem solved! The version osdtool that was sent to my mail works fine.

[jonandy]

I think I see what is going on now. Somehow, Disk 0 and Disk 1 flip-flopped identities...so that the script was directing that the backup drive be imaged. And that makes it large. I have an eSATA backup, and to be recognized, it has to be seen during bootup. I just need to find a reliable way to make sure it doesn't horn in in the Disk 0 identification.

[fat_kid]

Hi,
I have had the exact same problem with RDP breaking after running osdtool to remove drivers.
Just wondering if there is any way to fix this, other than reverting to the original image and re-running the device removal with the new version?
I've been running on new hardware for a couple of weeks now before I noticed the RDP issue.

Any help with fixing RDP would be appreciated, otherwise merging changes is going to be a mission.

[TeraByte Support]

Just use the latest version of TBOSDT and scripts. If you did it recently,
let it restore the backup and just run it again.



"fat_kid" wrote in message news:9438@public.tbosdt...

Hi,
I have had the exact same problem with RDP breaking after running osdtool to
remove drivers.
Just wondering if there is any way to fix this, other than reverting to the
original image and re-running the device removal with the new version?
I've been running on new hardware for a couple of weeks now before I noticed
the RDP issue.

Any help with fixing RDP would be appreciated, otherwise merging changes is
going to be a mission.