António,
You actually got very close (130Mb vs 128Mb?) to get the image that will fit on your target storage.
To have RDP working all your need is Terminal Services client stack. The Terminal Client surely has some heavy dependencies but
Explorer is not one of those. If you get rid of the Explorer Shell and Explorer app it will save you lots of space on the image
storage.
Moreover, you don't really need to have Winlogon in your image. The Terminal Server Client (RDP client) will work on Minlogon image
just fine (we talking about only client mode that is relevant to thin clients).
Basically I suggest you to start with an image that would include the following:
- Your hardware + HAL (only hardware you plan to support in the image)
- NTFS FS/File format. The latter is zero-size and may bring more components in as dependencies - however not actually required
if you don't plan to format disks in NTFS under XPe.
- Basic: NT Loader/Nt Detect/Windows API - GDI, Kernel, User, Advanced/Shell32 API/Ole32, OleAut32/Language
support/Winsock/Common Controls and dialogs/etc.
- Terminal Server Client
- Windows RAM Disk Driver (this is for Remote Boot support)
- Winlogon or Minlogon (big difference in image footprint and significant difference in boot time)
- CMD shell (useful for debugging purposes). You can remove this shell later when you are done with the image config, or replace
it with your own custom shell or the MSTSC.exe (RDP client) running as the shell.
If you do the above with Minlogon your image size can be less than 96Mb (uncompressed). With Winlogon it will grow by ~20-30Mb.
The given numbers are rough and I got those off some of my demo images I have here with RDP client working. The actual image size
may very dependent on some other system specs.
I often do more optimizations for image sizes in TD and post-FBA even if Minlogon used. Then 96Mb can go down to 64Mb or less (with
RDP still working).
Perhaps, the most sensitive area is the hardware support. If you use TAP output to create platform macro component please make sure
to disable there as many component dependencies as possible based on your final target device specs.
Often, the challenge is to get the networking to work properly in the MS Client network environment and not blow the image size with
lots of network components that have over-crossing dependency chains.
--
=========
Regards,
KM
Hi.
Does anyone have/know the minimum component configuration in Target
Designer to boot from PXE (Ramdisk) and run RDP to logon onto a
domain?
I've putted:
- Windows based Terminal Professional Template
- NTFS file system
- NTFS format
- Explorer Shell Interface
- NT Loader
- Windows RAM Disk Driver
but the image size is too big (130MB)!!!! even with NTFS compression.
How it's possible to have THIN CLIENTS with 130MB???? The thin clients
i should work on only have 128MB.
Thanks, greetings
António Soares
