HI,
I'm trying capture Windows 7 VM ( 60 GB HDD , 1 vcpu, 4 GB RAM) But this take long to copy to network.
So if i add second hdd , can i capture to that ?
Will this cause any issues when deploying?
As
Technology Tips and News
HI,
I'm trying capture Windows 7 VM ( 60 GB HDD , 1 vcpu, 4 GB RAM) But this take long to copy to network.
So if i add second hdd , can i capture to that ?
Will this cause any issues when deploying?
As
You 'could' try adding the new HDD - sharing a folder as a network share and then capturing the that share..
I haven't tried this so I am not certain if it would work.
But worth a try!
Yours
Ed
You 'could' try adding the new HDD - sharing a folder as a network share and then capturing the that share..
I haven't tried this so I am not certain if it would work.
But worth a try!
Yours
Ed
Won't work, because the client is rebooted in WinPE for capturing so you won't see a share.I haven't tried this so I am not certain if it would work.
But worth a try!
You 'could' try adding the new HDD - sharing a folder as a network share and then capturing the that share..
I haven't tried this so I am not certain if it would work.
But worth a try!
Yours
Ed
I use this method to build and capture.
Works great and is (unfortunately) necessary in our draconian networking environment.
I have been for years. It w
Hi ,
You can capture to new HDD or capture in the same drive.
Yes, but I see where that could be an issue with ConfigMgr.
If the ConfigMgr build/capture allows you to enter alternate credentials for access to a share to capture an image, then that should work fine, but I haven't tested that.
My build/capture is done exclusively via MDT and imported into ConfigMgr.
I created a share on a second hard drive.
Via the MDT Deployment Wizard I, enter the UNC path to that share to capture the image to.
You only can capture to a network location.
Make sure you have rights to the location obviously.