Bump... anyone? From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, October 18, 2013 9:35 AM To: [email protected] Subject: [mssms] RE: Issue with MS13-091 take 2
I believe so, as that's what's referenced in the KB link Rick provided. Question: how are people handling this within their OSD process? I am thinking I can just remove that update from the Software Updates deployment, but then how do I target the systems outside of OSD to ensure it is installed after the fact? Or can this be slipstreamed in to the WIM during an "Install Updates Offline" step? Thanks in advance, Andrew From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, October 18, 2013 8:12 AM To: '[email protected]' Subject: [mssms] RE: Issue with MS13-091 take 2 isn't it 081 not 091? ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of JONES, RICK J Sent: Thursday, October 17, 2013 8:26 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Issue with MS13-091 take 2 Just wanted to give you all a heads up and how to fix it for the issues where a client might flip into Provisioning Mode from this last month's MS13-091 patch (http://support.microsoft.com/kb/2862330) where a dual reboot during task sequencing could freak out the client. Here is Microsoft's Information on the problem and fix; http://support.microsoft.com/kb/2894518 The alternatives were not very attractive, namely reloading the client or remotely finding a broken system and running the PowerShell script. I have confirmed that a DCM still works while in the Provisioning Mode (and have PowerShell bypass enabled for clients), this is the command I used to get the information; (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\CCM\CcmExec).ProvisioningMode [cid:[email protected]] Validate it as Value = false [cid:[email protected]] And then use the command referenced in the link for Remediation; Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false [cid:[email protected]] Rick J. Jones Wireless from AT&T Domestic Desktop Application Management D: (425) 288-6240 C: (206) 419-1104 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company. ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company.
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
