Hard to say, as I don't know exactly when I did what anymore. My assumption is it wasn't the unlock cmdlet, but the 30min autodeletion.
Actually, on the first TS I had the same, just didn't think about it when it suddenly worked. And I also was able to actually lock an already locked object. That was weird. I know, not making sense. Let's see next time. The console crashed several times already, maybe I get the same issue again. -R From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Donnerstag, 20. Februar 2014 11:59 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: <mailto:[email protected]> [email protected] To: <mailto:[email protected]> [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
