XPe PXE RDP minimum config?


A

amsps

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
 
Ad

Advertisements

G

Guest

Explorer Shell, thats the biggest part of your problem.

Try building an image without it and see how you go. Perhaps use the Task
Manager as a shell and have the RDP Client start on startup.

I like to include "Explorer Application" so I have a way of checking my files.
"Explorer Application" is separate from the "Explorer Shell". Leaving out
the shell is good sometimes, cause then people can't muck arond with the
local machine, unless they know how to move around without a shell.
 
K

KM

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
 
K

KM

I forgot to mention very important point here. When you are going by the image footprint reduction path you must accept the fact
that you will have to live with some errors in TD log (Dependency/Build) and perhaps some errors during FBA. This is necessary in
order to get the image optimized.

Just to prove the concept. I just did some quick optimizations for my VM based image (note: one real device the image would be
smaller). It is Minlogon image with fully capable RDP client running (tested). The current image size: uncompressed ~38Mb /
compressed ~28Mb.
(Plus you'd want to add 2-3 more Mb for the Terminal Services dynamic cache)

I must also point out here that due to extremely small size and minimum components included in the image the boot time is just 10+
seconds (again, this is on relatively slow VM). Compression here is perfectly acceptable and doesn't really eat much CPU or RAM.
In the image the RDP client is running as shell.
 
A

amsps

Hi.
I've tried to reduce the footprint but i couldn't. Can you help me? I
only want to start mstsc.exe (RDP) to connect to a domain controller
server.(I've added and extra registry data on target designer (HKLM
\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) running a batch file
a.bat:

:loop
start /wait c:\windows\system32\mstsc.exe /v:asterix
goto loop

What components can I delete from the list below? I've tried to delete
some components like Indexing Service, but when i check dependencies
they appear again. What do you suggest? Should I eliminate components
without checking dependencies? Probably, but it's an tedious task.
Please help me.
I want to reduce the footprint to a minimum.

Accessibility Core
Active Directory Service Interface (ADSI)
Active Template Library (ATL)
Administrator Account
Base Performance Counters
Basic TCP/IP Networking
Certificate Request Client & Certificate Autoenrollment
Certificate User Interface Services
Class Installer
Client / Server Runtime
Client for Microsoft Networks
CMD- Windows Command Processor
COM Base
COM+ Services
Command Shell
Common Control Libraries Version 5
Common Control Libraries 6
Common Control Libraries 6
Common Control Libraries Version XPSP2
Common File Dialogs
Compression and Expansion Tools
Core Networking
Credential Management User Interface
Cryptographic Network Services
Cryptographic Services Providers
DHCP Client Service
Direct memory access controller
DirectX Registry Info
Disk drive
Disk Management Basic Volume Runtime
Disk Management Dynamic Volume Runtime
Disk Management Services
Disk Performance Counters
Distributed Transaction Coordinator
Explorer Application
FAT/NTFS Common Format/Tools
FBA: Crypto
Filter Mime Messages for the Indexing Service
Font: Marlett
Fonts: EGA
Fonts: Fonts Microsoft_San_Serif
Fonts: Fonts Tahoma
Fonts: Fonts tahoma_bold
Fonts: vgaoem_fon
Format Common User Interface
Friendly Logon User Interface
GUI Based Format Common Libraries
Headless VGA Driver
I/O Error Log Messages
Intel ...
Intel Microcode Update Driver
Intel ...
Intel Protocol Network Address Translation
IP Security Services
ISAPNP Read Data Port
Kernel Mode Crypto Driver for RSA
Key Manager
Lightweight Directory Access Protocol
Logical Disk Manager
Microsoft Audio Compression Manager
Microsoft Foundation Class Library
Microsoft Line Services
Microsoft Visual C++ Run Time
Motherboard resources
MSFS
Msxml 3.1
Ndisuio Inf
Netbios Driver
NetIP6 Inf
Netlogon/Netjoin
Netmscli Inf
Netnb Inf
Netshell
Nettcpip Inf
Network Command Shell
Network Performance Counters
Netwzc Inf
NLS: Core Files
NLS: Locale Map IDs
NLS: Time Zones
NT Loader
NTFS
NTFS Format
NTFS Format Tools
Numeric Data Processor
PC/AT Enhanced PS/2 Keyboard
PCI Bus
Performance Counter Configuration
PnP (User-mode)
Portuguese Language Support
Primary IDE Channel
Programmable interrupt controller
Regional and Language Options
Removable Storage Service
Rich Edit Control Version 1.0
Rich Edit Control Version 3.0
Routing Common Files
RPC Local Support
RPC Server
S3 Trio64V+
Secondary IDE Channel
Security Accounts Manager Server Library
Session Manager
Shell Core Registry Data
Shell Explorer Registry Data
Shell Explorer Registry Data (Pro)
Shell Legacy Registry Data
Smart Card Cryptographic Service Providers
Smart card Subsystem
SMB Redirector
Standard PC
Standard Template Libraries
System Board
System CMOS
System Timer
TCP/IP Networking
TCP/IP Networking with Client For MS Networks
TCP/IP Version 6
Terminal Server Client
Terminal Server Remote Desktop
Terminal Services
Terminal Services Client ActiveX Core
Terminal Services Core
Terminal Services Runtime
Time Service Core
USB 2.0
USB Root Hub
User Interface Core
Visual C++ Runtime Libraries (Side X Side)
Visual C++ Runtime Libraries Policy XPSP2
Visual C++ Runtime Libraries XPSP2
Volume Manager
Volume Shadow Copy Service
Windows Firewall
Windows Logon
Windows NT MARTA Provider
Windows RAM Disk Driver
Windows Script Engines
Windows Security Configuration Editor Client Engine
Windows-based Terminal Professional
WinHTTP
Wireless Zero Configuration
WMI Core
WMI Correlation
WMI Filter
Workstation Service


Thanks, regards
Antonio

KM escreveu:
 
Ad

Advertisements

K

KM

You have to disable Auto-Dependency Resolving option in TD (Options dialog).

As I also mentioned you can easily eliminate CMD related components and then you will have to launch the RDP client as the Shell,
not using batch script or similar.

--
=========
Regards,
KM


Hi.
I've tried to reduce the footprint but i couldn't. Can you help me? I
only want to start mstsc.exe (RDP) to connect to a domain controller
server.(I've added and extra registry data on target designer (HKLM
\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) running a batch file
a.bat:

:loop
start /wait c:\windows\system32\mstsc.exe /v:asterix
goto loop

What components can I delete from the list below? I've tried to delete
some components like Indexing Service, but when i check dependencies
they appear again. What do you suggest? Should I eliminate components
without checking dependencies? Probably, but it's an tedious task.
Please help me.
I want to reduce the footprint to a minimum.

Accessibility Core
Active Directory Service Interface (ADSI)
Active Template Library (ATL)
Administrator Account
Base Performance Counters
Basic TCP/IP Networking
Certificate Request Client & Certificate Autoenrollment
Certificate User Interface Services
Class Installer
Client / Server Runtime
Client for Microsoft Networks
CMD- Windows Command Processor
COM Base
COM+ Services
Command Shell
Common Control Libraries Version 5
Common Control Libraries 6
Common Control Libraries 6
Common Control Libraries Version XPSP2
Common File Dialogs
Compression and Expansion Tools
Core Networking
Credential Management User Interface
Cryptographic Network Services
Cryptographic Services Providers
DHCP Client Service
Direct memory access controller
DirectX Registry Info
Disk drive
Disk Management Basic Volume Runtime
Disk Management Dynamic Volume Runtime
Disk Management Services
Disk Performance Counters
Distributed Transaction Coordinator
Explorer Application
FAT/NTFS Common Format/Tools
FBA: Crypto
Filter Mime Messages for the Indexing Service
Font: Marlett
Fonts: EGA
Fonts: Fonts Microsoft_San_Serif
Fonts: Fonts Tahoma
Fonts: Fonts tahoma_bold
Fonts: vgaoem_fon
Format Common User Interface
Friendly Logon User Interface
GUI Based Format Common Libraries
Headless VGA Driver
I/O Error Log Messages
Intel ...
Intel Microcode Update Driver
Intel ...
Intel Protocol Network Address Translation
IP Security Services
ISAPNP Read Data Port
Kernel Mode Crypto Driver for RSA
Key Manager
Lightweight Directory Access Protocol
Logical Disk Manager
Microsoft Audio Compression Manager
Microsoft Foundation Class Library
Microsoft Line Services
Microsoft Visual C++ Run Time
Motherboard resources
MSFS
Msxml 3.1
Ndisuio Inf
Netbios Driver
NetIP6 Inf
Netlogon/Netjoin
Netmscli Inf
Netnb Inf
Netshell
Nettcpip Inf
Network Command Shell
Network Performance Counters
Netwzc Inf
NLS: Core Files
NLS: Locale Map IDs
NLS: Time Zones
NT Loader
NTFS
NTFS Format
NTFS Format Tools
Numeric Data Processor
PC/AT Enhanced PS/2 Keyboard
PCI Bus
Performance Counter Configuration
PnP (User-mode)
Portuguese Language Support
Primary IDE Channel
Programmable interrupt controller
Regional and Language Options
Removable Storage Service
Rich Edit Control Version 1.0
Rich Edit Control Version 3.0
Routing Common Files
RPC Local Support
RPC Server
S3 Trio64V+
Secondary IDE Channel
Security Accounts Manager Server Library
Session Manager
Shell Core Registry Data
Shell Explorer Registry Data
Shell Explorer Registry Data (Pro)
Shell Legacy Registry Data
Smart Card Cryptographic Service Providers
Smart card Subsystem
SMB Redirector
Standard PC
Standard Template Libraries
System Board
System CMOS
System Timer
TCP/IP Networking
TCP/IP Networking with Client For MS Networks
TCP/IP Version 6
Terminal Server Client
Terminal Server Remote Desktop
Terminal Services
Terminal Services Client ActiveX Core
Terminal Services Core
Terminal Services Runtime
Time Service Core
USB 2.0
USB Root Hub
User Interface Core
Visual C++ Runtime Libraries (Side X Side)
Visual C++ Runtime Libraries Policy XPSP2
Visual C++ Runtime Libraries XPSP2
Volume Manager
Volume Shadow Copy Service
Windows Firewall
Windows Logon
Windows NT MARTA Provider
Windows RAM Disk Driver
Windows Script Engines
Windows Security Configuration Editor Client Engine
Windows-based Terminal Professional
WinHTTP
Wireless Zero Configuration
WMI Core
WMI Correlation
WMI Filter
Workstation Service


Thanks, regards
Antonio

KM escreveu:
 
Ad

Advertisements

V

V.V.Gatt

amsps -

I guess that the drive geometries are different on your CF and on the USB
Stick. I think that EWF relies somewhat on geometry, so your problem may
come from there

Good luck

- V.V.





You have to disable Auto-Dependency Resolving option in TD (Options
dialog).

As I also mentioned you can easily eliminate CMD related components and
then you will have to launch the RDP client as the Shell,
not using batch script or similar.

--
=========
Regards,
KM


Hi.
I've tried to reduce the footprint but i couldn't. Can you help me? I
only want to start mstsc.exe (RDP) to connect to a domain controller
server.(I've added and extra registry data on target designer (HKLM
\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) running a batch file
a.bat:

:loop
start /wait c:\windows\system32\mstsc.exe /v:asterix
goto loop

What components can I delete from the list below? I've tried to delete
some components like Indexing Service, but when i check dependencies
they appear again. What do you suggest? Should I eliminate components
without checking dependencies? Probably, but it's an tedious task.
Please help me.
I want to reduce the footprint to a minimum.

Accessibility Core
Active Directory Service Interface (ADSI)
Active Template Library (ATL)
Administrator Account
Base Performance Counters
Basic TCP/IP Networking
Certificate Request Client & Certificate Autoenrollment
Certificate User Interface Services
Class Installer
Client / Server Runtime
Client for Microsoft Networks
CMD- Windows Command Processor
COM Base
COM+ Services
Command Shell
Common Control Libraries Version 5
Common Control Libraries 6
Common Control Libraries 6
Common Control Libraries Version XPSP2
Common File Dialogs
Compression and Expansion Tools
Core Networking
Credential Management User Interface
Cryptographic Network Services
Cryptographic Services Providers
DHCP Client Service
Direct memory access controller
DirectX Registry Info
Disk drive
Disk Management Basic Volume Runtime
Disk Management Dynamic Volume Runtime
Disk Management Services
Disk Performance Counters
Distributed Transaction Coordinator
Explorer Application
FAT/NTFS Common Format/Tools
FBA: Crypto
Filter Mime Messages for the Indexing Service
Font: Marlett
Fonts: EGA
Fonts: Fonts Microsoft_San_Serif
Fonts: Fonts Tahoma
Fonts: Fonts tahoma_bold
Fonts: vgaoem_fon
Format Common User Interface
Friendly Logon User Interface
GUI Based Format Common Libraries
Headless VGA Driver
I/O Error Log Messages
Intel ...
Intel Microcode Update Driver
Intel ...
Intel Protocol Network Address Translation
IP Security Services
ISAPNP Read Data Port
Kernel Mode Crypto Driver for RSA
Key Manager
Lightweight Directory Access Protocol
Logical Disk Manager
Microsoft Audio Compression Manager
Microsoft Foundation Class Library
Microsoft Line Services
Microsoft Visual C++ Run Time
Motherboard resources
MSFS
Msxml 3.1
Ndisuio Inf
Netbios Driver
NetIP6 Inf
Netlogon/Netjoin
Netmscli Inf
Netnb Inf
Netshell
Nettcpip Inf
Network Command Shell
Network Performance Counters
Netwzc Inf
NLS: Core Files
NLS: Locale Map IDs
NLS: Time Zones
NT Loader
NTFS
NTFS Format
NTFS Format Tools
Numeric Data Processor
PC/AT Enhanced PS/2 Keyboard
PCI Bus
Performance Counter Configuration
PnP (User-mode)
Portuguese Language Support
Primary IDE Channel
Programmable interrupt controller
Regional and Language Options
Removable Storage Service
Rich Edit Control Version 1.0
Rich Edit Control Version 3.0
Routing Common Files
RPC Local Support
RPC Server
S3 Trio64V+
Secondary IDE Channel
Security Accounts Manager Server Library
Session Manager
Shell Core Registry Data
Shell Explorer Registry Data
Shell Explorer Registry Data (Pro)
Shell Legacy Registry Data
Smart Card Cryptographic Service Providers
Smart card Subsystem
SMB Redirector
Standard PC
Standard Template Libraries
System Board
System CMOS
System Timer
TCP/IP Networking
TCP/IP Networking with Client For MS Networks
TCP/IP Version 6
Terminal Server Client
Terminal Server Remote Desktop
Terminal Services
Terminal Services Client ActiveX Core
Terminal Services Core
Terminal Services Runtime
Time Service Core
USB 2.0
USB Root Hub
User Interface Core
Visual C++ Runtime Libraries (Side X Side)
Visual C++ Runtime Libraries Policy XPSP2
Visual C++ Runtime Libraries XPSP2
Volume Manager
Volume Shadow Copy Service
Windows Firewall
Windows Logon
Windows NT MARTA Provider
Windows RAM Disk Driver
Windows Script Engines
Windows Security Configuration Editor Client Engine
Windows-based Terminal Professional
WinHTTP
Wireless Zero Configuration
WMI Core
WMI Correlation
WMI Filter
Workstation Service


Thanks, regards
Antonio

KM escreveu:
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top