Create a TS Variable in MDT 2013 to set Computer Name to Wifi Mac Address

Hello,
I'm currently using the following rule to pick up the MAC address of the computer:
OSDComputername=#Right(Replace("X%macaddress001%",":",""),15)#
I have created an image for the Linx Tablets, which don't have an ethernet MAC Address, so I'd like to use the Wifi address instead (which would also help with network registration in our environment). Does anybody have a solution?
Thank you,
Garin

Hi,
I highly recommend asking this question in the MDT forum, since this question is very MDT-specific:
http://social.technet.microsoft.com/Forums/en-US/home?forum=mdt&filter=alltypes&sort=lastpostdesc
Perhaps someone who is familiar with MDT will see this, but I still think you stand a much better chance at getting a good answer over in the MDT forum.
Good luck.
Don't retire TechNet! -
(Don't give up yet - 12,700+ strong and growing)

Similar Messages

Setting computer name on a VM created from template (SCSM, SCVMM and SCORCH)

We've set up some basic server provisioning automation to see how it works. It's a fairly simple setup so far:
1. User submits ticket via the SCSM portal; the ticket includes the desired machine name.
2. Ticket requires our team's approval before the workflow continues into Orchestrator.
3. If approved, an Orchestrator runbook is kicked off, using SCVMM to create the server from a template.
The resulting server has the correct machine name in SCVMM, but the machine name inside the OS is randomly generated (the template currently has * in OS Configuraiton -> Identity Information in the VM Template properties).
What's the best way to make the computer name inside the OS reflect the desired machine name? I can think of a number of ways we could accomplish this, but I don't know SCORCH/VMM that well yet. I'm wondering if I have overlooked something simple inside
the existing process we're using. I suspect that, if there is an easy solution, it would lie in VMM.
Many thanks for your time and consideration.

I've got the Guest OS Profile partially working, but frustratingly, it doesn't seem to be applying all of the settings.
Here is what I have done so far:
1. A Guest OS Profile has been set up which includes all of the settings I am currently trying to test: domain join, feature installation (nothing fancy for now, just Powershell and Telnet Client), and a KMS key for Server 2012.,
2. Orchestrator Runbook gets the existing OS Profile, creates a new one based on the VM, and uses the parameter -ComputerName to pass the name of the VM to the Guest OS Profile. The new Guest OS PRofile is showing up correctly in VMM, with the right settings.
3. The runbook then deploys the new VM from template, using the newly set up Guest OS Profile. The machine is set up correctly, and will boot. Not all of the settings from the Guest OS Profile transfer over, however. The Domain Join and KMS portions work
without a problem. The features I have tried to add are not installed, though, and the computer name remains randomly generated.
I know the Guest OS Profile must be getting used, since the machine gets domain joined; the template does not include domain join credentials. What I can't work out is why some of the settings are being applied while others are not.

MDT 2013 and RES Automation Manager

Hi,
In one of the first step of MDT I'm using a simple script that asks for the country code (e.g. NL), which I would like to store in an environment variable, which I can later on read into RES Automation Manager. But it seems that after MDT is finished and
Windows starts up, the environment variable is gone. Are there any other ways to accomplish this? I'm using it to install language specific applications from RES AM, after MDT is finished. The Windows language settings itself I set with the
CustomSettings.ini, that is based on the same simple script
[Settings]
Priority=ByCountry, CountryAbbr,Model,Default
Properties=CountryAbbr, CountryOU,CustomProperty
[ByCountry]
UserExit=ZTIGetCountry.vbs
CountryAbbr=#GetCountryCode()#
[NL]
CountryOU=NL
CountryOrRegion=31
InputLocale=0409:00020409
KeyboardLocale=nl-US
UserLocale=nl-NL
UILanguage=nl-NL
TimeZoneName=W. Europe Standard Time
ZTIGetCountryCode.vbs
Function UserExit(sType, sWhen, sDetail, bSkip)
oLogging.CreateEntry "entered UserExit ", LogTypeInfo
UserExit = Success
End Function
Function GetCountryCode()
Set objShell = CreateObject("WScript.Shell")
Set objEnv = objShell.Environment("SYSTEM")
GetCountryCode = InputBox("Fill in Country Code (NL DE DA FR PT); If default, use None")
objEnv("MDT_Language") = GetCountryCode
Set objShell = Nothing
Set objEnv = Nothing
End Function
Any idea what I can do else??
Thanks,
Mario

Hi, this looks quite similar to my blog post I did some time ago:
MDT 2012 LTI Deployment, Regional and Locale settings based on #chars of Hostname
The trick in your specific case is to either, not reboot your machine, or to set the installation of RES Automation Manager right after the reboot.
Basically MDT clean's up it's act after it is finished. This also means the environment variables which are stored in a .dat file in the C:\MININT folder are removed after MDT has finished.
So either you need to find a way to perform your RES AM job, during the MDT task sequence, or set or dump the environment variables to a file are temporarily variable which RES AM can use.
Here are some articles that will help you get further:
MDT and RES Automation Manager – Let’s come together (in Sweet Harmony)
Creating custom variables in MDT 2013
Finding All References to MDT Variables in a Deployment Share: VariableDocumentor
v1.0
Dumping Task Sequence Variables
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT Database - Auto Computer Name Using MAC Address

I am trying to build a MDT server which will auto name any computer by using the MAC Address of the Network Card, I have read lots of articles and there isn't a definitive answer but I am looking for a simple answer which will work. I have tried all sorts
of things customising the Customsettings.ini and the unattend.ini and the database.
These are the settings I am looking at .
Can anyone please advise me how to get MDT to query the database and output the computer name using one of these variables.
%OSDComputername%
%Computername%
Can you please help.

Hi Walkermescc,
Since it is related to SQL database, our help might be limited. I suggest you refer to this article and it might be helpful.
http://blogs.technet.com/b/deploymentguys/archive/2011/08/05/dynamic-computer-naming-in-zti-deployments-using-mdt-and-configmgr.aspx
If you need more support about MDT and Database, you could post your issue to the MDT forum and there might be more suggestion for you.
MDT server forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Regards

MDT 2013 - Create New User

Hello,
I've recently setup MDT 2013 to deploy some customized images that we deploy to student laptops, that were sysprep-ed and captured with ImageX. I've uploaded the custom image WIM files to MDT, and setup a task sequence. Almost everything works,
thanks to Microsoft documentation and searches of this forum for various questions I've had, however I'm stuck on two items:
1.) MDT forces an administrator account to be created during the process. That's not such a huge issue, but I'd like to disable the administrator account at the end of the task sequence. I'm not sure where/what to add to do this.
2.) We would like the machine, after imaging, to deploy the generic Windows Welcome, as if it had just been purchased from the OEM. This way when the student receives the imaged laptop, they can create their own personal account. These laptops are
not bound to AD. Right now, when the task sequence finishes the systems are logged in as an administrator. Again, I'm not sure what code to add to the task sequence (and where) to accomplish this.
Any information or links on what I'm looking for would be greatly appreciated. I'm sure that both these items are possible, but I'm not using the proper terminology on my searches to find the information I'm looking for. Thanks!

I question the usage of MDT in this scenario. I also question your premise that your users should go into OOBE Setup.
MDT is designed to assist IT departments in getting windows up on machines in a End to End scenario.
MDT prompts which Task Sequence, Language/Locale/TImezone, Applications, drivers, and User Data Migration Status. Once the TAsk Sequence has started, MDT should be as automated as possible. No prompts, no user interaction.
What you are asking for is the opposite, you want user interaction during deployment, and rather than customizing each deployment, the image is pre-configured. (Unless you have different *types* of machines that require driver loading via MDT).
IN your case I would recommend just slapping an install.Wim up on a WDS server, and custom crafting an unattend.xml file to prompt each user for user accounts. (as long as you don't have to worry about drivers).
The other solution is to prompt the user for their new user account from the MDT wizard, and slam that into the machine during the task sequence (and removal of the Administrator account with net user administrator /active:no )
I actually created a powershell script to accomplish this:
http://keithga.wordpress.com/2013/09/24/microsoft-account-automation-in-windows-8/
This alternative solution is MDT 400 level work. Scripting required. :^(
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Create Image using MDT 2013

Hi ,
I am quite new for MDT 2013. I have recently installed MDT 2013 in my Windows Server 2012.
Now , I do have about 10 physical machine with different hardware specification inside. I have installed Windows 8.1 with all required software in it and now I want to distribute the same image in all 10 another physical machine.
Can anyone provide me the steps to implement this...
Do I need to create the image using image x software and then use it as a standard image to be deploy it in rest of the systems..
Thank you...

I was getting exact same error.
here is what I did to fix it.
You need to do all this in a virtual envinronment.
1- import Windows 8.1 x64 from the DVD and add it to your listed os in MDT
2- create standard task sequence and select the OS you imported in step one. you need to add suspend to your TS ( look it up on how to )
3- For some reason WinPe x64 bit kept giving error during deployment so I used WinPe x86.
4- import Winpe x86 boot.wim into your WDS if you use Pxe boot or create a boot disk from the ISO and boot your VM from it.
5- deploy windows 8.1 x64 to your VM ,make sure to select " capture image ".
make all the necessary changes when windows is installed and MDT suspends the deployment, take snapshot of your VM , and then cintinue the deployment to finish the capture.
6- import the new captured image into MDT
7- creates new standard TS or modify your existing one to deploy the newly captured image.
8- update your deployment share and start the deployment of your new image.

MDT 2013 - Error creating WIN 7 Reference Image

Hi Guys,
I am pulling my hair out!
I have tried to create a .wim image of a Win 7 set up on a VM machine (VM Workstation)
I have used the MDT task sequence, standard client task sequence. It has always failed on the creating WIM image stage. I have looked through the forum and checked permissions, ensured I have used an IP address for my Share, just cannot get rid
past this....
Please help Thanks.
I have added error message

I have added error message
Where?
If you are still having problems, please copy your bdd.log file to a public site like OneDrive, and share the link.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013 + create 5 recommended UEFI/GPT drive partitions

Hi
My end goal is to deploy a custom x86 image to a UEFI device (tablet) using a USB stick. It is likely that my .wim file will be >4GB, but for now, I'm just trying to get the process working with a standard OEM <4GB .wim file.
As per this post, I have performed steps under sections 5.1, 5.2 and 5.3 MANUALLY, by booting the tablet using a WINPE 5.0 USB and running
1) diskpart /s E:\CreatePartitions.txt
and
2) E:\ApplyImage E:\Images\ThinImage.wim
Q: Above worked perfectly and it's exactly what I'm looking for. How do I incorporate 1) + 2) into MDT, or do I simply attempt to replicate the code from 1) + 2) under "Format and Partition Disk" under PreInstall\New
Computer only step?
Any advice or pointers would be really appreciated.
Many thanks in advance.

Recovery images, that's a different story.
First option is to increase the size of the System partition to the desired size:
BdeDriveSize=5000
Otherwise, the best solution I've seen is to build the standard MDT partition configuration using the default MDT "Format and Partition" step. and *THEN* shrink the partition to the desired size. Yes Shrink.
The other option is to increase the size of partition 1 from
See Mike's post on WimBoot for the example script LTIApplyWim.wsf script that shows how shrinking works.
http://blogs.technet.com/b/mniehaus/archive/2014/04/13/experimenting-with-wimboot-using-mdt-2013.aspx
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013: Wizard Pages by Task Sequence

Hi,
I believe what I am trying to do is not possible from previous readings on this forum, BUT then I see something in my MDT 2013 OSD wizard that seems to indicate there might be a way to get it done. So here goes.
For my own demos, I am trying to develop a deployment share that is much like Johan Arwidmark's hydration kit. Some machines, like a domain controller or a SQL cluster are all well-defined: computer names, IP addresses, etc. are fixed and can be set
in customsettings.ini or in the Task Sequence with variables. However, I would also like the ability to have to deploy a "generic" machine where I can select roles, applications, etc.
This would require having different wizard pages shown for different task sequences. From what I've read, this may not be possible without developing a custom wizard (and that might be too much effort). However, I currently have two task sequences and depending
on which one I select, I see a different number of steps to complete? See screenshots. I don't know what I have currently configured that makes it like that.
(when I select "Domain Controller 01" task sequence) (Task sequence ID "DC01")
(when I select the "generic" task sequence)
Below is my customsettings.ini [the only rules file I have].
[Settings]
Priority=TaskSequence,Default
[Default]
_SMSTSORGNAME=Demo Deployment
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
AdminPassword=P@ssw0rd!
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
EventService=http://192.168.232.1:9800
SkipUserData=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipFinalSummary=NO
FinishAction=SHUTDOWN
SkipLocaleSelection=YES
HideShell=YES
[DC01]
_SMSTSORGNAME=DC01 Deployment
SkipComputerName=YES
OSDComputerName=DC01
SkipDomainMembership=YES
JoinWorkgroup=DEMO
SkipRoles=YES
I would expect the settings for task sequence "DC01" to be applied after I select that task sequence in the wizard. That doesn't seem to work. The first task in the sequence is a "Gather" task that gathers local data and processes customsettings.ini.
I understand I can't override most settings from [Default] because they would have already been processed but as you can see, that's not what I am actually trying.
I am not opposed to having multiple rules files if that would work. However, it seems like that doesn't make much difference when it comes to actually seeing different wizard steps active. I've tried adding a second customsettings_dc01.ini file and having
a Gather step that specifically references that file in the "Initialize" group.
I've considered some alternatives to making it work this way, such as having multiple deployment shares and "linking" them (although I haven't done this before) so I wouldn't have to copy all the applications.
I would also set the computer name and all in the task sequence using variables, but that still doesn't address the problem.
Any insight is appreciated,
SA.

SpeedBird186 - There are several assumptions going on here.
1. by default MDT processes the CS.ini file *before* the wizard, and *after* the Task sequence has started. If you want CS.ini file to be processed just *after* you select your TS in the wizard, use Johan's trick above.
2. There are about 20 different wizard pages, and they don't appear in *all* scenarios. the wizard framework will attempt to do an intelligent job of filtering out pages that are not relevant to the scenario at hand. For example, in the graphic above, you
can see that the OS roles and Features page will appear/disappear. This can happen for example if the task sequence you selected earlier does or does *not* have a "OS Roles and Featrues" step in the Task sequence.
3. For me, the easiest way to process roles would be to create some new "Applications" and to put them in a folder.
Keith Garner - keithga.wordpress.com

Task seqence according to departments in a company and MDT 2013

Hi,
I have a problem and I need help from the SCCM community.
So here we go:
I am in a process of upgrading SCCM from 2007 to 2012, great. I have setup lab environment which consists of 2 DC, 1 DB server, 1 SCCM 2012 Server and 2 test clients (Windows 7).
My question is about planning and design of the task sequence for various departments in our company. I have no idea how to approach it or how to implement it. Right now we use HTA script.
The idea is to deploy a set of applications like Skype, acrobat, 7-zip to all windows 7 clients, and then based on what I choose in MDT(this is the actual procedure which we use in 2007):
…have other applications which are specific to the chosen department.
I want to move away from the hta script in SCCM 2012 but I have no idea how to do it. Only thing that I know it MIGHT work would be to make MDT 2013 TS user driven OS deployment TS.
This drags another questions:
Is there anywhere on the internet a guide for this? Youtube or something that I was not able to find.
Would that mean that I would have many Task Sequences?
By that I mean for example.
“Deploy Windows 7 – QA”
“Deploy Windows 7 – DEV”
“Deploy Windows 7 – IT”
“Deploy Windows 7 – CS”
“Deploy Windows 7 – PM”
And if I have windows 8.1 which I will that would mean too many TSs displayed I want to avoid that and have only 1 for windows 7 and 1 for windows 8.1 clients. I want to make a TS which deploys applications according
to what I choose in UDI Wizard Designer (Am I right? Is that being made in UDI?).
I would love to see a solution like this:
Any help is appreciated.
Thank you

Hi,
I am a bit stuck on the following...
I have created a custom UDI page called Gather data for OSD but i am not sure if I am doing a good job with variables:
I want to enter a name for the computer and for TS to of course give a name that I want to the computer.
I also would like to choose departments because then i can deploy different applications with different departments. I am basically trying to recreate the procedure written in my first post but without HTA:
Am I on the right path or?
Thanks,

MDT 2013 Roles and features failing to install for server 2012 r2

I am having issues trying to apply Server 2012r2 Roles and features via MDT 2013.
Below I have attached the log.
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole"
context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles specified in Role:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ FileAndStorage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[RoleServices specified in RoleService:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ File-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Storage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NET-Framework-Features]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NET-Framework-Core]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NET-WCF-TCP-PortSharing45]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ InkAndHandwritingServices]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Server-Media-Foundation]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ RDC]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ SNMP-Service]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ SNMP-WMI-Provider]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Telnet-Client]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ User-Interfaces-Infra]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Server-Gui-Mgmt-Infra]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Desktop-Experience]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ Server-Gui-Shell]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ PowerShellRoot]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ PowerShell]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ PowerShell-V2]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName FileAndStorage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\WIN-7VSNJRF3PNO\DeploymentShare$\Operating Systems\Windows Server 2012 R2 SERVERSTANDARDCORE x64]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context=""
type="1" thread="" file="ZTIOSRole">
<![LOG[Mapping server share: \\WIN-7VSNJRF3PNO\DeploymentShare$]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Already connected to server WIN-7VSNJRF3PNO as that is where this script is running from.]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread=""
file="ZTIOSRole">
<![LOG[Copying source files locally from \\WIN-7VSNJRF3PNO\DeploymentShare$\Operating Systems\Windows Server 2012 R2 SERVERSTANDARDCORE x64\sources\sxs]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole"
context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)]LOG]!><time="10:45:27.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">

I have narrowed this issue down to .net 3.5 install.
I have boot, efi, sources, support, autorun, bootmgr, bootmgr.edi, and setup.
I have confirmed that the sxs folder is there.
I also just added WindowsSource=%DeployRoot%\Operating Systems\Windows Server 2012 R2 SERVERSTANDARDCORE x64\sources\sxs to my customsettings and updated the boot iso. I am still receiving the errors.
One last bit of information I am able to get to the deployment share with the sxs folder in it from the reference machine I am creating but when I manually try to install .net 3.5 from roles and features to the share it fails. But if I copy the files local
they work fine.
I seem to have permission issues with other subfolders also.
Thanks,
Anthony

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

Hi All,
After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
with the tests I am using the MDT 2013 Server Task Sequence Template.
Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
\Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
Some background info:
As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
In both Task sequences the Format and Partition step is as follows:
Disk 0
Standard(MBR)
BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
OSDisk (Primary) - 90GB variable OSDisk assigned
In both Task sequences the Apply Operating System step is as follows:
Using Captured Image
Apply operating system from a captured image (Image 2-2)
Apply image to Logical Drive (OSDisk)
In both Task sequences the Apply Data Image step is as follows:
Using Captured Image
Image 1-1 (from the same captured image as shown above)
Apply image to Logical Drive (BDEDrive)
What has been done so far:
Already eliminated driver packs as the problem occurs with and without them
Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
are preserved.
I have disabled an UEFI Partitioning steps just as a precaution.
There is no Bitlocker steps involved yet.
I have trawled through the SMSTS.LOG. So far it looks OK to me:
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\use
The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
Any suggestions would be great.
NSutton

Hi,
If I were you, I would Streamline the MDT Task Sequence to find the root cause.
Moreover, please refer to the link below:
How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Issue with Capture Task Option showing correctly in MDT 2013

I am aware that having the variable of DomainJoin will prevent the capture dialog from appearing when running the task. The problem is, even when the options are greyed out due to the domain settings not being applied from a different setting in the workflow
it still breaks the task.
E.G.
I am using the database, and have my workflow as such:
[Settings]
Priority=Model, TaskSequenceID, LSettings, CRoles, RApps, LApps, MMApps, MMSettings, Default
Properties=MyCustomProperty
DataBase:
Location Settings: Overall settings for Domain join, wizard skips, etc info per gateway
Role Apps: Apps per role
Make/Model Apps: Apps specific to a piece of hardware
CustomSettings INI:
Model/Task Sequence/Default: I have tried to null out the DomainJoin settings with these variables by adding workgroup join by task ID, Model, etc and nothing seems to work. I've verified in other tasks
that these settings take place of what's in the DB, but the DB settings are still there, greyed out and causing an issue.
[X86SYSANDCAP]
JoinDomain=
JoinWorkgroup=WORKGROUP
[VMware Virtual Platform]
JoinDomain=
JoinWorkgroup=WORKGROUP
As shown below the model/TS specify the workgroup (1st pic is normal deploy, 2nd is cap) but the greyed out settings are still having an effect. Skip Capture is set to NO at each level, and when I remove the Domain from the DB it shows up correctly.
Not sure what to do besides removing the domain everytime I want to do a capture, which seems a bit unreasonable and I don;t want my T1s in the DB.

I highly recommend to always use the standard Client task sequence for a build and capture. Much more reliable.
Check out these Resources, the info is also valid for Windows 7:
TechNet Docs - Create a Windows 8.1 Reference Image
http://technet.microsoft.com/en-us/library/dn744290.aspx
Virtual Hands-On-Labs - Creating a Windows 8.1 reference image
http://go.microsoft.com/?linkid=9845755
How to deploy Windows 8.1 (and Windows 7) with MDT 2013 - The Resources
http://www.deploymentresearch.com/Research/tabid/62/EntryId/186/How-to-deploy-Windows-8-1-and-Windows-7-with-MDT-2013-The-Resources.aspx
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Create a TS Variable in MDT 2013 to set Computer Name to Wifi Mac Address

Similar Messages

Maybe you are looking for