Since upgrading to MDT 2012 the "Format and Partition Disk" task assigns the letter V: to the disk
-
19 Mart 2012 Pazartesi 16:10
Hi,
When I was using MDT 2010 the "Format and Partition Disk" task would always delete all partitions on the single disk and create one partition, format it and assign it the drive letter C:, whether there was anything on the disk or just bare metal, and this worked well. Since upgrading to MDT 2012, this task always formats the drive as the letter V: and this causes problems with the rest of the build process. I noticed that this task runs ZTIDiskpart.wsf in the Scripts folder. Even when I ran this script in debug mode it would say that C: was free yet it still assigns the letter V:
I managed to create a work around for this by editing ZTIDiskpart.wsf and hard coded "ASSIGN LETTER=C" instead of letting the script decide which is the next free drive letter. I am a bit wary of keeping this solution in for the long term in case there a problems down the line. My question is what has changed between the MDT 2010 version and MDT 2012 version of ZTIDiskpart.wsf to cause this issue?
Many thanks
Tüm Yanıtlar
-
20 Mart 2012 Salı 00:35
The Driveletters assigned in WinPE are only temporary and can really be anything. If you still get V: after rebooting into Windows you should file a bug on connect. MDT 2012 is still in development and the more bugs they get, the better solution in the end.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
-
20 Mart 2012 Salı 09:43
Thanks Johan
I have a C:\drivers folder specified the in the OfflineServicing section of the unattend.xml so that I can have these drivers pre injected into the driver store file repository. On MDT 2010 these drivers were successfully injected, but on MDT 2012 they were not. I managed to find out what was going from the log file C:\Windows\Panther\cbs_unattend.log. I could see an error where it said that it could not find any drivers in C:\Drivers, this was because they were in V:\Drivers due to the driver letter V: being assigned to the disk. I could easily modify this path, but would rather find out the cause of this issue. I will raise it as a possible bug on connect.
Ian
-
21 Mart 2012 Çarşamba 23:58
Use only <Path>\Drivers</Path>
That's what MDT is doing...
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
-
31 Mayıs 2012 Perşembe 23:30
There seems to be a bug in the 2012 release version of ZTIDiskPart.wsf. If the OS is Windows 7 or greater, the last available drive letter is chosen for the partition. That is why v: is assigned.
To fix it change these lines, starting at around line 470 :
If Left(oEnvironment.Item("ImageBuild"),3) >= "6.1" then
sNextDriveLetter = left(GetLastAvailableDriveLetter,1) & ":"
Else
sNextDriveLetter = left(GetNextAvailableDriveLetter,1) & ":"
End if
To:
sNextDriveLetter = left(GetNextAvailableDriveLetter,1) & ":"This line will probably be a problem if a bootable partition does not already exist (line 377):
sBootDrive = GetLastAvailableDriveLetterChange to:
sBootDrive = GetNextAvailableDriveLetter -
02 Haziran 2012 Cumartesi 10:20
Driveletters in WinPE are only temporary, there should be no need to change that script...
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
-
04 Haziran 2012 Pazartesi 16:01
All I know is that when I change the script, the Windows 7 OS install completes and with the script unchanged, it fails. Installing Vista works fine either way.
Dale
- Düzenleyen disaak 04 Haziran 2012 Pazartesi 16:08
-
04 Haziran 2012 Pazartesi 17:20
Well, if it works it works... :) Anyway, would you mind submit your findings on Connect so that the MDT team becomes aware of the issue?
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
-
04 Haziran 2012 Pazartesi 18:53
Johan,
I went to http://connect.microsoft.com/ but it doesn't look like any feedback or bug reports are being accepted regarding MDT.
Do you know of another location where I can submit my feedback?
Thank you,
Dale
-
04 Haziran 2012 Pazartesi 21:38
Look for Solution Accelerators, there you will find MDT 2012 beta which still accepts (and reads) bug reports.
Here is a quick link to the invitation: https://connect.microsoft.com/InvitationUse.aspx?ProgramID=1646&InvitationID=MDTH-PJBM-CBVJ&SiteID=14
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
-
04 Haziran 2012 Pazartesi 22:19
Is the checkbox named Create extra 'Active' partition enabled or disabled in your Format and Partition Disk action? From a little testing I've noticed that if it's disabled then the letter in PE stays as V: (or similar) and when the checkbox is enabled it changes it to C: as a part of the same action.
As Johan says, in theory it shouldn't make the slightest bit of difference but if you're having issues then this may be a way around it without hacking about with the scripts.
The other point he makes is also worth your time looking into - does your xml have a hardcoded reference to <Path>C:\Drivers</Path>? If so then you might want to change that to <Path>\Drivers</Path>
-
04 Haziran 2012 Pazartesi 22:22
Done, thank you.
Dale
-
01 Ekim 2012 Pazartesi 09:25
Hi,
I am using MDT 2012 with SP1, the "Format and Partition Disk" task formats the disk 0 partition 1 and always assign the drive letter as "W:" and this causes problems with the build process. Before in MDT 2010, it was assigning the drive letter as "C"
I have single HDD im my machine and i am creating only (Whole disk) one partition.
Can any one help me on this to resolve?
Regards,
Sudhakar.
-
02 Ekim 2012 Salı 14:05
Is there any reason why the above fix can't be done?? This issue is giving us major issues but I'm unsure if I should change the code in case MS have done this for a reason.
Any comments from Microsoft on this one?
-
02 Ekim 2012 Salı 20:03
Driverletters in WinPE are only temporary, or do you mean that Windows end up on W:\Windows after the machines is deployed?
If you have script that runs in WinPE don't hardcode them to use C:, WinPE may very well enumerate differently
Check the ZTIGather.log and you will see what variables you can use instead.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch
.png)
