1.3 KiB
title, description, author, ms.assetid, ms.reviewer, manager, ms.author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod, ms.date
title | description | author | ms.assetid | ms.reviewer | manager | ms.author | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod | ms.date |
---|---|---|---|---|---|---|---|---|---|---|---|
Use a Test Environment | Use a Test Environment | mjcaparas | b8d7b3ee-030a-4b5b-8223-4a3276fd47a7 | dansimp | macapara | mdop | manage | library | w10 | 06/16/2016 |
Use a Test Environment
If you use a testing organizational unit (OU) to test Group Policy objects (GPOs) before deployment to the production environment, you must have the necessary permissions to access the test OU. The use of a test OU is optional.
To use a test OU
-
While you have the GPO checked out for editing, in the Group Policy Management Console, click Group Policy Objects in the forest and domain in which you are managing GPOs.
-
Click the checked out copy of the GPO to be tested. The name will be preceded with [AGPM]. (If it is not listed, click Action, then Refresh. Sort the names alphabetically, and [AGPM] GPOs will typically appear at the top of the list.)
-
Drag and drop the GPO to the test OU.
-
Click OK in the dialog box asking whether to create a link to the GPO in the test OU.
Additional considerations
- When testing is complete, checking in the GPO automatically deletes the link to the checked-out copy of the GPO.
Additional references