Basically, what Nash said. I would decouple the WMF 4.0 conversation from
any third-party modules. If you need to manage individual modules, do so
using the ConfigMgr Application model. You can use PowerShell itself as a
Detection Method to determine the currently installed module version.
Chee
Smita,
The article is telling you not to use the Group Policy Preferences method
because it is stored encoded. It is suggesting a SLAM engagement, or using the
MCS solution.
To use PSPasswd, the device must be online and available for you to talk to it.
While that might work for small orgs,
The issue with the method in the url in the email below is that the password
is not encrypted at all, it is stored in clear text and only protected by AD
rights.
You’re better off looking at the PsPasswd utility from Sysinternals:
http://technet.microsoft.com/en-us/sysinternals/bb897543.aspx
S
Great info, thanks Nash.
Will let everyone know what we find out.
Daniel Ratliff
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Nash Pherson
Sent: Wednesday, July 23, 2014 10:09 AM
To: scripting@lists.myitforum.com
Subject: RE: [scripting] PowerShell t
I usually try to get people to separate the two conversations so you are
talking about the Windows Management Framework separate from individual POSH
modules.
I know I can win on getting them to move to WMF 4 (and expect to have the same
success with WMF 5 when it gets out of beta) because of t
We have the Quest Active Roles for AD powershell module and the Microsoft
AD module in all of our images. The Quest package is in the image to
support some remaining legacy scripts that used it before the same
functionality was added in the Microsoft AD module otherwise I would remove
it from the
I have a question from the team which manages one of the more prolific images
we deploy (80% or more of our deployed workstations). They are debating the
need (the desire) to deploy POSH 4 with additional modules. The specific ask
was around the AD module, but I know there are plenty out there
Daniel,
This is certainly coming up a lot recently. People had been using Group Policy
Preferences to set it, but that runs into the same problem where the encoded
password is available (Ok, it is encrypted, but there is one key used for
Active Directory… and I mean everywhere…. Its available
