Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

INACCESSIBLE BOOT DEVICE error in Windows 10

$
0
0

Hello

Im using MDT 2013 and have been happily deploy windows 10 machines using a standard task sequence.

However we have just been sent in a new Dell XPS 13 (we have used these before and have imaged fine) and each time i image the machine i restart and get the INACCESSIBLE BOOT DEVICE.

I can re-install using a windows 10 usb key fine, but each windows 10 image i select in the MDT task sequence produces this error.

I thought it may have been driver error so i have tried also to disable the part where it installs the device drivers.

Any ideas?

Thanks


MDT 8443: Invalid DeploymentType value "" specified. The deployment will not proceed.

$
0
0

I previously had MDT 2013 Update 2 installed, and upgraded to MDT 8443. I'm using ADK Win10 1607 with Windows 10 as the file server. This has been working for over a year now.

I upgraded the MDT software and updated my deployment share and litetouch WIM. I deployed my litetouch WIM to our WDS and booted off it.

Now, no matter what Task Sequence I select, after the "Ready to begin" screen, I get the following error:

Deployment Error
"Invalid DeploymentType value "" specified. The deployment will not proceed."
[OK]

I've tried every Task Sequence, I even built a new Task Sequence, I get thesame issue. I've tried manually specifying the "DeploymentType" various in both my bootstrap and in the Task Sequence itself, with no improvement.

I am currently completely down and unable to image systems.

==RULES==

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
SkipBDDWelcome=YES
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipDomainMembership=NO
JoinDomain=domain.com
EventService=http://computer:9800

==BOOTSTRAP.INI==

[Settings]
Priority=Default

[Default]
_SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%
SkipBDDWelcome=YES
DeployRoot=\\computer\DeploymentShare
OSDComputerName=DAL-%SerialNumber%

SkipDomainMembership=NO
JoinDomain=domain.com
UserDomain=domain.com

SkipLocaleSelection=YES
UILanguage=en-US
UserLocale=en-US
KeyboardLocale=en-US

HideShell=YES
FinishAction=REBOOT

SkipTimeZone=YES
SkipLocaleSelection=YES
TimeZoneName=Central Standard Time

SkipFinalSummary=YES

Exclude Outlook OST from Image Capture (MDT 2013 Update 2 / DISM Capture)

$
0
0

We're currently using the MDT script ztibackup.wsf to capture images of all our computers prior to a Windows 7 to 10 migration. We'd like to exclude the Outlook OST from the capture since they are so large.  The problem is our OST files are stored in the default location, C:\User\Username\AppData\Local\Microsoft\Outlook.  I cannot find any mention of using environment variables in the wimscript.ini, but did try using the following entries and when I do, the capture fails.  Any thoughts on how to exclude files in the user's AppData\Local folder?

%UserProfile%\AppData\Local\Microsoft\Outlook\*.ost

%LocalAppData%\Microsoft\Outlook\*.ost


how to define settings and priority custom settings and bootstrap.ini

$
0
0


Hi MDT professionals i am looking syntax and setps to define in custom settings and bootstrap.ini file for 2 deployment shares. i have created 2 deployed share  for capturing images from windows 8/8.1/10 noticed 2 second deployment share struck in bootstrap steps

so looking if files needs to edit in MDT 2013 update 2 and how to define settings and priority  custom settings and bootstrap.ini (i used default) noticed 2 second deployment share struck in bootstrap steps

Running a reg.exe in a Task Sequence

$
0
0

Still fairly new to MDT but am learning. I am trying to add a Reg delete to the task sequence. The command line I have is:

reg.exe delete HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate /f

This does not work but if I enter it in the command prompt afterwards it works fine.

I have tried looking through the logs and searching for reg.exe but cannot find any trace of it. Everything else in my TS works fine but this. Do I have to specify C:\Windows\System32? I thought I had tried that but could try it again. I just didn't know if there was anything obvious I am missing.

Where can I look for my problem at?

Thanks,

Scott

Enabling BitLocker for just one Task Sequence

$
0
0

I want to enable BitLocker for just one Task Sequence. Currently, on my deployment share in customsettings.in I have these Bitlocker settings for everything:

BDEInstallSuppress=YES
SkipBitLocker=YES
BDEInstall=TPM
BDERecoveryKey=AD

It looks like I'll need to change BDEInstallSuppress and SkipBitLocker to NO. And also I'll need to disable the Enable BitLocker steps on the Task Sequences that I don't want to enable BitLocker on.

Does this look like the best way to get there?


Orange County District Attorney

WDS prompting for Locale and Keyboard despite having Answer File

$
0
0

Hi all, I'm trying to implement WDS to help in deploying servers in our environment but during testing as seen in the image below, keeps prompting for locale despite having it in the answer files which is attached as well. Further more the files i've packaged into the $OEM$ folder does not get installed as well while some of the settings such as the administrator account takes effect. Any idea where I'm doing it wrong?

1st Answer File 

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="windowsPE"><component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SetupUILanguage><UILanguage>en-US</UILanguage></SetupUILanguage><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component><component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><DiskConfiguration><WillShowUI>OnError</WillShowUI><Disk wcm:action="add"><CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Size>100000</Size><Type>Primary</Type></CreatePartition></CreatePartitions><ModifyPartitions><ModifyPartition wcm:action="add"><Active>true</Active><Format>NTFS</Format><Order>1</Order><PartitionID>1</PartitionID><Letter>C</Letter><Label>OS</Label></ModifyPartition></ModifyPartitions><DiskID>0</DiskID><WillWipeDisk>true</WillWipeDisk></Disk></DiskConfiguration><WindowsDeploymentServices><Login><Credentials><Domain>test.domain</Domain><Password>P@ssw0rd</Password><Username>Administrator</Username></Credentials></Login><ImageSelection><InstallImage><Filename>2012R2-(2).wim</Filename><ImageGroup>2012R2</ImageGroup><ImageName>Windows Server 2012 R2 SERVERSTANDARD</ImageName></InstallImage><InstallTo><DiskID>0</DiskID><PartitionID>1</PartitionID></InstallTo></ImageSelection></WindowsDeploymentServices><ImageInstall><OSImage><InstallFrom><Credentials><Domain>test.domain</Domain><Password>P@ssw0rd</Password><Username>Administrator</Username></Credentials><Path>E:\RemoteInstall\Images\2012R2\2012R2-(2).wim</Path></InstallFrom><InstallTo><DiskID>0</DiskID><PartitionID>1</PartitionID></InstallTo><InstallToAvailablePartition>false</InstallToAvailablePartition></OSImage></ImageInstall></component></settings><cpi:offlineImage cpi:source="wim:d:/remoteinstall/2012r2.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

2nd Answer file

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="oobeSystem"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><OOBE><NetworkLocation>Work</NetworkLocation><ProtectYourPC>1</ProtectYourPC><HideEULAPage>true</HideEULAPage><HideOEMRegistrationScreen>true</HideOEMRegistrationScreen><HideOnlineAccountScreens>true</HideOnlineAccountScreens><HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE></OOBE><ShowPowerButtonOnStartScreen>true</ShowPowerButtonOnStartScreen><BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled><DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet><TimeZone>Singapore Standard Time</TimeZone><UserAccounts><LocalAccounts><LocalAccount wcm:action="add"><Password><Value>UABAAHMAcwB3ADAAcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value><PlainText>false</PlainText></Password><DisplayName>Administrator</DisplayName><Group>Administrators</Group><Name>Administrator</Name></LocalAccount></LocalAccounts></UserAccounts><FirstLogonCommands><SynchronousCommand wcm:action="add"><Order>2</Order><CommandLine>E:\$OEM$\Bigfix\install.bat</CommandLine><RequiresUserInput>false</RequiresUserInput></SynchronousCommand><SynchronousCommand wcm:action="add"><Order>1</Order><CommandLine>E:\$OEM$\SEP\setup.exe</CommandLine><RequiresUserInput>false</RequiresUserInput></SynchronousCommand></FirstLogonCommands><RegisteredOwner /></component><component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component></settings><settings pass="specialize"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ProductKey>D2N9P-3P6X9-2R39C-7RTCD-MDVJX</ProductKey><RegisteredOwner /></component></settings><cpi:offlineImage cpi:source="wim:d:/remoteinstall/2012r2.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>


A Connection to the Deployment Share

$
0
0

I have active directory domain environment and configured MDT2012 for installation of Windows 8.1.

Recently i just changed my domain account password which was also put in "bootstrap.ini" but after when i try to install windows 8.1 an error occurred however i try different domain admin account password but in continously failed

please help me


MDT 2013 update 2, FAILURE ( 5212 ): Welcome wizard failed or was cancelled

$
0
0

I'm trying to deploy Win7 & Win8.1 sysprep images using update 2.  These .wim's have been used in my production environment for over a year on multiple servers and have been deployed/redeployed well over 20K times without issue.  Using update 2 I've tried every combination (upgrading MDTU1 to U2, clean U2 install, creating new sysprep images, multiple deployment servers...) except for the correct one.

My last attempt was with a fresh deployment share using only the default scripts and minimal modifications (cs.ini & bootstrap.ini).  The task sequence only includes the following default items under State Restore;

Gather local only, Post-Apply Cleanup, Recover From Domain, Tattoo, Install Applications, Custom Tasks (folder), Restore Groups

same result.  The only errors/failures in the smsts.log are TSManager components;

  • Failed to delete directory 'C:\_SMSTaskSequence'
  • SetNamedSecurityInfo() failed.
  • SetObjectOwner() failed. 0x80070005.
  • RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.
  • RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence
  • RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
  • GetTsRegValue() is unsuccessful. 0x80070002.


Because of the limited amount of hair I have left I'm reluctant to pull it out, so any useful MDT recommendations would be greatly appreciated.

MDT using SQL databases.

$
0
0

I've been using MDT for a few years now, and never opened SQL Database. This server was handed down to me and I wasn't given the chance to wipe it clean before constructing MDT. It has SQL Server 2008 and 2012.

Recently, my server has been showing some SQL errors in Event Viewer. My preference would be to just remove both versions since I don't use it directly. My question is: does MDT use SQL in any way where my removing it would cause issues with MDT's function and performance?

I solely use MDT, no WDS or SCCM. The only other program I use on this server is Hyper-V to create my images (along with ADK of course).
I'd like to clean things up on this server, including removing SQL 2008/2012 if it's safe.

Client is getting an IP address of 10.10.10.11 during deployment process

$
0
0

Hello,

I am using MDT and WDS  to image clients with Windows 10 1511 Enterprise. I have ADK 1511 installed.

At the beginning of the deployment process, the client pulls a correct IP address form the DHCP server. When logging on to the machine after the initial deployment process, I get an error stating that the client cannot connect to the DeploymentShare$.

Checking the IP address of the client shows an IP address of 10.10.10.11 which is not in my DHCP scope.

The client is configured for DHCP but it is assigned the 10.10.10.11 address. ipconfig /release and /renew fail to obtain an IP address.

I can manually change the IP address to an IP in the DHCP scope and it fixes the issue but I do not know why the client is getting the 10.10.10.11 IP to begin with.

I have also tried deploying with a MDT boot CD on a VLAN that does not have DHCP but the client will pull an IP of 10.10.10.11 in windows PE.   Does anyone know why the client would be pulling this IP address?

MDT Failure with Unreadable Summary Screen

$
0
0

I have a system fail an OSD task sequence around half way through and the failure screen HTA popup that would normally be salmon colored with a description of what the problem was, popped up white with no readable text.  It was faded and blank as if"not responding" trying to load.

What would cause this issue?



MDT2013 Update 2 - Invalid DeploymentType=""

$
0
0

I have just upgraded MDT 2013 to Update 2 (skipped Update 1) and tested one of many self contained Media deployment ISO images we have. These use a specific Task Sequence ID which is hidden from the Wizard using "SkipTaskSequence=YES" and"TaskSequenceID=..." in CustomSettings.ini.

Unlike the previous MDT2013 (non-updated) version, the install now fails to proceed past the "Wizard Ready" stage with the error 'Invalid DeploymentType of "" '.

The Deployment Type (NEWCOMPUTER) is not set in CustomSettings.ini (never has been), but the logs clearly show it is discovered correctly set (to NEWCOMPUTER) by ZTIGather and LiteTouch; but the Wizard log then reports it as equal to "" at the very end of the Wizard run. Same thing happens if I actually add "DeploymentType=NEWCOMPUTER" to customsettings.ini.

I reinstated the TaskSequence Wizard page based on a previous posting, selected my Task Sequence in the Wizard at install and voila it worked!

So what has changed? Why can I no longer skip the TS Wizard page? What is resetting DeploymentType from NEWCOMPUTER to blank? Where should I be looking? Why does an update make things worse?

Logs available, any and all help appreciated!

STEVE

MDT 2013 Missing Storage Driver

$
0
0
I have a WDS server running MDT 2013 update 1 that I am having an issue deploying Windows 7 to both an HP 6200 Pro, and HP 6300 Pro. I have the WDS names which I pulled from other machines we have which is both HP Compaq 6200 Pro MT PC and HP Compaq Pro 6300 MT. I have downloaded the drivers from HP (the large package and individual ones), imported them to the Out Of Box Drivers in MDT, create the profile for that particular model, then the task sequence to inject the drivers during deployment. I then completely regenerated the Boot Images, which it shows importing the drivers into, copy the new Lite Touch Windows PE files and when I boot, the drivers do not load. I can deploy images to the newer 600 G1, G2, 800 G1, G2 etc etc with no issues at all. I am stumped, log files do not show me the hardware ID that it is failing on, all I get is Possible Cause: Missing Storage Driver.

PreferredPlan in Unattend.xml

$
0
0

Hi,

I use MDT 2010 to deploy Windows 7 Enterprise x86 (default install.wim from Microsoft VL media).

I created a Standard Client Task Sequence. Then I went to edit it in Windows SIM.

There I added x86_Microsoft-Windows-powercpl to the specialize pass. I set the PreferredPlan to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c which should be the High performance plan.

I launched LTI and the installation went through OK. But when I looked at the installed computer it says it has the Balanced power plan.

What did I miss to make the setting apply correctly?

Regards Erik


Lite Touch error - ZTIUtility!GetAllFixedDrives (False)

$
0
0

Hi. I've been trying to solve this issue for days now.

I was trying to deploy Windows 7 Professional using MDT 2012U1 on HP Pro 3400/3500 workstations. I've generated x64 Lite Touch WIM with network and chipset drivers integrated in it.

When Lite Touch image is loaded, target computer reboots shortly after default splash screen. By starting Lite Touch with command line (F8 button) and running

cscript.exe x:\\deploy\\scripts\\litetouch.wsf

I've came across this error: ZTIUtility!GetAllFixedDrives (False).

I've also tried replacing mentioned function in ZTIUtility.vbs using function version from MDT 2010, but with little success (error was slightly different but drive related as well).

So any help is appreciated.

PS. Network is fine, NIC gets it's IP; HDD is running in AHCI mode.

MDT 8443 - Windows Server 2016 - Unidentified Network after OS installation

$
0
0

I've have a really strange issue with my MDT 8443 environment when deploying Windows Server 2016. We're using a WinPE ISO (ADK 1607) for booting our virtual machines on VMware vSphere. The VM's are using the VMXNET3 adapter.

When I boot the VM with this ISO, I fill in 'static IP configuratie' and 'Computername' during the deployment wizard. The other settings are customized in the customsettings.ini en bootstrap.ini.

After the OS Install phase, the server restarts and MDT logs in with the local administrator account. From that point there's is a delay of 10 to 15 minutes. The network shows 'Unidentified Network' and the adapter has a APIPA address. If I check the logfiles (BDD.log and SMSTS.log) everything looks fine, no errors at all.

After 10 to 15 minutes, the network connections pops up, and there's a active network connection with the static IP configuration what I've fill in during the deployment wizard! From that point the task sequence will continue.....I'm using the latest VMXNET3 driver (1.6.7.0), but also the 1.6.6.0 and 1.5.2.0 has the same issue.

Does anybody know this issue? And a solution to resolve this issue.

Thanks in advance!

/Mark

how to test in stimulated way I looking syntax

$
0
0
kindly let me know syntax for testing MDT custom.ini settings means I have created task sequence, cusstomsettings.ini, bootstrap.ini so how to test in stimulated way I looking syntax

I want to know default and priority settings in customsettings.ini needs to be different for both deployment share please help me

$
0
0
I had created 2 deployment share customsettings.ini bootstrap will be same but I noticed processing bootstrap stage (while running task sequence) it struck so just I want to know default and priority settings in customsettings.ini needs to be different for both deployment share please help me

syntax is correct any troubleshooting tip

$
0
0
I have created task sequence to capture reference image and included suspend action but I noticed suspend action is working syntax is correct any troubleshooting tip
Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>