drinking12many

We recently purchased another company and we need to migrate tons of machines to our image probably about 2000 this year at 13 sites. Our idea was to setup a laptop as a DS and attach a couple external 1TB drives to it as to back many of them up. Until we could get our permenant ds's setup and installed.

Problem occurs when PXE using both DOS and Winpe tries to map the shared folder on the external USB drive. It gets a memory error 8 on dos when trying to create the mapping then the image fails (because the drive map doesnt exist). Winpe just kicks out at the rdeploy failure.


We added the mapping to the Control panel options. We tried to create the drive as both an NTFS folder and as a stand alone drive letter. Same results. We werent sure if this was something that had to do with the way Windows internally sees the drives. We set it to use write caching thinking maybe that was it. Same result. The external drives do have eSata connection so that may be our next attemtp since at that it should see it no differently than an internal drive.

Anyone tried this or found a way around it? Last resort for us it to remove the drives from the enclosure and stick them in a desktop to ship to the locations. Any suggestions appreciated.

andykn

If you are using the external drives as backup for the old laptop images all I can suggest is a workaround whereby you image to the laptop internal drive then manually copy in Windows to the external drive afterwards. You caould maybe have a DS taks to do this as part of your migration Job.

drinking12many

thought of that but the internal drive is only about 60GB we only will be at each site 2 or 3 days so thats going to add alot of time. I have to find some way to do it directly. Ill probably try the esata card route next since they are dirt cheap.

drinking12many

SOLVED


“Not enough server storage is available to process this command.” error. » The PC Doctor’s blog

Set this reg key to 50 and rebooted. All is good. You would think that with large drives being the norm that this key would be set higher than 25 though it appears to be related to symantec AV that we use
. Maybe this will help someone in the future.