Sharing Endpoint Technology Experience

Wednesday, 10 June 2015

Log File Investigation Part 4 (Software Updates Log Reading)

Yes it is been a while since I blogged as I was trying to fix up my VM lab, plus I am doing up several implementation document for SCCM 2012 R2, that is why, I haven't blog since, but I will blog more and share soon as my lab is ready and I have more things to cover :)

Just in case you miss it, the below were the previous three blogs that I have covered in trouble-shooting in different deployment scenarios (It's two for now, more coming up):

Log File Investigation Tool (Part 1)

Application Deployment Log Investigation (Part 2)

Package Deployment Log Investigation (Part 3)

Today, we are going to spend time on Windows Update deployment, these days, administrators face a enormous task to ensure that the organisation's machines are patched on time. Therefore SCCM 2012 R2 is your best patching companion .

So the process of getting your computers patch is already a full page topic. But for the benefit of readers I have come up a simple patching flowchart for client machines:

Because the chart does not account for CAB meetings and approval timeline you should know that the 1 month time frame is just an estimate.

Next windows update, what log files we should be looking at?

https://technet.microsoft.com/en-us/library/bb693878.aspx

Of course you could go through every log file, but let us focus on several logs files that in my opinion will be the fastest way to see the issue the client is having. First the log files to look at:

WUAHandler.log: Provides information about when the Windows Update Agent on the client searches for software updates.

UpdatesHandler.log: Provides information about software update compliance scanning, and the download and installation of software updates on the client.

Why go through WUAHandler first because it allows you to see the GUID number of the patch that the client machine needs to install. In this log, you will know how the system decide for the client machine what patch to be installed.

But the main reason is to see the GUID number so that you can trace the UpdatesHandler.log. So here you get to see the GUID number of the software update:

In this screenshot from my lab machine, you get to see the patch that is required and the GUID number accompanied with it.

Next UpdatesHandler.log:

Do a search base on the previous GUID number and you get to find several lines of information in this log, the above log is trying to show case the installation percentage.

Next after installation it will give a status message, in this screenshot you will see actually it is pending to reboot after the patch has been installed.

Lastly it will the reboot option for the patch. This is of course determined during your software update deployment.

Hope it helps.

Happy Investigating :)

Wednesday, 3 June 2015

SCCM 2012 R2 Design Thoughts

Having to read and watch a lot of materials on SCCM 2012 R2 from Microsoft and SCCM MVPS, coupled with own implementation experience, I have actually consolidated a set of design principles which can be a good reference to implement your SCCM 2012 R2.

This document is good for standalone primary setup which should satisfied most of the scenarios if you have less than 2,000 client machines to handle in the environment. If you have more than 10,000 clients, you could use the client facing components like DP and MP out of the box, use your existing file server to become a DP or MP to save cost.

Of course you can try your hands at CAS implementation etc, the design principles have details of CAS hardware requirements etc, this can be use as a reference as well. With that I would like to thanks MVP Brandon Liew who has help me to read through the document.

You can download the PDF version here:

http://1drv.ms/1I7PcHo

Happy reading. :)

SY

Thursday, 21 May 2015

Upgrade to SCCM 2012 R2 SP1

Most of the blogs would have been writing what services to download and how to perform a upgrade.

I find this blog comprehensive (One of my favourite SCCM Guru) enough and would like to share with you guys:

http://blog.coretech.dk/kea/upgrade-to-system-center-2012-r2-configuration-manager-sp1/

For the list of service packs upgrade you can read it in my earlier post:

http://cmxp.blogspot.sg/2015/05/sccm-2012-sp-upgrade.html

Enjoy reading and have fun!

SY

Thursday, 14 May 2015

SCCM 2012 SP Upgrade

Spotted this nice article that advises what update to apply base on your current SCCM 2012 setup.

Check the table listed in this article, it should give you a idea on how to upgrade:

http://myitforum.com/myitforumwp/2015/05/14/service-pack-madness/?utm_medium=twitter&utm_source=twitterfeed

Have fun! :)

SY

Wednesday, 13 May 2015

Wednesday, 6 May 2015

New and Upcoming with Microsoft Intune and System Center Configuration Manager

Well it s a bit late now, but because of time difference, just get to watch this clip this morning.

http://channel9.msdn.com/Events/Ignite/2015/BRK3861

There will be a lot of focus on mobile devices management.

Mobility the new normal...enjoy watching! :)

SY

Tuesday, 5 May 2015

Configuration Manager 2016

This is a exciting year for Microsoft as they have line up a lot of Technical preview for download that you can try it in your lab environment.

As a SCCM administrator, you would like to know that Configuration Manager 2016 is finally out for evaluation download:

Technet on CM16:

https://technet.microsoft.com/library/dn965439.aspx

To download the technical preview, you can register and download a copy for yourself to try out in your lab environment:

http://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection-technical-preview

And if you want to know more about new Microsoft products details, don't forget to tune in the ongoing event:

http://channel9.msdn.com/Blogs/MicrosoftIgnite

This is truly exciting, I hope I have the time to place up the setup of CM16. :)