Is it possible to parse the MDT TaskSequenceID in the CustomSettings.ini file? I would like to be able to breakdown the TaskSequenceID to get the values from it. Below is an example of what I would like to be able to do.
TaskSequenceID = Windows 7-x64-BaseLoad
OS = Windows 7
Arch = x64
Drivergroup = %OS%\%Arch%\%Make%\%model%
I would be using the variables created from the parsing for other things but the drivergroup example best shows what they would be used for.
Hello,
We have Windows 8.1 setup in MDT, works great.
I've added Windows 10 in addition, but having trouble with the driver groups. Allow me to describe:
Windows 8.1 Task Sequence is setup with:
1. Set Task Sequence Variable: Task Sequence Variable: DriverGroup001 & Value: Windows 8.1\%Model%
2. Inject Driver: Choose Selection Profile: Nothing, Install all drivers from the selection profile (no pnpid)
I have added a new folder to the Out-Of-Box Drivers labeled Windows 10.
Within that I have models of laptops, matching the same wording and structure in the Windows 8.1 Out-of-Box Drivers
This is where i need clarification,
What would the Task Sequence Variable be for the new Windows 10 T/S?
Win 8.1: Task Sequence Variable: DriverGroup001 Value: Windows 8.1\%Model%
Win 10: Task Sequence Variabel: DriverGroup001? Value Windows 10\%Model% ?
I am learning deployment with MDT 2013 u1. have a VM where I have WDS plus MDT, and running DHCP on a ADCS VM; and its been working fine until a few hours ago when my Task sequence is no longer listed in the LTI interface that comes up after the PXE boot.
I have Regenerated new images, Reimported boot images in the WDS, Restarted the WDS, Made a new Task sequence, Reimported the VIM file.
Running default Rules.
Its a W7 x64 I am deploying, the boot image is also x64, the only boot image that I have.
Im sure its a Layer 8 issue. :-)
MDT 6.3.8298.1000 , ADK 10,
Hi,
I have download windows 7 x64 enterprise iso from VL and capture wim file, imported to deploy it. when I try to open unattend.xml file to customized it, I am getting error message
when I click on log file:
6:58 PM : This application requires version 10.0.10240.16384 of the Windows ADK.
Install this version to correct the problem
6:58 PM :
6:58 PM : Error opening D:\MDTProduction\Control\W7PRD1124\Unattend.xml.
6:58 PM :
6:58 PM : System.IO.FileNotFoundException: Could not find file 'D:\MDTProduction\Control\W7PRD1124\Unattend.xml'.
File name: 'D:\MDTProduction\Control\W7PRD1124\Unattend.xml'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlTextReaderImpl.FinishInitUriString()
at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)
at Microsoft.ComponentStudio.ComponentPlatformInterface.Serializer.Validate(XmlSchema schema, String filename, ValidateCallBack additionalValidation, Object additionalParameter)
at Microsoft.ComponentStudio.ComponentPlatformInterface.AnswerFile.DoLoad(Boolean useImagePathInAnswerFile)
at Microsoft.ComponentStudio.MainForm.MainForm_Load(Object sender, EventArgs e)
I have adk 10 installed.
unattend.xml file is in right folder and has access to file.
It only happening on windows 7, I can open windows 10, windows 8.1 unattend.xml file and also able to create catalog file.
Is this know issue with adk build 10.0.10240.16384??? because in my other test server has Build 6.3.9600.17029 and same file is able create catalog and unattend file fine.
thanks in adv
orion
I currently deploy Windows 7 x64 to a variety of different systems using MDT 2012. All systems that I have in my inventory use intel processors with the exception of one particular HP Laptop. On all Intel models, if I do not change the SATA mode from AHCI to compatibility/IDE the MDT imaging process hangs up at "Preparing disk 0 partitions" I have verified that all required storage drivers are present. Are there any settings or changes that I can make to get around this issue? Thanks.
-Joe G
I am deploying a non-domain client and would like to deploy Trend Officescan during the deployment. The trend msiexec is located on a network share. Is there a task sequence to connect to a network share or do I need to create a script to connect to the network share?
Also, I will be using WSUS to get updates on this same machine. Again since this is a non domain joined computer, how do I specify the WSUS server? Some of the forums I have seen mention that I need to manually update the registry to add all of the WSUS parameters. Is this correct?
Hi,
I know I can deploy Office 2010 and activate it with MDT. But now I want to capture this image with Office 2010 already included. If I deploy this image, Office isn't activated. Is there way to do just the activation of Office 2010 (and Windows) with a MAK key after I install an image with Office already included?
I'm able to dynamically set and prepopulate the the computer name based on the customsettings.ini file I have and would now like to prepopulate the domain and the organizational unit (OU) but am not having any luck. Any assistance would be greatly appreciated.
Here is the contents of the customsettings.ini file:
[Settings]
Priority=StdSerial, ByLaptop, ByDesktop, ByVM, Default
Properties=MyCustomProperty, ComputerSerialNumber
[StdSerial]
ComputerSerialNumber=#Right("%SerialNumber%",7)#
[ByLaptop]
subsection=Laptop-%IsLaptop%
[ByDesktop]
subsection=Desktop-%IsDesktop%
[ByVM]
subsection=VM-%IsVM%
[Desktop-True]
OSDComputerName=SON-%ComputerSerialNumber%
OSDDomainOUName=OU=Desktops,OU=Workstations,OU=SON,OU=Resources,DC=sub,DC=domain,DC=com
[Laptop-True]
OSDComputerName=SON-M-%ComputerSerialNumber%
OSDDomainOUName=OU=Laptops,OU=Workstations,OU=SON,OU=Resources,DC=sub,DC=domain,DC=com
[VM-True]
OSDComputerName=SON-VM-#Mid(oStrings.GenerateRandomGUID,2,7)#
OSDDomainOUName=OU=Virtual Lab,OU=Workstations,OU=SON,OU=Resources,DC=sub,DC=domain,DC=com
[Default]
OSDDomainName=sub.domain.com
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YESAnd here is a screenshot of the UDI Settings:
Hi I'm trying to image a HP zbook 15u G2 with out any success. It applies the Operating system, then the unattend and DISM stage restarts the machine and then all I get is a black screen and the machine doesn't boot.
I've readded the drivers from the HP driver pack. The same image for on 4 other types oh HP including other zBooks.
What am I missing?
Thanks
Hi everybody,
I'm trying to setup new MDT environment (MDT 2013 Update 1) but I'm having some trouble in the process.
What I did and should be OK :
My problem :
I try to make a deployment with a VM. I'm able to select the boot image I put into WDS but afterwards it's stuck on Windows logo.
Thank you in advance for your help ;)
Hello everyone,
I have to change the index of an Windows 10 image so I mustn't change all my scripts.
Is it possible to change the index of an install.WIM file from the index 2 to the index 1?
regards
-Nikolai
Has anyone here implemented LAPS in their environment and if so how does is affect using MDT. Obviously it won't have any affect when booting to the boot image but what about when you run MDT from within Windows.
LAPS - https://technet.microsoft.com/en-us/library/security/3062591.aspx
If this post is helpful please vote it as Helpful or click Mark for answer.
Trying
OSDComputerName=PC-#Left(“%SerialNumber%”,12)#
But it those not work, Using MDT 2013u1.
Should it work now days?
Hi,
I have (had) WDS working with MDT to serve up MDT boot images. Now, all of a sudden (I have no idea what happened over the weekend), PXE clients cannot get an IP address. The PCs get their DHCP addresses when they boot into Windows, but not via PXE. I have enabled logging on the WDS server, but there is no log in the tracing folder. This is Windows Server 2012 with MDT 2013. If I use a boot key to try and contact MDT, which runs on the same server, I get an error stating the TaskSequence.xml file cannot be found (whatever that means). I'm NOT using SCCM, just MDT and WDS. All of the help articles I can find online relate to MDT/WDS with SCCM, which is useless to me.
Where does WDS keep it's log files? I can't find a clear answer on that.
Thanks
Jason
I'm banging my head against a wall trying to figure this out. I have a Windows 7 lite touch deployment image that I deploy to multiple models of PCs and laptops. It works fine for all models except one (HP 6005 SFF).
For this model, I PXE boot, manually approve the pending device in WDS, and the process starts. It downloads the correct LiteTouchDeployment wim file, then goes to a black screen with a green spinning bar and just stays there. I've left it alone for hours with no progress. Are there logs anywhere that I can see what's causing this? Where do I start looking?
I am using MDT 2012. I have implemented the DomainOUList.xml in my control folder of my deployment share. The first code snippet works fine. When I try the second, I get the following error when selecting the OU: "Invalid OU format (must start with OU=)"
Am I missing something? Can you not make the OU a value to be able to use a cleaner display name?
<?xml version="1.0" encoding="utf-8"?><DomainOUs><DomainOU>OU=XP Computers,DC=domain,DC=com</DomainOU></DomainOUs>
<?xml version="1.0" encoding="utf-8"?><DomainOUs><DomainOU value="OU=XP Computers,DC=domain,DC=com">XP Computers</DomainOU></DomainOUs>
Guys, I've run into this error while trying to make a new MDT task sequence using SCCM 2012 R2 in my test lab. Does anyone know, what could be the problem here? Google doesn't give any answers.
Started processing.
Existing boot image 00000000 will be used.
Creating MDT files package.
Microsoft Deployment Toolkit files package created.
Existing OS image package 00000000 will be used.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.FormatException: Input string was not in a correct format.
at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
at System.Version.TryParseComponent(String component, String componentName, VersionResult& result, Int32& parsedComponent)
at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at Microsoft.BDD.Core.Utility.GetVersion(String strVersion)
at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
Greetings,
I need to start deploying MS Surfaces Pro 3/4. I just got them in and of course management thinks I can just wipe up an image pretty quick.
Since this is my first Surface, it won't be quick as I have to learn the in/outs of its UEFI etc differences from a starndard laptop.
I've search and read and it seems pretty simple (but something is not working though).
Here is my plan, I'm using a Offline USB drive, which I know they work as I have to used them to deploy to laptps at remote locations (PXE is not allowed).
I build a USB flash drive using the URL below. Also, below are the drivers I imported.
Out Of Box Drivers
SurfacePro3_Win8x_151026_1.zip (all of them drivers and Firmware)
Drivers for WinPE
Surface Ethernet Adapter
Surface Gigabit Ethernet Adapter
UEFI USB Setup
http://deploymentresearch.com/Research/Post/471/UEFI-and-NTFS-Friends-to-MDT-2013-at-last
Drivers
https://www.microsoft.com/en-us/download/details.aspx?id=38826
Surface Settings
Trusted Platform Module (TPM) = Enabled
Secure Bootl Control = Enabled
Configure Alternative System Boot Order = USB -> SSD
BitLocker was never enabled.
Questions / Issue.
When booting from UEFI USB flash drive on teh Surface Pro 3, I get an error "Invalid Signature detected. Check Secure Boot Policy in Setup"? Does this mean I need to disable Secure Boot or something?
Will the UEFI USB with the Offline media be enough to boot the MS Surface Pro 3/4?
Our AD (for now) does not have the BitLocker schema added, so I was thinking of enabling BitLocking with a startup PIN. Will this be possible or do I need to tweak my Task Sequence?
Any suggestions?
Thank you for your time.