I'm starting to think that the success of the boot.wim depends on what packages are installed. Of the available ones, it looks like the ones that EdT uses creates a WMI too large for ghost, which wants it below ~120MB.
Looking at the listing of cabs, which ones are necessary for a succesful WinPE environment for the ghost client/server automated interaction?
WinPE-HTA
Support for HTML applications.
With this package you can create applications with a graphical user interface by using the Internet Explorer script engine and HTML services.
WinPE-MDAC
Support for Microsoft Data Access Component (MDAC).
With this package you can query a SQL server with Active Directory Objects (ADO). With this package you can, for example, dynamically build an Unattend.xml answer file from unique system information.
WinPE-PPPoE
Support for Point-to-Point Protocol over Ethernet (PPPoE).
WinPE-Setup-Embedded
Parent package for setup-related files for Standard 7.
You must add this package before adding the WinPE-Setup-Embedded-Standard package.
WinPE-Setup-Embedded-Standard
Child package that contains EULA files that appear in Image Builder Wizard, and background bitmap files and image resource DLLs for setup of Standard 7.
To add this package you must first add the WinPE-Setup-Embedded package.
WinPE-Scripting
Support for Windows Script Host (WSH), with which you can process batch files by using WSH script objects.
WinPE-WMI
Support for Windows Management Instrumentation (WMI).
Provides a subset of WMI providers for minimal system diagnostics.
WinPE-WDS-Tools
Feature package for Windows Deployment Services tools.