LogoLogo
OSDeploy.comTwitterGitHub
  • Overview
  • OSDeploy Home
  • Download
    • Release Notes
    • GitHub
    • LGPO
    • OSDeploy PowerShell Module
  • Docs
    • Deployment
      • ConfigMgr New PC TS Package
      • ConfigMgr New PC TS Unattend.xml
      • ConfigMgr New PC TS Provisioning Package
      • MDT New PC TS
    • Customize
      • Alpha
      • Apps
      • Background
      • LocalPolicy
        • ImportGPO
        • ImportTXT
        • LGPO
        • Import-GPO.ps1
      • RegistryXML
      • Scripts
      • Start
      • Theme
      • Zeta
    • Group Policies
      • Best Practices
        • Edit Local Policy with Reg Keys
      • Active Directory GPO
      • Build a Domain Controller
      • Update ADMX Templates
      • Local vs Domain Policies
      • Import OSDeploy GPOs
      • Edit OSDeploy Branding GPO
    • Provisioning Packages
      • PowerShell Script to PPKG
      • OSConfig to PPKG
    • Registry
      • Group Policy Preferences
      • GPP Registry.xml
      • RegistryXML Files
      • Convert REG to RegistryXML
      • Apply RegistryXML Files
    • How To
      • Theme Customization
Powered by GitBook
On this page

Was this helpful?

  1. Docs
  2. Group Policies

Active Directory GPO

You can create a Local Policy for OSConfig by creating an Active Directory Group Policy Object. If you have Full Control of Active Directory and you can create a GPO, then good for you. My role in my Enterprise is to customize the Operating Systems, and to create our Deployment strategy for Operating Systems. I am not a Security Expert . . . so I will not get deep into the Security side of things when working with GPOs.

For the purpose of this guide, I will detail how to create a GPO for OS Customization only. It is up to you to determine the strategies for enforcing and item level targeting. To be clear, the GPO's that we will use will not be used for Policy on a Domain, but for OS Deployment only.

Back to AD . . . I have rights in my Enterprise to create a GPO, but not to link it to an OU. I turn those into our AD team to implement, but if I am going to use a GPO for OS Customization only, then no need to turn over the GPO . . . which means I maintain full control.

If you do not have rights to create a GPO, get with your Active Directory guys to create these for you and grant you permission to edit them, and let them know it's ok if you don't get permission to link them to an OU.

I manage a mixed Enterprise of both Windows 10 and Windows 7 so this guide will detail both

If you do not have rights to Active Directory Group Policy Management, then why not create a VM Domain Controller?

Create GPO's

I recommend creating the following GPOs in Active Directory

​

PreviousEdit Local Policy with Reg KeysNextBuild a Domain Controller

Last updated 5 years ago

Was this helpful?