Hey Paul,
Thanks for the reply.
So far this only seems to be an issue in our Cali offices. what I do know there is a Secondary Site server in LA, but what I dont know is the setup for all of the remote offices(bandwith, etc...).
depending on everyones work load because of the holiday next week not sure if we can make it happen, but the plan is to have another tech go out to the site and image a machine or two. So I'm waiting to find out about hubs, ports, etc... Also not sure if they have a license for VMware to run that, but we do have plenty of physical machines. Another thing that I dont know at this exact moment is if this is a new problem for this tech or if he has alway experienced this issue. I know the tech contacted me a few weeks back because the cert on our boot media had expired. I provided him with new boot media and a week later heard about this image time problem. I assume that it was not an issue before.
I did speak to another tech out in Cali and she is of the opionon that if you start a machine before 9am it will image in the normal time frame of about an hour, anytime after that it will take a bit longer. I checked on one of her machines and it took just under two hours. Its not great time, but 2 hours is more acceptable that the 3-8hour range.
I compared her 2 hour imaged machine to mine and on her machine it took 30 min to do the Partition Disk 0 step compared to my 10 min on one of my machines.
while I am waiting on info from other people and other sites, would you have any idea as to why or what to check to see why that step could be taking so long?