Pause Task Sequence, Manually Installs Software

I'm not sure what I need to do but I have a build and capture (SCCM not MDT) task sequence and I would like to pause it and manually install software, no I can't automate it unfortunately and I'm not wanting to use MDT. Now I know how to pause
a task sequence but I never get to a point where I'm logged in to the OS as a user thus I can't install software. I have added a reboot command in to the TS and told it to reboot in to the installed OS but that did not work. I 'thought' I configured
the unattend.xml to login to the OS but maybe I screwed that up.
How do i get to a point that I am logged in to the OS and before we need to sysprep....?

I would go down the MDT route.
You are going to save yourself a look of trouble, as this solution already exists.
http://deploymentbunny.com/2011/05/10/ltipause-vbs-take-a-break-in-deployment/
It doesn't take long to setup a Build and Capture with MDT using a hyper-v machine and then import the WIM into ConfigMgr.
The Build and Capture process in ConfigMgr is desiged to be a zero touch process, which makes what you want to achieve difficult. My understanding is that even if you do get the T.S to pause and get to the desktop, you will then have issue due to the
custom GINA that ConfigMgr uses to prevent GPO and other stuff getting in the way of builds. The second reason is that you will running as the system account and not as a user per se. Not sure if this will cause any issues, but why take the chance.
If you really don't want to go with MDT... you will have to work out a way to automate your software. I agree with Torsten, what is stopping it done being automated?
Regards, Martin
Because until an AI is integrated with ConfigMgr the software that I need to install can't be automated. It
requires a phone call to the manufacture with a live human to activate the license. Stupid I know but this is not something that I can change.

Similar Messages

A custom task sequence to install software is always listed as Operating System on Software Center

Hello,
I have built several custom task sequences to install software in SCCM 2012 R2 CU1 environment, but the type of task sequence is always listed as Operating System on the Software Center. I tried creating a simple task sequence (Task Sequence 1) that contains
a single restart computer step only and tried deploying it to a test machine. This task sequence is also listed as Operating System. This task sequence fails because this is not the one for OS install and I do not specify a boot image for this task sequence.
All task sequences that I have created in SCCM 2012 RTM environment are working as expected. All task sequences that I create in SCCM 2012 R2 CU1 are listed as Operating System regardless of its actual type (I upgraded my environment from CM2012 RTM to CM2012
R2 CU1 last month).
Here is a test task sequence that contains a single step of restart computer. This is not Operating System install but listed as Operating System. Any thoughts?

If you use OSD steps in your task sequence you will get this prompt.
http://social.technet.microsoft.com/Forums/en-US/3eb7569c-0b5a-4b40-86c3-d4f092c70aca/task-sequence-warning?forum=configmanagerosd
Per Mikko:
Using any of following steps (and possibly others as well, I did not check all of them) will change the task sequence type from generic to OSD:
General - Join Domain or Workgroup
General - Restart Computer (Only "The boot image assigned to this task sequence" option)
Disks - Format and Partition Disk
User State - Request State Store
User State - Release State Store
Images - Apply Operating System Image
Images - Setup Windows and ConfigMgr
Daniel Ratliff | http://www.PotentEngineer.com

Build & capture task sequence fails during software update installation

I'm sure this has been discussed a thousand times already, so I hope no one minds talking about it at least one more time. About 6 months ago I created a reference image using a build and capture task sequence within SCCM. After discovering
there were certain updates that would kill a task sequence (because they required multiple restarts), I was able to exclude these updates from deployment so that my task sequence completed successfully. Fast forward to today. I'm working on updating
our reference image to include the last 6 months of updates. Again, I'm having trouble with the task sequence failing to complete. I have excluded all of the updates mentioned in
Microsoft KB article 2894518. I'm able to build the image with all software updates up until 6/30/2014. When I deploy my software group that contains updates from 7/1/2014 to 12/31/2014,
however, the task sequence fails. I'm pulling my hair out trying to figure out which update may be causing the issue, and trust me, I don't have much hair as it is. So, here's my question to all of the experts out there. What is the best
method of debugging this issue and finding which update may be the culprit? The log files really are confusing, so I'm hoping there are some common codes or phrases I can search for within those files. Any and all help is much appreciated. Thanks...

> I'm working on updating our reference image to include the last 6 months of updates.
Since this is a Build & Capture task sequence and not joined to the domain, you'll need to treat it
like a workgroup computer. Here are the big three things that usually trip things up:
1. Initial Management Point: The Setup Windows and ConfigMgr step should have the SMSMP=<fqdn>
property specified, as the device won't be able to see the list of MP's in Active Directory
2. Content Location: Make sure the reference machine's IP address falls within an IP Range
or Subnet ID boundary, since it can't use a AD Site boundary as a workgroup machine.
3. Win 7 - NTLM Fallback: Windows 7 devices may need
hotfix KB2522623 installed (as a package/program or with offline servicing) to ensure they fall back to NTLM properly when they fail to authenticate with Kerberos.
If you have those 3 things taken care of, then you should copy all the logs off of the machine while the
error message is still being displayed, zip them, and then share them out through OneDrive or Dropbox.
I hope that helps,
Nashs
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Installing "Applications" during the task sequence and installation enforcement

Hello,
Kind of a weird question here, so it seems like I'm seeing that if you install an application on a system during its OSD task sequence, then you later manually uninstall that application, that SCCM considers that system now out of compliance?
And then reinstalls the application as indicated in AppEnforce.log? Is this true? If so, how do you get around this behavior? I guess I thought that this application compliance only took effect when you actually deploy an application to a
system, through an actual deployment. I didn't realize that it would enforce compliance even if an application was installed during a task sequence. So if you have hundreds of systems that were imaged with the same task sequence and you have
a small handful of machines that can't have application X on it (so you want to uninstall it), which was installed via the task sequence, how do you disable this compliance enforcement and disable its automatic reinstall?
Thanks for any help you can provide.

Sorry for the delayed response, thank you both for your input. To answer both your questions, no these workstations do not have any required deployments for this application directed at them. I have confirmed that, however, they do have
the OSD task sequence deployment (that contains this application) constantly "available" to them (via only "media and PXE") as this makes it very easy for our technicians to reimage any machine whenever they need to (love that feature
by the way).
I can only assume that because they still have this task sequence deployment pointed at them is why they continue to attempt to reinstall this application when ConfigMgr finds that it's not installed anymore. In fact it does it at the same day/time
each week, which I believe is the same day/time of the week that the machines were imaged. I must have the compliance part of the clients configuration to check every 7 days for stuff like this? Anyway, that's my conclusion for now.
Since even Wally Mead felt that this must be an actual required deployment outside of the task sequence I'm really curious to see if anyone else sees this behavior. It would be fairly simple to attempt to recreate, image a machine with a task sequence
that has "application" installs included, where the deployment for it is just "available" and keep the deployment "available" after the machine is reimaged. Then after that, uninstall one of the apps that was installed
during the task sequence via an "application" and then see if it reinstalls automatically, it may wait a while (may 7 days by default?). You can see the evidence of our application reinstalling itself in the "AppEnforce.log".
Is it even remotely possible that this is a new "feature" or behavior of ConfigMgr 2012 and "Applications"?

Error 16389 running a Task Sequence to install software

We've run into multiple WinXPProSP3 computers generating error code 16389 when trying to run a TS. After searching on Google, we found this,
http://blogs.technet.com/b/smsandmom/archive/2007/10/29/sccm-2007-task-sequence-fails-drive-letter-not-displayed.aspx
, which led to another article to modify a RegKey, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} , to add a key of UpperFilters, with a value of PartMgr. The key WAS missing on the machines with
the error, and, adding that key and value DOES fix the problem. This key and value seem to be default for the OS.
However, searching Google for that RegKey has a LOT of suggestions to delete that key and value, due to issues with USB Thumbdrives and iPods not being seen when plugged in--so, it seems that there may be a conflict.
Does anyone know of a fix for Error 16389 without having to add that key, if it's going to cause other problems?
Thanks.

Hi,
Will you please past the detailed errors in the smsts.log?
From your description your are using TS to install software right?
If so you should first make sure this software package meats the following requirement when it was deployed through TS:
this program can be installed under local system account.
this program can be installed without any user interaction (such as: press next button).
this program will not force computer reboot, it allows sccm ts to manage the reboot.
If your OSD TS return 16389 exit code, you can try to change the volume license keys. Because once i have seem this error and it was solved by changing the volume license key.
Hope this will help.
Thanks

Task Sequence Fails after Software Updates Install Step - Lenovo X240

Hi All.
I'm having a strange issue trying to run an OSD on Lenovo X240 machines.
After the Software Update step, it reboots as expected, then exits the task sequence and sends you to the windows logon screen.
Review the SMSTS.log, it appears the reason is:
Found network adapter "Intel(R) Dual Band Wireless-AC 7260" with IP Address 0.0.0.0.
TSMBootstrap 24/07/2014 15:07:10
1824 (0x0720)
Found network adapter "Intel(R) Ethernet Connection I218-LM" with IP Address 0.0.0.0.
TSMBootstrap 24/07/2014 15:07:10
1824 (0x0720)
Full log file:
SMSTS.log
If I remove the Software Updates step, the task sequence completes without any problems.
Don't think it is a driver error, as above, every other step completes without issue. Other models use the same task sequence (including software updates step) without any problems.
Any ideas? I'm completely stuck.
Thanks!

Looks like I am deploying KB2965788 which requires two restarts.
Thanks all for your help.
P.S. - I periodically update the base image with a build & capture to include the latest updates, so in the times between this I deploy the software updates as part of the task sequence.
I've found the offline servicing to be very flaky, have attempted to use it many times and found it either a) doesn't apply the updates to the image b) corrupts the image.

OS Uptdates - The proper sequence of installation & Software

Hello Hello
I just did a new fresh install of OS 10.4.4, from my older Black Disc Full Retail OSX, (to a New Hard Drive), and then I downloaded the Apple Updates to bring the OS up to version 10.4.9
I then re-installed iLife 06; iMovie,iDVD,iPhoto, etc., and all went well. Although I haven't actually got back into using iMovie and the other programs - all looks good.
That being said, I'm about to perform the same tasks on my freind's G5, (same identical equipment and new hard drive).
Now just to make absolutely sure, do you guys know if it matters whether we do the OS updates FIRST. Or stick with OS 10.4.4 (intially), then re-install iLife (iMovie etc), THEN after the iLife install, THEN update the OS to 10.4.9?????
Of course the iLife updates will follow as well
Thank you all
Mike

I just did a new fresh install of OS 10.4.4, from my older Black Disc Full Retail OSX, (to a New Hard Drive), and then I downloaded the Apple Updates to bring the OS up to version 10.4.9
Just so you know, when it is a new hard drive it is called "Install Mac OS X for the first time." There is no "fresh install" option.
When installing on the friend's G5, you need to find out if the G5 came out before or after 10.4's as this article explains:
http://docs.info.apple.com/article.html?artnum=25517
If after, you should use the disks which came with the G5. If before, you need a separate license to install Tiger from retail disks, unless your friend is part of your family and you purchased a family pack.
Once you determine what you can use to install, be sure to follow the tips my FAQ* for upgrading:
http://www.macmaps.com/upgradefaq.html
* Links to my page may give me compensation.

How do I add a step to run at the beginning of an existing task sequence?

I need a way to add a step to run at the beginning of an existing task sequence like you see up above. We need to do so to all task sequences that install software in our environment. I understand PowerShell very well but, I am not sure of how I would modify
(if possible) an existing task sequence, let alone add a step to the beginning.
This is super important and would most appreciated for any help. Thanks! :)
http://i61.tinypic.com/2nlv8zb.png

I understand how to perform the above action. I need to have that in a PowerShell script. I need to insert a "Install Package" step at the top of all 900+ task sequences with a specific package. I am good with PowerShell, just not that good.
ActionInProgress : 1
AlternateContentProviders :
BootImageID :
Category :
CustomProgressMsg :
DependentProgram :
Description : ML - 1/5/15
Duration : 360
ExtendedData :
ExtendedDataSize : 0
ForcedDisconnectDelay : 5
ForcedDisconnectEnabled : False
ForcedDisconnectNumRetries : 2
Icon :
IconSize : 0
IgnoreAddressSchedule : False
ISVData :
ISVDataSize : 0
IsVersionCompatible :
Language :
LastRefreshTime : 2/16/2015 10:18:25 AM
LocalizedCategoryInstanceNames :
Manufacturer :
MIFFilename :
MIFName :
MIFPublisher :
MIFVersion :
Name : TS: Adobe_ReaderXI_11.0.10_R01-Install
NumOfPrograms :
PackageID : P12005DB
PackageSize :
PackageType : 4
PkgFlags : 0
PkgSourceFlag : 1
PkgSourcePath :
PreferredAddressType :
Priority : 2
ProgramFlags : 152084496
References : {
instance of SMS_TaskSequence_Reference
Package = "P1200541";
Program = "Adobe_Cleaner_9_R01";
Type = 0;
instance of SMS_TaskSequence_Reference
Package = "P1200542";
Program = "Adobe_Cleaner_10_R01";
Type = 0;
instance of SMS_TaskSequence_Reference
Package = "P1200598";
Program = "*";
Type = 0;
instance of SMS_TaskSequence_Reference
Package = "ScopeId_5E2F018E-6A55-4DF6-BC64-43B2E205E619/Application_d5c1b17b-12e1-
4ad6-9916-72fdefc834b8";
Program = "";
Type = 1;
ReferencesCount : 4
RefreshPkgSourceFlag : False
RefreshSchedule :
Reserved :
SecuredScopeNames : {Default}
SedoObjectVersion : EF958AC5-D6E3-460E-A666-6A8CAF4AEB8C
Sequence : <sequence version="3.00"><referenceList><reference package="P1200598"/><reference
package="P1200541" program="Adobe_Cleaner_9_R01"/><reference package="P1200542"
program="Adobe_Cleaner_10_R01"/><reference application="ScopeId_5E2F018E-6A55-4DF6-BC6
4-43B2E205E619/Application_d5c1b17b-12e1-4ad6-9916-72fdefc834b8"/></referenceList><ste
p type="SMS_TaskSequence_RunPowerShellScriptAction" name="SDLSetupWait"
description="ML - 2/16/15" runIn="WinPEandFullOS" successCodeList="0" runFromNet="fals
e"><action>OSDRunPowerShellScript.exe</action><defaultVarList><variable
name="OSDRunPowerShellScriptExecutionPolicy"
property="ExecutionPolicy">Bypass</variable><variable
name="OSDRunPowerShellScriptPackageID"
property="PackageID">P1200598</variable><variable
name="OSDRunPowerShellScriptParameters" property="Parameters"></variable><variable
name="OSDRunPowerShellScriptScriptName"
property="ScriptName">SDLSetupWait.ps1</variable></defaultVarList></step><step
type="SMS_TaskSequence_InstallSoftwareAction" name="Purge Adobe 9.x -"
description="ML - 1/5/15" runIn="FullOS" successCodeList="0"
runFromNet="false"><action>smsswd.exe /pkg:P1200541 /install /basevar:
/continueOnError:</action><defaultVarList><variable name="PackageID"
property="PackageID" hidden="true">P1200541</variable><variable
name="_SMSSWDProgramName"
property="ProgramName">Adobe_Cleaner_9_R01</variable></defaultVarList></step><step
type="SMS_TaskSequence_InstallSoftwareAction" name="Purge Adobe 10.x+"
description="ML - 1/5/15" runIn="FullOS" successCodeList="0"
runFromNet="false"><action>smsswd.exe /pkg:P1200542 /install /basevar:
/continueOnError:</action><defaultVarList><variable name="PackageID"
property="PackageID" hidden="true">P1200542</variable><variable
name="_SMSSWDProgramName"
property="ProgramName">Adobe_Cleaner_10_R01</variable></defaultVarList></step><step
type="SMS_TaskSequence_InstallApplicationAction" name="TS:
Adobe_ReaderXI_11.0.10_R01-Install" description="ML - 1/5/15" runIn="FullOS"
successCodeList="0" runFromNet="false"><action>smsappinstall.exe /app:ScopeId_5E2F018E
-6A55-4DF6-BC64-43B2E205E619/Application_d5c1b17b-12e1-4ad6-9916-72fdefc834b8
/basevar: /continueOnError:False</action><defaultVarList><variable name="OSDApp"
property="AppInfo" hidden="true">1</variable><variable name="OSDApp0Description"
property="AppInfo0Description">Valid</variable><variable name="OSDApp0DisplayName"
property="AppInfo0DisplayName">Adobe_ReaderXI_11.0.10_R01</variable><variable
name="OSDApp0Name" property="AppInfo0Name">ScopeId_5E2F018E-6A55-4DF6-BC64-43B2E205E61
9/Application_d5c1b17b-12e1-4ad6-9916-72fdefc834b8</variable><variable
name="ApplicationName" property="ApplicationName" hidden="true">ScopeId_5E2F018E-6A55-
4DF6-BC64-43B2E205E619/Application_d5c1b17b-12e1-4ad6-9916-72fdefc834b8</variable><var
iable name="ContinueOnInstallError" property="ContinueOnInstallError"
hidden="true">false</variable><variable name="OSDAppCount"
property="NumApps">1</variable></defaultVarList></step><step
type="SMS_TaskSequence_RunCommandLineAction" name="Change Reg Key" description="ML -
1/5/15" runIn="WinPEandFullOS" successCodeList="0 3010"
runFromNet="false"><action>smsswd.exe /run: reg add HKEY_LOCAL_MACHINE\SOFTWARE\Classe
s\Installer\Products\68AB67CA7DA73301B744BA0000000010 /v ProductName /d
Adobe_ReaderXI_11.0.10_R01 /F</action><defaultVarList><variable name="CommandLine"
property="CommandLine" hidden="true">reg add HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Insta
ller\Products\68AB67CA7DA73301B744BA0000000010 /v ProductName /d
Adobe_ReaderXI_11.0.10_R01 /F</variable><variable name="SMSTSDisableWow64Redirection"
property="DisableWow64Redirection">false</variable><variable
name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable><variable
name="SuccessCodes" property="SuccessCodes" hidden="true">0
3010</variable></defaultVarList></step></sequence>
ShareName :
ShareType : 1
SourceDate : 1/5/2015 10:14:08 AM
SourceSite : P12
SourceVersion : 1
StoredPkgPath :
StoredPkgVersion : 1
SupportedOperatingSystems : {}
TaskSequenceFlags : 0
Type : 1
Version :

UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhet

your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

OSD Task Sequence Keeps re-running

I am running SCCM 2012 R2 and have been imaging with it with no issues until recently. I have a Task Sequence which installs an OS image, then a couple of packages, nothing special about it except for the fact that it keeps rerunning on the machines
in both collections it is advertised to, even though the rerun behavior is set to "Never Rerun". I have several other OSD TS's out there, all of which are advertised to dynamic collections and all set to rerun if failed, and none of them are
behaving this way. Correct me if I'm wrong, but shouldn't "Never rerun" prevent it from running on these machines? If not, then why are the dynamic collections which have "rerun if failed" set not rerunning their TS's as well?
Thanks for any and all who respond.

Hi Jeff,
I agree that when the new object for the imaged computer gets created, it would act as if it had never run the TS before and so it would be normal behaviour to run it, however what I'm seeing and have experienced over the years is the opposite. For
example, yesterday, in one area, I imaged about 150 systems. The advertisement was set to "Rerun if failed" and it ran flawlessly on all systems, and none of them re-ran. In the other area, I imaged about 18 systems. These ones
had previously been imaged with the advertisement set to "Rerun if failed" and several of them just kept imaging over and over, so when we imaged them yesterday, I set it to "Never rerun", and they still kept imaging. The only thing
I can think of is that the very last step in the TS runs "c:\windows\system32\slmgr.vbs /ato" because we had some issues with activation in that image, could that be causing the unusual behaviour?

Second Task Sequence to collection. Will it auto-deploy?

We have a SCCM 2007 R3 setup with a "All Windows 7 Computers" collection with two sub-collections for Desktop and Mobile computers.
There is a Task Sequence on it with Windows 7+Office 2010, and I now want to add a second Task Sequence which installs Windows 7+Office 2013.
Creating a seperate collection and adding a test computer to it and adding the two Task Sequences (new advertisement for each) works fine when I PXE boot. I can then select between the two Task Sequences.
When I added the computer it showed no sign of wanting to deploy a Task Sequence using the Computer Configuration Manager, but I do wonder (read: need to be damn sure about this) what happens if I add the second Task Sequence to the collection holding all my
other computers.
I can't have all computers suddenly deploying the Windows 7+Office 2013 Task Sequence of course.
Can anyone tell me if this is safe to do or will I get in trouble, loose my job, name and shame, etc?

Is your intention o make it a mandatory advert or not? That's really the key factor. I'm assuming by your statement that its not so just make sure that you don't add a [mandatory] schedule to the advert. Also, if your intention is to only make to available
via PXE for new computer/bare metal scenarios, set the OS requirements criteria on the properties of the TS to be only applicable to Windows Vista or Windows 2000 systems. This criteria is not evaluated during a bare metal WinPE boot but will prevent any non-PXE
(or media) booted systems from seeing the TS.
Jason | http://blog.configmgrftw.com | @jasonsandys

Prompt for location - Task Sequence Variable

I am wondering if it is possible to have a task sequence pop up asking for user input on their current location.
I am trying to create a task sequence that will prompt the user where the computer is going to be deployed to, so it will put the computer in the correct OU and such by using seperate Network Settings based on the users input. I would like it to have a list
of options the user can choose from.
I am not running MDT.

I've not used UDI that much myself, but why not take a look at it. It's really worth while to start learning MDT, it will only benefit you in the long run, trust me!
But creating your own PowerShell front end isn't really that hard (assuming you've worked a little bit with PowerShell before).
Here's a great guide on UDI:
http://osdblog.com/2014/01/23/integrate-udi-with-your-sccm-task-sequence-for-optional-software-deployment-and-other-features/
Regards,
Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

Deploying 100% of available software updates during a task sequence

Hi,
Can somebody tell me if it actually possible to fully patch a computer via an SCCM 2012 task sequence using the install software updates task? If you have managed this can you shed some light on where I'm going wrong? For me, this behaviour is exactly
the same as ConfigMgr07... It simply doesn't work as it should.
I've integrated IE9 into my image and then added in all available updates via offline servicing. My task sequence installs windows, installs Adobe Reader, Office 2010 and Visio Viewer 2010. I then reboot the machine and perform all my patching via the Install
Software Updates task (with it set to 'all'), then reboot again. I do this four times in total.
It downloads and installs some 24 updates in the first instance. The second, third and fourth time it doesn't download or install anything.
When the task sequence completes and the OS first starts up there are 10 updates waiting to be installed (including updates for Adobe Reader and Flash that I have published to the WSUS server via SCUP). After installing those and rebooting there is a single
hotfix available (KB2533552). After installing that and rebooting, .NET4 Client Profile is waiting for me. After that there another nine more updates are available (mainly .NET4). Reboot, .NET4 Framework, reboot 5x .NET4 framework updates.
Why does the software update task not install 'all' updates when that is what I've selected? I have an automatic deployment rule targeted to my OSD and Unknown Computers collections. The rule is set to include Windows 7, Office 2010 and Adobe products with
all update classification types.

I don't have a pause in my script and have not encountered any issues with the scan not finishing before the Software Update installation step. This is true for my B&C TSs which install in the region of 200 updates, including custom trusted publisher
updates from SCUP 2011. So I can't really comment on that side of things.
With regards to the patching side of things: I tried removing the multiple reboot patches from my Task Sequences by excluding them from the Auto Deployment Rules that target the same containers as the task sequences by adding -KBxxxxxx in the ADR. Unfortunately,
due to me having the multiple reboot updates targeted up 'update' collections that are populated by hardware/software DB queries, any PC that is performing a 'Refresh' TS ends up with the offending patches being targeted for install anyway and the TS fails.
For a long time I was just removing the client record from the DB and recreating it so that the offending updates would not be targeted to the client. Once the client has been refreshed, a hardware inventory is performed, the collections updated daily, the
multiple reboot patches are detected and are scheduled for install for the following Friday afternoon. This used to annoy me as I don't like 'incomplete' clients being delivered to users' desktop.
Recently though I've been toying with offline servicing. At first I attempted to integrate every available update but this just ended up killing things too. A number of the updates that can be installed via offline servicing have a .net 4 pre-requisite
but because .net 4 cannot be slipstreamed, the prerequisite is not satisfied, Windows setup fails and so does the TS. So using this method there is a chance you'll end up installing a patch that will kill your image... Still not ideal.
What I have settled on is slipstreaming specific patches into my installation media using dism and then running a B&C TS to update my image.
This is the batch file I use (you'll need to change to suit):
Dism /mount-wim /wimfile:D:\SCCMContentSources\Applications\Microsoft\Windows\7\Professional\SP1\64-bit\Sources\install.wim /index:1 /mountdir:D:\HotFixIntegration\Offline
Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\Updates
Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\IE
Dism /unmount-wim /mountdir:D:\HotFixIntegration\Offline /commit
The first line mounts the image.
The second line slipstreams the following .msu updates:
kmdf-1.11, KB2526870, KB2529073, KB2545698, KB2561285, KB2574819-v2, KB2592687, KB2617858, KB2670838, KB2726535, KB2729094-v2, KB2786081, KB2834140-v2, KB2847311, KB2855844, KB2862330-v2, KB2862335, KB2864202, KB2868038, KB2876284, KB2883150, KB2884256,
KB2965788, KB2984976, KB917607, KB971033, KB976399, KB977944, KB981750
These are essentially just the multiple reboot patches and their pre-requisites, IE11 prerequisites, and a few KBs that not published to WSUS.
The third line slipstreams IE11 from the IE11 .cab file.
The fourth line commits the changes to the install media.
After running a B&C TS from this modified installation source there are no updates available to freshly deployed images (until the next patch Tuesday!).
Unfortunately this a manual process as I need to check the multiple reboot KB article each time updates are released but it's the only way I can put out 100% patched PCs and have a PC Refresh task sequence that doesn't fail.

Creative Cloud: "Build" MSI Hangs During SCCM OSD Task Sequence Installation

I wanted to share problem and solution I found when deploying Creative Cloud Packager-created packages/application using SCCM 2012 R2. I encountered this problem packaging this as both a Package and as an Application in SCCM.
When installing the software through SCCM Software Center onto a client, Software Center would close right as the installation of the "Build" folder MSI completed. This is abnormal behavior.
When installing the application as part of an OSD Task Sequence, the software would get installed (as shown by logs) but SCCM would hang forever at the "Installing Application" step.
I tried all sorts of different settings in SCCM and with the MSIEXEC command line and eventually traced it to the Reboot Manager functionality in MSIEXEC that will close and attempt to restart processes using files that the installer needs. Reboot Manager clobbered part of SCCM and in the Task Sequence, the connection between SCCM and the installer was broken.
The solution is to pass the property "MSIRESTARTMANAGERCONTROL=Disable" along the command line when calling MSIEXEC on the Build folder MSI file. This setting disabled Restart Manager so it didn't mess up SCCM. Once I did this, my Software Center installs and OSD Task Sequences ran as intended.
For reference, I used the REBOOT=ReallySuppress property for reboots and let SCCM determine what to do with reboots based on the return code. My testing was done with Windows 8.1 Enterprise x64.

Like said, did you configure my proposal: "Configuration Manager client will force a mandatory device
restart" ? After you've configured that, update your deployment type manually and remove the old revisions of the application and try running the TS again. I'm guessing you're a little bit too fast on your doings so the ConfigMgr doesn't play a long very
nicely...
The TS stops because of your Hard Reboot (exit code 1641), I've seen this before and I configured my application so that ConfigMgr client will force device restart and that fixed my problem. Although, also my application is the last one in the TS, but still,
the TS continues after the reboot.
Btw. have you tried changing your command line to:
msiexec.exe /i cd-ord.msi TRANSFORMS=sv-se.mst MVLICENSE_KEY=xxxxxxxxxxxxxxxxx /L*V "%temp%\cdord.log" /qn
/norestart

Allow this application to be installed from the install software task sequence action without being deployed

What functionality does this setting enable when checked? The only thing I find in product documentation (CM2012_Web.chm, 2/1/2014) states:
For applications to be installed by using a dynamic variable list, the following setting must be enabled on the
General tab of the application’s Properties dialog box:
Allow this application to be installed from the Install Application task sequence action instead of deploying manually
Note - My ConfigMgr 2012 R2 CU1 Application Properties now displays a tab labeled "General Information". I do not find one labeled "General". The configuration setting also reads "Allow this application to be installed
from the install software task sequence action without being deployed" instead of "Allow this application to be installed from the Install Application task sequence action instead of deploying manually"
Is application installation using a dynamic variable list the only time this configuration setting is used and functions?

Yes, you only have to check that when using the dynamic variable list(s).
Torsten Meringer | http://www.mssccmfaq.de

Pause Task Sequence, Manually Installs Software

Similar Messages

Maybe you are looking for