Running Configuration Manager 2012 Remote Control standalone

In some scenarios you may want for instance servicedesk or helpdesk personnel run the Configuration Manager 2012 Remote Control without having to install the Admin Console and grant them permissions to use the Admin Console when they really only need to run Remote Control.

Here is how to do it, the following files are needed.

From the directory where the AdminConsole is installed, example: E:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\i386, copy the following files:

In the directory 0000409 you need one file as well.

Copy the whole directory with these files present to the computer you want to run Remote Control from so you have a folder structure like this:
And then simply launch the CmRcViewer.exe and you are good to go:

Important information, if you want the standalone Remote Viewer to report back to the SCCM Site Server which client is remote controlled and by who, you can add the registry value below on the client as well. 

For 32 bits

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr10\AdminUI\Connection]
“Server”=”Site Server Name”

For 64 bits
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Connection]
“Server”=”Site Server Name”

VBSCRIPT TO RENAME LOCAL BUILTIN "ADMINISTRATOR" AND "GUEST" ACCOUNT

'This specifies the local computer
strComputer = "."

'This tells it what name to look for
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colAccounts = objWMIService.ExecQuery _
("Select * From Win32_UserAccount where localaccount = True and Description = 'Built-in account for administering the computer/domain'")
'This tells it what to rename the account to
For Each objAccount in colAccounts
    objAccount.Rename "ADMIN"
Next

'This tells it what name to look for
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colAccounts = objWMIService.ExecQuery _
("Select * From Win32_UserAccount where localaccount = True and Description = 'Built-in account for guest access to the computer/domain'")
'This tells it what to rename the account to
For Each objAccount in colAccounts
    objAccount.Rename "Guest"
Next

SCCM 2007 Port communication details

Please refer following link:

http://technet.microsoft.com/en-in/library/bb632618.aspx

Client installation Port details:

http://technet.microsoft.com/en-in/library/ff189805.aspx

Cannot insert more than 1 WSUS update source with different unique ids WUAHandler

1      Cannot insert more than 1 WSUS update source with different unique ids  WUAHandler

Problem Statement:

Most of the times the reason for this behavior is: a previous installation or reinstallation of the site server, which left stale record or for some reason, the hierarchy between the site server has changed (uninstallation - new installation, attaching a site server to a different site), etc..

Symptoms:

WUAUHANDLER.log

Cannot insert more than 1 WSUS update source with different unique ids  WUAHandler

Failed to Add Update Source for WUAgent of type (2) and id ({##-##-##-####}). Error = 0x80040694.        WUAHandler

Its a WSUS Update Source type ({##-##-##-####}), adding it.  WUAHandler

Applies to: SCCM 2007

Troubleshooting Steps:

1.        According to the above log lines, there was a duplicate WSUS registration in the site’s database. TheCI_UpdateSources table in the site’s database, probably contains aged data – a stale record.In order to disable the inactive entry, we need to execute the following steps against the site database:

2.         select * from CI_UpdateSources

3.        The above query should ideally return 1 result. If you get two results, then you have an additional entry of the update source from a previous installation. 
Both the entries may have the IsTombstoned value = 0 which is not correct. 
You need to find the active id by: either comparing the DateCreated and Modified values in the table or the UpdateSource_UniqueID, which should be the same as the one that the client is trying to run the scan against, that we see in the log:

4.         Failed to Add Update Source for WUAgent of type (#) and id ({##-##-##-####}). Error =0x80040694.  WUAHandler        

5.          To disable the inactive entry, we need to run the following command :

6.          update CI_UpdateSources set IsTombstoned = 1 where UpdateSource_ID = '#'

7.         Run  select * from CI_UpdateSources again which results only one entry now

8.        SUP role alone should be uninstalled and install in-order to update wsus registration in SCCM database.

Root Cause Analysis:

According to the above log lines, there was a duplicate WSUS registration in the site’s database. TheCI_UpdateSources table in the site’s database probably contains aged data – a stale record. This needs to be removed manually.

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