Wednesday, November 16, 2016

Error when installing SCCM client

Error message : "The client version 5.00.7958.1000 does not match the MP version 4.00.6487.2000"

Solution :

Copy the ccmclean.exe to the client machine and then run ccmclean /MP.

After this run the client installation , this should be work.

Get download ccmclean.exe at http://download.cnet.com/CCMClean/3000-2096_4-76115934.html

Wednesday, September 28, 2016

How to view windowsupdate.log in Windows 10.

Using Windows PowerShell cmdlet to re-create the WinodwsUpdate.log, like it has been in previous versions of Windows.

1. Launch Powershell
2. Run command "Get-WindowsUpdateLog -logpath C:\Temp\WindowsUpdate.log"

3. Wait until the command successfully completed.

4. Open the windowsupdate.log from c:\temp with cmtrace

How to activate Windows 10 license with command line.

1. Run Command Prompt as Administrator
2. Type slmgr -ipk XXXX-XXXX-XXXX-XXXX-XXXX
3.. Activatiton done.

Friday, June 10, 2016

SCCM Software Updates Error : onsearchcomplete - failed to end search job. error = 0x8007000e in WUAHandler.log and Windows update.log

Reason:
This error due to memory leakage of System (which system performance can be decreased during scans) or Not enough storage on client machine.

Microsoft have released patch to resolve this issues. refer to this link.

https://social.technet.microsoft.com/Forums/windows/en-US/4a782e40-bbd8-40b7-869d-68e3dfd1a5b4/windows-update-scan-high-memory-usage?forum=w7itproperf

Solution : -

Apply this patches to windows 7 and restart the machines. Run the SCCM cycles to generate the scan.

This time client will successfully scanned and receive windows update from sccm.

Tuesday, June 7, 2016

Message ID 2719:

Inventory Data Loader failed to process the file D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\Process\HDD6EP0U.MIF because it is larger than the defined maximum allowable size of 5000000.

Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size (the default is 5 MB), and wait for Inventory Data Loader to retry the operation

This is an easy fix.

On the CM12 Site Server, open regedit.exe.

Drill down to HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER.

Find Max MIF Size and double click it.

Change the value to 3200000 (Hex), which is 50 MB. By the way, the actual default value is 4c4b40 (hex) or 5000 kilobytes which is just under 5 MB.

Close regedit.exe and clear out any errors/warnings for SMS_INVENTORY_DATA_LOADER.

Now you’re done!

Thanks for http://www.enhansoft.com/blog/change-the-maximum-file-size-of-management-information-files-mif-in-sccm-2012

Monday, May 23, 2016

Error in windows 10 activation - 0xd0000272

Workaround:-

1. Delete "windows update" key from HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.

2. Try activate again , the activation should be successful.

Wednesday, April 13, 2016

SCCM Agent Failed to install

Checked the c:\windows\ccm\ccmsetup.log and found

Error message: Download Update: copy has been queued.

Resolution:-

Stop BITS Service and Ccmsetup service.
Run below command

-Bitsadmin.exe /RESET /Allusers

-Bitsadmin.Exe /List

Then force install SCCM Agent by run this command

CCMSetup.exe /BITSPriority:FOREGROUND

From <http://www.myitforum.com/forums/SCCM-Client-will-not-complete-m228253.aspx>

How to Prepare Master Image for SCCM Agent 2012 R2/R2 SP1 or SP 2

1) Install the ConfigMgr client on the Master Image
2) After succesfully installed then Stop the SCCM client service as below
- Start > Run - CMD.exe
- Type > Net stop "SMS Agent Host"
3) Delete the SMSCFG.ini file from the Windows folder at “ %WINDIR%\smscfg.ini”
4) Remove the 2 SMS certificates in the local certificate store by run this command in powershell 1. Remove-Item -Path HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force
5) Remove the Inventory Action ID 1 in WMI = run the command wmic
/namespace:\\root\ccm\invagt path inventoryActionStatus where InventoryActionID=”{00000000-0000-0000-0000-000000000001}” DELETE /NOINTERACTIVE
6) Sysprep and shutdown
7) Create Master Image.

SCCM build numbers.

System Center Configuration Manager Current Branch

Build Number	Release Date	Description
5.0.8299.1000	2015, September 22	SCCM Update 1509
5.0.8315.1000	2015, October 14	SCCM Update 1510
5.0.8325.1000	2015, November 12	SCCM Update 1511
5.0.8336.1000	2015, December 18	SCCM Update 1512
5.0.8347.1000	2016, January 27	SCCM Update 1601
5.0.8355.1000	2016, March 10	SCCM Update 1602

System Center Configuration Manager 2012 R2

Build Number	KB	Release Date	Description
5.00.7958.1000	–	2013, October 18	SCCM 2012 R2 RTM
5.00.7958.1101	KB2905002	2013, November 02	SCCM 2012 Post R2 Hotfix
5.00.7958.1203	KB2938441	2014, March 28	SCCM 2012 R2 CU1
5.00.7958.1303	KB2970177	2014, June 27	SCCM 2012 R2 CU2
5.00.7958.1401	KB2994331	2014, September 23	SCCM 2012 R2 CU3
5.00.7958.1501	KB3026739	2015, February 2	SCCM 2012 R2 CU4
5.00.7958.1604	KB3054451	2015, May 6	SCCM 2012 R2 CU5
5.00.8239.1000	–	2015, May 14	SCCM 2012 R2 SP1
5.00.8239.1203	KB3074857	2015, August 4	SCCM 2012 R2 SP1 CU1
5.00.8239.1301	KB3100144	2015, November 10	SCCM 2012 R2 SP1 CU2
5.0.8239.1403	KB3135680	2016, February 26	SCCM 2012 R2 SP1 CU3

System Center Configuration Manager 2012 SP1 & SP2

Build Number	KB	Release Date	Description
5.00.7804.1000	–	–	SCCM 2012 SP1
5.00.7804.1202	KB2817245		SCCM 2012 SP1 CU1
5.00.7804.1300	KB2854009		SCCM 2012 SP1 CU2
5.00.7804.1400	KB2882125		SCCM 2012 SP1 CU3
5.00.7804.1500	KB2922875		SCCM 2012 SP1 CU4
5.00.7804.1600	KB2978017	2014, July 23	SCCM 2012 SP1 CU5
5.00.8239.1000	–	2015, May 14	SCCM 2012 SP2
5.00.8239.1203	KB3074857	2015, August 4	SCCM 2012 SP2 CU1
5.00.8239.1301	KB3100144	2015, November 10	SCCM 2012 SP2 CU2
5.0.8239.1403	KB3135680	2016, February 26	SCCM 2012 R2 SP2 CU3

System Center Configuration Manager 2012

Build Number	KB	Release Date	Description
5.00.7711.0000	–	2012, March 31	SCCM 2012 RTM
5.00.7711.0200	KB2717295	2012, August 22	SCCM 2012 CU1
5.00.7711.0301	KB2780664	2012, November 27	SCCM 2012 CU2

System Center Configuration Manager 2007

Build Number	KB	Release Date	Description
4.00.5135.0000			SCCM 2007 Beta 1
4.00.5125.0000			SCCM 2007 Beta 1 Escrow
4.00.5221.0000			SCCM 2007 Beta 1 Refresh Escrow
4.00.5224.0000			SCCM 2007 Beta 1 Refresh
4.00.5224.0000			SCCM 2007 Beta 1 Refresh
4.00.5571.0000			SCCM 2007 Beta 2 Escrow
4.00.5574.0000			SCCM 2007 Beta 2 Escrow Update
4.00.5578.0000			SCCM 2007 Beta 2 with a hotfix
4.00.5578.0002			SCCM 2007 RC0 Preview
4.00.5790.0000			SCCM 2007 RC0 Preview
4.00.5815.0000			SCCM 2007 RC0
4.00.5924.0000			SCCM 2007 escrow
4.00.5931.0001			SCCM 2007 RTM
4.00.6086.1000			SCCM 2007 SP1 (prerelease)
4.00.6221.1000			SCCM 2007 SP1
4.00.6221.1193	KB977203		FIX for SCCM 2007 SP1 and SP2
4.00.6425.2000			SCCM 2007 SP2 beta
4.00.6468.2001			SCCM 2007 SP2 RC
4.00.6487.2000			SCCM 2007 SP2
4.00.6487.2111	KB977203		FIX for SCCM 2007 SP1 and SP2
4.00.6487.2157			SCCM 2007 SP2 R3
4.00.6487.2207	KB2750782	2012, December 03	FIX for SCCM 2007 SP2
4.00.6487.2700			SCCM SP2 R2 with ICP2
4.00.6487.2857			SCCM SP2 R3 with ICP2

SMS 2003

Build Number	KB	Release Date	Description
2.50.2726.0020	–	–	SMS 2003 RTM
2.50.3174.1018	KB885644	2004, September 10	SMS 2003 SP1
2.50.4160.2000	KB899738	2006, February 13	SMS 2003 SP2
2.50.4253.3000	KB933867	2007, May 2	SMS 2003 SP3

SMS 2.0

Build Number	KB	Release Date	Description
2.00.1239.0000	–	–	SMS 2.0 RTM
2.00.1380.1000		–	SMS 2.0 SP1
2.00.1493.2000	KB258682	–	SMS 2.0 SP2
2.00.1493.3000	KB280756	–	SMS 2.0 SP3
2.00.1493.4000	KB308269	–	SMS 2.0 SP4
2.00.1493.5000	Description	–	SMS 2.0 SP5

SMS 1.X

Build Number	Release Date	Description
–	1994, November 7	SMS 1.0
–	1995, July 25	SMS 1.1
–	1996, July 29	SMS 1.2

Ref :https://buildnumbers.wordpress.com/sccm/

Tuesday, February 23, 2016

Error in deploying Office 2013:
Software centre Error code 0x80110449

Cause :

Office 64 Bits version try install on machines which already installed Office component 32 bits

Resolution:

Remove 32 bits version and the office 64 Bits version will install successfully.

Problem:
Received error below when deploying Office Pro Plus 2013.

"The software change returned error code 0x756b(30059)"

Cause:-
The license key specified in the config.xml or the customized MSP file is invalid.

Resolution:
Specify a valid license key in the config.xml or recreate the MSP with a valid license key and deploy the software

Thursday, January 14, 2016

How to stop a client push installation in Configuration Manager

There is a very big red stop button, it's called follow this process and stop the activity immediately.

Perform the following bulleted steps on the Site server that you want the Client Push to cease on:

Stop the SMS_EXECUTIVE
Stop the SMS_SITE_COMPONENT_MANAGER
Go to <CONFIGMGR PATH>\INBOXES\CCR.BOX and delete all CCR files
Go to <CONFIGMGR PATH>\INBOXES\CCR.BOX\INPROC and delete all CCR files
Go to <CONFIGMGR PATH>\INBOXES\CCRRETRY.BOX and delete all CCR files
Start the SMS_SITE_COMPONENT_MANAGER (wait a few moments, it'll start the SMS_EXECUTIVE automagically)
Monitor the CCM.LOG in <CONFIGMGR PATH>\LOGS and you'll see the activity has died off.

If you get a build up again check your Discovery methods, could be that you are doing (AD) discovery and CCR's are being generated as a result.

From <https://social.technet.microsoft.com/Forums/systemcenter/en-US/397f37e6-d426-4d9c-b5bf-2811f1a89406/how-to-stop-client-push-started-?forum=configmgrgeneral>

Muru System Center Experience