Home Made SCCM Videos: Log File Investigation Series Part 1

This is an continuation to previous video: 

http://cmxp.blogspot.sg/2016/01/home-made-sccm-videos-cmtrace-intro.html

In this episode I will touch on the workflow of a typical software distribution cycle, once we understand the workflow we can match the respective log file to the workflow which will be easier for administrator to troubleshoot any issues that arises from software distribution: 

Here's the blog that compliments the above video: 

http://cmxp.blogspot.sg/2015/10/log-file-investigation-part-7-software.html

I hope you guys enjoy this video!. :) 

Happy watching. 

SY 

SCCM 2012 SP2 and SCCM 2012 R2 SP1 CU2 is out

This new CU enhances performance issues for hybrid Intune device enrolment and DP performance as well, to know more read the below: 

http://blogs.technet.com/b/configmgrteam/archive/2015/11/10/now-available-cu2-for-sc-2012-r2-configmgr-sp1-and-sc-2012-configmgr-sp2.aspx

One thing to note, the CU that was downloaded before 13 Nov 2015 will remove some files that are necessary to MS Intune. Do take note. 

For your information. :) 

SY

Log File Investigation Part 8 (Software Distribution End To End Log Investigation)

With sweat and tears, the mapping is complete, now looking at it, it will definitely be easier to look at which log file. A thing to note the logs displayed here are based on application deployment not package based deployment. If it is package deployment it will be easier, Just replace the app log file with execmgr.log instead will do fine. 

Here's the diagram: 

And in case you want to re-read the whole series so far:

http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-1.html

http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-2.html

http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-3.html

http://cmxp.blogspot.sg/2015/06/log-file-investigation-part-4.html

http://cmxp.blogspot.sg/2015/08/log-file-investigation-part-5-software.html

http://cmxp.blogspot.sg/2015/08/log-file-investigation-part-6-software.html

http://cmxp.blogspot.sg/2015/10/log-file-investigation-part-7-software.html

Happy reading! :) 

SY 

Log File Investigation Part 7 (Software Distribution End To End Overview)

Well, I certainly didn't see myself writing up to 7 parts of log file investigation series. While there is certainly no fan base, from time to time when I pass such workflow to friends and colleagues, it certainly helped them to cut short the log file hunt. 

So I thought, why not I do it for software distribution as well? Even though I did highlight on the previous series, part 7 & 8 will be more comprehensive. Here is a typical flow of software distribution. I try to be more generic and possible the below flow might differ from environment to environment. 

Here it is: 

Don't forget to check out the rest of the log investigation series blogs as well: 


http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-1.html

http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-2.html

http://cmxp.blogspot.sg/2015/04/log-file-investigation-part-3.html

http://cmxp.blogspot.sg/2015/06/log-file-investigation-part-4.html

http://cmxp.blogspot.sg/2015/08/log-file-investigation-part-5-software.html

http://cmxp.blogspot.sg/2015/08/log-file-investigation-part-6-software.html

Happy reading! :) 

SY 

Did You Know 3: AD Schema Troubleshooting Flow

This is not something new and the are many methods that are circulating around the internet to troubleshoot the issue. Here are some of the personal finding and preference to resolve the issue. 

Problem: 

Upon extending the schema, you saw error code 8202 in the log file. And you realise that the AD schema extension is not complete

Steps: 

1) Make you that the AD account your are using has Enterprise Admin and Schema Admin rights. 

2) Ensure that the replication partners are all there in AD. This can be easily achieve when you go into the console of "AD sites and services" Make sure all the DC are replication partners this is to ensure that the extension is replicated across the DC

3) Ensure that the DC you are working at has the Schema master FMSO roles or else you will hit the above error as well.  Fire up the command prompt as administrator in your DC and key the following: netdom /query fmso You must ensure that the DC holds the Schema Master FMSO role. 

Conclusion:

While people have argument to say that the AD schema extension can be done on site server. Base on my personal experience it would be best to do it on a DC with Schema Master FMSO role. Make sure you go through the above checkpoint so that you won't get the error. 

Happy reading!

SY 

Personal Ranting: AD Schema Extension (Part 1)

Fear always stems from doubt and disbelief. If you can understand the underlying issues, you will not have a problem in implementing the technology to your environment. Over the years as a system engineer and consultant, you will be confronted by the customers why is there a need to perform AD schema extension before SCCM installation?

When you can understand the actual rationale behind of AD schema extension you will not reject the idea the next time you deploy SCCM. But nonetheless, AD schema extension is only performed once. So if you are using SCCM 2007 and upgrade to SCCM 2012, then you do not have to perform this action again. 

What is AD schema actually?

In a nutshell, AD schema is part of AD component where it keeps the data of all the AD objects. And these objects are term under class and attributes. 

What is an attribute?

Attributes contain data that defines the information that is stored in an object or in another attribute. For example, a user account object has attributes that store user information, such as the user’s first name, last name, password, office number, and telephone number. 

What is an class?

Object definitions are categorized into groups that are called classes. Classes act as blueprints that can be used each time a new object is created. When a new object is created in the directory, the object’s class determines the attributes that are associated with the new object, including which attributes are required and which attributes are optional.

The above information is taken from: 

https://technet.microsoft.com/en-sg/library/cc773309%28v=ws.10%29.aspx
  

https://technet.microsoft.com/en-sg/library/gg712272.aspx

A one time only AD schema extension will create 14 attributes and 4 classes in AD. (18 in total) 

Attributes: 

cn=mS-SMS-Assignment-Site-Code

cn=mS-SMS-Capabilities

cn=MS-SMS-Default-MP

cn=mS-SMS-Device-Management-Point

cn=mS-SMS-Health-State

cn=MS-SMS-MP-Address

cn=MS-SMS-MP-Name

cn=MS-SMS-Ranged-IP-High

cn=MS-SMS-Ranged-IP-Low

cn=MS-SMS-Roaming-Boundaries

cn=MS-SMS-Site-Boundaries

cn=MS-SMS-Site-Code

cn=mS-SMS-Source-Forest

cn=mS-SMS-Version

Classes: 

cn=MS-SMS-Management-Point

cn=MS-SMS-Roaming-Boundary-Range

cn=MS-SMS-Server-Locator-Point

cn=MS-SMS-Site

Happy reading!

SY

Did You Know 2: WSUS Maintenance

While this is actually old news, but the sites I went usually do not update the WSUS option. Especially for those SCCM to download different language windows patches, the private memory pool will be easily hit. 

Bear in mind that WSUS capacity is slightly different from SCCM. Therefore remember to setup this simple maintenance option in your site server: 

Make sure you set at least 8GB and above in KB. 

Information was taken from here: 

http://blogs.technet.com/b/configurationmgr/archive/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors.aspx

http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

Happy reading!

SY 

Using PowerShell To Check The OS Architecture

This post was actually inspired by the previous post: 

Using Batch File To Check The OS Architecture

I was thinking using Powershell instead, the previous batch file serves the purpose, check for that particular folder and wah la you got your program installed. But I want to tap on Powershell's advance feature to ensure that the machine is really on 64 bit OS to install. 

So here goes: 

$OSArchitecture = (Get-WmiObject -Class Win32_OperatingSystem | Select-Object OSArchitecture -ErrorAction Stop).OSArchitecture

if ($OSArchitecture -eq '64-bit')

{& path:\a.exe}

else

{& path:\b.exe}

The idea is to use Powershell to check on the OS architecture. The strings behind Win32_OperatingSystem can be found here

You will need to change the variable yourself for the software path. 

Afterwards you can deploy the a batch file to invoke the above Powershell script to install the programs. Make sure you add in the required installation parameters as well. 

In case you do not know how to use a batch file to run Powershell scripts you can take a look of my previous posts on simple scripting to get the job done: 

Clear CCMCache Contents

Using Batch File To Check The OS Architecture

Software inventory using PowerShell

Enjoy!

SY

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