After SCCM 2012 It Will Be SCCM

I think it will be easier for SCCM to name by SCCM YYMM format. I like to keep it simple. :) 

http://blogs.technet.com/b/configmgrteam/archive/2015/10/27/system-center-configmgr-support-for-win-10-and-intune.aspx

Have fun reading! 

SY 

Did You Know 4: SQL Server Collation

Chances are your SQL server installation should be on SQL_Latin1_General_CP1_CI_AS and not something else, because a SCCM server deployment will not pull through if you choose other than the above collation. What collation really does it that it actually is how your character data is stored and compared. 

So during the deployment of SCCM server, as I forgot to tell my customer that the SQL server collation should be the default one instead: 

In order not to re-install SQL again you could rebuild SQL server. 

WARNING: The below option will wipe all DB information, you use this rebuild option for new setup like my case, for any existing setup with data in is beyond this article. 

Here's the command line below: 

Make sure that: 

1) You have a domain admin rights ID to perform the above rebuild or else your rebuild is not going to work. 

2) Since it is a re-build, it would be better to have your SA password reset just in case that you have forget the previous SA password on the existing account or for some queer reason your existing AD account is unable to gain access to the SQL server. 

3) I cannot stress again, this should be done on a new setup DB server, to do this on a production server is risky. You better know what you are doing. 

Happy trying! :) 

Shawn Yuen

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