Information Technology Reference
In-Depth Information
Managing GPOs with Windows PowerShell
Group Policy Cmdlets
As stated earlier in this topic, Windows PowerShell is a Windows command-line shell and
scripting language. Windows PowerShell can also help an administrator automate many of
the same tasks that you perform using the Group Policy Management Console.
Windows Server 2012 R2 helps you perform many of the Group Policy tasks by
providing more than 25 cmdlets. Each of these cmdlets is a simple, single-function
command-line tool.
The Windows PowerShell Group Policy cmdlets can help you perform some of the
following tasks for domain-based Group Policy objects:
Maintain, create, remove, back up, and import GPOs
Create, update, and remove GPO links to Active Directory containers
Set Active Directory OUs and domain permissions and inheritance flags
Configure Group Policy registry settings
Create and edit Starter GPOs
The requirement for Windows PowerShell Group Policy cmdlets is Windows Server
2012 R2 on either a domain controller or a member server that has the GPMC installed.
Windows 7 and Windows 8 also have the ability to use Windows PowerShell Group Policy
cmdlets if they have Remote Server Administration Tools (RSAT) installed. RSAT includes
the GPMC and its cmdlets. PowerShell is also a requirement.
Deploying Software Through a GPO
It's difficult enough to manage applications on a stand-alone computer. It seems that the
process of installing, configuring, and uninstalling applications is never finished. Add in
the hassle of computer reboots and reinstalling corrupted applications, and the reduction
in productivity can be substantial.
Software administrators who manage software in network environments have even more
concerns.
First, they must determine which applications specific users require.
Then, IT departments must purchase the appropriate licenses for the software and
acquire any necessary media.
Next, the system administrators need to install the applications on users' machines.
This process generally involves help desk staff visiting computers, or it requires end
users to install the software themselves. Both processes entail several potential prob-
lems, including installation inconsistency and lost productivity from downtime experi-
enced when applications were installed.
Finally, software administrators still need to manage software updates and remove
unused software.
 
Search WWH ::




Custom Search