Win7PE vs Windows ThinPC for RDP client
Posted 30 December 2011 - 08:54 AM
I imagine I can just build a Win7PE for this, although his old PC is a P3 933Mhz with 512MB, so I'm not certain it will work! If it will though, what are the supposed advantages of the what appears to be much larger Windows ThinPC, compared to Win7PE for a RDP client platform?
Posted 30 December 2011 - 02:37 PM
A good idea though might be first installing WES7 onto a VHD, and then copying the VHD image file to your brother's HD, adding Win7 boot environment to the host drive, and booting WES7 natively from the VHD. This way you don't have to mod the existing OS install if any, and MBR changes can easily be reverted. Just follow Test New OS Releases on VHD Tutorial.
- doveman likes this
Posted 30 December 2011 - 06:41 PM
I guess I should just try and build a suitable PE (all I need it to do is RDP (and maybe run IE or Portable Opera or Portable Chrome occasionally to quickly check something without having to boot/resume the RDP server) to see how small I can get it, and by then maybe someone will have built a WES7 and we can compare sizes
Posted 30 December 2011 - 06:47 PM
I didn't compare sizes either because it wasn't important to me, since WES7 VHD booted from an old Vaio laptop as filedisk pretty fast (no need to boot into RAM), and that's all I needed to get past bothering with WinPE scripts. Every user or developer is free to make their own choices... and not only with WinPE...
However, for a developer it makes sense to envision future demand and diversify product portfolio to fit the new tech. Otherwise one may eventually end up downloading his own scripts and apps...due to fallen demand. Not to mention empty Paypal account...
Posted 30 December 2011 - 07:30 PM
Obviously with a RDP client station one wants it to boot quite quickly as well, so keeping the size down will help it compete with Thinstation in that respect.
Posted 30 December 2011 - 08:16 PM
Posted 20 March 2012 - 01:30 AM
There's so many options I'm a bit overwhelmed and whilst I'll probably experiment with them when I've got more time, I'm a bit under pressure to just get this done.
Building WES7 (seems to be the most complicated because I've got to learn all about using the toolkit)
Installing W7 to a Virtualbox, updating and stripping it down and then copy the files to the CF card. Then boot the destination PC with that and let it install the necessary drivers (I'm not even sure this will work though!)
Do this http://reboot.pro/14...133#entry131133
Do this http://www.911cd.net...showtopic=23931
Do this http://reboot.pro/9830/
So if anyone can advise me which approach to take, that would help a lot and save me wasting my time trying out the inappropriate (for this project) methods. I'm guessing it's probably not necessary to bother with VHD as I can have the Win7 RDP client and thinstation on the CF card together and choose which to boot with grub4dos, but if it's better to use a VHD I'll just do that. I'll probably stick an nlite XP on there as well (with a write filter to protect the CF) to use in case the Win7 server goes down, and various portable apps that can be shared between Win7 and XP.
Posted 22 March 2012 - 08:51 PM
Posted 31 March 2012 - 04:19 PM
I cheated & used Wyse ready image
Just re-created it from BRB0_0827_4096 in Workstation 8:
1. restore the par1.img with physdiskwrite to VM with IDE HD
2. create image of the restored partition with Ghost32 to image
3. clean IDE HD with diskpart
4. create primary partition with diskpart leaving at least 100 Mb of free space
5. Restore Ghost image BACK onto the newly created partition
6. make the restored partition active
6. bootsect /nt60 c:
7. mount registry hive c:windowssystem32configsystem & stop 4 wyse services
8. rename few drivers in c:windowssystem32drivers
9. edit unattened in c:windowspanther (you can change administrator password here)
10. wait till machine build itself
11. reboot to WinPE again & disable autoadmin logon in HKLMMicrosoftWindows NTCurrentVersionWinlogon & any policies you want
12. login as administrator & (if you want) disable the filter (shortcuts are on the desktop)
13. uninstall any unrelated software (but for this you need to adjust any references to Z: in registry)
It does what I need it to do, I am sure it could do even more
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users