Disable a Task Sequence step

If you disable a step will it still check for the package content during an image drop?

The answer is no. It won't.
Test it yourself. Choose a task sequence and look at the References tab below. These are the objects required by the task sequence and must be available on a DP. Now disable a step containing a package. See that the package disappears from the References
tab. It is no longer required content.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

SCCM 2012 R2 Task Sequence Step "Install Package" downloads all content

Hello,
Task Sequence step "Install Package" I have several packages with multiple programs. When I use one of these packages with one of its programs it appears to download all the package content is there a workaround to stop this
from happening?
Regards!

Hi,
You could change it to run directly from the DP, then it will only use the files it needs and doesn't download anything at all. You will have to make sure that all the content needed by the task seqeunce is copied to the package share otherwise it will not
work in a task sequence.
The other would be to split up the package in multiple packages if that is possible.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Disable SCCM Task Sequence Using WMI

Hello everyone,
So I'm attempting to use WMI/SDK to disable a task sequence. I've dug for a method to do it, but am not having any luck. I am aware of the Disable-CMTaskSequence Cmdlet, but I really wanting to find the WMI method, assuming one exists.
I've used the WMI Code Creator to browse the classes with methods and of the 99 available, I can't find any that seem to fit.
If anyone has any ideas where I might look, then that would be great. If not, I'll integrate PS into my solution, but I was hoping to keep everything to using .Net/SDK/WMI without any PS integration.
Thanks!

Hi,
I don't understand why you don't want to use the cmdlet?
I'm not a big fan of the native cmdlets either, but when they work, they do save you a lot of work going the WMI route.
If, for whatever reason, you really want to use WMI, then have a look at SMS_TaskSequencePackage. You have to then change the property ProgramFlags via a bitwise operation. In this case it's Bit 12.
Don't try to hardcode the value, that might work, but is a wrong way to go. Have a look at one of my previous articles where I show a similar thing on SMS_Program :
http://www.david-obrien.net/2014/01/24/convert-configmgr-applications-packages-powershell/
Hope that helps!
My blog on ConfigMgr automation: www.david-obrien.net | me on Twitter: @david_obrien Please remember to mark the post(s) that helped you resolve the issue (even if it was your own)

Inject Drivers Task Sequence Step vs Using DriverSelectionProfile in Database

I'm using a Database and 'Make and Model' in MDT 2012. I wonder if I specify a DriverSelectionProfile in the Database, what happens when the Task Sequence reaches the Preinstall > Inject Drivers step? Does it process the selection there and ignore the
Database settings? Or should I disable this step in the Task Sequence?
Orange County District Attorney

If you are having driver folders that are named after the computer models a single line is enough. MDT will replace the variable with the real model name. If you only deploy Windows 7 SP1 x64 you can set in the CustomSettings.ini file.
[Default]
DriverGroup001=Windows 7 x64\%Model%
If you deploy multiple operating systems (Windows Server 2012 R2, Windows 8.1 and Windows 7) it's easier to set it in the task sequence instead.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

How to select domain OU for "Apply Network Settings" task sequence step, based on the ip address.

We are finally getting ready to migrate from SCCM 2007 to 2012 R2.
Our current setup has 5 site servers with five OSD setups with boot media and Windows 7 task sequences.
I want to move all that to one site with a single OSD W7 task sequence.
The current, "apply network settings", step adds the workstation to one of five different OUs. The same with the "apply windows settings" step, we have five local admin passwords for five regions around the state.
I thought I might run five versions of each step and add a condition to each one that would only run if the machine was on the right subnet. Or the right Boundary group or maybe the right active directory site.
Currently I'm creating five boundary groups that I hope to detect by running a power script get-CmBoundaryGroup. Then apply the results maybe as a task sequence variable in the task steps options/Add Conditions.
Anybody have a better approach. Or alternate plan.

Are you integrated with MDT? If so, you can use customsettings.ini to put machines into specific OUs based on the DefaultGateway.
See these links for ideas:
https://scriptimus.wordpress.com/2011/05/10/mdt-2010-joining-a-domain/
http://deploymentbunny.com/2012/04/21/back-to-basic-customsettings-ini-explained/
Jeff

Is it possible to disable Mandatory Task Sequence Warning Message ?

Hello,
When I deploy a mandatory OSD task sequence, the client pc's receives the request, however, a "Mandatory Task Sequence" messages appears saying that the OS deployment will commence in 180 seconds.
Is there an option to disable this warning or reduce the timeout value of 180 seconds ?
Thanks
Imran
Imran

Hi,
The following thread might be helpful, although it is for SCCM 2007.
http://social.technet.microsoft.com/Forums/systemcenter/en-US/da7b304b-457e-4fff-bcb9-d40ceb0675ec/configuration-manager-mandatory-task-sequence-warning?forum=configmgrosd
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Question about Disable Step Task Sequence

Hello guys,
I have 2 doubt about my scenario, I hope you help me.
Scenario1
I want deploy SO Windows7, I have only one partition.
If a disable step: Apply data image1 my deploy ocurred with sucess.
But if no disable step I saw up, ocurred error 0X8004005.
My question so: Why is
mandatorily I
disable this step?
Print1 Partition Disk0
Print2 Apply Data Image
Thanks any idea.

It seems the answer has been staring us in the face this whole time.
In the above image you posted previously, you are clearly applying an image that, from the title, contains an OS despite the warning below the selection box stating that this image
can not contain any operating system.
The apply operating system task sequence step is for applying any WIMs involved with OS or boot partitions. The apply image step should only be used if you had data partitions that you wanted all machines to have, for instance raw storage sections with company
specific data on it. I have never seen it used but I can imagine where it would come in handy.
I would recommend replacing all of those steps with the appropriate task sequence step.
I also recommend you stop using hardware specific WIMs, as it seems you are using based on the title
WIN7HP8200... above. You should be able to go fairly hardware independent with the WIM and only apply drivers to the Task SEquence based on hardware detected.
Dustin Estes - MCP | www.dustinestes.com

Build and Capture task sequence fails at 'Prepare ConfigMgr Client for Capture' step

The scenario is as follows:
Task Sequence is a Build and Capture of Windows 7 SP1 x64 Enterprise
There are 17 Applications installed split into 2 'Install Application' steps due to the 9 item limit
129 Software Updates are installed
SCCM 2012 RTM
I have built and captured on this system previously however there were no 'applications', just traditional SCCM 'packages'
All task sequence steps run successfully until it gets to the 'Prepare ConfigMgr Client for Capture' step and it fails here. Here are the relevant parts of the SMSTS.log file:
<![LOG[No certificates to delete]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1013">
<![LOG[Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded.]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:922">
<![LOG[Reseting the Trusted Root Key successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1088">
<![LOG[Deleting instance of 'CCM_Client' successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:170">
<![LOG[Successfully reset Registration status flag to "not registered"]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:309">
<![LOG[Successfully disabled provisioning mode.]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1273">
<![LOG[Start to cleanup TS policy]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2773">
<![LOG[getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient"
context="" type="0" thread="2880" file="wminamespace.cpp:389">
<![LOG[ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2800">
<![LOG[Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="utils.cpp:2800">
<![LOG[End TS policy cleanup]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2821">
<![LOG[TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880"
file="preparesmsclient.cpp:457">
<![LOG[Failed to delete policies compiled by TaskSequence (0xffffffff)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:457">
<![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:472">
<![LOG[pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="main.cpp:136">
<![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="main.cpp:136">
<![LOG[Process completed with exit code 4294967295]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="commandline.cpp:1098">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="instruction.cxx:3011">
<![LOG[Failed to run the action: Prepare ConfigMgr Client for Capture.
Unknown error (Error: FFFFFFFF; Source: Unknown)]LOG]!><time="15:35:21.046-660" date="11-13-2012" component="TSManager" context="" type="3" thread="2152" file="instruction.cxx:3102">
It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
and removed - however I would rather avoid this very time consuming process if possible.
I have also testing this using 'capture media' in the full OS and that also fails at the same step with the same errors in the smsts.log
The only workaround I have for now is to let the task sequence fail at the 'Prepare ConfigMgr Client for Capture' step, then I uninstall the SCCM client using 'ccmsetup.exe /uninstall' and use the 'capture media' method - obviously with no SCCM client installed,
it skips the 'Prepare ConfigMgr Client for Capture' step and goes straight to the 'Prepare OS' step and then to the actual capture to the WIM step.
Anybody else seeing this or have any suggestions?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
and removed - however I would rather avoid this very time consuming process if possible.
You dont have to test it 18 times....
Just test with 50% of the applications first, if it fails, test with 25% and then on of the time...
You should be able to find the application, within 4-5 tests...
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter
@ronnipedersen

Whats the best way to apply office updates during OSD task sequence with Software Update Agent disabled?

I am trying to update office via the SCCM 2012 R2 OSD task sequence. I know offline updating only updates the core components in the WIM and I'm trying to figure out how to add office updates as well. I am aware of using powershell to try and kick off
a WU scan as seen here:
http://myitforum.com/myitforumwp/2012/01/24/use-powershell-commands-to-assist-with-patching-during-sccm-image-build/
But the kicker is we don't use SCCM to update the workstations (Solo WSUS install). Is there a way to do this (maybe set the client in the TS to switch on SUP, then off again when it goes off into production) rather than have to build a new image every month?

You could use the ZTI_WindowsUpdates.wsf script from MDT.
http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
How does it work?
The task sequence steps run a script called ZTIWindowsUpdate.wsf. The script uses the
Windows Update Agent API to manage the downloading and installation of updates. All audit information is written to the
ZTIWindowsUpdate.log file. If you find any unusual error codes in your log returned from the API (although I never have) you can compare the codes
here. The script will also check and update the
Windows Update Agent(WUA) as needed at the start.
In its default state, the ZTIWindowsUpdate.wsf script will connect to Microsoft Update then search for and download all available updates including Security Patches, Drivers, Browser Updates and Service Packs. This is essentially the same
as opening the GUI and selecting check for updates.
Daniel Ratliff | http://www.PotentEngineer.com

As step in Task Sequence : Deleting all existing partitions on harddrive before partitioning, is it possible? Thoughts appreciated

Everyone,
I have just received a load of 100+ computers off corporate lease for the school district I manage, and while imaging them in SCCM, i've noticed that of those 100 computers about 7 or 8 have failed during the task sequence. Just on a guess, I tried
booting up off a windows 7 disk and physically deleting all partitions and THEN running the task sequence it fixes the issue and the task sequence jumps off/completes without any problems (which there's only been one main partition and one system reserve partition).
My question to you all, I want ALL computers that run my task sequences to completely wipe ALL partitions...and then go forward with the standard partitioning step that's in the task sequence (Step name Partition Disk 0 - BIOS, where it sets up a 350mb system
reserve and then a 100% remaining space NTFS windows Primary partition)
Can someone point me in the right direction? I feel this is a simple process to add to my task sequence, but I wanted to confirm with some of you that might can ease my anxiety a bit first.
Thanks so much!

as above, you could even use a prestart command to achieve this before displaying the task sequence however i'd be VERY careful about doing so, as you could end up wiping out a whole estate of computers without intending to if you deploy it to the wrong
collection or wrong query, far better to keep the logic in the task sequence as a scripted diskpart step (or two)
you can download a diskpart script and view the associated step in the
following task sequence
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Domain join account for apply network settings step in task sequence

Hi Guys,
Just want to confirm that the domain join account credentials is in clear text during the winpe phrase. I understand we can a user account with just domain join access but it still a security breach for us. Is there an alternative? We are using SCCM 2012
R2. Thanks in advance.

Hi,
The article
Task Sequence Steps in Configuration Manager shows the Apply Network Settings task sequence step store the specified values in the appropriate answer file format for use by Windows Setup when the
Setup Windows and ConfigMgr task sequence step is run. The account credentials stored in answer file should be in plain text.
If you are still worried about this, you could create a custom answer file to join domain. The article
Configure Settings in an Answer File in Image Configuration Editor shows the credentials are stored in plain text in the answer file.
Best Regards,
Joyce

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).
I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation. "Install Application" TS was readded but now when I try to
image I get this error:
"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."
I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.
-Thanks in advance!

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or
get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:
diskpart
list disk
select disk 0
list part
select part 1
clean
create part primary
assign
active
exit
Please mark this as the answer if it works.
You are awesome this worked for me I didn't see how I was going to get my new computer to reimage again Thank you sooooooooooooo much!!!

Using partition variable in task sequence

I need to configure a piece of software as part of a task sequence to direct some of its files to a specific partition. I have the ts creating 3 partitions and I'm specifying variables for each: DataDisk = 10GB, UsersDisk = 100GB, OSDisk = 100% remaining
free space.
The 100GB partition is the one I need the software to use. In the "Custom Tasks" section of the ts "Dump MDT Variables" step dumps all MDT variables to a text file on the local machine so I can see at that time UsersDisk = D:\, DataDisk
= C:\ and OSDisk = V:\, but after the deployment finishes UsersDisk = E:\. Also in the "Custom Tasks" section I'm running the "Configure Data Igloo" to configure the program. Is there a way to set UsersDisk = E:\ before I run
the "Configure Data Igloo" step when there's also an internal DVD drive likely using E:\?
Edit: I should add that it's all working properly at the moment but the "Configure Data Igloo" step is referencing E:\, not %UsersDisk% and I see this causing problems latter. Does anyone know how the drive letters are assigned? That is,
why does %DataDisk% = D:\ and %UsersDisk%= E:\ after deployment, why not the reverse?

Thanks for the reply Keith. I'm not thrilled about having to customize the partition structure either but because we use Deep Freeze we need use Data Igloo to cache user profiles on a partition other than C:\.
What I've ended up doing is using the 'Set Task Sequence Variable' tasks to set DataDisk = D:\ and UsersDisk = E:\ and then I can reference these variables for the task that configures Data Igloo. To be clear for anyone trying to follow this, I'm not
actually changing the letter assigned to the partitions, I'm just assigning a value to a variable which is then referenced in later task sequence steps.
The thing that I'm not sure about is how the partition letters are assigned. In my case the DataDisk partition is always assigned D:\ and UsersDisk is always assigned E:\. I thought it might be alphabetical but I changed the 'Format and Partition
Disk' step to rename UsersDisk to ADisk and it still gets letter E:\.
This isn't a big deal but if anyone knows how the letters are assigned please let me know.

Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)

Hi there
Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
After searching about this, I found this page from Niall Brady, which explained the problem:
http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
Now...
...I have a question.
The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
However there seems to be some confusion over whether this would actually make a difference.
I read through this link:
http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
There's seems to be no consensus on this.
Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
or
Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
I'd be grateful for some clarity on this.
Regards,
John, Glasgow.

Hi Jason
Thank you for replying, I appreciate it.
1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
deleting all but the latest software update group?
2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
"The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
Can you shed some light on why there isn't a policy for an image?
Thanks again for replying,
John.

Powershell commands to change operating system image in task sequence

Hello,
I am looking for a way to script changing a task sequence to use a different OS image file. So far the only thing I can find using the powershell MDT module is the "import-mdttasksequence" command, but it looks like that can only create a whole
new task sequence.
My end goal is to automate our master image builds and the last step is to take the captured master wim file, import it into the Operating Systems folder, and then update the associated custom image task sequence to use that new OS image. With
"import-mdttasksequence" I have to create a new task sequence with a new ID, when I already have one present that would be easier to just update to point to a different OS image. I do not see anyway to edit task sequence steps using the powershell
module.
Is this possible? Maybe using Get-Item to get the OS GUID and then editing the task sequence XML file directly?
MDT 2013
Server 2008 R2
Regards,
Darren

Hi Darren,
If I understand correctly, you can use the same name for the captured WIM file? Then you can just copy it to the operating systems and it will be picked up by your TS.
I've found this
thread on the forums that probably has your solution in it.
From that thread:
I now capture to the Captures folder and name the WIM file after the task sequence ID. So for example, my "Update Windows 8 General Purpose" task sequence with ID "8_GP" now creates "\\server\DeploymentShare$\Captures\8_GP.wim"
In the Scripts folder on the deployment share I created "Relocate.cmd" with the following contents:
MOVE /Y "%DEPLOYDRIVE%\Captures\%1.wim" "%DEPLOYDRIVE%\Operating Systems\%1"
And finally, I added a step at the end of my task sequences that runs this custom command (no
Start in value defined):
cmd /c %SCRIPTROOT%\relocate.cmd %TaskSequenceID%
This works great and MDT does in fact recognize the changed .wim file in Operating Systems and copies it to linked deployment shares, so no worries there.
Hope this helps.

Disable a Task Sequence step

Similar Messages

Maybe you are looking for