I have noticed that after i enabled UEFI on a Dell Laptop the boot sequence uses: Windows Boot manager
Upon re-imaging the same laptop i now see 2 Windows Boot Manager entries in the boot sequence.
Does that mean that one entry is created each time I image a computer? Do i need to add some logic to a TS to get rid of old Windows Boot Manager entries?
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
Hello,
I am trying to get up a Windows 10 task sequence for the first time and am running into some issues. I have created a reference image for Windows 10 using MDT and then imported the custom WIM into a deployment share. However when I select the Windows 10 task sequence, the TS stops shortly after installing the custom WIM. The step that it fails at is during the action Add Windows Recovery (WinRE). The error is shown in the photo below.
After clicking ok about a dozen times the task sequence resume, reboots, then gets stuck at the run once Welcome setup screen for about 20 minutes (this should be considered a bug IMO, although I know it is not really).
I have tried creating a new clean task sequence, and besides generating and saving a Sysprep file, do not touch anything. Though I do find it odd that I have to manually set the Display setting in the OOBE step and clear the OOBE default network profile (that is deprecated but for some reason defaults to Work).
With the new clean task sequence, the success screen/end of deployment screen is eventually shown and seems to boot OK. With my customized TS it fails spectacularly straight to the desktop though I belive this may be an error somewhere in my Sysprep or modifications.
In both my reference share and deployment share, I have a fully functioning Windows 7 and Windows 8.1 deployment system set up and being used. Both deployments shares were created from scratch after upgrading my workstation to MDT 2013 Update 2 and Windows ADK 10 in the last few weeks.
Any ideas where I went wrong or what could cause this weird behavior from just Windows 10? Thanks.
BDD and SMST log located here for the fresh/clean task sequnce: https://drive.google.com/folderview?id=0BysFVmHr4PKmYXdPOGV3dHRRVm8&usp=sharing
Javier
I have an environment with about 40 (and growing) deployment shares with various connection speeds around the globe. I have setup DFSR (remote differential compression role feature installed) to replicate content and all seems to be working fine (minus the initial sync at remote sites with 1MB connections)!
I have a bootstrap.ini that has paths entered to each deploymentshare based on the gateway of the machine. New site comes up, sync content (or copy if someone has source), update bootstrap, update deployment share to create new boot wims, and within 15 minutes, bootsrap.ini and boot wims are replicated throughout the environment.
I have a deployment share that I specifically have set up for my build and capture. Following Johans post on reference image building (see Build it like a boss! and Back to Basics - MDT 2013 Update 2). Captured images are rougly 9-12GB (Win7EntSP1, Office 2007, Skype For Business 2015, All Security and Critical Patches, Antivirus). I try to keep the reference images up to date for my admins with virus definitions and windows updates, so captures are done monthly - so really only changing updates and definition files.
My issue:
I haven't bee able to grasp how to correctly utilize DFS and its remote differential compression to distribute updated captured images to my sites. I tried it once by manually copying the captured wim from my build Capture folder into my production operating systems deployment share and it didn't work out too well. So right now, i create a new wim each time, import it, wait for it to replicate, change my task sequence, and delete the old captured WIM - which seems counterproductive as its not really using dfs to its fullest.
Is there a specific way to import the monthly captured wim OS into MDT and have it only replicate the deltas, instead of forklifting entire new wims?
Hi,
I've just moved the MDT database to a new SQL server, and there seems to be something I've missed or gone wrong in the process.
I detached the DB from the original server, and then restored the DB from backup to the new server (which is not the MDT Workbench/WDS server).
I have set the necessary user permissions (for the UserID) on SQL for login, and the SQL database as db_datareader.
Connecting to the MDT database again in the Deployment Workbench seemed to go OK - the Database shows up as connected, and I can browse the database via the Deployment Workbench.
I re-ran the Database rules wizard and reset the rules we want - just Computer Options>Query Computer Specific Settings and Query for Applications to be installed on this computer, with all else unticked. I checked the CustomSettings.ini and this looked ok and updated, and checked this against the Rules tab on the Deployment Share (which appears to just look at the CustomSettings.ini).
I have even Updated the Deployment Shares and replaced the Boot Images, just in case, and rebooted all the servers.
However when now PXE boot, it gets to the Custom Settings screen, takes a LONG time to go past the CSettings and CApps, and then has none of this information when it gets to the Task Sequence screen. I assume therefore that it's failing to make the necessary connection (though I'm not sure where this would be logged as it's before the task sequence has begun).
I have set the necessary user permissions on SQL for login, and the SQL database as db_datareader.
Any help appreciated!
Ben.
Hi,
Are there any good resources for configuring and using the MDT database WITHOUT SCCM? I don't have SCCM. The database is set up, but does not seem to be applying my settings. CS.ini is at it's defaults following DB creation. Everything I can find online pertains to using MDT with SCCM, and there is nothing on how to actually use the database. Things like syntax for fields like "DriverGroup" etc...
Any other place I can look?
Thanks
Jason
image was working on 3/3, on 3/4 it stopped working. Every application install fails like this, but the sequence keeps chugging along, despite it not being set to continue on error.
LOG:
Change directory: Z:\applications\Microsoft RSAT Tools\Windows 10
WARNING - unable to set working directory: (-2147024893)
then Eventually:
Application Microsoft RSAT Tools returned an unexpected return code: 2
I have been unsuccessful in trying to get the hotkey features integration driver to install as an app on four different ThinkPad models. I import the app into a subfolder listed under Applications [MDT Share\Applications\Drivers Setup\ThinkPad All Models) and specify where the source files are located and verify that the source directory was populated and is correct.
Then I update the media folder and as I view the real-time output as the image is being updated it appears that it completely skips the Drivers Setup folder altogether. I have verified that all of the folders involved are active and not disabled and that the imported app folder is included in the selection profiles for all of the models that need the hotkey driver. I created 4 separate task sequences (one for each model) and have verified that they are also enabled and pointing to the correct app package. I also verified that the entry was created in the Applications.xml file and that the GUID and source directories match what is shown in the deployment share, but then when I update the deployment share the hotkey driver app is no where to be found in the Applications folder in the MDT media.
I deleted the driver app, verified that the app folder was removed from the MDTShare\Applications folder and reimported the app several times, but with always the same results when I update the media.
Please help.
So recently installed the MDT 2013 Update 2 along with the associated ADK (10.1.10586.0).
Now all the sudden my latest Deployment share for my spring 2016 build gives me the error shown below. No matter what WIM I am attempting to deploy my "Language to install: " field is blank. I have even imported my WIM from last years build, which works fine from its 2015 deployment share, but in this new deployment share the language is also blank.
I am at a loss for what to try next, any help would be greatly appreciated.
Hi All,
I have been a long time user of MDT since version 2010/Windows 7. I am now using the latest build of 2013U1 (re-release) with a Windows 10 1511 ISO and having some trouble.
When I specify HideShell=YES in CustomSettings.inithe deployment completes but all applications fail to deploy - errors are listed in the Deployment Summary window. If I change the value to No all applications deploy successfully:
Office 2013 ends with error 1618 (another installation is running)
App deployed using batch file ends with unexpected error -2147467259
I have created a new deployment share and new task sequences with this latest MDT build to make sure I'm using all the correct versions.
I'd like to be able to use HideShell as it is cleaner and reduces the likelihood of human error. Can anyone point me out to what I'm doing wrong?
Please have a look at my BDD.log here:
https://www.sendspace.com/file/qnnh7w
Thanks
I have created a New Folder in my Task Sequence, all the logic needed to enable TPM , install MBAM client and start encryption is there.
I want to add a dialog box when the TS starts where the user can choose whether he wants to run all the steps in that folder.
I would like to be able to use the same logic as Bitlocker in CS.ini, i would put SKIPMBAM=NO and the user would have to select either to install Mbam or not.
I have tried the Wizard Editor but the lack of documentation is very challenging.
My HTML code is:
<H1>Choose to install MBAM Client and Start OS drive Encryption or not</H1><table><tr><td><input type=radio id="NoMbam" name="Mbam" value=No checked language=vbscript onclick=ValidateMbam AccessKey=D></td><td><Label class="Larger"><u class=larger>D</u>on't install Mbam client.</Label></td></tr><tr><td></td><td><div>The operating system will be deployed but no Bitlocker encryption will be performed.</div></td></tr><tr><td colspan=2> </td></tr><tr><td><input type=radio id="YesMbam" name="Mbam" value=YES language=vbscript onclick=ValidateMbam AccessKey=A></td><td><Label class="Larger">Install <u class=larger>M</u>bam client and start Bitlocker encryption.</Label></td></tr><tr><td></td><td><div>The operating system will be deployed after which Mbam client will be installed and encryption started</div></td></tr><tr><td colspan=2> </td></tr><tr><td colspan=2> </td></tr></table>
But i have no clue what to do next.
Do i need an Initialization and validation steps or one simple VBS script would do here?
I have started writing the following script mimeting a post i found online:
Function InitializeMbam
'Get values from CS.ini
Mbam.Value = Property("Mbam")
'Determine the default value
If UCase(Property("Mbam")) = "YES" then
YesMbam.checked = true
Else
NoMbam.checked = true
End if
Else
NoMbam.checked = true
End if
ValidateMbam
End Function
Function ValidateMbam
Dim IsMbam
IsMbam = YesMbam.checked
If not isMbam then
Mbam.disabled = true
Else
Mbam.disabled = false
ValidateMbam = true
End if
End Function
Upgrade MDT 2013 Update 1 -> Update 2
Updated Deployments
I have a task sequence with just Windows Update. I have configured FinishAction=Restart in custom.ini. After Windows Update is completed, system does not restart. The line "lti initiating task sequence-requested reboot" is present in the logs,
but nothing happens.
There was no such issue on MDT 2013 Update 1
Any ideas?
Hi All,
I already have a suspect for this issue (the server hosting the deployment share), but just want to check with other MDT users to see if I'm missing something and barking up the wrong tree.
We have a Windows 7 build for capturing our reference image, and this has started saying <Message containing password has been suppressed> in the completion summary, sometimes once, sometimes more, and sometimes none.
Our last change (last year, and several captures before) was to start using ZTIWindowsUpdate.wsf to patch the image (which had already worked a number of times), so I turned off those entries in the task sequence and found I was still getting the same error.
The build doesn't have credentials set in customsettings.ini or bootstrap.ini, so I added some in to customsettings.ini and built two PCs about 30 mins apart from the same server with the same build and this time on one PC got "The network path was not found" twice instead, the other PC had no errors.
I tried it again and then got the following where the WIM failed to be captured this time. I've done it since and it worked.
The server was up, and this worked since (though still giving us the <Message containing...> error).
I've had a look at the logs, and each time (with no credentials) I think it seems to sometimes struggle to authenticate, and then just work and continue.
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="19:19:01.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">These builds are done in hyper-v, and I've set up another test VM on another hyper-v server and we still get the <Message containing...> error.
Does anyone have any ideas what could be causing this? Am I missing a clue?
Thanks
I am new to using the MDT. I have installed and configured it on my deployment server per Microsoft's guidelines. I am attempting to upgrade domain joined Windows 7 x64 Pro machines, but the process eventually hangs on the client and closes. Using the monitoring tool within the workbench, I can see that the process always fails at the "Upgrade Windows" step (8 of 23.) I'm using Windows 10 Pro x64 media obtained from the Volume Licensing site, and I've setup my task sequence per the guidelines. Here's a quick snapshot of the log from the point at which the process fails:
It looks like the process is calling for a reboot after the initial failure, but that never happens.
I'm able to browse out to the OS folder on the production share from the client machine, and initiate the upgrade manually without any issue. I've seen similar posts with the same errors caused by language variations with the chosen media, but all of my media is the same version as the client OS. Just for the sake of troubleshooting, I added WindowsUpgradeAdditionalOptions=/compat IgnoreWarning to the CustomSettings.ini, but that doesn't work either. I'm at a bit of a loss. Any info or ideas would be most appreciated.
Hello. Has anyone else noticed that clicking the UDI Wizard preview does not do anything ?
I have tried on several systems with the same result, nothing happens.
I monitored the activity with process monitor, but the processes it fires seems to exit normally.
eshe
I have configured the customsettings.ini
;Bitlocker
BDEInstall=TPM
BDERecoveryKey=AD
Enabled the tasks in the Task Sequence, with the TPM check variable (ZTICheckforTPM_v2):
TPMReady equals TRUE
TPMActivated equals TRUE
The script do give an FALSE on TPMReady
I configured the Group Policy in AD.
But in the end the command: manage-bde -status gives me:
Percentage encrypted: 100%
But no Key Protectors (Not Found)
When I enable Bitlocker via right clicking the c:\ drive. and let Windows print the protection key (and backup) to a file.
In AD, the computer object get's immediately populated with the recovery key.
Can anybody help? Don't want the manual actions to enable Bitlocker.
MDT 2013 Update 2
Windows 10
Lenovo X250