MDT 2010 Task Sequence Issue

Hi,
We are facing issue with MDT build.
We have added following new version of application and disable the old version of application in task sequence.
but when we rebuild the system its still installing old version of below applications.
Application Name
Latest Version
Old Version
Cisco AnyConnect
3.1
2.4.0202
Swivel Secure ltd Pinsafe Taskbar 1.4
1.4
1.3.2
If any one facing same issue with MDT build please provide the solution for the same.
Thanks

Thanks for the answer.
We are using MDT 2010 and its a production environment.
We are not able to do any changes in customsettings.ini.
but when add application in TS that time applications.xml and app ApplicationGroups.xml file
was change on this date.

Similar Messages

SCCM 2012 SP1 and MDT 2012 Task Sequence Templates, MDT File/Settings Packages

We're setting up SCCM 2012 integrated with MDT 2012 for our OSD. My main issue is finding actual reference material for the MDT task sequence templates when integrated with SCCM. The MDT documentation has a lot of information on variables and task sequences
outside of SCCM integration.
One thing I'd love to find information on is what's actually going on during an MDT Client Task Sequence template. I found this http://social.technet.microsoft.com/Forums/en-US/645a77b2-5be6-431d-818c-57d24b1435cc/understanding-mdt-task-sequence?forum=configmgrosd but
it doesn't delve into the kind of detail I'm looking for. I can dig up information through the MDT reference material on some things, but I just can't find anything out there that actually walks you through an SCCM/MDT task sequence template. For instance,
under State Restore what is being referenced in Install Software with base variable name PACKAGES, vs Install Applications and base variable name COALESCED APPS. And, where are you supposed to put these applications? That's just a specific example, I'm hoping
to find some kind of walkthrough.
Two things I'm hazy on are the MDT packages. What exactly are the MDT Settings Package, and the MDT Files Package? What are they used for? What benefits do you get out of using them? And, how exactly do you use them? I know one of them has something to do
with customsettings.ini, but what's the point of using SCCM with MDT if you still have to muck around in the customsettings.ini file?
Either way, it seems like there are a lot of references to SCCM task sequences, and a lot of references to MDT task sequences. But, not together. Which is a bit annoying since the MDT-integrated task sequence templates are very obviously different than either
SCCM or MDT by itself. Any help would be appreciated, even just information on where to look. Maybe I'm just really bad at finding reference material for SCCM/MDT. Thanks.

When MDT integrated with SCCM, We need the following MDT components to be created:
MDT Boot image
MDT Toolkit Files
MDT Settings
The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA Refer here:
http://www.windows-noob.com/forums/index.php?/forum/98-frontends-and-web-services/
MDT Files once created, you will find UDIWizard_Config.Xml file in which you can start User driven Installation OSD using UDI designer.
Refer these links for better understanding:
http://www.windows-noob.com/forums/index.php?/topic/5131-using-sccm-2012-rc-in-a-lab-part-16-integrating-mdt-2012-rc1-with-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5221-using-sccm-2012-rc-in-a-lab-part-17-using-mdt-2012-rc1-within-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5250-using-sccm-2012-rc-in-a-lab-part-18-deploying-a-udi-client-task-sequence-with-mdt-2012-rc1-integrated-in-configuration-manager-2012/
Thanks, Prabha G
Thanks for the quick reply. But, what about the MDT Settings Package? Also, both have a pretty big folder structure for each package. Surely it does more than just provide a couple xml and ini files? I'm not looking for anyone to spoon-feed me the information,
but at least a pointer in the right direction for finding the reference material. It seems for SCCM/MDT integration you have to go all over the place finding scraps of information to put together.
Also, any info on the SCCM/MDT task sequence templates? Thanks.

Setting the Administrator password on a MDT Server Task Sequence

I've created a SCCM 2012 R2 CU3 MDT 2013 task sequence using the Server Task Sequence template to deploy Windows Server 2012 R2. I'm not doing a capture but just using the .wim file from the source DVD. The problem I'm having is setting the local admin
password in Apply Windows Settings. It's not taking the password that I've assigned it. I'm not sure how many others have created a Server Task Sequence or not but I'd be interested to know how to get around this problem.

Sorry, in Apply Windows Settings I've selected "Enable the account and specify the local administrator password" and entered the local password there. When the system is imaged and I try to log in locally it gives the the error "The user name
or password is incorrect. Try again." error.
I have checked that the local administrator account is enabled so I know it's not that and I've tried multiple times. I even took one of our client task sequences that I know works, made a copy of it, and added the Server 2012 R2 install to it and get the
same result.

OSD SCCM 2012 R2: MDT integrated task sequence central logging not working

Hi,
Please advise on making dynamic logging work for SCCM 2012 R2 MDT integrated tasks sequence.
This is what I specified in customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
; Copy Logs if en error occurs or when deployment is successfully completed
SLSHARE=\\sccmserver\OSD\Logs\MDT
; Enable Dynamig Logging
SLSHAREDynamicLogging=\\\sccmserver\OSD\Logs\MDTDynLogs\%OSDComputername%
UserID=administrator
UserDomain=ourdomain
UserPassword=ourpassword
Jan Hoedt

I keep on getting access denied though when I connect in a dosprompt with the credentials I can make a connection.
Mapping server share: \\ourdomain.com\share   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 5 seconds.   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 10 seconds.   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 15 seconds.   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 20 seconds.   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:09:04   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 25 seconds.   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
ERROR - Unable to map a network drive to \\ourdomain.com\share.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
An invalid SLShareDynamicLogging value of \\ourdomain.com\share\PackageSources\OSD\Logs\MDT-DynLogs\computername was specified.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
Jan Hoedt

SCCM 2012 R2 and MDT 2013 Task Sequence Bugs

Any links that list issues with the default MDT 2013 deploy task sequence: UEFI, local administrator password, Machine OU settings, OS installation partition and computer replace scenario.

Hi,
If you want to file bugs or feature requests, you'll need to go to the MDT and ConfigMgr connect site:
https://connect.microsoft.com/ConfigurationManagervnext/Feedback
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT Capture Task Sequence not working correctly

Hello All<o:p></o:p>
I need some help to tell me what I am doing wrong. I am using Hyper V and trying to capture a image of Windows 7 x64. From within the OS I run the
Litetouch.wsf from the deployment share. I get the normal MDT Wizard windows. I pick my capture task sequence and everything looks like it is running fine sys prep happens and I but back into windows PE I start to process the rules again and I am taken
back to the Select task sequence screen in WinPE. If I pick the capture task sequence again the deployment fails. <o:p></o:p>

(posting for anyone else that found this page, this was my fix)
I had the same problem as the initial poster apart from what I wanted to capture was a 'real' pc. The reason my 'capture' task sequence wasn't booting into WinPE from the local disk and continuing on with the capture was because the local disk was
being wiped when the boot wim - LiteTouchPE_x64.wim, was being run.
A few weeks prior to me wanting to capture a PC I'd been working out how to stop the occasional error when you boot a PC off the WDS server - “The Task Sequence Has Been Suspended”. I was particularly interested in stopping this error as I want to
remotely start a Win7 install on a PC, this error would stop the install happening but I wouldn't see this error and end up visiting the PC only to find the install hadn't really started. After googling around, I found a page that explains how to edit
the unattend.xml file in the boot image - LiteTouchPE_x64.wim, in the xml file to run the command wscript.exe X:\Deploy\Scripts\LTICleanup.wsf. Sounded good so I done what the page said (myitforum.com/cs2/blogs/cnackers/archive/2010/10/20/microsoft-deployment-toolkit-lite-touch-lti-the-task-sequence-has-been-suspended.aspx)
but it didn't stop the message appearing. In the end I fixed this problem by adding the line 'SkipWizard=YES' in my customsettings.ini file. I didn't remove the LTICleanup.wsf from unattend.xml, it didn't seem to do any harm, that was until I tried
to capture a PC.
When I ran though my 'sysprep and capture' task sequence, the PC would sysprep ok and then reboot, ready to capture it. Instead of the 'capturing a WIM file' sequence I was expecting to see, I, like the original posted got shown the list of available
task sequences window. If you try again to run the capture sequence, it will fail as this has to be started in a running Windows environment, not in WinPE. After several hours wondering what is going wrong, I dawned on me what was going wrong,
the LTICleanup.wsf was being run when the boot image was being run and wiping my disk, a disk that was ready to run an existing task sequence, the capture sequence, no wonder it was failing. Removing the LTICleanup.wsf command from within unattend.xml
or rebuilding the boot image (by running 'Update Deployment Share' within MDT 2010) fixed the problem, the capture now worked.
Hopefully this will help someone else like me who was wondering what was going wrong with a capture.

What determines whether an application gets a green check or a yellow warning sign in the deployment summary screen when using an MDT/UDI task sequence?

I am trying to get Office 2010 to install using a UDI task sequence, and it IS installing, but it has a yellow exclamation point next to it at the summary screen after the task sequence completes, as does another app I am trying to install.
The apps that use an .MSI are fine, and get the green check, but the two apps that use .exe for their installers get the yellow warning sign. I assume this has to do with exit codes or detection rules, but I am very new to SCCM (using 2012 and MDT
2012 Update 1), so I need some help.
Thank you!
EDIT: This probably has to do with the fact that SuccessOrFailureCode being blank. I have been pouring over .vbs scripts and logs, but they all seem to indicate that my application installs just fine, with an exit code of 0. Where does this screen
get the SuccessOrFailureCode?
Like
This
Quote
MultiQuote
Edit

I have some updated info on this problem.
I am trying to install Symantec Endpoint Protection with a custom wrapped .EXE file, and I have created detection rules for the install.
According to AppEnforce.log, SEP is installing and returning an Exit code of '1', and that is being handled with my custom return code handling, which I've defined as a 'success'. However, the deployment summary is still showing a yellow exclamation point
next to the SEP install, and the SuccessOrFailureCode is blank.
Why isn't the SuccessOrFailureCode equal to '1'? Where is the disconnect between the AppEnforce.log and the deployment summary.

Task sequence issue[OS Deployment]

Hi All,
we have created a test environment for OS deployment. we are using SCCM 2012 SP1. Dp is installed on same server. SCCM site server OS is windows 2008 R2. we have captured the image using MDT tool. We have problem that whenever we do a deployment we
get below issues.
1. OS installed on next available logical drive(in my case it's D:\)
2. when we create a task sequeste using task sequence veriable(http://sccmfaq.wordpress.com/2013/02/14/sccm-2012-sp1-install-windows-7-to-drive-letter-c/
) it gives us error "There is not enough space on the disk. (Error: 80070070; Source: Windows) ApplyOperatingSystem"
3. When we create a task sequence and provide dive name for "Apply operating system", it works fine on a system which has two partition(c & D) but which has one drive( only C) gives error("There is not enough space on the disk. (Error:
80070070; Source: Windows) ApplyOperatingSystem" ) as mentioned in 2.
Any help will be highly appreciated.
Rakesh Kumar

Thanks for the suggestion but that did not help me either.
To brief more about the scenario,
I have captured the image using MDT and deploying the image via SCCM 2012 Sp1.
I also found that the same image when deployed via MDT wipes the second parition (D:\ drive). IS this is the root cause of my problem. Is there any way i can customise and handle it within TS.
Regards, Shweta Karalkar

SCCM OSD and MDT 2012 - Task Sequence query

Hi All
I have single server SCCM 2012 R2 server with MDT 2013 successfully integrated. I'm looking to create a 'Sysprep and Capture' type Task Sequence within SCCM, so that this can be done via PXE rather than SCCM's more manual 'Capture Media' method. Just
wondering if anyone has thoughts on this, experience, pointers etc?
Couple of options that look possible are:
MDT Toolkit Package - include in SCCM based Task Sequence. Would it then be fairly easy to mimic ts steps detailed in MDT's existing 'Sysprep and Capture' TS, but within SCCM?
SCCM TS Steps - I've seen there are a number of TS Steps that look like they may enable OS Capture, but if so, bit confused there isn't more documented \ blogged on this kind of TS, would have thought this was a common requirement for a
SCCM TS? (TS Steps of interest within SCCM: 'Prepare Windows for Capture' and 'Capture Operating System Image')
Any assistance much appreciated!
Kind Regards
Andrew

There is a bit of debate about the best way to capture reference images. Check out this good blog that reviews the options:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/163/The-battle-begins-Building-the-perfect-reference-image-for-ConfigMgr-2012.aspx
Having said that, you can certainly create a capture task sequence in SCCM. If you choose to create a new task sequence,you should see a build and capture option. Simply create a build and capture task sequence and then remove the build steps.
You will be left with:
I've used this method in certain cases.
Or as you said, if you are integrated with MDT, you can create an MDT task sequence to do the capture or add MDT steps as needed.
Hopefully that helps!
Jeff

MDT 2012 - Task Sequence Not Completing

I'm a complete novice with MDT 2012, but I have had pretty good luck getting a deployment for Server 2008 R2.
I have a reference system, and I do a very vanilla sysprep and capture using the template task sequence with no changes.
My deployment has a few app installs and other configuration items, but nothing too exotic.
My problem is this: during deployment, after applying the system from WinPE, I perform the final reboot. At this point, the expected action is for an autologon to take place, and for the local Administrator account to run c:\Litetouch.vbs, which does some final
cleanup and a few tasks that require the target system to be running.
This isn't happening on my system. And a look at the registry shows that the autologon stuff has not been set up, so it won't ever happen. It's not a matter of having an incorrect account, or a count of 0, none of the autologon registry keys are even present.
In trying to solve this (I believe it worked when I first started!) I've stripped down my deployment to a pair of task sequences that have no customization
at all in either the capture or the deployment task sequences, and still no luck. So I believe that something has changed in my reference system - but I unfortunately can't roll back.
What is driving me a little nuts is that I can't tell when that autologon information is supposed to be inserted in the registry. There is code in Litetouch.wsf that appears to do it, in function PopulateAutoAdminLogon, but I can't come up with a scenario in
which this function gets called. I am guessing that perhaps sysprep does it when creating the WIM, but I can't seem to find good information on that.
I've done a lot of searching on this, and unfortunately the answer space is cluttered with people who have a similar sounding but completely different problem - they want their deployed system to do an autologon, and after deployment their system comes up with
the logon screen instead of doing what they want. I've seen a few people post similar problems to mine, but nobody has received an answer. This one is pretty close, it suggest I might have a group policy item that disables the local admin account, but I don't
think it hits the mark for me.
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e625aa88-2415-4a2a-9e79-ac6b37119c27
So in a nutshell: when deploying a system using MDT 2012, at what point do the autologon items from unattend.xml stuffed into the registry for use after state restore/reboot in the task sequence? And what can go wrong with that?
- Mark

Same here, can't find any solution though. Did you ever work it out?

MDT 2013 Task Sequence return to command prompt

Hey All,
I created a fresh MDT 2013 share on a 2008 R2 machine that also holds the WDS for PXE.
Right after it applies DISM, it restarts back to a command prompt, my logs don't report any errors. When I type exit, the machine reboots and the task sequence continues as normal. Here is the peice in my dynamic log where it stops logging. Last line is
where it stops and I type exit.
ZTIdrivers processing completed successfully.
ZTIdrivers 11/3/2014 11:11:59 AM
0 (0x0000)
Event 41001 sent: ZTIdrivers processing completed successfully.
ZTIdrivers 11/3/2014 11:11:59 AM
0 (0x0000)
Will boot into Windows PE architecture x64 to match OS being deployed.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
OSDTargetDriveCache was determined earlier : C:
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Property OSDTargetDriveCache is now = C: ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
Property OSDisk is now = C: ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
WinRE is not enabled, Skip. ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
ZTIWinRE processing completed successfully.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Event 41001 sent: ZTIWinRE processing completed successfully.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Property PHASE is now = STATERESTORE ZTINextPhase
11/3/2014 11:12:00 AM 0 (0x0000)
ZTINextPhase COMPLETED. Return Value = 0
ZTINextPhase 11/3/2014 11:12:00 AM
0 (0x0000)
ZTINextPhase processing completed successfully.
ZTINextPhase 11/3/2014 11:12:00 AM
0 (0x0000)
Event 41001 sent: ZTINextPhase processing completed successfully.
ZTINextPhase 11/3/2014 11:12:01 AM
0 (0x0000)
A little further along I noticed it changed the state to dirty. But I don't think that's related. Could be wrong.
-G

While in Windows PE, the cmd.exe window will appear in one of two scenarios:
1. The user pressed the F8 key.
or
2. Litetouch.wsf returned some kind of failure during processing. This is weird.
Under what instances would the Litetouch.wsf crash (fail)? Well, the most common scenario is that there are some mixmatched source files in MDT. Updating the deployment share could fix the problem.
The only other way to know for sure is to run the program in a debugging mode. When you first boot up to WinPE, instead of starting the deployment wizard, when you are at the welcome wizard, break out into the cmd.exe prompt (not by pressing F8). Then
run the command:
cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture
At the end of the script we should see an error with a line number.
If we don't see an error then something else is going on.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2012, Task Sequence Comments, can I change to have line breaks?

I added comments to a few Task Sequences. They all run into each other, I'd like to be able to type a sentence, press enter, then put another, but when I do this, that's not how it looks in LiteTouch.vbs.

I wanted to do the same thing and could not come up with a nice way to do it. Ended up using the hidden character Alt+0160 to space it out. Looks good now but took some trial and error to get it all lined up.

Wiping a disk with MDT task sequence?

I'm thinking that I could use MDT/WDS to do a secure disk wipe for old computers. Has anyone implemented something like this with MDT?

Take a look at the "Client Replace" Task sequence template supplied with MDT
This Task Sequence is designed to de-commission a client computer, first saving the data to a external network share.
The task sequence also calls the ZTIWipeDisk.wsf script to peform a multi-pass wipe of all partitions.
Then again, if you have machines with sensitive information on them, you should be using disk encryption like Bitlocker to ensure that the data is protected. Simply install a new OS without suspending the old BitLocker protection.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Multiple OS options in a single task sequence

Hi
I work as a contractor for a client which has three separate computer models but want their systems set up in almost the same way.
As almost all steps are alike, I tried to set up a single task sequence but with multiple "Install Operating System" steps (one for each model) and filtered them as per model (manufacturer is the same).
Unfortunately it appears that while it displays the correct label for the task, in reality it only picks the top image for the deployment and it keeps using the top image even if I disables that task or include a filter to use the top image if the manufacturer
both is and isn't Fabricam to make sure the condition will never be true.
Is there a way for me to get around this? I would prefer to keep it as a single task sequence as if my client want a change in the deployment, I only need to make the change in one location while maintaining easy overview of all steps.
Peter

The MDT litetouch Task Sequence is designed to have 1:1 relationship with the selected Operating System.
It might be possible to dynamically change the OS during deployment, but I wouldn't recommend it.
Remember, you can "clone" task sequences by taking the ts.xml reference image from your \deployment\share\TS\ts.xml share and copying it to Program Files\microsoft deployment toolkit\templates folder (don't forget to rename it within the <sequence
name"xxx"> element).
You could customize the cs.ini file to auto-select the correct Task Sequence to run based on the platform type, to abstract that selection from your customer.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

SCCM Task Sequence Fail to Connect Share Folder on SCCM server

those days we have an task sequence issue- can't connect to share folder on the SCCM server
Enviroment
in our network, we have DHCP server, DC server, DNS server. we are trying to bring up an new server to boot from the SCCM server. we have two VLAN in our environment. VLAN 54 and VLAN 200.
the DHCP/DC/SCCM/DNS are all running on VLAN200
Issue
we have those steps in this task sequence
Installing OS
setup windows and configuration manager
connect to an share folder to SCCM(run some sicrpts)
run the scripts
install the sqlserver
1. when the VM running on VLAN 200, no issue on all the task list, we can access the share folder on SCCM server.
and task sequence run ran success.
2. but when VM running on VLAN 54, issue came. when the task sequence run into the [Setup Operation System]/[Connect to network folder]. this step can't get the share folder to sccm server.
then the task sequcne was quit, so we logined to vm have a look. run the ipconfig/all. no IP address get from DHCP server.
but when we run the command ipconfig/renew on this VM, then we can get the IP address from DHCP server.
we have tried an alternative solution like below.
add an step ipconfig/renew before connect to share folder, then the task sequence can connect to share folder, but when the task run into last step- install the SQL from package.
unfortunately, we came cross another issue.
Failed to invoke Execution Manager to Install Software for PackageID='GDL00008' ProgramID='Install SQL 2005 Standard SP4' AdvertID='GDL2001F' hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)
InstallSoftware failed, hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)
Quetions
so we suspect there may something to do with network, but the network team said there is no issue on their side. so what i can go to research, how can i fiind the root cause or how to confirm it is an network issue. do you guys have any idea on this issue?

The error means RPC server unavailable. TS needs to invoke Execution Manager by RPC. This may be caused by the issue of RPC starting. I suggest you check the RPC service availability first. Another try is to add a restart computer step before installing
SQL. If still no avail, add a Delay "cmd.exe /c timeout /t 900".
Regarding the connecting network share issue, seems the network services has not been initializing or ready. Another possibility is the DHCP time out. Check the Event log and this may give you some clues of why the network is not ready or DHCP cannot get
IP address. Network Monitor can also be used to monitor the IP helper when the Client try to send DHCP request after reboot.
Juke Chou
TechNet Community Support

MDT 2010 Task Sequence Issue

Similar Messages

Maybe you are looking for