Computer Enterprise: September 2011

29 Sept 2011

How To Find Your Windows 7 Product Key

If you're preparing to reinstall Windows 7 you will need to locate your unique Windows 7 product key - also known as the Windows 7 serial or Windows 7 CD key. Normally this product key is on a sticker on your computer or located with the manual that came with Windows 7.

However, if you've lost your product key, all hope is not lost - your Windows 7 key is stored in the registry but is encrypted and not readable, making finding it difficult. Luckily there are several free programs that can help.

1.Manually locating the Windows 7 product key from the registry is nearly impossible due to the fact that it's encrypted.

Note: The manual techniques used to locate the product key for operating systems like Windows 95 and Windows 98 will not work in Windows 7. Those manual procedures will only locate the product ID number, not the actual product key used for installation. Lucky for us, several free programs exist to help find product keys.

2.Choose a free product key finder program that supports Windows 7.

Note: Any product key finder that locates Windows 7 product keys will locate the product keys for any version of Windows 7: Ultimate, Enterprise, Professional, Home Premium, Home Basic, and Starter.

3.Download and run the key finder program. Follow any instructions provided by the software.

4.The numbers and letters displayed by the program represent the Windows 7 product key. The product key should be formatted like xxxxx-xxxxx-xxxxx-xxxxx-xxxxx - five sets of five letters and numbers.

5.Write this key code down exactly as the program displays it to you for use when reinstalling Windows 7.

Note: If even one character is written down incorrectly, the installation of Windows 7 that you attempt with this product key will fail. Be sure to transcribe the key exactly.

Tips:

If you need to install Windows 7 but you still can't find your Windows 7 product key, even with a product key finder, you have two choices.

You can either request a replacement product key from Microsoft or you can purchase a brand new copy of Windows 7.

Requesting a replacement Windows 7 product key is going to be cheaper but if that doesn't work out, you may in fact have to buy a new copy of Windows.

14 Sept 2011

Configuring Windows Server 2008 Server Core Basic Networking Settings

In my previous articles (see list below) I have written about how, in Windows Server 2008, Server Core installation does not include the traditional full graphical user interface (GUI). Therefore, once you have configured the server, you can only manage it locally at a command prompt, or remotely using a Terminal Server connection.

Like any other server, Server Core machines must be properly configured to be able to communicate on your network. Some of these settings include:

Configuring an IP address
Configuring an administrator's password
Configuring a server name
Enabling remote MMC snap-in management
Enabling remote RDP connections
Enabling remote Windows Firewall management
Enabling remote shell management
Activating the server
Joining a domain
Configuring Windows Updates
Configuring error reporting
Adding server roles and features

And other tasks.

Before you start, you need to configure the server's IP address.

To set the server with a static IP address

At a command prompt, type the following:
```
netsh interface ipv4 show interfaces
```
Look at the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address.
At the command prompt, type:
```
netsh interface ipv4 set address name="" source=static address= mask= gateway=
```
Where:
- ID is the number from step 2 above
- StaticIP is the static IP address that you are setting
- SubnetMask is the subnet mask for the IP address
- DefaultGateway is the default gateway
At the command prompt, type:
```
netsh interface ipv4 add dnsserver name="" address= index=1
```
Where:
- ID is the number from step 2 above
- DNSIP is the IP address of your DNS server
Repeat step 4 for each DNS server that you want to set, incrementing the index= number each time.
Verify by typing ipconfig /all and checking that all the addresses are correct.

To set the administrative password in Windows Server 2008

At a command prompt, type the following:
```
net user administrator *
```
When prompted to enter the password, type the new password for the administrator user account and press ENTER.
When prompted, retype the password and press ENTER.

Next, you might want to change the computer's name, as the default name is a random-generated name (unless configured through an answer file)

To change the name of the server

Determine the current name of the server with the hostname or ipconfig /all commands.
At a command prompt, type:
```
netdom renamecomputer  /NewName:
```
Restart the computer by typing the following at a command prompt:
```
shutdown /r /t 0
```

To manage a server running a Server Core installation by using the Windows Remote Shell

To enable Windows Remote Shell on a server running a Server Core installation, type the following command at a command prompt:
```
WinRM quickconfig
```
Click Y to accept the default settings. Note: The WinRM quickconfig setting enables a server running a Server Core installation to accept Windows Remote Shell connections.
3. On the remote computer, at a command prompt, use WinRS.exe to run commands on a server running a Server Core installation. For example, to perform a directory listing of the Windows folder, type:
```
winrs -r: cmd
```
Where ServerName is the name of the server running a Server Core installation.
You can now type any command that you require, it will be executed on the remote computer.

To activate the server

At a command prompt, type:
```
slmgr.vbs –ato
```
If activation is successful, no message will return in the command prompt.

To activate the server remotely

At a command prompt, type:
```
cscript slmgr.vbs -ato
```
Retrieve the GUID of the computer by typing:
```
cscript slmgr.vbs -did
```
Type
```
cscript slmgr.vbs -dli
```
Verify that License status is set to Licensed (activated).

To join a Windows 2008 server to a domain

At a command prompt, type:
```
netdom join  /domain: /userd: /passwordd:*
```
Where:
- ComputerName is the name of the server that is running the Server Core installation.
- DomainName is the name of the domain to join.
- UserName is a domain user account with permission to join the domain.
Note: Entering * as the password means you will be prompted to enter it on the command prompt window in the next step. You can enter it in the initial command, if you wish to. Note: Note that the word "passwordd" has 2 d's in it…
When prompted to enter the password, type the password for the domain user account specified by UserName.
Restart the computer by typing the following at a command prompt:
```
shutdown /r /t 0
```

To remove the Windows 2008 server from a domain

At a command prompt, type:
```
netdom remove
```
Reboot the computer.

To configure automatic updates

To enable automatic updates, type:

cscript C:'Windows'System32'Scregedit.wsf /au 4

To disable automatic updates, type:

cscript C:'Windows'System32'Scregedit.wsf /au 1

BTW, in order to view your current settings you can type:

cscript C:'Windows'System32'Scregedit.wsf /au /v

To configure error reporting

To verify the current setting, type:
```
serverWerOptin /query
```
To automatically send detailed reports, type:
```
serverWerOptin /detailed
```
To automatically send summary reports, type:
```
serverWerOptin /summary
```
To disable error reporting, type:
```
serverWerOptin /disable
```

Advanced Group Policy Management #5

Withdrawing a Pending Request

Figure 1 shows the situation after Jacky Chen, who holds the Editor role, created three new controlled GPOs for managing Windows BitLocker encryption, Folder Redirection and wireless networking policies in Seattle. These new controlled GPOs are currently displayed on the Pending tab, which means they will not actually be created until Karen Berg, who holds the Approver role, approves their creation. Jacky is currently logged on to her administrative workstation and is looking at the Pending tab as shown below:

Figure 1: Three new controlled GPOs created by Jacky are waiting for Karen's approval.

Jacky realizes that her request to create the Seattle Wireless Networking Policy was a mistake. Instead of sending a personal email to Karen asking her to ignore the approval request email she received from the AGPM Server for this item, Jacky decides to withdraw her earlier request. To do this, Jacky right-clicks on the Seattle Wireless Networking Policy item on the Pending tab and selects Withdraw:

Figure 2: Jacky withdraws her earlier request to create a Seattle Wireless Networking Policy GPO.

In the Submit Withdraw dialog, Jacky specifies the reason she is withdrawing her earlier request:

Figure 3: Jacky specifies the reason she is withdrawing her earlier request.

Once Jacky clicks Submit, her request to create the Seattle Wireless Networking Policy GPO is withdraw and this item is removed from the Pending tab:

Figure 4: Jacky's request to create a Seattle Wireless Networking Policy GPO is no longer pending Karen's approval.

Approving a Pending Request

In Figure 5 below, Karen is currently logged on. The Pending tab shows two requests from Jacky to create new controlled GPOs, one to create a Seattle BitLocker Encryption Policy GPO and the other to create a Seattle Folder Redirection Policy GPO. These requests are awaiting Karen's approval, and after reviewing the first request (Seattle BitLocker Encryption Policy) Karen decides to approve creation of this GPO. To do this, she right-clicks on the pending request and selects Approve:

Figure 5: Karen approves Jacky's request to create a new controlled GPO.

Karen adds a comment when approving the pending request:

Figure 6: Adding a comment when approving a pending request.

The AGPM Progress dialog shows that the new controlled GPO has been successfully created:

Figure 7: AGPM Progress dialog.

Once the pending request to create the Seattle BitLocker Encryption Policy has been approved, the request is removed from the Pending tab:

Figure 8: The pending request for Seattle BitLocker Encryption Policy has been approved.

The Seattle BitLocker Encryption Policy is now displayed on the Controlled tab, which shows that the new controlled GPO has indeed been created:

Figure 9: The Seattle BitLocker Encryption Policy has been created

In addition, when the Group Policy Objects node is selected in the Group Policy Management Console (GPMC) the new GPO is displayed there as well:

Figure 10: Seattle BitLocker Encryption Policy GPO

Rejecting a Pending Request

After reviewing the second pending request from Jacky (to create a Seattle Folder Redirection Policy GPO) Karen decides that this particular request should be rejected since the new GPO does not satisfy the requirements of the organization. To reject this pending request, Karen right-clicks on it and selects Reject:

Figure 11: Karen rejects Jacky's request to create a new Seattle Folder Redirection Policy GPO

Karen enters a comment indicating why the request has been rejected:

Figure 12: Karen adds a comment to her rejection.

Once the pending request is rejected, it is removed from the Pending tab:

Figure 13: The request is no longer pending.

Rolling Back a GPO

One of the powerful capabilities of AGPM is change control, which enables you to roll back GPOs to earlier versions when needed. Let's see this feature at work. At this point in time, the Seattle BitLocker Encryption Policy GPO created earlier by Jacky and approved by Karen has been edited several times, and therefore has gone through several versions. As described earlier in article 2 of this series, the AGPM Server maintains older versions of controlled GPOs in the AGPM archive, with the number of stored versions being configurable from 0 to 999.

Karen decides that the current version of the Seattle BitLocker Encryption Policy GPO does not satisfy the needs of the organization, and she wants to revert back to the previous version of this GPO instead. To do this, Karen begins by selecting the Controlled tab of the History dialog for the Seattle BitLocker Encryption Policy GPO. She then right-clicks on the Seattle BitLocker Encryption Policy GPO and selects History:

Figure 14: Step 1 of rolling back a controlled GPO to a previous version.

Karen selects the Unique Versions tab to display the different versions of this GPO that are stored in the archive. The current version of the GPO has 4 as its Computer version number (User version numbers for GPOs are displayed in a column off to the right of this figure):

Figure 15: Step 2 of rolling back a controlled GPO to a previous version.

Karen wants to roll back to the previous version (Computer version 3) of this GPO, so she right-clicks on this previous version and selects Deploy:

Figure 16: Step 3 of rolling back a controlled GPO to a previous version.

A dialog box asks Karen to confirm whether to perform the roll back operation:

Figure 17: Step 4 of rolling back a controlled GPO to a previous version.

After Karen clicks Yes in the above dialog box, the AGPM Progress dialog displays the results of the operation:

Figure 18: Step 5 of rolling back a controlled GPO to a previous version.

Karen switches to the All States tab of the History dialog for the Seattle BitLocker Encryption Policy GPO. The second history item in the list indicates that the previous version (Computer version 3) of this GPO has now been deployed to the production environment:

Figure 19: The roll back operation has been completed.

Note:
In the above walkthrough, the roll back operation was performed on a controlled GPO that was stored in the AGPM archive but was not yet deployed to the production environment. You can also use AGPM to roll back controlled GPOs that are already deployed, and the procedure is similar except you also have the option of choosing whether to restore the GPO links as well.

Deleting and Restoring a Controlled GPO

The following week Karen decides that the Seattle BitLocker Encryption Policy GPO is no longer needed, so she decides to delete this GPO from the AGPM archive. To do this, Karen selects the Controlled tab, right-clicks on the GPO and selects Delete:

Figure 20: Step 1 of deleting a controlled GPO.

In the Delete dialog, Karen has the option of deleting the GPO only from the archive or deleting it from both the archive and the production environment:

Figure 21: Step 2 of deleting a controlled GPO.

Deleting a GPO can be a serious thing, so Karen is prompted to confirm the operation:

Figure 22: Step 3 of deleting a controlled GPO.

The progress dialog indicates the GPO has been deleted from the archive (by uncontrolling it) and also from the production environment:

Figure 23: Step 4 of deleting a controlled GPO.

To confirm that deletion has occurred, Karen notes that the GPO is no longer listed on the Controlled tab, which means it is no longer present in the AGPM archive:

Figure 24: The GPO has been deleted from the AGPM archive.

Selecting the Group Policy Objects node in the GPMC shows that the GPO is also no longer present in the production environment:

Figure 25: The GPO has also been deleted from SYSVOL.

But Karen suddenly realizes she has made a mistake—she should not have deleted the Seattle BitLocker Encryption Policy GPO! It was a different GPO that she should have deleted. What can she do? Fortunately, AGPM allows undeletion of controlled GPOs, so Karen selects the Recycle Bin tab which displays the recently deleted GPO. She right-clicks on this GPO and selects Restore:

Figure 26: Step 1 of restoring a previously deleted controlled GPO.

Karen adds a comment to her operation:

Figure 27: Step 2 of restoring a previously deleted controlled GPO.

The undeleted GPO disappears from the Recycle Bin tab:

Figure 28: Step 3 of restoring a previously deleted controlled GPO.

And re-appears on the Controlled tab, indicating that the undelete operation has been successful:

Figure 29: The previously deleted GPO has been restored!

Note that restoring a controlled GPO that has been previously deleted does not redeploy the GPO to the production environment. To see this, select the Group Policy Objects node—the undeleted Seattle BitLocker Encryption Policy GPO is not displayed:

Figure 30: But it hasn't been redeployed to production.

So if you restored a deleted GPO from your production environment using AGPM, you must still redeploy it to your production environment afterwards.

Advanced Group Policy Management #4

Editing a Controlled GPO

In the previous article of this series, Jacky Chen, an AGPM Editor, proposed creating a new controlled GPO named New York Computers – Power GPO. Karen Berg, an AGPM Approver, received Jacky's request and approved it. Karen then deployed the new GPO into the CONTOSO production environment and linked it to the New York Computers OU so the policy settings configured in the GPO would be applied to computers in that OU. However, the New York Computers – Power GPO was deployed in a pristine state, that is, with no policy settings configured. In line with company policy, Jacky now proposes that the active power plan for New York computers be changed to Power Saver.

Jacky begins by logging on to his administrator workstation and opens the Group Policy Management Console (GPMC). He selects the Change Control node and then on the Controlled tab as shown here:

Figure 1: Step 1 of editing the controlled GPO.

Before Jacky can edit the controlled GPO, he must first check the GPO out of the AGPM archive. Checking a GPO out of the archive prevents any other AGPM Editor from making changes to the GPO until Jacky finishes working with it. To check out the New York Computers – Power GPO, Jacky right-clicks on it and selects Check Out as shown here:

Figure 2: Step 2 of editing the controlled GPO.

In the Check Out GPO dialog that displays next, Jacky enters a comment to help track the history of all changes made to the GPO:

Figure 3: Step 3 of editing the controlled GPO.

After clicking OK, the checked out GPO is displayed with a red icon on the Controlled tab:

Figure 4: Step 4 of editing the controlled GPO.

The checked out GPO can now be edited, so Jacky right-clicks on the GPO and selects Edit from the context menu:

Figure 5: Step 5 of editing the controlled GPO.

Doing this opens the New York Computers – Power GPO in the Group Policy Management Editor for editing. Jacky navigates to the Select An Active Power Plan policy setting as shown next:

Figure 6: Step 6 of editing the controlled GPO.

Jacky double-clicks on the Select An Active Power Plan policy setting to open it for editing. He then enables the policy setting and selects Power Saver as the Active Power Plan:

Figure 7: Step 7 of editing the controlled GPO.

After clicking OK to close the policy setting and then closing the Group Policy Management Editor, Jacky returns to the Change Control node of the GPMC. He then right-clicks on the New York Computers – Power GPO on the Controlled tab and selects Check In to check the modified GPO back into the AGPM archive:

Figure 8: Step 8 of editing the controlled GPO.

In the Check In GPO dialog that is displayed next, Jacky enters a comment so the history of changes made to this GPO can be more easily tracked in the future:

Figure 9: Step 9 of editing the controlled GPO.

The New York Computers – Power GPO has now been configured, but only on the copy that is stored in the AGPM archive. The copy of this controlled GPO that exists in the CONTOSO production environment (i.e. in SYSVOL) has not been changed at this point, but Jacky is confident that he's configured the right policy changes so he decides to request redeployment of the GPO he has just modified. To do this, Jacky again right-clicks on the New York Computers – Power GPO and this time he selects Deploy from the shortcut menu:

Figure 10: Jacky requests redeployment of the controlled GPO he just modified.

Jacky adds his comment to the Submit Deploy Request as shown below:

Figure 11: Jacky's request for redeploying the controlled GPO to production.

Once Karen receives Jacky's Submit Deploy Request email via AGPM, it's up to her to review the changes and decide whether the modified GPO should be rolled out production. That's what we'll look at next.

Reviewing and Redeploying the Modified GPO

Karen, who as an AGPM Approver also holds the AGPM Reviewer role, is now going to review the changes that Jacky has made to the archived copy of the New York Computers – Power GPO and then redeploy the modified GPO into the production environment. To begin doing this, Karen logs on to her administrator workstation, opens the GPMC, selects the Change Control node, selects the Controlled tab, right-clicks on the New York Computers – Power GPO and selects History from the shortcut menu:

Figure 12: Step 1 of reviewing and redeploying a controlled GPO that has been modified.

In the History For dialog that displays next, the All States tab provides more information that Karen needs at he moment concerning the change history of the New York Computers – Power GPO:

Figure 13: Step 2 of reviewing and redeploying a controlled GPO that has been modified.

So Karen selects the Unique Versions tab and sees that the most recent change version was checked in by Jacky and is ready for her review:

Figure 14: Step 3 of reviewing and redeploying a controlled GPO that has been modified.

Karen then clicks the Differences button at the bottom left of the History For dialog shown above. Doing this opens Internet Explorer and displays any differences between the selected version of the controlled GPO (the version labeled "Checked in" in Figure 14 above) and the previous version of the same controlled GPO (the version labeled "Created" in Figure 14 above). The Difference Report shows that the only change Jacky made to the GPO was to enable the Active Power Plan policy setting and set it to Power Saver:

Figure 15: Step 4 of reviewing and redeploying a controlled GPO that has been modified.

Karen decides that the changes Jacky has made to the New York Computers – Power GPO are OK, so she closes Internet Explorer and clicks the Close button in the History For dialog shown in Figure 14 previously. Doing this displays the Approve Pending Operation dialog shown here:

Figure 16: Step 5 of reviewing and redeploying a controlled GPO that has been modified.

After typing her comment into the above dialog, Karen clicks Advanced to make sure the modified GPO will be redeployed properly. Clicking the Advanced button opens the GPO Links For Selected GPOs dialog, and Karen notes that redeploying the New York Computers – Power GPO will re-link it to the New York Computers OU as expected:

Figure 17: Step 6 of reviewing and redeploying a controlled GPO that has been modified.

Karen clicks OK to close the GPO Links For Selected GPOs dialog. Then she clicks OK in the Approve Pending Operation dialog shown previously in Figure 16. A progress bar indicates when the modified New York Computers – Power GPO has been redeployed into production:

Figure 18: Step 7 of reviewing and redeploying a controlled GPO that has been modified.

The modified GPO will now be applied to computers in New York according the usual Group Policy processing mechanisms.

Advanced Group Policy Management #3

Creating a New Controlled GPO

To begin, Jacky Chen (who holds the Editor role) logs on to his administrator workstation:

Figure 1: Jacky Chen (AGPM Editor) logs on.

To create a new controlled Group Policy Object (GPO) using AGPM, Jacky launches the Group Policy Management Console (GPMC) from Administrative Tools in the Start menu, and selects the Change Control node for the contoso.com domain:

Figure 2: Step 1 of creating a new controlled GPO.

Jacky right-clicks on the Change Control node and selects New Controlled GPO from the context menu:

Figure 3: Step 2 of creating a new controlled GPO.

In the Submit New Controlled GPO Request dialog that is displayed, Jacky enters a name for the new GPO and, optionally, a descriptive comment (see Figure 4 below). By default, the new GPO is created in both the AGPM archive and in the production environment (SYSVOL) but Jacky decides to create the new GPO only in the AGPM archive in case Karen makes the decision not to deploy the new GPO into the CONTOSO production environment.

Figure 4: Step 3 of creating a new controlled GPO.

After Jacky clicks Submit in the dialog above, the newly created GPO is displayed in the Group Policy Objects area of the Contents tab as shown here:

Figure 5: The new controlled GPO has been created in the AGPM archive.

What if Jacky changes his mind after creating the new controlled GPO and decides that the new GPO isn't needed? In that case, Jacky can withdraw his request for the new GPO by right-clicking on it and selecting Withdraw as shown here:

Figure 6: If needed Jacky can withdraw his request to create the new controlled GPO.

Doing this displays the Submit Withdraw dialog shown below. If desired Jacky can add a comment explaining to the recipients why he is withdrawing his request for the new GPO.

Figure 7: Submitting a request to withdraw an earlier request for creating a new controlled GPO.

But for this walkthrough we'll assume that Jacky does not withdraw his request, so Jacky's earlier Submit New Controlled GPO Request has been sent to Karen (AGPM Editor) for review and approval.

Approving a Request to Create a New Controlled GPO

Karen Berg, who holds the AGPM Editor role which also includes the AGPM Reviewer role, is logged on to her administrator workstation:

Figure 8: Karen Berg (AGPM Approver and Reviewer) logs on.

Karen has received an email from Jacky via AGPM that indicates she needs to review and approve/disapprove Jacky's request to create a new controlled GPO. After reviewing Jacky's email, Karen decides to approve Jacky's request and deploy the new controlled GPO into the CONTOSO production environment. To begin doing this, Karen opens the GPMC and selects the Change Control node for the contoso.com domain. She then selects the Pending tab and notices that the New York Computers – Power GPO is listed as being in a Pending Create state:

Figure 9: Step 1 of approving a request to create a new controlled GPO.

To approve the pending GPO, Karen right-clicks on it and selects Approve from the context menu:

Figure 10: Step 2 of approving a request to create a new controlled GPO.

Doing this opens the Approve Pending Operation dialog where Karen can enter a comment if desired to explain her decision:

Figure 11: Step 3 of approving a request to create a new controlled GPO.

After clicking Yes, a progress bar indicates the successful creation of the new controlled GPO:

Figure 12: Step 4 of approving a request to create a new controlled GPO.

The new GPO is now no longer listed on the Pending tab:

Figure 13: The new GPO is no longer listed on the Pending tab.

Instead, the new GPO is now listed on the Controlled tab indicating that the new controlled GPO has been successfully created in the AGPM archive:

Figure 14: The new controlled GPO has been created and is now listed on the Controlled tab.

At this point, the new controlled GPO has been created but it has not yet been deployed into the CONTOSO production environment, so that will be Karen's next task described below.

Deploying a Controlled GPO to Production

Once Karen has approved Jacky's request for creating a new controlled GPO, Karen's next task is to deploy the new GPO to production. To begin doing this, Karen right-clicks on the controlled GPO and selects Deploy from the context menu:

Figure 15: Step 1 of deploying a controlled GPO to production.

Doing this displays the Deploy GPO dialog as shown here:

Figure 16: Step 2 of deploying a controlled GPO to production.

Karen clicks Yes to deploy the GPO and a progress dialog indicates when this has been done successfully:

Figure 17: Step 3 of deploying a controlled GPO to production.

To confirm that the controlled GPO has been deployed from the AGPM archive into the CONTOSO production environment, Karen expands the Group Policy Objects node for the contoso.com domain in the GPMC. Because the New York Computers – Power GPO is displayed under this node, a copy of this controlled GPO is now present in SYSVOL:

Figure 18: Step 4 of deploying a controlled GPO to production.

While the controlled GPO is now present in the production environment, it is not yet being applied to any target computers because it has not yet been linked to an organizational unit (OU). To link the New York Computers – Power GPO to the New York Computers OU, Karen begins by expanding the New York Computers OU:

Figure 19: Step 5 of deploying a controlled GPO to production.

Karen then right-clicks on the New York Computers OU and selects Link An Existing GPO from the context menu:

Figure 20: Step 6 of deploying a controlled GPO to production.

In the Select GPO dialog that is displayed next, Karen selects the New York Computers – Power GPO as shown here:

Figure 21: Step 7 of deploying a controlled GPO to production.

After clicking OK, the New York Computers – Power GPO is now linked to the New York Computers OU:

Figure 22: The controlled GPO has been deployed to production.

The controlled GPO that Jacky proposed creating has now been fully deployed by Karen into the CONTOSO production environment.