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.

Similar Messages

Deploy all software updates using SCCM task sequences

Hi, we are using System Center Configuration Manager 2012 R2 and I want to include software update installation part within the OSD.
So far I tried below links but not able to make it work:
https://technet.microsoft.com/en-in/library/bb632402.aspx
http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part_5.html
http://dptechjournal.blogspot.in/2014/04/weekly-lab-patching-task-sequence.html
https://social.technet.microsoft.com/Forums/systemcenter/en-US/b525aafc-b613-49a2-9015-3ae1c2db2e01/applying-software-updates-through-a-task-sequence
Can someone help me with this please?
~VST
~VST

Hi,
Please provide more information. If the task sequence failed to run, you need to check smsts.log and update logs on the client.
https://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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

I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion - NOT Mountain Lion. Tried all available software updates - no joy. Any ideas please?

I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion (10.7.4) - NOT Mountain Lion. Tried all available software updates - all up to date apparently but still no joy. OS X Lion shows the LX5 as a supported file format. I dont want to have to upgrade to Mountain Lion just to see if this solves the problem. Any ideas please.

Since when did this happen? Directly after you upgraded to Aperture 3.3.2?
If it happened directly after the upgrade the problem may be, that the raw support for your camera got lost. For some posters it helped to register the raw support again, see this post by Alan Roseman:
Aperture 3 preview of raw file greenish
If this does not help, you may need to reinstall Lion to bring back the raw support.
But if the problem occured independent of a new installation, ypu may have a problem with your camera or the card you are using. Have you tried to use a different card or to reformat the card in the camera?

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"?

Does 2012 OSD get around requirements to get to the MP during the task sequence?

Currently right now I am working in an environment where we are on SCCM 2007, but will be going to 2012 next year. We are in the process of trying to make it so we can build on a secure network that cannot route to any other network. I am prepared to put
a DP out on this same network, but the problem I am running into is that during the task sequence starting, it downloads the task sequence from the MP, not the DP as it is not associated with the package. The MP is not on the same un-routable network. We will
need to have about 6 or so of these, so we do not want to setup 6 MP because now you are looking at not only 6 primary site licenses, but 6 SQL installs (Our environment will not let me get away with doing SQL express for support reasons) which adds up quickly.
Below is a link to exactly what I am speaking about:
http://blogs.technet.com/b/configurationmgr/archive/2009/04/16/configmgr-2007-primary-site-mp-is-used-for-the-task-sequence-even-when-deploying-osd-images-to-secondary-sites.aspx
What I am wondering is if SCCM 2012 OSD was structured differently in a way that access to the MP is no longer necessary during the task sequence process (say for example the task sequence xml is replicated to DPs too)?
Thanks.

My apologizes. I was meaning to say Primary, Secondary Sites. Not MPs. I brought this up to give reference to idea about the boundaries that I am going to have to use to prevent these clients from contacting DPs they they can't route to.
The idea behind getting off the build network and onto a prod is that security requirements from my companies Infosec require that we limit the amount of traffic on production networks. The idea is that the server be built on the build network, disconnected
and brought into prod. The whole time the MP would be the same, but the DP would switch based on the prod network they were brought into as DP will reside in these prod networks which will get flipped over by the boundary for the prod subnets. Once on the
prod network they would be able to contact the MP.
I would love to do stand-alone media, this is one of the first roads I started looking down as I have done them in the past for offline builds, but I need the machine to auto assign its hostname from a external servers that will script the build. The build
process we are trying to put into place will be started from an external website. My first thought was to have it add the machines to a collection and add a variable that would be turned into a task sequence variable during the TS and use it for the hostname
when it attempt to apply the Windows settings. The only way I think I could get this to work would be to write a script that is executed during the task sequence that would match the MAC address of the machine and assign the hostname by calling on another
share that is written to by the external website with the MAC and hostnames. The only problem that I cannot get around is that this build process needs to be fully automated and this is for both virtual and physical. I have no problems mounting a stand-alone
build ISO using a script for VMWare, but the problem starts when I look at the physical and limitations of scripting for both iLo and iDRAC for performing this step. iLo can be done, but iDRAC is limited.
As for a reverse-proxy I will not be able to look at that. They have specific requirements against using reverse-proxies in only specific situations and this it not allowed. I got turned down on this one. This requirement is created by a federal regulation
my company has to follow.

Nvidia (Quadro K2000) Driver isn't installed during OSD (Task Sequence succeeded) - HP Z620

Hi everyone,
I have added a driverset (HP Z620) in SCCM for the first time using our internal procedure (Importing Drivers to SCCM, Create Driver package with specific category, apply driver package in TS using WMI to query for the model).
The Task Sequence succeeded, but the NVIDIA K2000 Graphics driver isn't installed (only HD Graphics 4000 driver).
Looking at the drivers in the Driver Package, this should normally apply since the driver is compatible with this specific GPU.
At the forums, I can see that some people have created a seperate package for the GPU driver installation using command line switches.. But looking at the environment at the customer, we have never done this and in the past, we have succesfully installed
the driver for this GPU before.
PS: The driver for the GPU in my new driver package (HP Z620) isn't the same as for previous models (HP Z220, Z230, Z600).
Could you please advise me what to do? Should I have added something in the driver sources before importing the driver to SCCM?
Thanks in advance!
Kind regards

Hi
I m installing Nvidia (Quadro K2000) Driver during OSD (Task Sequence succeeded) - HP Z420
Remove the Graphics driver for NVIDIA from the current driver database
Added below task in the existing task sequence as invidual installation based on the Condition (WMI query)
Command Line
HP_Z420_Graphics_x64\Win64_332_50\setup.exe -s -k -clean -noeula
This will install the desired driver and related configurable components
WMI Query
select * from win32_ComputerSystem where manufacturer like '%hewlett%' and model like '%z420%'
Currently I m looking out for the Errors codes needed to add to this task . Success codes 3010 and 0 already added

Install Software Updates fails (timeouts) during OSD Task Sequence

Hi
As one of the lasts steps in our OSD Task Sequence we have an "Install Software Update" step where "Mandatory Software Updates" is choosen. It worked a week ago, but now the step fails with error code 0x800705B4
(This operation returned because the timeout period expired.)
When examining the WindowsUpdate.log I see an error followed by several minutes without log activity:
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:999
1632 4e4
COMAPI - Updates found = 260
2014-02-18 10:39:13:999
1632 4e4
COMAPI ---------
2014-02-18 10:39:13:999
1632 4e4
COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]
2014-02-18 10:39:13:999
1632 4e4
COMAPI -------------
2014-02-18 10:39:18:835
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 11:08:12:225
416 4dc
AU AU received policy change subscription event
2014-02-18 11:08:12:334
416 4dc
AU AU Options changed from policy.
2014-02-18 11:08:12:334
416 4dc
AU Successfully wrote event for AU health state:0
2014-02-18 11:08:12:334
416 4dc
AU ########### AU: Policy change processed ###########
When examining the WUAHadler.log - again there is no log activity during the Software Update step.
Its a WSUS Update Source type ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}), adding it.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Existing WUA Managed server was already set (http://<servername>:8530), skipping Group Policy registration.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Added Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Scan results will include all superseded updates.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching of updates using WUAgent started.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching completed. WUAHandler
18-02-2014 10:39:13 1108 (0x0454)
Successfully completed scan. WUAHandler
18-02-2014 10:39:15 2016 (0x07E0)
Removed Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 11:06:25
1160 (0x0488)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
for bundles WUAHandler
18-02-2014 11:09:25 2232 (0x08B8)
The Software Update Step started at 10:27 and the timeout came at 11:05.
Any ideas why the step times out? Or which logs I should look at?
Regards,
FC

PolicyEvaluator.log:
No errors. The last event is:
Received notification that Local policy has changed.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:11
1692 (0x069C)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095123.565000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 1768;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:23 1768 (0x06E8)
Forcing settings update for local policy change.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:23
2900 (0x0B54)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:33
2900 (0x0B54)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095144.641000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 2900;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:44 2900 (0x0B54)
UpdatesHandler.log:
No errors. A couple of lines:
Successfully initiated scan. UpdatesHandler
19-02-2014 10:54:10 1768 (0x06E8)
Updates scan completion received, result = 0x0.
UpdatesHandler 19-02-2014 10:55:23
3572 (0x0DF4)
UpdatesStore.log
No errors. Just quering updates, and the last line:
Querying update status completed successfully.
UpdatesStore 19-02-2014 10:56:27
3300 (0x0CE4)
In the smsts.log I found an interesting thing:
Successfully initiated RefreshUpdates operation
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
Waiting for RefreshUpdates complete notification from Updates Deployment Agent
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
Timedout waiting for updates refresh complete notification
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
It times out after exactly 30 minutes. Does 2012 have the same "feature" as 2007? (http://support.microsoft.com/kb/2009754/da)
Still the last event in windowsupdate.log is:
2014-02-19 10:55:37:251
324 dd0
Report CWERReporter finishing event handling. (00000000)
Regards,
FC

IPhoto 6.0.4 says update available, Software Update disagrees

OK, I'm a bit confused here. I've got a fairly new Mac Pro (2.66 quad xeon). When I start iPhoto (6.0.4), it says that there is a new update available (6.0.5), but when I run Software Update, it says "Your software is up to date.". Ditto for iDVD and iMovie HD. Am I missing something here? Any suggestions?

It's working now. I had moved a few applications around so my applications folder wasn't so cluttered, and the update only works if the app is in /Applications.

ITunes says new version available / Software Update says no updates???

I started iTunes today on my MacBook Air and it immediately reported that there is a new version of iTunes available. After responding to the prompt regarding a new version by clicking on the "Download iTunes" button, iTunes launched Software Update. However, Software Update does its check and then comes back with a message that there is no software to update.
The version of iTunes on my system is 10.2, not the new 10.2.1. Anyone have any idea why Software Update does not believe there is an update when iTunes does? Any way to fix this?

Same problem here...
I've a 2010Mini and a late2008MBP15, both running OSX 10.6.6.
Updating to 10.2.1 went charming well on the mini, but not the same on the MBP:
iTunes "info on iTunes" shows version 10.1.1 running... even after I removed iTunse (and iTunes Helper) from the HDD and re-installed from a freshly downloaded 10.2.1 DMG file.
As i start iTunes, it shows "upgrade available" message, but software upgrade utility doesn't find any upgrade, of course.
BTW, I even verified iTunes.app version using "file information" and the one in my Applications folder is 10.2.1... but as I run it, it "believes" to be 10.1.1
Any Clue?

Remote Software Updates and Sending Task Status to User

I am updating user's machines using ARD 3 with the unix command 'softwareupdate -i -a'. With some updates, a restart is required and ARD posts this within the task status column.
I was wondering if there was a way to grab that task status of "restart needed" or "succeeded" and then send that to the user when the software update has completed.
Any help would be appreciated.
Thanks.

System restart checkbox is used to control what happens outside of MW.
If you have no MW and did not select to restart outside of MW then systems will reboot after installation completes (unless user overrides it and does it sooner). Keep in mind that the 90 minute and 15 minute restart countdowns will be displayed if user is
logged in (unless you have changed the times) if user did not interact with any notifications to select other options like install and reboot ahead of time.
If you have MW and did not select to restart outside of MW, then PC will not reboot until MW starts (unless user overrides it, of course).
If you select to reboot outside of MW checkbox then PC will reboot after installation ends, no matter if MW is set or not.

KB2509007 did not fix problem with Install Updates hanging at 0% during OSD task sequence

Hi everybody. We recently started building our Build & Capture Task Sequence for our Windows 7 gold image. However, I keep running into the problem where the Install Software Updates step keeps hanging at "downloading updates 1 of 164 (0%).
This is a known issue that is supposed to be addressed with hotfix KB2509007. I followed the instructions
here to install the hotfix on my site server. I then added the PATCH= argument to my "Setup windows and ConfigMgr" step in my TS. But still my TS was hanging in the same spot.
Then I found
this page, which says that there is another known issue with KB2509007, and the order in which it is installed along side other hotfixes (such as R3). So I followed those instructions, and confirmed that UpdatesHandler.dll is at version 4.00.6487.2188,
and BOOM, the updates installed and I captured my gold image. This was about a week ago.
Well, since then, we have had a patch Tuesday, and I am trying to run by Build & Capture TS again to integrate the latest updates into my gold image, but now my TS is hanging at 0% again! I have confirmed that UpdatesHandler.dll is at the correct version,
so I am unsure what the issue could be now.
Does anybody have any experience with this issue? Thanks in advance for any help!
UPDATE: I re-ran my TS, and now the updates are installing. I'm not sure why the behaviour is so inconsistent though...

Hi everybody. We recently started building our Build & Capture Task Sequence for our Windows 7 gold image. However, I keep running into the problem where the Install Software Updates step keeps hanging at "downloading updates 1 of 164 (0%).
This is a known issue that is supposed to be addressed with hotfix KB2509007. I followed the instructions
here to install the hotfix on my site server. I then added the PATCH= argument to my "Setup windows and ConfigMgr" step in my TS. But still my TS was hanging in the same spot.
Then I found
this page, which says that there is another known issue with KB2509007, and the order in which it is installed along side other hotfixes (such as R3). So I followed those instructions, and confirmed that UpdatesHandler.dll is at version 4.00.6487.2188,
and BOOM, the updates installed and I captured my gold image. This was about a week ago.
Well, since then, we have had a patch Tuesday, and I am trying to run by Build & Capture TS again to integrate the latest updates into my gold image, but now my TS is hanging at 0% again! I have confirmed that UpdatesHandler.dll is at the correct version,
so I am unsure what the issue could be now.
Does anybody have any experience with this issue? Thanks in advance for any help!
UPDATE: I re-ran my TS, and now the updates are installing. I'm not sure why the behaviour is so inconsistent though...

Update Content and Task Sequence Changes are Slow

ConfigMgr 2012 R2
When choosing "Update Content" from the deployment under the Deployment Types tab, the revision number changes but the update takes about 30 minutes to complete. When app testing this is becoming increasingly frustrating. A change made
and then having to wait ~30 minutes is wasting too much time. This delay doesn't always occur. When its working quickly, the pie chart would immediately turn yellow and a few minutes later files would be updated and the Last Update: under the pie
chart would show the current time/date. The packages being tested are all small and being distributed to a couple local DPs over 1GB connections. When triggering "Update Content", the distmgr.log does not display any information about
the distribution of the files until it actually does start which as mentioned earlier starts roughly 30 minutes after triggering "Update Content". Keep in mind it's not exactly 30 minutes. This timeframe is variable.
Also noticed that when an app install was set to disabled in a Task Sequence, when PXE booting, the app was still trying to run. Sometimes an app can be changed to disabled and an immediate PXE boot will not attempt to install the app. This also
applies to enabling a disabled app.
The update content issue would appear to be some type of backlog issue but disabling an app in a Task Sequence seems like it would be more like a DB transaction. Although it seems like two issues, both issues rear their ugly head at the same
time.
Any thoughts?
Thanks

Hi ,
Thanks for the info. When you create a package, the files are copied from the source path to the content library on the site server. Then, the content is copied from the content library on the site server to the content library on the distribution points.
Please also check if "Allow clients to connect anonymously" is enabled on the DP Properties. See this link:
https://social.technet.microsoft.com/Forums/en-US/a291c1cd-ab00-47f0-a99a-6befe178dfc7/sccm-2012-r2-osd-very-slow-at-driver-package-and-config-manager-client-stage-still-after-kb2905002?forum=configmanagerosd
http://blogs.technet.com/b/configurationmgr/archive/2010/06/03/solution-you-may-experience-slow-performance-when-using-bits-and-kerberos-authentication-on-configmgr-2007-distribution-points.aspx\
Thanks.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Software Center showing Application Task Sequence as Operating System

I have created a custom task sequence and it includes 2 applications. The first one uninstalls an app using a batch file and the 2nd TS installs a new version. The problem is that software center is showing type Operating System so when I click
on it to install, it gives a message about installing an operating system and it may delete/format the drive.
Is there a setting I need to change so it sees it as an application rather than an OS? I have other application Task Sequences that show as application rather than Operating System...
Thanks
Rick Ray

That's by design. And by design Task Sequences were meant for Operating System Deployment, that's why you also get notified about "Operating System Installation" in the Software Center.
You should use SCCM Applications with supersedence to accomplish what you are trying to do:
Do an application for App 1 (your old app)
Do an application for App 2 (your new app)
Configure App2 to supersede App1 (uninstall the App1)
Deploy App2 to your computers
This way the App1 will be uninstalled before the App2 is installed.

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.

Deploying 100% of available software updates during a task sequence

Similar Messages

Maybe you are looking for