Configuration Manager 2016 Technical Preview 4

The actual release will be near soon. Latest TP edition focus more on Windows 10 devices and update feature. 

Read more at: 

http://blogs.technet.com/b/configmgrteam/archive/2015/11/19/now-available-system-center-configuration-manager-technical-preview-4.aspx

Download over here: 

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

Have fun! :) 

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

SQL Setup For SCCM 2012 (Part 2)

This second part of the series is really to compliment the first part I wrote. Some may not know or most of you already know, this was some notes that was taken way back in the SQL 2005 days. But it is a simple and nice overview to understand a SQL query better, and it really explains why the SQL performance is always pointing back to:

1) Processor

2) Memory

3) Disk

Although the process may differ from product to product, but this is very general overview. Usually at the 2nd phase of the query it will check for syntax, look out for the resources available and set a "cost" for the query before it really process the query.

When the processing take place it will really take a performance toll unto the server memory, disk and CPU that is why we whenever we need to setup any SQL server, we need to really take into consideration of the above three components first, and subsequently to look into the SQL statement to enjoy better performance.

Happy reading! :)

SY

Did You Know 5: PXE Boot Workflow

I thought I would want to deep dive into PXE Boot workflow and present it as a pictorial format as there isn't much troubleshooting workflow out there. (At least for me) This may differ from your environment, but generically this workflow should apply most of the SCCM PXE boot environment. (UEFI and Legacy boot).

This diagram will be helpful when I shared with my fellow colleagues, so I thought this will be useful as well. Identify the phase you are stuck in, and check for possible reasons:

In "User Machine" phase, chances are: 

a) PXE boot BIOS settings are not set correctly.

b) Firewall or DHCP server are not set correctly.

In network phase, ensure that your switch has: 

a) IPHELPER configure to point from your switch to DHCP and WDS/TFTP server which in my case the DP server is holder the roles.

b) Your firewall you allow the necessary protocols like port 69 (TFTP), 4011 (PXE related ) and high port range that is required by SCCM server.

In DHCP phase, ensure that: 

a) Your DHCP server do not have port 66 & 67 if you want to do UEFI boot.

b) Port 69 (TFTP) is set.

In DP phase, ensure that: 

a) WDS services are up and running. If this service fail, the machine will have no chance to validate its details with SCCM MP.

In MP phase, ensure that: 

a) You have the SMSPXE.log file to check the connectivity between the MP is valid plus in the log you be able to check the machine validation between MP. If the machine is unable to validate, this could means that the machine detail you have imported in your SCCM console is not correct. (Mis-type a MAC address, happens all the time)

Enjoy reading and hope you guys find it useful. :)

SY

SQL Setup For SCCM 2012 (Part 1)

I am not a DB expert but I did went through great length to do a lot of research for DB setup for SCCM 2012, this is including some of the previous MS chalk talks I have attended plus of course some of the tips and tricks from various MVPs and here is the platform for me to share my findings.

A lot of time this may not sound like SCCM to you, but trust me SCCM performance issue is closely knitted with the performance of its own database that is why I thought I spend a lot more time on this topic which is seldom shared.

Why am I writing this? Because chances are, you be like me who will be handling several systems in the company and you have little time for SCCM. Therefore you really want SCCM DB to be designed nicely to give you lesser headache.

I tried to generalise the concepts shared here so that you could use the concepts here for typical SQL server as well. But for MS products every product has specific requirement of the SQL settings. So it will be best to consult MS technet or consultants on this matter.

Before I end part 1. Here are the typical three areas professionals look at, when they deal with SQL performance. While network should not be overlooked as well however I am giving network a miss because seldom the performance related issue with SQL server is due to network.

The above areas are not in any order. 

Happy reading! :) 

SY