kaleshire

Ok, this is very odd. Turns out the problem was I enter the MAK key into the Task Sequence, and recreating the Task Sequence without the MAK key fixed the issue. This is obviously not driver related as the smsts.log file lead me to believe. Any idea why the MAK key would cause problems like this?? If I can't create a task sequence with a MAK, then what's the point of asking for it?? Or is this just because it is a Build and Capture TS??

I'm trying to build a win 7 image in a Hyper-V vm and have created a boot image with the Hyper-V 6.1 drivers. Yet i still recieve the following error messages and it causes my task sequence to fail. I am running the task sequence through PXE boot process with the client VM setup using the Legacy Network Adapter. Any help would be greatly appreciated Thanks, Kevin smsts.log