Windows PowerShell 3.0 adds a lot of new features that weren't available in PowerShell v2.0.
* Workflow Engine * Remoting enhancements (eg. disconnected, robust sessions) * Parameter value auto-completion (and mid-line auto-completion) * New modules / cmdlets If any of the features like Remoting or Workflow are being used, the server would be required to run PowerShell version 3.0. Additionally, once you've grown accustomed using PowerShell v3.0, going back to v2.0 is tough. So is it true that they still have not fixed this issue once and for all? Cheers, Trevor Sullivan <http://trevorsullivan.net/> <http://twitter.com/pcgeek86> <http://facebook.com/trevor.sullivan> <https://plus.google.com/106658223083457664096> From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, August 29, 2013 1:30 PM To: [email protected] Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points Sorry, not sure what I was thinking but I'm mixing up two separate issues here. Ivan's answer below is applicable and correct. Is there a reason you want to do WMF 3.0 right now though; i.e., why isn't PowerShell 2.0 sufficient? Or alternatively, adding PowerShell 3.0 to the site systems/servers right now doesn't give you any additional ConfigMgr centric capabilities so why not just install that on your workstation to continue your learning and not play with fire? You'll still be able to connect to the server (via WMI) and do everything that you need. J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Thursday, August 29, 2013 1:01 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points Which update are you referring to? Can it be installed outside of an SP1 update/upgrade? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, August 29, 2013 1:47 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points It's all moot though. The update which was included in the re-released media fixes the issue. J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Thursday, August 29, 2013 12:34 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points The article is (still) lacking detail. For every computer with WMF 3.0 where you have CCMEVAL set to Repair if it finds an issue (which is the default), if a WMI repair is initiated by the CCMEVAL it will corrupt WMI. This is because WMF 3.0 is makes fundamental and permanent changes to WMI that the SCCM client RTM can't handle. This is fixed in SP1 as Jason stated. We have disabled the repair part of CCMEval at install time with a regkey change on all computers pushed via GPO. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly=True We may have needed to create the key, I don't recall. Ivan Lindenfeld Fidelity National Financial Jacksonville, Florida From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Thursday, August 29, 2013 1:15 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points Sorry, should have specified. Not on SP1 *yet*. Plan to deploy SP1 and R2 in tandem rather than risk breaking things twice in such a short window. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, August 29, 2013 1:11 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Windows Management Framework 3.0 & Configuration Manager 2012 Management Points Are you at SP1? If so, this is all OOBE (as long as you've downloaded the updated media from Jan 24th I think). J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Thursday, August 29, 2013 11:58 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] Windows Management Framework 3.0 & Configuration Manager 2012 Management Points Hello All, I've been recently brushing up on my PowerShell 3.0 skills and I'd like to add PowerShell 3.0 to our Configuration Manager 2012 Primary Site (and only management point), a Windows Server 2008 R2 box. I'm aware of this KB about the known issues on MP's after installing WMF 3.0: https://support.microsoft.com/kb/2796086 However, it specifically says "management points that are collocated with the client fail daily by returning HTTP 500 errors to calling clients". Does that mean that if I do not have the CM client installed on the management point, the ccmeval doesn't run (would make sense, since there is no client installed), consequently doesn't fail, no repair is initiated, and the MP functions normally? I would assume so (especially given that WMF 3.0 is a prerequisite for SP1, and SP1 is required for WMF 3.0 support from what I've seen), but I'd like to get some confirmation since it doesn't explicitly say. Thanks in advance, Andrew _____ 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. _____ 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.
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
