I am new to MDT and have just started to work with this technology this week.
I am creating an installation that will have several tasks panes.
My question is how do you disable the next button on a pane until some predefined events have occured.
As an example on pane 1 I will have several text fields and drop down boxes.
I want the next button disabled or to trap the next button event so that i can validate that the user has properly completed entry in the fields on the pane.
Thanks!
Can anyone throw light on this issue? I run two MDT servers both exhibiting similar issues. I can no longer run litetouch.vbs from an administrator login where the deployment share is mapped using the username password pair as set in the custom.ini file. Running litetouch.vbs from the scripts folder manually USED to work fine. I would then choose a post deployment task from the pop up dialogue box to deploy applications as necessary. What happens now is strange; I'll get output like "cannot find script file z:\scripts\litetouch.wsf" although it is in the same folder I have just launched litetouch.vbs from. I also see on the other server an error that there is an error "y:\scripts\litetouch.vbs, line 88 character 1, network path not found, code 80070035". This line incidentally is "iRetVal = oShell.Run(sCmd, 1, true)"
Logs are not helping me much. I tried running Litetouch.wsf instead manually (as this would appear to be the step that is never being processed from litetouch.vbs) but the MDT dialogue box just sits there hanging on "Processing Bootstrap Settings". I can see the c:\Minint folder being created on the pc calling litetouch to deploy (from a local administrator login). Any ideas anyone? Please!
This has been working fine until now...and I am resisting installing again from scratch alhough I suppose it is an option.
BTW. Running MDT version 6.1.2373.0 on one server, 6.0.2223.0 on the other, OS is Windows 2008 R2 on both.
Cheers!
C Edwards
Hi Folks.
I have a working MDT 2012 setup on Server 2012. Multicasting is all good and my images are deploying smoothly.
Looking though the "What's New" for WDS 2012 it mentions that "You can apply the install.wim file while it is being downloaded"
Does anybody have any idea on how to get this working with MDT? I can't find any info about this new feature anywhere.
PS. Should add that my Windows PE is built from the Windows ADK via MDT and I'm pushing out Win 7.
Cheers
Chris
I am getting an error when I do update deployment share in MDT. It only happens if I fill the "extra directory to add" or add in "packages". If I don't have any packages or leave the extra directory blank, the share updates successfully. I am using MDT 2012 and have tried from different computers. I have enough space and full write access to the MDT share. Any help would be appreciated.
Joe
Set Windows PE system root.
Set Windows PE scratch space.
Copy: \\gvault\galdeploy$\Extra Files\x64 to c:\temp\2\MDTUpdate.2440\Mount\
System.Management.Automation.CmdletInvocationException: Access to the path 'c:\temp\2\MDTUpdate.2440\Mount\Windows\System32\bcdboot.exe' is denied. ---> System.UnauthorizedAccessException: Access to the path 'c:\temp\2\MDTUpdate.2440\Mount\Windows\System32\bcdboot.exe'
is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopy()
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
Wondering if anyone has any ideas or suggestions why my 'post cleanup' script on a Windows XP image doesn't seem to be fully running.
The image will install, but when you boot into the OS the following folders are present under the C:\ drive which should be cleaned up:
_SMSTaskSequence
MININT
LTIBootstrap.vbs
The big pain is when we try and image anohter workstation and boot using the WinPE we always receive:
Dirty Environment found
An existing ins deployment was found but is not in an expected state.would you like to ignore this in progress deployment and start a new one?
Using a very similar TS when installing Windows 7 .wim image everything is working.
ZT
Hello, at my current company we have to whitelist our devices via their Mac Address and I'm trying to figure out a way to display the Mac Address before continuing with the imaging process. I know that MDT gathers the Mac Address (macaddress01, etc) but how can I display that mac address to the user before imaging?
Any help in the right direction will help me. Thanks!
Hi,
Does anyone know a way to activate and take ownership of the Tpm without having to reboot and press f10 using command line?
Thanks,
Bobby
We have a customized installation of Office 2010 baked into our images and we have found an error in the Outlook 2010 settings. We have since updated the customization msp file on the server so that future installations will have the correct Outlook settings.
Is there a way to add a task sequence to update the Office 2010 customized settings during deployment so we do not need to create a new image and reinstall Office?
Hi All,
I have the following in my customsettings.ini:
UserDataLocation=AUTO
USMTMigFiles1=MigApp.xml
USMTMigFiles2=MigUser.xml
;USMTMigFiles3=Config.xml
ScanStateArgs=/v:5 /o /c /localonly /ue:da* /ue:maverick /ue:admin* /ue:all*
LoadStateArgs=/v:5 /c /lac
Account starting with da etc still however gets migrated. Does hardlink migration keep the complete users folder, or can you still use the scanstate args to exclude certain profiles?
Hello,
i have a big problem. I want to install some applications over mdt 2012. it works fine when i log in automatically with the administrator account of the new machine. But i want to install the applications to a domain user. Because my company want to install some new computers and i create a deployment share for a domain user and now i want to install the applications from the task sequence to the user. how can i do this?
thanks for your help!
I've seen a number of posts regarding use of the default gateway and I've used this successfully for setting locations of network resources and the like for a while, however, I have been asked now for the ability to image machines in the wider environment and the default gateways in the wild will be different to those in the Service Desk offices.
Is there some way of using partial default gateways by doing something akin to:
[Gateway] 10.100.*=Server1 10.20.*=Server2 10.30.*=Server3 [Server1] DeployRoot=\\Server1\Deploy$ [Server2] DeployRoot=\\Server2\Deploy$ [Server3] DeployRoot=\\Server3\Deploy$ [Default] DeployRoot=\\MasterServer\Deploy$
When using MDT to deploy an OS to a completely empty disk (zero partitions) - MDT will fail to make the disk bootable, it would seem:
SMSTS.log
User did not specify local data drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume A:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume D:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume W:\ has 30643773440 bytes of free space TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume W:\ is not bootable TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume X:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume Z:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
TSM root drive = TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
We do not find an available volume to store the local data path TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a global environment variable _SMSTSNextInstructionPointer=47 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a TS execution environment variable _SMSTSNextInstructionPointer=47 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a global environment variable _SMSTSInstructionStackString=41 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a TS execution environment variable _SMSTSInstructionStackString=41 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Save the current environment block TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save environment to (80070057) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to persist execution state. Error 0x(80070057) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save execution state and environment to local hard disk TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
-----
However, it's showing that it is successfully making it bootable:
LTIApply.log
Event 5625 sent: The image \\SERVER\AdminDeployment$\Operating Systems\win2008r2\win2008r2.wim was applied successfully. LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
About to run command: "\\SERVER\AdminDeployment$\Tools\X64\bootsect.exe" /nt60 W: LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Command has been started (process ID 1880) LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > Target volumes will be updated with BOOTMGR compatible bootcode. LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > W: (\\?\Volume{c3ed9a1f-cda5-19e2-b519-00155d546500}) LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > Successfully updated NTFS filesystem bootcode. LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Console > Bootcode was successfully updated on all targeted volumes. LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Return code from command = 0 LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Find the boot drive (if any) [True] [6.1.7601.18015] [False] LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
New ZTIDiskPartition : \\MININT-QSI0A4R\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-QSI0A4R\root\cimv2:Win32_LogicalDisk.DeviceID="W:" LTIApply 6/4/2013 10:43:42
PM 0 (0x0000)
-----
If I reboot and try again (now that the system has a formatted disk) - it always works. This happens 100% of the time under the following condition -If there is more than one physical disk. I can't purposely recreate this on a single disk. I'm not even touching that second disk during build, so I don't know why it would affect it. I've tried both booting from media as well as PXE - same thing each time.
Oddly, when the disk is clean to begin with, MDT chooses W: for OSDisk. When it has to clean the disk, it chooses V:.
Anyone have any ideas?
How can I create my own MDT varaibles? I would like to create a variable to identify the first two characters of a the current hostname, and use it for some further action.
TIA
Hi, thank you for this post!
I have an issue with trying to capture a Windows 7 x86 reference image from a VM but don't have any problems capturing: Windows 8 x86, Windows 8 x64 and Windows 7 x64 reference images from a VM. I currently have MDT 2012 setup on 2012 Server and using the Sysprep and Capture Task Sequence. Looking through the MDT forum I have tried the:
1. Go to your sysprep and capturing task sequence, Execute Sysprep, Options tab, Add, Registry Setting. Enter SYSTEM\Setup in the key box, and enter CloneTag in the value name box and leave the value box blank. This whole step is to add the registry key back to HKLM\SYSTEM\Setup after the sysprep completed
2. (Same as the fix suggested by Jimmy Lam-My) You can also modify the script to prevent the registry key from being deleted. Go to your deploymentshare folder and look for a script named LITSysprep inside the scripts folder. Right click, edit to do modification in the script. You can either remove theoShell.RegDelete "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" or you might want to add .// infront to turn it into a comment.
I tried adding a drive letter to the System Reserved partition, causing the "not enough space on the disk" error. I corrected these by editing the unattend file with Microsoft-Windows-PnPSysprep\PersistAllDeviceInstalls=True to the Generalize phase.
CS.ini
[Settings]
Priority=Default, ByVM
[ByVM]
Subsection=RunningAsVM-%IsVM%
[RunningAsVM-True]
DoNotCreateExtraPartition=YES
[RunningAsVM-False]
The Build and Capture Windows 7 x86 Task Sequence runs, REBOOTS and hangs at Windows is loading files. Need some help here…
Hi gang,
I'm running into an issue when imaging multiple computers with MDT 2012. Let me give some background info.
I have installed Windows 7 64 bit on a laptop in audit mode, made my configurations, sysprepped the machine, and captured a .wim using WDS (captured to an external hard drive). I then imported this .wim into MDT, created a Standard Client Task Sequence to deploy
the image, and successfully deployed it to a machine.
My problem comes up when I initiate this task sequence on multiple computers simultaneously. If I put 6 computers side-by-side and run the task sequence at the same time, only a couple machines will actually succeed. The rest fail with the following:
FAILURE ( 5624 ): 2: Run ImageX: /apply "\\CAAPPWN40\DeploymentShare$\Operating Systems\T731 (Final) Windows 7 64 bit May 2013\T731 (Final) Windows 7 64 bit May 2013.wim"
1 C:
Litetouch deployment failed. Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operating aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
BDD.log is saying that "The file or directory is corrupted and unreadable."
If I restart the computer, boot back into PXE, and run the task sequence again, this time on it's own (as opposed to 6 computers at once) it works fine.
Can anyone help?
Hi guys
I am currently setting up a deployment in MDT. I have configured a vanilla win7.wim deploy and capture task. During the deployment I have a custom script within the task sequence. I have used a script (Johan wrote it) to copy a folder from the deploy root to the "C:\Windows\Setup" folder.
Custom script location and name: "DeploymentRoot\Scripts\CustomScripts\CopyDeploymentAssets1.wsf"
Location where folder to copy is: "DeploymentRoot\Deployment Assets\Scripts"
Script:
<job id="CopyDeploymentAssets1.wsf"><script language="VBScript" src="ZTIUtility.vbs"/><script language="VBScript">
Option Explicit
Dim iRetVal
On Error Resume Next
iRetVal = ZTIProcess
ProcessResults iRetVal
On Error Goto 0
Function ZTIProcess()
' Declare the variables
Dim sSourceFolder
Dim sTargetFolder
' Define Source and Target folders
sSourceFolder = oEnvironment.Item("DeployRoot") & "\Deployment Assets\Scripts"
sTargetFolder = "C:\Windows\Setup"
oLogging.CreateEntry "Copying " & sSourceFolder & " folder to the local machine", LogTypeInfo
' Optional progess logging to the task sequence progress bar
oLogging.ReportProgress "Copying " & sSourceFolder & " folder to the local machine", 20
' Do the actual copying
oFSO.CopyFolder sSourceFolder, sTargetFolder, true
End Function</script></job>CL in task sequence:
cscript.exe "%scriptroot%\CustomScripts\CopyDeploymentAssets1.wsf"
Every time i deploy, the task sequence errors out
BDD Log: http://snipt.org/Amjd3
Failed to run the action: Copy Additional Deployment Files 1.
Incorrect function. (Error: 00000001; Source: WindowsTSManager6/7/2013 4:39:02 PM2648 (0x0A58)"
SMS Log: http://pastebin.com/pLvhi6nC
Does anyone have any suggestions why this is? I have tried adding in the task sequence:
Commandline: cscript.exe "\CustomScripts\CopyDeploymentAssets1.wsf"
Start In: %scriptroot%
But this makes no difference
We have created media in MDT only a few times and didn't notice at first, but it seems that our media is growing in size by large amounts on each capture.
We image a machine, sysprep, use ImageX to capture, import to MDT, create new media.
Last two iterations seem to have grown by 12 GB or so each; with no content change large enough to explain (did updates for last 3 months on one, and added hyperv on next.)
It's almost like it might be saving a copy of the PAGEFILE each time?
Any ideas?
Any way to cut it down?
--
HerbM
Hello,
my boot-image is hanging op the following :
Howto fix this?
Hi Team,
We have created windows 8 media for deploying x86 UEFI machines. Unfortunately we are not able to make target machines boot successfully using MDT media.
We are able to see the USB listed as bootable but goes into blue screen..hang and then shutdown automatically. I am following give articles.
http://support.microsoft.com/kb/2845990/EN-US
Any pointers will be appreciated.
Regards,