Start a Conversation

Solved!

Go to Solution

1356

August 5th, 2021 07:00

ImageAssist Capture time is now 8+ hours

So I installed into my image the latest Image assist and my first capture was done in 3 hours and I thought that was excessive. Now the latest capture took 8 hours 15 minutes (roughly).
Has anyone else run into this issue with the new version? With any version?
If so, how did you remediate the issue?

August 5th, 2021 16:00

Root Cause.  Hyper-V had somehow reset the configuration for the VM to the defaults.
Set Memory to 8196 and CPU to 4 and the image capture now takes 7 1/2 minutes.  It takes longer to copy it to the network location than it does to capture now.

52 Posts

August 5th, 2021 08:00

Hello, normally long capture times are caused by the hardware on the host system. The number of processors should be 4, memory 2-4 gb on the VM. The host system must have at least that much resources left over too. The speed of host system and hard drive plays a big  part in how fast everything runs. When I use a newer workstation with NVME drives, the capture of a 10gb image takes about 15 minutes. Hope this helps.

August 5th, 2021 10:00

That's the thing, the previous version of ImageAssist, that's exactly how it worked.  This machine is wildly powerful (i9, 3.4Ghz, 32GB, Enterprise Class NVME), and the VM has 8GB ram and 4 cores.  This used t image in 20 minutes, now not so much.  I am going to troubleshoot it further to see if there is something I missed...

August 5th, 2021 16:00

Well, you put me on the right path.  Somehow, and I am hoping that it was a Windows update, but my VM was reset to 1 CPU and 1024 for ram.  Reset it to the correct settings and ImageAssist works again.
No one on the teams seems to know why/how it could reset like that.

No Events found!

Top