Authorization is required to manipulate objects such as queues and work items in Microsoft System Center Service Manager 2010. These authorizations are managed by using profiles. A profile is a collection of items that are used for authorization. For operations such as create, read, update, and delete, the following structure is used for the items of authorization:
ProfileName Operation Type Property Relationship RelationshipEndPoint
For authorization, a user role specifies operations that specific users can perform on specific objects by associating a profile, a scope, and users. Profiles are also used by the Service Manager console to filter objects such as tasks and templates.
The three stored procedures that are included in this hotfix have the following file names:
These SQL stored procedures let you add or remove rights for an operation in profiles to support custom types that were added to the Service Manager environment. The Service Manager console cannot add or remove these rights. For example, you can add the following authorization to the IncidentResolver profile if you customized the User type by adding a new New Relationship relationship:
ProfileName Operation Type Property Relationship RelationshipEndPoint IncidentResolver Object_Set User New Relationship
These stored procedures also give you more details for accessing properties of specific types. The Service Manager console cannot provide these details. These SQL stored procedures cannot add new operations to a profile and can perform only the following tasks:
For all the details and to download this hotfix please see the following Knowledge Base article:
KB2525307 - A hotfix is now available to let you add or remove rights for an operation in profiles to accommodate custom types that were added to the System Center Service Manager 2010 environment
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
Hi J.C., Is there any issue with the way this is packaged? I keep getting an error "The installation source for this product is not available. Verify that the source exists and that you can access it." I checked the SCSMPatcherSetupWizard01.log and it stated the same and to check the SCSM2010_SP1_KB2525307.msp.0.log which indicated "SOURCEMGMT: Source is invalid due to missing/inaccessible package." Any help would be appreciated. Thanks.