MDT Task Sequence with standard "Create Task Sequence Media" image capture?

Hello,
After much research and a lot of exhausted attempts/hours between two of us we have broken down and decided to ask a very direct question. Is it possible to run an MDT Task Sequence with an image captured within SCCM and not MDT?
Reason for asking is the sequence fails every time with the error:
“Task Sequence: NAME has failed with the error code (0x80070490).”
I should note that there is no smsts log because it fails during the install and comes back with "no OS available" and there is no sccm client on the machine either. From what I could gather the error code is related to the HDD and I have tried
every setting within the task sequence I know of in different combinations to no avail. Which led us to wondering if maybe the whole process isn't even possible since we are using an MDT task sequence with an sccm image capture.
The standard task sequences work fine with the sccm image capture, but as soon as we try to the MDT sequence it fails. ANy advice/information/help on this is much appreciated.

I can't thank you enough, that was exactly it. I should have known that it would be something so simple, I've been going crazy looking through the task sequence properties trying to figure out what I could be missing.
No problem at all, happy to help! I was in the same boat driving myself crazy looking at the task sequence properties. I just happened to stumble upon that setting and decided to give it a shot since I had exhausted seemingly every other avenue.
Also, to answer your other question, in a standard task sequence, you can name the computer by using the collection variable "OSDComputerName". Just right click the collection you have your task sequence deployed to, choose properties, and then the collection
variables tab. Click the starburst, enter the variable name OSDComputerName, uncheck the box for "do not display" (I think that's the setting) and apply your changes. When you run your task sequence again, you'll choose your TS from the list, click next, double
click OSDComputerName (just clicking next will skip it and begin the TS), enter the computer name, click OK, and kick off your TS.
I'm still finding my way around SCCM since it was thrown into my lap with no prior experience so I'm happy to help when someone is stuck. I've been there more times than I can count and others have helped me.

Similar Messages

Image Capture - Automatic Task

I wanted to put an applescript to post process images downloaded from my digital camera. I tried putting the applescript file in the following directories:
/Library/Scripts/Applications/Image Capture/
/Library/Workflows/Applications/Image Capture/
/System/Library/Image Capture/Automatic Tasks/
And restarting Image Capture and restarting computer and nothing shows up in the Automatic Task list. I tried selecting Other... but Automater or Applescripts are unselectable.
Any ideas?
Thanks
Tom
iMac G5 Rev.B Mac OS X (10.4.4)
iMac G5 Rev.B Mac OS X (10.4.4)

That's helpful, but doesn't provide a way to get the automatic task that Image Capture offered in 10.5. A folder action is not nearly as good, because typically one downloads multiple items off a camera, and you want the automatic task to run after this completes. I believe a folder action is triggered when the first item is added.
(You can add a kluge to the folder action script to wait for some amount of time, but that is a poor way of doing things, since you don't know the right amount of time; too short and you miss items; too long and the items aren't adjusted before you want to play with them.)
I'm puzzled why Apple would take away such a handy feature.

Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1. I'm using the standard client task sequence in MDT.
The MDT task sequence consistently fails after the reboot in the "Postinstall" group. The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
completes successfully. There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
Successfully complete the action (Restart Computer) with the exit win32 code 0
Sending status message
Executing in non SMS standalone mode. Ignoring send a task execution status message request
Set a global environment variable _SMSTSLastActionRetCode=0
Set a global environment variable _SMSTSLastActionSucceeded=true
Expand a string %_SMSTSMDataPath%\Logs
Deleting file without retrying
The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state. Would you like to ignore this in-progress
deployment and start a new one?"
I have found one post that suggested modifying customsettings.ini with HideShell=Yes, which I tried. It didn't help.
I am not sure why MDT thinks the reboot was unexpected? Has anybody run into this? What steps can I take to narrow down the problem?
Any help/suggestions are appreciated.
Thanks,
FP

Thanks for your reply Phil.
Setuperr.log is empty, zero bytes. Setupact.log looks good to me, it has these entries at the end:
OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
OOBELdr.exe exiting with code [0x0]...
Process exited with exit code [0x0]
c:\windows\panther\SetupInfo succeeded.
c:\windows\panther\setupinfo.
Windeploy.exe exiting with code [0x0]
SetupSQM Started
Panther path is C:\windows\Panther
SQM not opted in
SetupSQM is finished
Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini. I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking...
Any suggestions are appreciated.
Thanks,
FP

Missing create MDT task sequence

I have been put in charge of the imaging/task sequence creating of SCCM for my company. I had the sysadmin here set up the MDT integration with SCCM but i still don't see a "Create MDT Task Sequence" in the sccm console. If he logs into the server
he can see it, but if him or i do it through the admin console there is nothing.
thanks

You need to install MDT locally on the same system as the console you are using and then integrate MDT with your console as these options are local console extensions. Make sure you run the integrate task elevated also.
Jason | http://blog.configmgrftw.com | @jasonsandys

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

SCCM 2012 with MDT: osd, apply wim captured with CM task sequence in MDT task sequence: "cannot find the file specified"

Hi,
Please see titlte. When I try to apply an CM captured WIM via an MDT task sequence, it starts, applies but stops after 15 minutes.
Logfile says it "cannot find the file specified".
Full error: "Installation of image 3 in package mypackage failed to complete. . The system cannot find the file specified. (Error: 80070002, Source: Windows).
Though the image IS there, redistributed it (if it wouldn't be there the task sequence would not start).
Please advise.
J
Update: could it be the fact I'm using an old (SCCM 2012) MDT wim? If I need to recreate the WIM boot image, where do I get the SCCM 2012 R2 boot wims?
Jan Hoedt

See how to manually re-create your boot images
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to install Office 365 Pro Plus Ms office 2013 Offline through MDT Task Sequence

Hi
How can i deploy the Office 365 pro Plus Ms Office 2013 (that come with Office 365 E3 License) offline to Client Machines through MDT Task Sequence?
Shailendra Dev

There is a wealth of information on Office 365 deployments at:
http://technet.microsoft.com/en-us/library/gg715562(v=office.15).aspx
Overview:
Download the office deployment tool
configure your config.xml file
download the bits locally to your server.
create a package for MDT.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Custom Image Capture that Auto Imports the OS WIM and Creates a New Task Sequence

We just finished a consulting project where our customer requested an easy solution to capture thick images. After hearing their reasoning it made sense for their circumstances. The people that
will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve. They wanted the ability to Deploy the images via PXE.
This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.
So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
Automatically Import the Captured OS into the MDT Deployment Share
Automatically Create a new Task Sequence that references the newly imported image
Auto Name the Task Sequence with the Model Name, Date and Time of Capture
The Final Solution:
Customer will setup a Windows PC Thick Image (All software and drivers)
The customer will Kick-off the Sysprep and Capture Task Sequence
The customized Task Sequence will capture, import the new image, and create a new TS with the new image
Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably. If anyone is interested in this functionality
let me know and I can send you instructions. We used Vbscript, Powershell and PSExec.exe from PowerShell. It seems to being working pretty good so far
MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610

We just finished a consulting project where our customer requested an easy solution to capture thick images. After hearing their reasoning it made sense for their circumstances. The people that
will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve. They wanted the ability to Deploy the images via PXE.
This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.
So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
Automatically Import the Captured OS into the MDT Deployment Share
Automatically Create a new Task Sequence that references the newly imported image
Auto Name the Task Sequence with the Model Name, Date and Time of Capture
The Final Solution:
Customer will setup a Windows PC Thick Image (All software and drivers)
The customer will Kick-off the Sysprep and Capture Task Sequence
The customized Task Sequence will capture, import the new image, and create a new TS with the new image
Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably. If anyone is interested in this functionality
let me know and I can send you instructions. We used Vbscript, Powershell and PSExec.exe from PowerShell. It seems to being working pretty good so far
MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610
I would love to get the instructions to this process, as I have a simular client.

Hyper-v Virtual machine creation as part of MDT task sequence

Hello,
I have an existing MDT 2013 environment where I deploy Server 2008 R2 core with Hyper V role to HP Microservers.
The next step is to use hyper v manager and remotely configure the network and build VMs.
I would like to try and bring this together, and am sure I have seen similar powershell scripts online, but have not been able to find them despite an afternoon/evening of searching.
Ideally what I would like to happen is run a powershell script as part of MDT task to do the following.
1) create switch on hyper v host
2) build two VMs with fixed hard discs
3) VMs to automatically start and either PXE boot, which will connect to my existing automated MDT environment, or load the MDT iso image to initiate OS install.
Is anyone aware of existing scripts which can do this?
Or have any links which could help me achieve this?
Please note i am only using server 2008 r2 OS at present.
Many Thanks

Basically this has a little to nothing to do with MDT.
It's more about having the powershell scripts to do it, here's a good start:
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/16/powertip-create-a-virtual-switch-in-hyper-v-with-windows-powershell.aspx
http://technet.microsoft.com/en-us/magazine/jj933287.aspx
Once you have the script's tested and working, you can try to incorporate them into your MDT task sequence. Just add an "Run PowerShell Script" and refer to the script as: %DeployRoot%\Applications\Name Of Script\createVM.ps1 or something like that.
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Lenovo Power Manager Software - MDT Task Sequence

I'm working in an environment which does Operating System Deployment via SCCM 2007 SP2 R2 with MDT 2010 Update 1 Integration. I have an MDT Task Sequence that deploys my captured Windows 7 WIM file to predominantly Lenovo laptops (98% Lenovo fleet too). Part of this Task Sequence uses rules to specifically target drivers and applications to individual models. I'm am having GREAT difficulty in getting the Lenono Power Manager software (V3.31) to install as part of the Task Sequence.
The summary of the story is as follows:
Lenovo Bluetooth software is installing OK (msiexec /i Win32\BTW.msi /t 1033.mst /qb-)
Lenovo Hotkey software is installing OK (SETUP.EXE /S)
I've put logs for the Power Manager installation, and there are no errors i.e. it "seems" to install OK (SETUP.EXE /S)
I can advertise the Power Manager software POST image and it installs and works OK
Applications in the Task Sequence run in the order of Power Manager, Bluetooth, Hotkeys.
That hopefully provides the information for someone to maybe shed some light. It's a little frustrating given that the package actually will successfully install. I'm almost to the point where I want to try and create a collection with rules to populate it with Lenovo laptops and then mandatory install it. It's not a critical application - it would just be nice to have.
Solved!
Go to Solution.

I did some more searching and found this method to do it - http://www.windows-noob.com/forums/index.php?/topic/1231-os-deployment-and-lenovo-computers/. I used the idea of creating a Task Sequence step to copy the files locally, followed by a step to install it from the local files. It worked fine for this. If anyone has a "cleaner" method though, let me know.

Is it possible to edit a MDT Task Sequence after starting a deployment, between Hyper-V snapshots?

Using a Hyper-V VM, I take snapshots of my base image build between major sections (automatic updates, application installation, scripts and extras, etc.) with the intention of being able to go back to that area and look at it for troubleshooting's sake.
Each of these snapshots is manually taken during a pause in my MDT task sequence (using LTISuspend). I would like to be able to roll back to these snaphots make edits to the task sequence (obviously to sections that haven't yet run), then resume and
see the changes implemented - but I don't know where the task sequence file(s) resides on VM being imaged, or if that can be changed after kicking it off at the very start of the build.
Is it possible to replace the task sequence file (and any other necessary files) that are cached locally on the VM during the imaging process? Where are those files located? Or any other way to implement changes to my task sequence so I wouldn't
have to start the image build completely from scratch?
This build takes about 6 hours. Having to make even the slightest modification causes me to lose an entire day, so this would be golden even if I have to manually edit certain files!

Hi,
Based on my known, you cannot edit the task sequence after starting the deployment.
However, I suggest you ask this issue in MDT forum for more professional solution:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn
from your interaction with us. Thank you for your understanding.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Where to put unattend.xml when using create task sequence media

SCCM 2012 R2.
I created a capture task sequence media to a flash drive. I noticed the capture media does run sysprep even though it is not located on the flash drive. Where do I put my customized unattend.xml for sysprep? Does it go in c:\sysprep
There is no documentation on this that I can find.

sysprep doesn't use an unattend.xml file so you don't put it anywhere. You supply a custom unattend.xml during the deployment task sequence which in turn is delivered as part of the TS for use by WIndows Setup (which is what actually uses an unattend.xml
file). Task Sequence media has nothing to do with sysprep either. I think you may be confusing sysprep with Windows mini-setup. sysprep is the process of generalizing a system generally preparing it to be captured. Windows mini-setup is what runs the first
time a syspreped system is booted. They are two different things.
You *can* place an unattend.xml file the image for use by Windows mini-setup -- the locations mini-setup will look for this file are detailed at
http://technet.microsoft.com/en-us/library/cc749415(v=WS.10).aspx . But that is rarely done anymore with task sequences because you generally want to dynamically inject an unattend.xml
file into the process instead of statically placing one in the image -- that defeats the purpose of having a generic reference image. This is done by configuring the Apply Windows step in a deployment task sequence.
Still, that begs the question posed by narcoticoo. Your reference image(s) should be hardware agnostic, built on a VM, and automated. What you are doing will cause you pain in the long run.
Jason | http://blog.configmgrftw.com | @jasonsandys

Cannot Create Full Task Sequence Media

------------------------------------------- CreateTsMedia 18/03/2015 13:38:20 14880 (0x3A20)
Omitting AppContent source \\server1.fqdn because server1.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server2.fqdn because server2.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server3.fqdn because server3.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server4.fqdn because server4.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server5.fqdn because server5.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server6.fqdn because server6.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server7.fqdn because server7.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server8.fqdn because server8.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Content Library: Path='F:\SCCMContentLib', Drives='F:\,G:\,C:\,H:\,E:\' CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Found contentID Content_c5cc628a-fafe-4d7f-bcaa-2b44cebf1bfa.1 of App package SiteCode00790, size 24 Mb CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CContentDefinition::GetFileProperties failed; 0x80070003 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CContentDefinition::TotalFileSizes failed; 0x80070003 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to find size of contentID Content_0ba3179e-0762-494f-bdaf-b4a16794e07c.1 of App package SiteCode00790 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to download app content CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to get App content info CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to create media (0x80070003) CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CreateTsMedia failed with error 0x80070003, details='[Application]' CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
MediaGenerator::~MediaGenerator() CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
[Application] CreateTsMedia 18/03/2015 13:38:22 14880 (0x3A20)
Media creation process that was started from Admin Console completed.
CreateTsMedia 18/03/2015 13:38:22 7152 (0x1BF0)
CreateMedia.exe finished with error code 80070003 CreateTsMedia 18/03/2015 13:38:22 7152 (0x1BF0)
The content path for the App is valid, the files are in that folder, the app installs fine, this is a live task sequence, i cannot see anything wrong with this application.
Why is this failing?

Seems as if the application cannot be found on the DP(s) you selected for creating the TS media.
Torsten Meringer | http://www.mssccmfaq.de
Thats what i assumed, so i check the path, repushed a new version of the source to DPs, that succeeded, and as i mention that Application is in use so devices are pulling and installing it in the same boundary.
I have tried creating the ISO on a remote machine and the server with the same error.
Seems to me like another issue that exists with applications but not with packages.......grumble grumble.....

No Available distribution points when i create task sequence media wizard

Hi All,
I need your support with the following issue
when I try to Create task sequence media and choose the location and boot image x64 or x86 I found this issues
FYI: I am using the administrator and i cheeked the permissions and i have the full permissions for all roles

For this issue, You can refer below link
http://blogs.technet.com/b/configurationmgr/archive/2012/08/28/troubleshooting-missing-management-points-when-creating-a-bootable-media-task-sequence-in-system-center-2012-configuration-manager.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

How to exceute some commands to Laptops only through MDT Task sequence

Hi
I just created one commands below in batch file for Add wifi profile , and I add a Command line Step in Task sequence
that batch file run successfully but I need to execute such batch file only on laptops. please guide how can I do this -- I need to change batch file or I need to set some logic in Command line steps in MDT Task sequence.
command in my batch file
netsh wlan add profile filename="sockmonkey.xml" user=all
ScreenShot of my TS

hi
Thanksfor your quick reply , I will check and let you know..
I am getting error code 1618 while deploying multiple Application (.exe and .msi both) through MDT Task Sequence, can you please provide me a sample script to install below Applications through MDT TS.
Intel IPPRODIFX--     iProDifX.exe
Intel Pro Wireless 16.7 ---     msiexec /i "WiFi.msi" /qb /norestart ADDLOCAL=all REMOVE=WIFI_Admin_Toolkit,WIFI_PROSet,WIFI_MWT_Software
Juniper junos 3.1 --   Junos64.exe /q
Lenovo HotKey --   SETUP.EXE /s
CCM :- ccmsetup.exe
MBAM client 2.0 ---    msiexec /q /i MBAMClient.msi
Shailendra Dev

MDT Task Sequence with standard "Create Task Sequence Media" image capture?

Similar Messages

Maybe you are looking for