HOW TO CHANGE "SCCMADMIN' PASSWORD IN SCCM2012

SCENARIO :
                       We need to change SCCMADMIN Password in AD, and how to make changes in SCCM2012 Console,

SOL : it's pretty easy to configure new "SCCMADMIN" password in sccm console, as shown above,

goto - > Administration -> Security -> Accounts -> Select "sccmadmin" account -> right click Properties

The connection was successfully Verified, once it finished,

Also we need to change in SQL Reporting services, Open Reporting service config Manager, as shown below, and update the new credentials.

 And update credentials as shown below in Reporting SSRS Webpage.

NOTE : In My case i added "sccmadmin" credentials in

Determining the Version of BITS on a Computer

To determine the version of BITS on the client computer, check the version of QMgr.dll. To find the version number of the DLL:

• Locate QMgr.dll in %windir%\System32.
• Right-click QMgr.dll and click Properties.
• Click the Version tab.
• Note the version number.

If the DLL also exists in %windir%\System32\Bits, repeat the previous steps. BITS uses the DLL with the higher version number.

The following table lists the versions of BITS and their corresponding QMgr.dll file version numbers.

          

BITS version	QMgr.dll file version number
BITS 4.0	7.5.xxxx.xxxx
BITS 3.0	7.0.xxxx.xxxx
BITS 2.5	6.7.xxxx.xxxx
BITS 2.0	6.6.xxxx.xxxx
BITS 1.5	6.5.xxxx.xxxx
BITS 1.2	6.2.xxxx.xxxx
BITS 1.0	6.0.xxxx.xxxx

You can also use the symbolic class identifiers to determine the version of BITS that is registered on the computer. The following table lists the versions of BITS and their corresponding symbolic class identifiers. The CoCreateInstance function returns REGDB_E_CLASSNOTREG if the class is not registered.

  

BITS version	Symbolic class identifier
BITS 4.0	CLSID_BackgroundCopyManager4_0
BITS 3.0	CLSID_BackgroundCopyManager3_0
BITS 2.5	CLSID_BackgroundCopyManager2_5
BITS 2.0	CLSID_BackgroundCopyManager2_0
BITS 1.5	CLSID_BackgroundCopyManager1_5
BITS 1.2, 1.0	CLSID_BackgroundCopyManager

Failed to get client version for sending messages to FSP. Error 0x8004100e in SERVER 2008 R2

Failed to get client version for sending messages to FSP. Error 0x8004100e in SERVER 2008 R2

Issue : Error installing SCCM Client 2012 on windows server 2008 R2

ccmsetup.log : Failed to get client version for sending messages to FSP. Error 0x8004100e

Solution :

Step 1 :   Use ccmclean.exe to uninstall sccm client completely

Step 2 : Delete ccmsetup folder under system root

Step 3 : start ccmsetup.exe installation now with command line

Following command line i used to fix this error :

<Browse to ccmsetup package folder>ccmsetup.exe /MP:<mp server > /BITSPriority:low SMSSitecode=< Site code > fsp=< mp server FQDN name >

REF : http://social.technet.microsoft.com/Forums/en-US/2db264c9-1769-4f6b-bb77-5dcf1106fd18/sccm-2012-agent-installation-using-orchestrator?forum=configmanagergeneral

CONFIGURATION MANAGER DID NOT FIND A SITE TO MANAGE THIS CLIENT + SCCM2012

CONFIGURATION MANAGER DID NOT FIND A SITE TO MANAGE THIS CLIENT + SCCM2012

Error Screen shot :

SOLUTION :

Site Configuration -> Sites -> Hierarchy Settings -> select check box *use a fall back site, as shown below

 Select check box -> Use a fallback site -> apply -> ok

Discover Site from client now

CcmSetup failed with error code 0x80004005

SCCM 2012 Client Installation failed with following error code : 0x80004005

ERROR 1: Couldn't verify 'C:\Windows\ccmsetup\Silverlight.exe' authenticode signature. Return code 0x800b0003

ERROR 2 : CcmSetup failed with error code 0x80004005

Solution : Install Silver light 5.5 and start SCCM2012 Client Installation, it really works.

WSUS Connection ERROR

ERROR :

WSUS ERROR LOG :
                                    The WSUS administration console was unable to connect to the WSUS Server via the remote API.

EVENTVIEWER :


                                  The description for Event ID 17137 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

RESOLUTION : 

WSUS internal Database corruption is due to the patching of WSUS Server. restarting of “Windows Internal Database” service was established the successful connection.

DEPLOYING OFFICE TEMPLATE TO ALL LOGGED ON USERS USING SCCM

Deploying Office Template to all workstations Using SCCM

Step 1 : Make batch Script, save this file as .bat

Batch SCRIPT :


@echo off
copy <shared path of Template file> "%Appdata%\Microsoft\templates"
copy <shared path of Template file> "%Appdata%\Microsoft\Templates"

Step 2 : Create package -> Follow standard steps
Step 3 : Create Program -> Follow standard steps + environment option -> only when user is logged in
Step 4 : Create Advertisement -> Follow standard steps

It Took 2 days to find this simple script......

How to create software distribution : http://technet.microsoft.com/en-us/library/bb632640.aspx

SETUP WAS UNABLE TO CREATE THE WMI NAMESPACE CCM

Error : SETUP WAS UNABLE TO CREATE THE WMI NAMESPACE CCM
           Installation Failed with Error code 1603

You can resolve this issue by deleting the WMI repository. Perform the following steps to accompish this.

1. Stop the “Windows Management Instrumentation” service.
2. Rename the C:\Windows\System32\Wbem\Repository folder to repository_old or delete it.
3. Restart the “Windows Management Instrumentation service”.
4. Reinstall the SMS client.

THE PROCESS IS NOT IN BACKGROUND PROCESSING MODE SCCM 2007 + PATCH DOWNLOADING ISSUE

1) patchdownloader.log in sccm gives following error :

HttpSendRequest failed HTTP_STATUS_FORBIDDEN or HTTP_STATUS_DENIED
ERROR: DownloadContentFiles() failed with hr=0x80070193

Solution :

1) Login to sccm server.
2) Open Internet Explorer
3) if Proxy is enabled, provide your credentials, and check any website that is connecting to internet,

that's it, you are done.

Start downloading patch now,

SITE MAINTENANCE TASK PREDEFINED - SCCM

Predefined Maintenance Task Planning

Predefined Maintenance Task Schedules

The following table displays the predefined maintenance tasks and their default schedules.

Maintenance Task	Enabled by default	Default schedule
Backup ConfigMgr Site Server	No	None.
Clear Install Flag	No	Sunday between midnight and 5:00 A.M.
Delete Aged Client Access License Data	No	Saturday between midnight and 5:00 A.M.
Delete Aged Collected Files	Yes	Saturday between midnight and 5:00 A.M.
Delete Aged Computer Association Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Configuration Management Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Discovery Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Inventory History	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Software Metering Data	Yes	Daily, between midnight and 5:00 A.M.
Delete Aged Software Metering Summary Data	Yes	Sunday between midnight and 5:00 A.M.
Delete Aged Status Messages	Yes	Daily, between midnight and 5:00 A.M.
Delete Inactive Client Discovery	No	Saturday between midnight and 5:00 A.M.
Delete Obsolete Client Discovery Data	No	Saturday between midnight and 5:00 A.M.
Evaluate Provisioned AMT Computer Certificates	Yes	Saturday between midnight and 5:00 A.M.
Monitor Keys	Yes	Sunday, between midnight and 5:00 A.M.
Rebuild Indexes	Yes	Sunday, between midnight and 5:00 A.M.
Reset AMT Computer Passwords	Yes	Saturday between midnight and 5:00 A.M.
Summarize Client Access License Weekly Usage Data	No	Saturday between midnight and 5:00 A.M.
Summarize Software Metering File Usage Data	Yes	Daily, between midnight and 5:00 A.M.
Summarize Software Metering Monthly Usage Data	Yes	Daily, between midnight and 5:00 A.M.

  

Ref : http://technet.microsoft.com/en-us/library/bb693817.aspx

Batch script to copy any file to specified location

Copying any file to specified location :

step 1 : create a folder
step 2 : put any file which you want to copy
step 3 : specify that file name in script. as script shown below.
step 4 : script and file should be in same folder

@echo off
copy <file name> "<location>"




Deleting file using batch script

@echo off
del "c:\windows\system32\Onmobile-SP.scr"

Fix Windows Update Error 0x80070002 + SCCM

Symptoms of Windows Update Error 0x80070002

After you have downloaded an update from Windows Update, you may receive a 0x80070002 error in the Windows Update window, and a red X may appear next to the error message. This is usually caused because some of the crucial Windows Update files are missing or corrupt.

How to fix update error 0x80070002

As is generally the case with Windows Update errors, there are usually two main methods to fix it. There is the automated method, and there is the manual method which can be time consuming and quite technical.

Method 1: Run the Microsoft Fix It tool for the automatic fix.

• Download and run the Fix It tool from this link http://go.microsoft.com/?linkid=9665683. And follow the onscreen prompts.
• The tool has two modes, default and aggressive, try the default mode first, and if it doesn't work, try the aggressive mode. Don't forget to restart your computer before trying to run Windows Updates again.

Method 2: Fix the issue manually.

What you have to do is to remove the Windows Update SoftwareDistribution folder, and then rerun Windows Update.

• Click the Start Orb, then in the search box, type in services.msc, and click OK.
• When the services window opens, find the line that says Automatic Updates, then right-click it and choose Stop.
• Click the Start Orb->All Programs->Accessories, then open Command Prompt.
• Type in the command  cd %windir% and press ENTER.
• Type in the command  ren SoftwareDistribution SDTemp and press ENTER.
• Close the command prompt window.
• Run Windows Update again and the error should be resolved.

Ref : http://windowsupdateerror.blogspot.in/2012/09/fix-windows-update-error-0x80070002.html

SMS/ConfigMgr SQL query to find the list of systems in a specific IP subnet

SELECT SYS.Netbios_Name0, SYS.User_Domain0, SYS.User_Name0, AIP.IP_Subnets0, SYS.Client_Version0

FROM v_R_System  as SYS

JOIN v_RA_System_IPSubnets as AIP on SYS.ResourceID=AIP.ResourceID

WHERE AIP.IP_Subnets0 = '<IP Subnet>'

Order by SYS.Netbios_Name0

Determine which NTFS drive should have distribution point

First time when you distribute the package to distribution point then SMS/SCCM chooses the NTFS drive which has maximum free space.If you have 2 to 3 NTFS drives and you want to chosse one of them. There is no provision given at SMS/SCCM server side to prevent SMS/SCCM from using a NTFS dirve with maximum free space. Also, if any drive that is currently being used for distribution point is full, then SMS/SCCM starts using the next available drive with maximum. 

Method 1: 

Create the blank text file on the other drives with the name NO_SMS_ON_DRIVE.SMS which will prevent respective NTFS drive from creating SMSPKGC$ (Here C represents the drive) folder.This file named NO_SMS_ON_DRIVE.SMS needs to be placed at the root of the drive you want excluded.Drive which dont has NO_SMS_ON_DRIVE.SMS file,will have SMSPKGC$ folder. 
  
Method 2: 

Insted of installing a standard distribution point,install a distribution point on a server share. 

1) Create a folder called smspkgx$ on the partition you want it and share that folder. (x is the drive letter of your choice).

2) Create the distribution point on a share basis in the sms admin console instead of on a server name. (Share has to exist). Just right-click site systems inside the sms admin console, select new, server share, ...)

REF : http://support.microsoft.com/kb/871234

Operating System Deployment Using SCCM 2007

OPERATING SYSTEM DEPLOYMENT USING SCCM 2007

  1) Install windows deployment server ( WDS )

  2) Install Microsoft deployment toolkit ( MDT )- Optional

  3) Install PXE-Role point in SCCM.

         And verify following files also presented :

                C:\RemoteInstall\SMSBoot

                C:\RemoteInstall\ SMSIMAGES

                C:\RemoteInstall\ SMSTemp

                C:\RemoteInstall\ Stores

  

4) Add boot image to standard & PXE Distribution point.

  5) Add Install operating system image to standard distribution point

  6) Create sccm client package ( package from definition method ) and necessary software packages.

  7) Add DHCP Scope options :

Port 66 : <Boot server IP Address>

Port 67 : smsboot\x64\wdsnbp.com

  8) Create Task sequence & assign to required collection

Installing WDS :

Click Next & select Windows Deployment Services

Click Next.

 Click Next

 Click Install.

Click Close.

PXE- Role Installation : 

Site Database -> Site Management -> Site settings -> System systems -> right click

Select “PXE Service point”

 ( Optional: Enable unknown computer support ) & type PXE boot password. Click next

 Click next and finish.
PXE Installation Check : (C:\Program Files (x86)\Microsoft Configuration Manager\Logs\pxesetup.log )

Add Boot Image to Distribution Point :

Add default boot image to PXE Disrtibution point & standard distribution point.

Make sure that, required model network driver added to boot image.

After Boot image Distribution verify following files presented here : C:\Windows\Temp\PXEBootFiles\Windows\Boot\EFI

C:\Windows\Temp\PXEBootFiles\Windows\Boot\PXE

Add Operating System Image wizard :

Site Database -> computer management -> Operating system deployment -> Operating system images  -> right click -> add operating system image.(specify Captured image.wim file instead of install.wim )

Add this image to Standard distribution Point.


ADD Operating System Install Package :

Site Database -> computer management -> Operating system deployment -> Operating system install packages  -> right click -> add operating system install package.

Select operating system image share path and click next. Once completed add to standard distribution point.

TASK Sequence creation : 

NOTE : 

Type desired admin password in that text box.

Assign Task Sequence to Required collection.

 Program rerun behaviour should be : Never Rerun

Once Tasksequence Created and advertised,

Start workstation and press F12 select Network book

Need to provide password for entering to Task Sequence.

==============================================================

ERRORS Faced During OSD and solution : 



1) Error : pxe-e52 - tftp open timedout

add port 66,67 in DHCP

66 Boot server name : Boot server IP address
67 Boot file name  :  SMSBoot\x86\wdsnbp.com


2) Error : error 0x000000032

Sol : disable Apply drivers device option in task sequence.

3) Error : 0*80070005

Sol : access denied for DP,  whatever packages added to Task Sequence should be in Distribution points.
MY CASE : some packages were not added to any distribution points..

---------------------------------------------------------------------------------

Capture Image using Create task media - SCCM

Capturing Image using Task sequence create media wizard,

1) create task sequence capture media,

Select location where you need to save .iso image, click next and finish.

Once ISO Image created, burn it to CD or DVD.

2) Capturing Image using CD,
Run this CD or DVD to machine, where we need to capture image.


Run -> TSMBAUTORUN.EXE

Click Next & Specify destination folder and file name : C:\Windows7 32bit ent sysprep\Win7 32bit ent with all apps

Once Setup is started capturing Image, system will restart once, please wait.

After Restart you will get Following screen.

Thats it, now we can deploy this image with OSD.