Saturday, October 26, 2013

Cannot edit the Object, which is used by - Admin console - SEDO - Serialized editing of distributed objects" - ConfigMgr 2012


Hello guys. yesterday one of colleague called me and wanted me to look into an issue while editing Task Sequence. The admin console did not let him edit the task sequence with a message "Cannot edit the object, which is used by Domain\admin at site 000". On seeing the message i was able to explain him that admin console is preventing this edit, since another admin is editing the same object from different site or computer. This feature of ConfigMgr 2012 is called SEDO - Serialized editing of distributed objects"

  In earlier 2007 more than one admin user can edit the same object at a time and whoever writes last wins and others changes will be dishonored. This may cause unexpected results. But in 2012 we have SEDO and with this only one admin user can edit an object at a time. This prevents unexpected results.

  So how does this work ?. Consider that i have two admin users named admin1 and admin2. Admin 1 opens ConfigMgr console and starts Task sequence edit to edit an task sequence named Task sequence1. Now the object Task sequence1 will be locked to edit. So if admin2 launches consolle and tries to edit task sequence1 the admin to will receive a message like this and he will have an option to open Task sequence1 in read only mode.


The lock will be released only when Admin one closes Task Sequence editor.

  For whatever reason if the Admin1 is not able to close the task sequence editor in a regular way (Admin console crashed or Admin1 went for a break or Vm crashed) the lock will remain for 30 more minutes on the object.

  If you dont want to wait for 30 mins you may have to release the lock manually through SQL management studio.The Lock state will be maintained on the table SEDO_LockState. By running

"SELECT *
FROM SEDO_LockState
WHERE AssignedUser = 'Domain\admin1' AND LockStateID = 1"

in sql management studio you will get the Lock_State information. If you want to remove the lock you will have to run this query in SQL management studio.

"DELETE FROM SEDO_LockState WHERE AssignedUser = 'Domain\admin1' AND LockStateID = 1"

Listed below are the SEDO enabled objects
  • SMS_Application
  • SMS_AuthorizationList
  • SMS_BootImagePackage
  • SMS_ConfigurationBaselineInfo
  • SMS_ConfigurationItem
  • SMS_DeploymentType
  • SMS_Driver
  • SMS_DriverPackage
  • SMS_GlobalCondition
  • SMS_ImagePackage
  • SMS_OperatingSystemInstallPackage
  • SMS_Package
  • SMS_SoftwareUpdatesPackage
  • SMS_TaskSequencePackage

Hope this helps..
                                                                                                                                S A Delphin

Reactions:

0 comments:

Post a Comment

Twitter Delicious Facebook Digg Stumbleupon Favorites More

 
Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | Bluehost Coupons