We have this happening somewhat often,

The issue is your TS is doing stuff that requires a download (from the image, 
running MDT Toolkit Scripts) before wiping the disk. But for whatever reason, 
the disk is not yet writable/initialized.

We see this anytime we create a new VM in VMWare (we too use MDT and another 
bunch of scripts prior to wiping the disk, to ensure we don’t inadvertently 
wipe a disk) prior to the format disk step, As well as when reimaging encrypted 
disks (McAfee and Pointsec).

It happens because the disk is not initialized/not writable, so the TS doesn’t 
have a place to download the files, hence the error you see.

I’ve seen places say that setting the “Download Location” TS variable to X: 
works, but that opens up a whole slew of other edge cases that I didn’t enjoy 
trying to fix when I tried it out.

What worked for us (while not perfect) was to include a batch file with the 
appropriate DISKPART commands called Wipedisk.cmd in the WinPE image itself. We 
then leave F8 prompt enabled, and techs can simply F8 -> “Wipedisk” and then 
close it and continue.

An easy way to verify if this is indeed your issue, open up the cmd prompt in 
PE, and see if you can cd c: and/or create a file on the c: drive. If you 
can’t, you will get that, or the related 0x800070057 error, depending on what 
you are trying to do before the TS formats the disk.


Jason Lang

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kevin Johnston
Sent: Wednesday, November 12, 2014 8:36 AM
To: '[email protected]'
Subject: RE: [mssms] Issue with OSD from a DP


Password Alert! This message may contain a request for your password. NEVER 
SEND OR RESPOND TO E-MAIL REQUESTS FOR YOUR PASSWORD. For questions about this 
alert, please contact the ITS Service Desk at 585-475-4357, or 
[email protected]<mailto:[email protected]>.
So last night in our Australian office I had the same setup.

I had the same issue, so I then did the diskpart clean and then reimaged and 
everything worked fine.

The only issue I had outside of this was that the machine did not join to the 
domain for some reason.

What I do not understand is why for these machines it does not work, but it 
does work at HQ. It is the same model of machine, except the hdd is a different 
manufacture, that is all.

I am trying to come up with a zti solution in these countries, but having to 
manually run diskpart before each deployment defeats that purpose.

Is there anything else I can look at to see why this is failing on DP’s.

Thanks,

Kevin


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Tuesday, November 11, 2014 3:30 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Issue with OSD from a DP

Tried a DISKPART CLEAN on it?

On 10 Nov 2014, at 13:17, Kevin Johnston 
<[email protected]<mailto:[email protected]>> wrote:
I have a DP in the UK. I have everything configured like I do here for my 
deployments. I can PXE boot, I enter the TS password, then it loads some files 
and then I get the following:

<image002.png>

Looking at the SMSTSLog on the machine, I see that there are errors related to 
“C:\ not bootable, X: is not fixed drive” but that is all.

Because I am using vPro and VNC to see the machine, I can’t copy the log file 
here.

This is a brand new out of the box machine. When I do diskpart I see the OS as 
being letter D:
When I boot into the machine (Dell) the OS is actually C:
So I thought this may have something to do with it, but since this does not 
load the UDI wizard to complete I don’t think this is an issue as the drive 
will get wiped as part of the TS.

This same machine works without issue here in the local office, so I am not 
sure how to fix this issue. I was hoping it would load into the UDI wizard, but 
it never makes it there.


Thanks,

Kevin Johnston




Reply via email to