Best Practices

The \\k2000\petemp location is from the 3.4 KNIT before they integrated WIM imaging into the K2.  The file at \\k2000\peinst\wim is your captured WIM if you're using 3.5.

As for your 2nd request, are you sysprepping your image before capturing?  You said you installed with sysprep but I'm not clear on whether you sysprepped after the intial install and before you captured.

WIM imaging has been integrated and no longer requires KNIT. Deploy the WIM image by selecting Imaging > Deploy Image from within KBE. If your image is not in the available list, make sure you are in the same architecture KBE as the image itself (in other words, 32 bit images do not show as eligible deployments in the 64 bit KBE).

The BSOD is most likely due to hardware emulation and storage controller driver conflicts. Change the HDD emulation type in the system's BIOS to confirm that this is the case. Usually switching the type from SATA to IDE will fix the problem.

Thanks for your answer i have installed my system and all apps i need and i sysprep : c:\Windows\System32\sysprep>sysprep.exe /audit /generalize /shutdown - and i capture it a new win exists in folder peinst\Wim -> name C_C.wim in my k2000 -> tab -> deployments -> system images -> name of my capture : Win7x64masterwim (image type win AMD 64) do i need to apply preintall task, mid task or not? (i have read the knit 3.4 and i have prepared same task) or can i deploy directly thanks in advance