OSD import permission Issue

We might get when we are looking for only import permissions for a user or Group..

or

even when we setup the permissions at the end of the wizard we may get this error..

Errors

·You do not have security rights to perform this operation.

·ConfigMgr Error Object:

·instance of SMS_ExtendedStatus

·{

· Description = “User \”*************\” does not have permission of the current site to import machines.”;

· ErrorCode = 1112017920;

· File = “e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp”;

· Line = 766;

· ObjectInfo = “524288″;

· Operation = “ExecMethod”;

· ParameterInfo = “SMS_Site”;

· ProviderName = “WinMgmt”;

· StatusCode = 2147749889;

};

 

The actual permissions required at SCCM Console level is:

1. On SCCM Root Collections we must grant read & read Resource
2. and for the target of the collection we need to give the permissions to add or whatever you wanted
3. at computer Association level we must give permissions for importing
4. (The most common mistake or un- mentioned step ..this one we may forget most of the time)

On the top of the Site ==Properties=> Security Tab => Class Security rights and we must choose here read,Import Computer Entry (below screenshot)

OSD import permission Issue

We might get when we are looking for only import permissions for a user or Group..

or

even when we setup the permissions at the end of the wizard we may get this error..

Errors

·You do not have security rights to perform this operation.

·ConfigMgr Error Object:

·instance of SMS_ExtendedStatus

·{

· Description = “User \”*************\” does not have permission of the current site to import machines.”;

· ErrorCode = 1112017920;

· File = “e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp”;

· Line = 766;

· ObjectInfo = “524288″;

· Operation = “ExecMethod”;

· ParameterInfo = “SMS_Site”;

· ProviderName = “WinMgmt”;

· StatusCode = 2147749889;

};

 

The actual permissions required at SCCM Console level is:

1. On SCCM Root Collections we must grant read & read Resource
2. and for the target of the collection we need to give the permissions to add or whatever you wanted
3. at computer Association level we must give permissions for importing
4. (The most common mistake or un- mentioned step ..this one we may forget most of the time)

On the top of the Site ==Properties=> Security Tab => Class Security rights and we must choose here read,Import Computer Entry (below screenshot)

How to grant the SCCM Console permissions to Support Executive

Scenario SCCM installed on cm07.test.com & I have a test system with windows XP/7.
I have a User called RBAC and RBAC wanted some permissions on SCCM console.

Steps:-

Install the SCCM console on windows Xp/7

add the RBAC user to SMS Admins Group.

Follow these steps for granting the DCOM rights.

1. From SCCM Server the Start menu, click Run and type Dcomcnfg.exe.

2. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.

3. In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.

4. In the Launch Permissions dialog box, click Add.

5. In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, typeSMS Admins and click OK.

6. In the Permissions for SMS Admins section, select the check box to allow Remote Activation.

7. Click OK twice, and then close Computer Management.

Public SCCM 2007 Right Click Tools : TWO different versions available

One from Dan Ireland

http://myitforum.com/cs2/blogs/direland/pages/sccm-console-extensions.aspx

Second One from Rick Houchins

 

http://myitforum.com/cs2/blogs/rhouchins/0401ConfigMgrTools.zip

Unable to load console on Primary Site Server

Symptom: Unable to load console on Primary Site Server

Further Conditions - WMI Failures indicated by errors 0x80041002 in the Event Log, MPControl.log.  Unable to connect to namespace root/cimv2.

Use the WMI Diag tool for further analaysis and confirmation of namespace errors.

Restart WMI service and check corresponding event log for errrors.

If necessary rebuild WMI using the WMIMGMT /salvagerepository command

Restart SCCM Services and check collections etc