Sunday, 1 February 2015

DDRs Process Count in SCCM 2012

With SCCM 2012 Now we have Perfom Counters that can be useful to get the incoming and process rate total count of DDR’s. Of-course if you have SCOM you will get automated alert / Ticket if found more than 10000

DDR’s are located at inboxes\auth\ddm.box

When I have checked The SCOM Management Pack info there are perfmon counter info https://www.google.co.in/search?q=Non-User+DDRs+processed%2Fminute&rlz=1C1CHWA_enIN624IN624&oq=Non-User+DDRs+processed%2Fminute&aqs=chrome..69i57.343j0j7&sourceid=chrome&es_sm=93&ie=UTF-8#

Below are the Counters that we can use for counting

Total Non-User DDRs Processed
Total Bad User DDRs Processed
Total Client Registration Requests Processed
Total User DDRs Enqueued
Total User DDRs processed
User DDRs Processed/minute
Non-User DDRs processed/minute
Total Bad Non-User DDRs Processed
Total Non-User DDRs Enqueued

Just open the Perfmon from Run command and add the below counters that are available

Upgrade Check list to SCCM 2012 R2

Below are the check lists to Upgrade SCCM 2012 Sp1 to SCCM 2012 R2

https://technet.microsoft.com/en-us/library/jj822981.aspx#BKMK_PlanningR2Upgrade

	System Center 2012 R2 Configuration Manager Upgrade Checklist
1	Ensure that your computing environment meets the supported configurations that are required for upgrading to System Center 2012 Configuration Manager SP1.
2	Ensure that your computing environment meets the supported configurations that are required for upgrading to System Center 2012 R2 Configuration Manager.
3	Review the site and hierarchy status and verify that there are no unresolved issues.
4	Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles.
5	Review requirements for any add-ins or extensions for Configuration Manager that you use.
6	Disable database replicas for management points at primary sites.
7	Reconfigure software update points that use NLBs.
8	Back up the site database at the central administration site and primary sites.
9	Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
10	Run Setup Prerequisite Checker.
11	Download prerequisite files and redistributable files for System Center 2012 R2 Configuration Manager.
12	Prepare to upgrade secondary sites
13	Plan to manage server and client languages when you upgrade a site.
14	Plan for prerequisites for new site system roles, and ensure site system servers still meet prerequisite for installed site system roles
15	Review the list of considerations for site upgrades. https://technet.microsoft.com/en-us/library/jj822981.aspx#BKMK_UpgradeR2Considerations
16	Test the database upgrade process on a copy of the most recent site database backup.
17	Restart the site server and each computer that hosts a site system role to ensure that there are no pending actions from a recent installation of updates or from prerequisites.
18	Install System Center 2012 R2 Configuration Manager.
19	Upgrade stand-alone Configuration Manager consoles.
20	Reconfigure database replicas for management points at primary sites.
21	Reconfigure any database maintenance tasks you disabled prior to the upgrade.
22	Upgrade clients.

How Database Replication Services – DRS will work

Recently I thought to write article on Database replication on SCCM, However just found a good one than one in my mind… it answered below key questions

What are the main reasons to move to DRS in SCCM 2012?
What does DRS actually replicate in SCCM 2012?
What is Global Proxy in SCCM 2012?
What is Global Data and Site Data in SCCM 2012?
How the DRS does separates the Global / Site Data?
How to query the replication groups that belonging to a data?

KMDF error for Windows Update Agent failing with Error 23 and 17

Windows Update Agent is failing from ConfigMgr 2012 R2 Client installation with exit code Exit code is 17 and in CCmsetup.log file as

C:\WINDOWS\ccmsetup\WindowsUpdateAgent30-x64.exe returned failure exit code 23. Fail the installation.

Found my WIM file is missing KMDF file and I have injected KMDF file to WIM file and deployed the WIM file.

Download KMDF file from Microsoft sire http://www.microsoft.com/en-us/download/details.aspx?id=38423

Extract the kmdf-1.11-Win-6.1-x64.msu file to D:\KMDF (Using 7-Zip or any unzip software) and open command prompt as administrator and execute below

Note if you are using x82 /32 bit please use the 32 bit KMDF file

MKDir D:\KMDF\Mount

dism.exe /mount-wim /wimfile:"D:\Mont\Win7.wim" /index:1 /mountdir:D:\KMDF\Mount

dism /Image: D:\KMDF\Mount /Add-Package /PackagePath:D:\KMDF\Windows6.1-KB2685811-x64.cab

dism.exe /unmount-wim /mountdir:D:\Temp\Mount /commit

Once the Wim file is updated with KMDF driver we can try to deploy the OS then there will not be any issues.

Read more about KMDF http://support.microsoft.com/kb/2685811

AD schema Extension for SCCM 2007 /2012

When extended Active Directory (AD) 14 attributes will be created

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

When extended Active Directory (AD) 4 Classes will be created

CN=MS-SMS-Management-Point
CN=MS-SMS-Roaming-Boundary-Range
CN=MS-SMS-Server-Locator-Point
CN=MS-SMS-Site

You can find more information https://technet.microsoft.com/en-us/library/gg712272.aspx

SCCM 2012 / 2007 Active Directory (AD) Domain Functional Level for SCCM / Configuration Manager?

I had a question what should be the Active Directory Domain Functional Level Configuration Manager?

It actually required AD schema extended for below benefits;
Network Access Protection (NAP): - SCCM publishes health state references to Active Directory Domain Services so that the System Health Validator point (SHV) for validate the client’s statement of health.

For AD Domain Functional Level there is no minimum requirements however, as part of AD System Discovery if you wanted to get the last system logon information you required at least windows 2003 server.

See below ms documentation for more information https://technet.microsoft.com/en-us/library/hh368980.aspx

Friday, 23 January 2015

Creating Search Folder in SCCM 2007 – Software Updates

In Below Steps… with SCCM 2007 we can create Search Folders for software Updates, this will be very handy in every month patch criteria for getting exact patch lists in Updates repository.

In the Software Updates section, right click on Search Folders and choose New Folder,

give the new folder a name like Enterprise Searches (we willl store our yearly searches here)

Right click on our new folder and choose New Search Folder

select the following options from step 1 (in the screenshot),

BulletinID, Expired and Superseded

in step 2, Set the BulleinID to MS plus the last two digits of the year eg: MS11

Set Expired to No

Set Superseded to No

Make sure that Search All folders under this feature is selected and give the search a name, eg: 2011 patches

1.2 Create a New Search Folder for New Monthly Releases

1.Right click the folder that you created under search folders and choose New Search Folder

2. In “Step 1: Select object properties to search” Choose the following:

a. Bulletin ID

b. Date Released

c. Date Revised

d. Expired

e. Superseded

3. In “Step 2: Edit the property’s search criteria”

a. Bulletin ID

i. Set this to “MS”

b. Date Released

ii. Set this to “Last 1 month”

c. Date Revised

iii. Set this to “Last 1 month”

d. Expired

iv. Set this to NO

e. Superseded

v. Set this to NO

4. In “Step3: Specify search option” put a check in “Search all folders under this feature”

5. In Step 4: Enter a name for the search folder a. Name the folder “Monthly Updates”

6. Click OK

Similarly you can also create except Collections in almost every place you can create. all the best