Moriarty

Short Version: Is there a way to run setup with a mostly empty wim file against a volume that already contains a sysprep'd image? Longer Version: I need to run setup against a volume that already contains a sysprep'd installation. This is a niche use case where the boot drivers cannot be injected into the sysprep'd image. The first boot of the system is winpe. The winpe contains the network drivers needed for iscsi install. Notes/Ideas. This is for an iscsi project. There is no way to native boot the image as the hal and network boot drivers are written at the last part of the iscsi setup process. This project is working but the iscsi hosting per client is terribly inefficient. The server hosting the iscsi images ends up with a unique block volume per client. I would like each client to have it's own difference snapshot from the original sysprep'd volume. I can do that after I figure out how to sequence break the setup process.