Might have still been proceeding policy? I see that a lot with task sequences.
-Daniel Ratliff -----Original Message----- From: David O'Brien [[email protected]<mailto:[email protected]>] Sent: Thursday, February 20, 2014 05:59 AM Eastern Standard Time To: [email protected] Subject: RE: [mssms] RE: unlock-cmobject broken? No, it should happen straight away or after 30mins it's deleted from the DB automatically. Would be interesting to see what the SMSProv.Log told you when you tried to unlock the object. ------- David http://www.david-obrien.net ________________________________ From: [email protected] To: [email protected] Subject: [mssms] RE: unlock-cmobject broken? Date: Thu, 20 Feb 2014 11:52:07 +0100 Sight, just tried again, now it is unlocked. Is there a delay to wait for? From: Roland Janus [mailto:[email protected]] Sent: Donnerstag, 20. Februar 2014 11:50 To: '[email protected]' Subject: unlock-cmobject broken? CM12, R2: The console crashed and two TS got locked. While I was able to unlock the first, the 2nd doesn’t. unlock-CMObject -InputObject $(Get-CMtasksequence -Name Win8.1_LabBuild) Unlock isn’t doing anything, no errors, but it doesn’t get unlocked either. Trying to lock it first confirms it is still locked, hence unlock should work, well it doesn’t. Is that known? Reverting to sql now I guess. -R The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
