Software Updates 31/07/2015

Manufacturer
Device
Os
Os Version
Type
Status
Current/Expected Deployment
Blackberry
Classic
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Q10
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Z10
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Z30
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
HTC
One M9
Android
Lollipop 5.1
Platform update
Scheduling
10-Aug-15
Android Lollipop 5.1 update. This update also resolves the recently disclosed "Stagefright" Android security vulnerability.
Motorola Mobility
RAZR M
Android
Kit Kat 4.4.2
Platform update
Now deploying
13-Jul-15
Approved 26 June. FOTA deployment expected to commence by Monday 13 July
Microsoft
Lumia 532
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Microsoft
Lumia 640
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Nokia
Lumia 520
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Nokia
Lumia 530
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Nokia
Lumia 625
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Nokia
Lumia 635
Windows Phone
Blue 8.1
Bugfix only
Now deploying
20-Jul-15
Nokia
Lumia 830
Windows Phone
Blue 8.1
Bugfix only
Now deploying
17-Jul-15
Nokia
Lumia 930
Windows Phone
Blue 8.1
Bugfix only
Now deploying
17-Jul-15
Nokia
Lumia 1320
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Samsung
Galaxy Note Edge
Android
Lollipop 5
Platform update
Now deploying
13-Jul-15
Approved 6 July
Samsung
Galaxy S2 4G
Android
Gingerbread 2.3
Bugfix only
Testing
31-Aug-15
Due to an issue identified in testing a new version is required. New test submission received 19 June however test completion delayed due to Telstra resource constraints
Samsung
Galaxy S4 mini 4G
Android
Kit Kat 4.4.2
Platform update
Now deploying
13-Jul-15
Approved 29 June
Samsung
Galaxy Tab 3 8 inch
Unknown
N/A
Bugfix only
Scheduling
TBC
MR to address open SSL issues, Samsung ETA submission delayed
Samsung
Note 10.1
Android
Kit Kat 4.4
Platform update
Scheduling
11-Sept-15
Delayed software submission target 14 Aug
Samsung
Tab S
Android
Lollipop 5
Bugfix only
Testing
TBA
Software submitted currently in testing. Testing has blocking issues pending Samsung to re-submit software.
Sony
Castor T2
Android
Lollipop 5.1.1
Platform update
Testing
14-Aug-15
Software submitted currently in testing, on track to the current schedule.
Sony
Xperia Z
Android
Lollipop 5
Platform update
Testing
10-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approval has been delayed due to Telstra resource constraints
Sony
Xperia Z
Android
Lollipop 5.1
Platform update
Scheduling
TBC
Sony have delayed the submission to a date TBC
Sony
Xperia Z1
Android
Lollipop 5
Platform update
Testing
03-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approval was delayed due to Telstra resource constraints. Approved 28 July
Sony
Xperia Z1
Android
Lollipop 5.1
Platform update
Scheduling
TBC
Sony have delayed the submission to a date TBC
Sony
Xperia Z1 Compact
Android
Lollipop 5
Platform update
Testing
03-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approved 28 July
Sony
Xperia Z1 Compact
Android
Lollipop 5.1
Platform update
Scheduling
TBC
Sony have delayed the submission to a date TBC
Sony
Xperia Z2
Android
Lollipop 5.1
Platform update
Testing
03-Aug-15
Resource constraints have delayed approval of this update by 1 week. Approved 28 July
Sony
Xperia Z3
Android
Lollipop 5.1
Platform update
Testing
12-Aug-15
Resource constraints have delayed approval of this update
Sony
Xperia Z3 Compact
Android
Lollipop 5.1
Platform update
Testing
03-Aug-15
Resource constraints have delayed approval of this update by 1 week. Approved 28 July

TBA means that we don't have an expected available date at the moment. We are waiting for new software for this device to be submitted so until the manufacturer has advised when to expect the software or provided it we cannot be sure how long it will be.
the update was approved on the 28th of July. The expected available date is an estimate of when the manufacturer will release the update, however please be aware that the dates are not deadlines and there can be delays.
I will follow up with the testing team as the most recent information I have is the update was approved and sent back to Motorola.
the table shows all updates that are currently being tested or we have been advised by the manufacturer that it is coming. If your device is not listed then there we have not received or been advised of an upcoming update as yet.

Similar Messages

Software Updates 06/08/2015

Update 10/08: Added LG G4 to the table
Manufacturer
Device
Os
Os Version
Type
Status
Current/Expected Deployment
Blackberry
Classic
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Q10
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Z10
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
Blackberry
Z30
Blackberry
Blackberry OS 10.3.2
Platform update
TBC
Due to Telstra resource constraints delaying testing this update will now be skipped in favour of the next OS update due for submission in mid August
LG
G4
Android
Lollipop 5.1.1
Bugfix Only
Scheduling
7-Sep-15
This update implements the fix for the recently disclosed "Stagefright" Android security vulnerability.
LG
Nexus 5
Android
Lollipop 5.1.1
Bugfix Only
Now deploying
6-Aug-15
Fix for the recently disclosed "Stagefright" Android security vulnerability.
HTC
One M9
Android
Lollipop 5.1
Platform update
Now deploying
6-Aug-15
Android Lollipop 5.1 update. This update also resolves the recently disclosed "Stagefright" Android security vulnerability. Deployment of the update will commence at 13:00 AEST 6 August
Motorola Mobility
RAZR M
Android
Kit Kat 4.4.2
Platform update
Now deploying
13-Jul-15
Approved 26 June. FOTA deployment expected to commence by Monday 13 July
Microsoft
Lumia 532
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Microsoft
Lumia 640
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Nokia
Lumia 520
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Nokia
Lumia 530
Windows Phone
Blue 8.1
Bugfix only
Now deploying
13-Jul-15
Nokia
Lumia 625
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Nokia
Lumia 635
Windows Phone
Blue 8.1
Bugfix only
Now deploying
20-Jul-15
Nokia
Lumia 830
Windows Phone
Blue 8.1
Bugfix only
Now deploying
17-Jul-15
Nokia
Lumia 930
Windows Phone
Blue 8.1
Bugfix only
Now deploying
17-Jul-15
Nokia
Lumia 1320
Windows Phone
Blue 8.1
Bugfix only
Approved - waiting for deployment
03-Aug-15
Approved 28 July
Samsung
Galaxy Note Edge
Android
Lollipop 5
Platform update
Now deploying
13-Jul-15
Approved 6 July
Samsung
Galaxy S2 4G
Android
Gingerbread 2.3
Bugfix only
Testing
31-Aug-15
Due to an issue identified in testing a new version is required. New test submission received 19 June however test completion delayed due to Telstra resource constraints
Samsung
Galaxy S4 mini 4G
Android
Kit Kat 4.4.2
Platform update
Now deploying
13-Jul-15
Approved 29 June
Samsung
Galaxy S6
Android
Lollipop 5.1
Platform update
Testing
31-Aug-15
Samsung have withdrawn this update due to a stability issue identified in their internal testing. A new test submission is due 7 August and will include fix for the recently disclosed "Stagefright" Android security vulnerability.
Samsung
Galaxy S6 Edge
Android
Lollipop 5.1
Platform update
Testing
31-Aug-15
Samsung have withdrawn this update due to a stability issue identified in their internal testing. A new test submission is due 7 August and will include fix for the recently disclosed "Stagefright" Android security vulnerability.
Samsung
Galaxy Tab 3 8 inch
Unknown
N/A
Bugfix only
Scheduling
TBC
MR to address open SSL issues, Samsung ETA submission delayed
Samsung
Note 10.1
Android
Kit Kat 4.4
Platform update
Scheduling
11-Sept-15
Delayed software submission target 14 Aug
Samsung
Tab S
Android
Lollipop 5
Bugfix only
Testing
TBA
Software submitted currently in testing. Testing has blocking issues pending Samsung to re-submit software.
Sony
Xperia Z
Android
Lollipop 5
Platform update
Testing
10-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approval has been delayed due to Telstra resource constraints
Sony
Xperia Z
Android
Lollipop 5.1.1
Platform update
Scheduling
07-Sep-15
This is the Android 5.1 update and will include fix for the recently disclosed "Stagefright" Android security vulnerability.
Sony
Xperia Z1
Android
Lollipop 5
Platform update
Approved - waiting for deployment
03-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approval was delayed due to Telstra resource constraints. Approved 28 July
Sony
Xperia Z1
Android
Lollipop 5.1.1
Platform update
Scheduling
28-Sep-15
This is the Android 5.1 update and will include fix for the recently disclosed "Stagefright" Android security vulnerability.
Sony
Xperia Z1 Compact
Android
Lollipop 5
Platform update
Approved - waiting for deployment
03-Aug-15
Due to a Sony platform restriction it is not possible to update from Android KitKat 4.4 to Android Lollipop 5.1 without first updating to Android 5.0, hence this update is currently being tested and approved. Approved 28 July
Sony
Xperia Z1 Compact
Android
Lollipop 5.1.1
Platform update
Scheduling
28-Sep-15
This is the Android 5.1 update and will include fix for the recently disclosed "Stagefright" Android security vulnerability.
Sony
Xperia Z2
Android
Lollipop 5.1
Platform update
Approved - waiting for deployment
03-Aug-15
Resource constraints have delayed approval of this update by 1 week. Approved 28 July
Sony
Xperia Z2 Tablet
Android
Lollipop 5.1.1
Platform update
Testing
14-Aug-15
Software submitted currently in testing, on track to the current schedule.
Sony
Xperia Z3
Android
Lollipop 5.1.1
Platform update
Approved - waiting for deployment
10-Aug-15
Approved 3 August
Sony
Xperia Z3 Compact
Android
Lollipop 5.1.1
Platform update
Approved - waiting for deployment
03-Aug-15
Resource constraints have delayed approval of this update by 1 week. Approved 28 July

How about you get around to releasing Lollipop 5.1 or 5.1.1 to Samsung S5 customers? On reading the terminology post I came across this... "What is a showstopper?A “showstopper” is a bug or behaviour on a device’s hardware or software that is deemed so serious that we cannot release the device and/or software to customers. It essentially “stops the show” with the “show” being the device or software launch.
Showstopper issues can appear in many (in fact all) parts of a devices hardware/software implementation but in practice they are more common in some areas. Some common ones include compliance to emergency calling regulations, stability issues such as reproducible device resets/hangs, reproducible voice-call drops, network connection issues, poor data performance or coverage issues." Why was Lollipop 5.0 ever released to Samsung S5 when you knew full well it has a memory leak issue. I can barely use my phone. That's a show stopper for me and your slack release of updates quite frankly is a show stopper for my ongoing custom with Telstra.

New March software update (only retail at the mome...

Retail boxes are fetting a new update from today... When is it coming to BT? https://community.youview.com/youview/topics/automatic-software-update-for-march-2015
The On Demand section has been replaced with Players and apps to make it easier to find content. The full range of on demand players e.g. BBC iPlayer, Netflix can be found in Players. The new Apps section contains great additional content such as BBC News and BBC Sport, with more to follow soon.
A new Discovery section has been added to the main menu. Here you’ll find a huge range of the most popular On Demand programmes including Comedy, Sport, Entertainment and more
Update to the TV guide are now available in the YouView Guide. This makes it even easier to identify the different channels available for you to view.

I would also like the new update to come to BT soon as it looks a big improvment to the Youview boxs.
Darren

AT&T released a software update for the HTC One M9 (OPJA110) on July 15, 2015.

HTC One M9 users, AT&T released Android Version 5.1 for OTA download today!
To download:Drag down the notification bar with two fingers, and then tap Settings > General.Tap About Phone > AT&T software update.Tap Check for updates.Tap Update Now.Follow the on-screen instructions.Please note: Devices require Wi-Fi connection to download the update, and is recommended to be fully-charged.
To learn more about the software update, please go to www.att.com/softwareupdates! Enjoy!!!

The new update keeps failing OTA on my HTC one M9 Is anyone else experiancing this issue. If they let you post am image I captured the fail page.

I can't uninstall Apple Software Update.

In trying to uninstall ITunes, I was given a checklist from Apple Support to uninstall certain programs in a specific order. I need to reinstall ITunes, and they said that I needed to remove it first. I am running a Windows 7, 64 bit HP laptop. No program is removing this and it very specifically says to not remove them out of order.
Below are the instructions sent to me. (I tried to copy and paste. However, it doesn't look good, so I will include the link that Apple sent to me.)
Can someone please help?
Remove and reinstall iTunes and related software components for Windows Vista, Windows 7, or Windows 8
Learn how to completely uninstall iTunes and its related software components from Windows Vista, Windows 7, or Windows 8.
In some rare instances, you might need to remove iTunes and related software components before reinstalling iTunes. If you're directed to reinstall iTunes by AppleCare, an article, or an alert dialog, you can do so by following the steps below.
If you're running Windows XP, see Removing and Reinstalling iTunes and other software components for Windows XP.
Media you've bought from the iTunes Store or songs you've imported from CDs are saved in your My Music folder by default. They won't be deleted by removing iTunes. Although it's highly unlikely that you'll lose any of your iTunes Library when following the steps below, first make sure that your iTunes library is backed up. See iTunes: Back up your iTunes library by copying to an external hard drive for more information.
If you have issues installing iTunes, try the options outlined in Issues installing iTunes for Windows.
If you've received errors regarding inaccessible registry keys during installation, try the steps found in "Could not open key" message when installing iTunes, QuickTime or Apple components for Windows.
Steps
Remove iTunes and related components from the Control Panel.Use the Control Panel to uninstall iTunes and related software components in the following order. Then restart your computer.
iTunes
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support (iTunes 9 or later)
Don't uninstall these components in a different order, or only uninstall some of them. Doing so might have unintended affects.To remove the components:
Quit the following programs if they are running:
iTunes
Apple Software Update
Windows 8: Click File Explorer > Settings > Control Panel.
Windows Vista or Windows 7: From the Start menu, click Control Panel.
In Control Panel, click "Uninstall a program." The Programs and Features Control Panel will open.
Alternately, if you don't see "Uninstall a program," click Programs and Features.
Select iTunes.
Click Uninstall.
On some systems, iTunes might install two versions of Apple Application Support. This is expected. If both are present, be sure to uninstall both versions.
When asked if you would like to remove iTunes, choose Yes.
After the uninstallation is complete, don't restart your computer if you're prompted.
If you see other iTunes entries in the list, remove them by repeating steps 4–6.
Using steps 4–6, also remove all instances of:
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support
Restart your computer.
Make sure that iTunes and its related components are completely uninstalled.In most cases, removing iTunes and its related components from the Control Panel will remove all supporting files belonging to those programs. In some rare cases, files might be left behind. After following the steps above, confirm that the following files and folders have been removed. If any are left, remove them.
C:\Program Files\Bonjour
C:\Program Files\Common Files\Apple\Mobile Device Support
C:\Program Files\Common Files\Apple\Apple Application Support
C:\Program Files\Common Files\Apple\CoreFP
C:\Program Files\iTunes\
C:\Program Files\iPod\
Follow these additional steps if you receive a "Cannot delete iPodService.exe: It is being used by another person or program." message.
If you have a 64-bit version of Windows, confirm that the following folders have been removed:
C:\Program Files (x86)\Bonjour
C:\Program Files (x86)\Common Files\Apple\Mobile Device Support
C:\Program Files (x86)\Common Files\Apple\Apple Application Support
C:\Program Files (x86)\Common Files\Apple\CoreFP
C:\Program Files (x86)\iTunes\
C:\Program Files (x86)\iPod\
Follow these additional steps if you receive a "Cannot delete iPodService.exe: It is being used by another person or program." message.
To remove these files:
Windows Vista or Windows 7: From the Start menu, select Computer.
Windows 8: Click File Explorer.
Open Local Disk (C:) located in Computer, or whichever hard disk your programs are installed on.
Open the Program Files folder.
Right-click the Bonjour folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the iPod folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Follow these additional steps if you receive a "Cannot delete iPodService.exe: It is being used by another person or program." message.
Right-click the iTunes folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Open the Common Files folder.
Open the Apple folder.
Right-click the Mobile Device Support folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the Apple Application Support folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the CoreFP folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
If you're running a 64-bit version of Windows, continue with step 12. Otherwise, skip to step 23.
Windows Vista or Windows 7: From the Start menu, select Computer.
Windows 8: Click File Explorer.
Open Local Disk (C:) located in Computer, or whichever hard disk your programs are installed on.
Open the Program Files (x86) folder.
Right-click the Bonjour folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the iPod folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Follow these additional steps if you receive a "Cannot delete iPodService.exe: It is being used by another person or program." message.
Right-click the iTunes folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Open the Common Files folder.
Open the Apple folder.
Right-click the Mobile Device Support folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the Apple Application Support folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
Right-click the CoreFP folder (if it exists). Select Delete from the shortcut menu. Choose Yes when asked to confirm the deletion.
From the Start menu, select Computer.
Open Local Disk (C:) in Computer, or whichever hard disk your operating system is installed on.
Right-click the Recycle Bin and select Empty Recycle Bin.
Reinstall iTunes and related componentsAfter verifying that iTunes is completely uninstalled, restart your computer. Then download and install the latest version of iTunes.If the issue persists, look for more information on the iTunes Support page, including help with specific messages.
iPodService.exe Alert
Follow these steps if the message "Cannot delete iPodService.exe: It is being used by another person or program" appears when you try to delete the iPod folder.
Make sure that iTunes and the iPod Updater utility aren't open.
Press and hold Control-Alt-Delete.
Select Start Task Manager.
Click the Processes tab.
Locate the iPodService.exe in the list.
Click iPodService.exe and choose End Process.
Quit the Task Manager.
Important: Information about products not manufactured by Apple is provided for information purposes only and does not constitute Apple’s recommendation or endorsement. Please contact the vendor for additional information.
Last Modified: Jan 30, 2015

For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
If the advice above doesn't resolve things you could try this alternate version:
iTunes 12.1.0.71 for Windows (64-bit - for older video cards) - itunes64setup.exe (2015-01-28)
which is a 64-bit installer for the 32-bit version of the core application, similar to previous 64-bit releases. Or roll back to the previous build:
iTunes 12.0.1.26 for Windows (32-bit) - iTunesSetup.exe (2014-10-16)
iTunes 12.0.1.26 for Windows (64-bit) - iTunes64Setup.exe (2014-10-16)
tt2

Software Updates and Dealine

Hi
we installed the Citrix application lock on nearly all of our clients. So after a sucessfully logon the user is redireted to a central desktop. All messages related to sccm are not displayed to a user.
We deployed updates and some users reported that the computer reboots automatically. The reason for this behaviour is the defined dealine. To get rid of these reboots we set the deadline to 1.1.2015. Now it looks like the updates are not getting installed
at all.
My question is:
Are mandatory updates getting installed if the deadline date is a date in the future? The deployment itself is available as soon as possible.
Thanks

Not Working as expected :-(
1) Configured updates with deadline - I see that updates getting installed.
2) Reboot suppressed in deployment
3) RebootCordinator.Log
Including grace period 5400 seconds, the system restart turnaround time is 6000 seconds RebootCoordinator 09.04.2014 10:31:30 676 (0x02A4)
Including grace period 5400 seconds, the system restart turnaround time is 6000 seconds RebootCoordinator 09.04.2014 10:31:58 2112 (0x0840)
Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. Rebootby = 1397033412. RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
Scheduled reboot from agent UpdatesDeploymentAgent. Deadline local time: 04/09/2014 10:50:12 RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
No CCM Identification blob RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
ServiceWindowsManager has allowed us to Reboot RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
MTC task does not exist. Creating new request. RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
MTC allowed us to reboot RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
Raising client SDK event for class NULL, instance NULL, actionType 4l, value 1397033412 5400 900, user NULL, session 4294967295l, level 0l, verbosity 30l RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
Notified UI grace period start with 5400 grace seconds and 900 final seconds. RebootCoordinator 09.04.2014 10:50:12 1180 (0x049C)
4) So Deadline configured, reboot suppressed, and still reboot scheduled by ConfigMgr
What's wrong?
It's quite complex but the requierement is simple.
I want to deploy software updates with a deadline and reboots 100% suppressed because the user cannot see any notification.
Regrads

IBCM Software updates, Do I need an Internet SUP or not?

Hi,
A quick description of our current setup (relevant bits at least):
Site server
Windows Server 2012 R2 with ConfigMgr 2012 R2 C3 primary site, with intranet client only SUP
DMZ server
Windows Server 2012 R2 with MP and DP roles installed (no SUP)
I'm able to manage internet clients, apply policies and deploy software (both apps and packages). So I know my IBCM setup works
Here's is the issue:
I'm unable to deploy software updates to internet clients.
Windowsupdate.log shows the following
2015-02-04 14:48:21:811 1332 1d98 EP Got WSUS Client/Server URL: "https://primarysiteserver.fqdn:8531/ClientWebService/client.asmx"
2015-02-04 14:48:21:811 1332 1d98 Setup Checking for agent SelfUpdate
2015-02-04 14:48:21:811 1332 1d98 Setup Client version: Core: 7.9.9600.17489 Aux: 7.9.9600.17489
2015-02-04 14:48:21:811 1332 1d98 EP Got WSUS SelfUpdate URL: "https://primarysiteserver.fqdn:8531/selfupdate"
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: Send failed with hr = 80072ee7.
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: Send request failed, hr:0x80072ee7
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://primarysiteserver.fqdn:8531/selfupdate/wuident.cab>. error 0x8024402c
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2015-02-04 14:48:21:811 1332 1d98 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send failed with hr = 80072ee7.
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send request failed, hr:0x80072ee7
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://primarysiteserver.fqdn:8531/selfupdate/wuident.cab>. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send failed with hr = 80072ee7.
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send request failed, hr:0x80072ee7
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://primarysiteserver.fqdn:8531/selfupdate/wuident.cab>. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send failed with hr = 80072ee7.
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: Send request failed, hr:0x80072ee7
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://primarysiteserver.fqdn:8531/selfupdate/wuident.cab>. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Misc WARNING: DownloadFileInternal failed for
https://primarysiteserver.fqdn:8531/selfupdate/wuident.cab: error 0x8024402c
2015-02-04 14:48:21:827 1332 1d98 Setup FATAL: DownloadCab failed, err = 0x8024402C
2015-02-04 14:48:21:827 1332 1d98 Setup WARNING: SelfUpdate check failed to download package information, err = 0x8024402C
2015-02-04 14:48:21:827 1332 1d98 Setup FATAL: SelfUpdate check failed, err = 0x8024402C
2015-02-04 14:48:21:827 1332 1d98 Agent * WARNING: Skipping scan, self-update check returned 0x8024402C
2015-02-04 14:48:21:827 1332 1d98 Agent * WARNING: Exit code = 0x8024402C
2015-02-04 14:48:21:827 1332 1d98 Agent *********
2015-02-04 14:48:21:827 1332 1d98 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp Id = 2]
2015-02-04 14:48:21:827 1332 1d98 Agent *************
2015-02-04 14:48:21:827 1332 1d98 Agent WARNING: WU client failed Searching for update with error 0x8024402c
I can see the primary site server, which happens to be the only SUP on the hierarchy is still being referenced.
It is my understanding that internet clients will default to downloading updates from windows update when "if software updates are note available on preferred distribution point or remote distribution point, download content from microsoft updates"
enabled in the deployment settings (see screenshot below).
My question is: Am I missing something? do I need to deploy a SUP on the DMZ site system? If so... will this DMZ SUP synchronize according to the settings defined on the site settings?
Your help would be greatly appreciated.

You can have both, btw. Configure your GPO with a filter so it only applies a WSUS point if the SCCMExec isn't detected. More info can be found here:
http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/group-policy-preferences-and-software-updates-in-cm2012sp1.aspx
This way any clients without a SCCM agent still honor the GPO for updates but the GPO effectively stops "fighting" with the installed agent once it gets installed.
Also, I'm pretty sure you still need an internet facing SUP. THe checkbox you are playing with is only for downloading the patches ... not for detecting what patches are needed:
https://technet.microsoft.com/en-us/library/gg712701.aspx
"New
in System Center 2012 Configuration Manager, when you have a software update point that is configured to accept connections from the Internet, Configuration Manager Internet-based clients on the Internet always scan against this software update
point, to determine which software updates are required. However, when these clients are on the Internet, they first try to download the software updates from Microsoft Update, rather than from an Internet-based distribution point. Only if this fails, will
they then try to download the required software updates from an Internet-based distribution point. Clients that are not configured for Internet-based client management never try to download the software updates from Microsoft Update, but always use Configuration
Manager distribution points."

Creating Software Update Packages - Best Practice?

I am setting up our SCCM 2012 R2 environment to begin using it for Windows Updates, however I'm not sure 100% the best method of setting it up.
Currently my plan is to break out the deployment packages by OS, but I read\told that I should avoid creating to many dynamic deployment packages, as every time it changes all the computers will re-scan that package. So What I want to do is create
various packages for OS and years, so I would have a package that contains all updates for Windows 7, older then January 31, 2013 (assuming the package doesn't have 1000+ updates), and are not superseded\Expired. Then I would create Packages for the 2014
monthly updates each month, then at the end 2014, combine them all in 1 package, and restart the process for 2015. Is this a sound plan or is there a better course of action?
If this the best practice method, is there any way to automatically create these packages? I tried the Automatic Deployment Rules, but I can not set a Year of release, only the a time frame of the release,(older then 9 Months), unless I am missing
something. The only way I can see doing this is going into All Software Updates, and filtering on my requirements, and then manually creating the package, but this would less desirable, as after each year I would like to remove the superseded and expired
without having to recreate the package.
Mark.

First, please learn what the different objects are -- not trying to be rude, just stating that if you don't do this, you will have fundamental issues. Packages are effectively meaningless when it comes to deploying updates. Packages are simply a way of grouping
the binary files so they can be distributed to DPs and in-turn made available to clients. The package an update is in is irrelevant. Also, you do not "deploy" update packages and packages are not scanned by clients. The terminology is very important because
there are implications that go along with it).
What you are actually talking about above are software update groups. These are separate and distinct objects from update packages. Software Update groups group updates (not the update binaries) into logical groups that can be in-turn deployed or used for
compliance reporting.
Thus, you have two different containers that you need to be concerned about, update packages and update groups. As mentioned, the update package an update is in is pretty meaningless as long as the update is in a package that is also available to the clients
that need it. Thus, the best way (IMO) to organize packages is by calendar period. Yearly or semi-annually usually works well. This is done more less to avoid putting all the updates into a single package that could get corrupted or will be difficult to deploy
to new DPs.
As for update groups, IMO, the best way is to create a new group every month for each class of products. This typically equates to one for servers, one for workstations, and one for Office every month. Then at the end of every year (or some other timeframe),
rolling these monthly updates into a larger update group. Keep in mind that a single update group can have no more than 1,000 updates in it though. (There is no explicit limit on packages at all except see my comments above about not wanting one huge package
for all updates.)
Initially populating packages (like 2009, 2010, 2011, etc) is a manual process as is populating the update groups. From then on, you can use an ADR (or really three: one for workstations, one for servers, and one for Office) that runs every month, scans
for updates released in the past month, and creates a new update group.
Depending upon your update process, you may have to go back and add additional deployments to each update group also, but that won't take too long. Also, always QC your update groups created by an ADR. You don't want IE11 slipping through if it will break
your main LOB application.
Jason | http://blog.configmgrftw.com

Adding Software Updates to Software Groups After Deployment

Hi all -
I went through and created 3 software update groups (for 2013, 2014, and 2015), and then distributed all three of them to a certain collection (and to all DPs). After that point, I then realized I had forgotten a number of updates for each software
update group. I downloaded the software updates and edited their membership so they would be a part of the existing software groups. When I did that their statuses said they were deployed. However, when I look at content distribution I don't see
anything changing. Almost like the new updates didn't go out to the DPs.
Do you need to redeploy the software update groups after adding new software updates? Or should this automatically distribute the new updates as part of the existing deployments.
Kind of unrelated, and not really part of my main question. Is there a best practice on the maximum number of software updates for a group? My largest group has 632 updates. I realize the dependency on reporting and all that, I am purely speak from a performance
or issues best practice.
Thanks,
--Julius

A software update group and a deployment package are two different things. When you download the updates, you download them to your deployment package. To look at the status of that process you can look at
Content Status node in the console or the distmgr.log
file.
The best-practice maximum number of updates per update group is a 1000, see also:
https://technet.microsoft.com/en-us/library/hh692394.aspx.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Software Update Failed An error occurred downloading iOS 8.1.3

I can not get the phone to update the OS? I tried different wifi points, and still no luck. I tried this at least 6 times with the same result. It looks to download, and then says it is 'preparing' for a while, and then it pukes out the message "Software Update Failed An error occurred downloading iOS 8.1.3". Anyone know how to resolve this? Thanks!

I've made a blog post on this error "
SOFTWARE UPDATE FAILED AN ERROR OCCURRED WHILE DOWNLOADING IOS 8.X.X
I hope this might help for those who are facing problem to update their iPhone or iPad. Here is the link https://shrishailtalukar.wordpress.com/2015/01/20/software-update-failed-an-erro r-occurred-while-downloading-ios-8-x-x-solution/

Failed to run the action: Install Software Updates. CI Version Info timed out?

Hi,
I have a task sequence that runs on servers to automatically install the advertised updates in software center. I have one server that is not installing these updates and from the smsts log I see an error about "CI Version times out" Does anyone
know what this means? TIA
<![LOG[One or more updates failed to install, hr=0x87d00314]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="InstallSWUpdate" context="" type="3" thread="31312" file="main.cpp:202">
<![LOG[Process completed with exit code 2278556436]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="TSManager" context="" type="1" thread="26924" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="TSManager" context="" type="1"
thread="26924" file="instruction.cxx:804">
<![LOG[Failed to run the action: Install Software Updates.
CI Version Info timed out. (Error: 87D00314; Source: CCM)]LOG]!><time="06:37:50.434-120" date="04-25-2015" component="TSManager" context="" type="3" thread="26924" file="instruction.cxx:895">
<![LOG[Set authenticator in transport]LOG]!><time="06:37:50.434-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2016410860]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924"
file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="executionenv.cxx:807">
<![LOG[The execution engine ignored the failure of the action (Install Software Updates) and continues execution]LOG]!><time="06:37:50.652-120" date="04-25-2015" component="TSManager" context="" type="2"
thread="26924" file="instruction.cxx:962">
<![LOG[Set authenticator in transport]LOG]!><time="06:37:50.652-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="libsmsmessaging.cpp:7734">

Please have a look at this similar post:
https://social.technet.microsoft.com/Forums/en-US/7ebe1966-1417-4e5e-ba29-1aac6b5b0de1/sccm-2012-deployment-of-updates-failes-with-ci-version-info-timed-out?forum=configmanagersecurity
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM Software Update Agent remains disabled

Dear All,
on single notebooks the Software Updates Agent remains disabled even if the Client Settings policy is set to enale the agent as in the attached images:
Even though if I set e.g. the remote tool agent as disabled, the agent becomes disabled on the same notebooks, where the SUA does not change state. Therefore a communication error is excluded.
Does anyone know where to look after more information about this issue and eventually how to solve it?
CMClient Version on all Clients: 5.00.7804.1000
OS on the Client: Win 8 or Win 8.1 U1
SCCM Version on the Server: System Center Configuration manager 2012 SP 1 5.0.7804.1500
Policy:
Best,
Pictop

Hi t.c.rich,
Thank you for the response.
Here the log file.
<![LOG[Successfully completed scan.]LOG]!><time="12:09:30.983-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="3864" file="cwuahandler.cpp:3557">
<![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="12:51:54.966-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:1232">
<![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="12:51:55.045-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:936">
<![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="12:51:55.064-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:1265">
<![LOG[Scan results will include all superseded updates.]LOG]!><time="12:51:55.076-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:2913">
<![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="12:51:55.076-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:2916">
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="12:51:56.701-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:579">
<![LOG[Async searching completed.]LOG]!><time="12:52:18.732-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="336" file="cwuahandler.cpp:2068">
<![LOG[Successfully completed scan.]LOG]!><time="12:52:19.513-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="1880" file="cwuahandler.cpp:3557">
<![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="12:52:19.748-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:1232">
<![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="12:52:19.748-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:936">
<![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:1265">
<![LOG[Scan results will include all superseded updates.]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:2913">
<![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:2916">
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:579">
<![LOG[Async searching completed.]LOG]!><time="12:52:38.998-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4768" file="cwuahandler.cpp:2068">
<![LOG[Successfully completed scan.]LOG]!><time="12:52:39.888-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:3557">
<![LOG[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]LOG]!><time="13:38:54.626-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="3660" file="cwuahandler.cpp:2527">
<![LOG[Removed Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="10:28:37.696-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="488" file="sourcemanager.cpp:1338">
<![LOG[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]LOG]!><time="10:28:39.508-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="488" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="10:29:04.622-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2368" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="10:42:29.805-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="3092" file="cwuahandler.cpp:2527">
<![LOG[Tried to remove an update source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) that does not exist.]LOG]!><time="10:45:25.357-120" date="10-10-2014" component="WUAHandler" context="" type="2" thread="3944" file="sourcemanager.cpp:1315">
<![LOG[Failed to Remove Update Source from WUAgent ({543A840D-5C46-4239-ADB9-17E8FC7359E5}). Error = 0x87d00691.]LOG]!><time="10:45:25.357-120" date="10-10-2014" component="WUAHandler" context="" type="3" thread="3944" file="cwuahandler.cpp:2359">
<![LOG[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]LOG]!><time="10:46:37.231-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2540" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="10:49:55.122-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2128" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="11:31:03.370-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="1224" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="14:30:29.411-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3960" file="cwuahandler.cpp:2527">
<![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:1232">
<![LOG[Unable to read existing resultant WUA policy. Error = 0x80070002.]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="2" thread="2844" file="sourcemanager.cpp:920">
<![LOG[Enabling WUA Managed server policy to use server: HTTP://sccm.domain.com:8530]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:948">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="14:38:39.165-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:954">
<![LOG[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]LOG]!><time="14:40:06.416-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="5736" file="cwuahandler.cpp:2527">
<![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:40:06.416-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:1232">
<![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="14:40:06.447-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:936">
<![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="14:40:06.462-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:1265">
<![LOG[Scan results will include superseded updates only when they are superseded by service packs and definition updates.]LOG]!><time="14:40:06.478-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:2909">
<![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="14:40:06.478-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:2916">
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="14:40:06.494-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:579">
<![LOG[Async searching completed.]LOG]!><time="14:44:15.950-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="1120" file="cwuahandler.cpp:2068">
<![LOG[Successfully completed scan.]LOG]!><time="14:44:17.325-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="6180" file="cwuahandler.cpp:3557">
<![LOG[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]LOG]!><time="15:51:02.561-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="4008" file="cwuahandler.cpp:2527">
<![LOG[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]LOG]!><time="12:50:50.102-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="4444" file="cwuahandler.cpp:2527">
<![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:00:00.167-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:1232">
<![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="14:00:00.214-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:936">
<![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="14:00:00.214-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:1265">
<![LOG[Scan results will include all superseded updates.]LOG]!><time="14:00:00.229-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:2913">
<![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="14:00:00.229-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:2916">
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="14:00:01.995-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:579">
<![LOG[Async searching completed.]LOG]!><time="14:00:21.979-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5076" file="cwuahandler.cpp:2068">
<![LOG[Successfully completed scan.]LOG]!><time="14:00:23.354-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:3557">
<![LOG[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]LOG]!><time="08:12:47.409-60" date="01-30-2015" component="WUAHandler" context="" type="1" thread="5084" file="cwuahandler.cpp:2527">
Regards,
Pictop

How to calculate the compliance for an software update deployment

Hi All,
I am trying to find as how do we calculate the compliance for an software update deployment.
Scenario, We have about 4000 machine in the domain. but we have some stale records in the domain which is about 1200. The AD cleanup for the stale records is planned for sometime in March.
So total number of machines in a collection (including the stale machines) are 5200.
The current compliance of that deployment shows the following status:
Complaint : 1156
In Progress : 1724
Error : 38
Unknown : 2462
And in the unknown, we have :
Client check failed/Active: 2
Client check failed/Inactive: 6
Client check passed/Active: 732
Client check passed/Inactive: 1722
Can you please suggest in understanding the formula that should be followed to get the compliance.

Your Compliancy, should be based solely off of the number of computers within CM12.
There are no “if”, “and” or “but” able it. This is the only way to truly and reliably provide numbers to management.
Again it should be very simple calculation:
(Total outstanding Security SU, Total outstanding
Critical SU, Total outstand Service packs, Total outstand Update Rollups, Total outstand Updates, Total outstand Definition Updates, Total outstand tools, Total outstand Feature packs) Vs Total applied SU (all Classifications)
Or
Total # of 100% patched PCs vs Total # of PCs as seen by CM12.
If you use any other calculation then you MUST include a disclaimer that you are filtering out computers because they might be invalid. Or you MUST define exactly how you are calculating the number. Therefore any compliancy rate that your calculate maybe
invalid too or at least it will change once you clean up AD.
I will never hide low compliancy numbers to management, I will always show it to them.
In many case I will ask to give a presentation to Management to explain why the numbers are so low.
Provide them with a list of action items that need to be done in order to bring up the number to more reasonable level. I also set their expectation on what a reasonable level is.
100% is unachievable; there is no exception to this!
95-99% Very excellent but expect to spend lots of $$$s to obtain these percentages.
90-95% is really, really, good; expect to spend $$s in this range.
85-89% is good; expect to set strict procedures
81-84 is ok but you could do better
Below 80% is bad
In your case, I would start by saying AD is dirty and need to be clean up, this has been schedule for March 2015. I would follow up this to say, in order to keep AD clean the follow procedures need to be define / updated / followed. You should also define
exactly what you are doing to ensure that all computers are management by CM12.
IMO these is no simple answer of this.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Sky+ HD box broken since recent software update? what to do?

I'm going round in circles...SKY+ box now is not working since software update !.. I've been on the phone and online chat about the broken sky box ( account and box approx 3 years old ). I spoke to someone on chat who re-negotiated my package "cheaper" which was very nice but a bit pointless without a working sky box...was advise he would transfer me to different department to discuss replacement of the sky+ box, got through to other department and they had no idea why I'd been put through to them had no record of my previous conversation .. and unable to help!.. Yes I'm now getting agitated !.. phoned 03442 414 141 instead, on his advice and they said we can give you a new sky box for £214.00 ! , or get multiroom? for another £11 a month?? not helping ... annoyed as prior to the sky software update the box wasnt the problem !... Ive been then trying the fix by following the solutions online to still be in the state of amber light and no sky TV.... it then directs me to an engineer call out at £65. Who apparantly will either fix the old box ( until the next time ) or replace it with a refurbished one ? Obviously looking on e-bay etc you can buy boxes for between £10 to £40 ...feel annoyed why as a customer for well over 14 years I'm being shoved away at a massive cost to myself. Oh and look... a new customer could potentially have £125 from being recommend via friend, TV or Tesco /M&S £100 voucher... I'm annoyed and what do I do next ?.....

Same problem for me, 1TB Sky box. Box updated on the 22nd of July 2015. Scheduled recordings now do technical fault 7 (33) picture breaks up on play back, but not all the time. Others fail with fault 10. Done the full software, re-download (backup and switch on), new install, planner rebuild. Even down to a full system reset. All other features work. On demand works only if I let it download to 100%. Try any sooner and TF7 (33) faults again. All I can think is the update is causing excessive CPU usage. Call out this Sunday bringing a reconditioned box. So if it's same 1TB and same EPG I might get the same problem. I'll post more after the engineer had been.

Software Updates in a TS Question

Our company has recently began using OSD and right now everything works great for the most part. I built a virtual machine, updated it with all the patches through March 2015 and used Build and Capture to create the image. My applications and
packages install without an issue. However, the service desk started to question why there were over 100 updates available after the OS was deployed. I realized that some of them were updates for Office, .NET and Lync. I then realized
that the updates were not installed in the base OS because those applications were not there when I built the base machine.
Just as a side note, my updates are organized by month going back to March of 2014. So I have 2014-03 through 2015-04. The remainder are in groups that are just the years. So there is a 2015, 2014, etc. However, those are not deployed. Additionally,
we are currently required to keep desktops at IE 9 for compatibility with some of our older home grown applications. While that is in the process of being updated, I can't run IE 10 or 11.
So I was curious how everyone else manages this situation (or would) as I had a hard time finding someone discussing this scenario specifically. I did find
this article on the forums and thought that since I know which updates the system needs, I can make a special update group for OSD, deploy it to the Unknown computers collection and then setup the task Install Software Updates task sequence with only
mandatory updates. Then install them on the machine and see if more show up, which would go into a new task sequence and repeat that until there are none left. It feels like it would be a management nightmare because it would constantly have to
be updated.

First, what you described above is not "Build and Capture". As the name implies, a Build and Capture task sequence does not involve you installing Windows manually on a virtual machine; the whole point of Build and Capture is to automate the image
build process and then capture the automatically built system.
As for keeping the image up to date, there are two easy answers here. First, update your image with offline servicing. This uses DISM to effectively slipstream core OS updates into the image without having to recreate or rebuild your image in any way. As
noted though, this does not handle every possible update. That's where build and capture comes in, you simply re-run your build and capture using the updated core image with the Install Software Updates task included.
As for targeting your updates to both your build and capture as well as your deployment task sequence, yes, creating a new software update group and targeting a deployment of this group is an elegant way to handle them. Yes, you will have to update this
group regularly, but that's honestly what, a 10 minute task once a month? Alternatively, you can target all of your existing update groups at the appropriate TS collections. That adds a bit of messiness in having extra deployments but it eliminates the
need for the redundant update groups.
Both methods have overhead.
Jason | http://blog.configmgrftw.com | @jasonsandys

Software Updates 31/07/2015

Similar Messages

Maybe you are looking for