Tramp

Any other suggestions before I start a fresh installation? Thanks

Hi, Not a stupid question at all, it's one I asked myself, 32bit W7 prof is the one I've just tried sysprepping without using the unattend file which should take that out of the equation, at 47% Access Denied again. So far I have been able to find the f8 option for PXE boot, am about to look again. Thanks

Yes, plenty of space on both local drive (s) and server)

Thanks, I'll have a look when I'm in school and get back to you.

Thanks for your replies , Free780 and TheScarfedOne. I assume it's during file creation rather than transfer as the same problem occurs whether saving just to local drive or to drive and server. When I remove the 'Access Denied' message it goes straight into windows if I don't catch it quickly enough. That was one reason I ended up using another HD with a freshly installed Acronis image to make sure that the partial boot into windows hadn't corrupted the sysprepped image. I'm using the PXE boot to capture, how can I enable the f8 tools in this situation? So far I have only found one reference to this sort of problem and no reason was identified- WDS Capture "Access Permission" Problem Thanks

Just via WDS- capture image using x86 wim.

Hi, Using Server 2008R2 I have been unable to capture a Windows 7 Pro image- fails at 47% with message 'Access Denied' The Windows 7 image is set up and I have copied it both pre-sysprepped and sysprepped using Acronis. The source machine is an HP8200 i5 desktop with 4GB memory, the server is 2008r2 with 12GB memory The local drives used to capture were 80GB and 250GB SATA, connected to the same motherboard as the source drive. The capture fails at 47% whether saving direct to a local disk or to local disk + server. PXE boots up fine and using the wizard I go through the steps to capture- it then proceeds happily on its way until the message Access Denied comes up at 47%. This is a physical drive build not virtual, server permission is via a domain admin account. I have tried to capture 6 times and used three different hard drives as source, two as local target. Factors I've considered- Bad sectors?- probably not, 2 target and 3 sources drives used (re-imaged each time with the sysprepped image) Permissions?- server accessed via domain admin account, what about local drive should the wizard ask for an account, if so a local machine account? Uninstall file?- isn't this only brought into play on installation of a created image Something in the build?- what and how can it be tracked down- I can't see any obvious log file of how the image creation is going? Any suggestions would be much appreciated, it's driving me up the wall! Thanks