Windows 2008 has built in policy GPO for wireless setting management.
You can configure your network setting using Certificates. It is the most recommended and secure way
But if you like to deploy the wireless settings using static key, you will have to use other way.

The steps bellow describe the way to deploy Wireless LAN settings with a Pre-Shared Key
The purpose is to Automate Adding Wireless Profile in Windows.

Preparations

• Configure Wireless settings on one workstation
• from command prompt run
  netsh wlan export profile name="NameOfyourProfile" folder=c:temp interface="wirelesssettings”
• Confirm that under c:temp you have wirelesssettings.xml file
• Open wirelesssettings.xml file locate the following line
  <protected>true</protected>
• Change it to <protected>false</protected>
• Under you will see encrypted line <keyMaterial>01000000D08C9DDF0115D1118</keyMaterial>
• Change it to your key like that <keyMaterial>Yourkey</keyMaterial>
  

  Note: It means that your wireless key will be in clear text and everyone who has access to the file will be able to read your wireless key"

Deployment

• Copy your wireless settings xml file to NETLOGON
• Create a bat or cmd file with the following line
  netsh wlan add profile filename="\yourserverNETLOGONwirelesssettings.xml" user=all
• Run the bat file from some domain member computer and confirm that it works

After finishing all steps above you can deploy the script from GPO

Note: Setting are applicable for Windows Vista Windows 7 and Windows 2008 Only

In Previous version we used to work with CPL File Names  to define which one of control panel applets will be displayed.

In order to make it work Use Canonical names instead.
It should Look like that

You can get the full list from here

In System properties window you can various information about  Windows system .
You may wish to block it to prevent users from accessing it  and do changes.

You can easily disable access to My Computer context menu through AD Group Policy.
This solution doesn’t block access to menus, only hides it from right click. Menu  can still be accessed Windows key + Pause/Break key.

To disable it Open Group Policy Manager
Navigate to User Configuration > Policies > Administrative Templates > Desktop
Double Click on “Remove Properties from the Computer icon context menu” and change it to “Enabled”

Windows 7 Trial Download

There is no 100% foolproof  solution that blocks local admin users access the option of disjoining their computer from domain , but you can make it harder to get to system menu.

I remove the "properties" from when you right click on my computer.
Then i also remove system applet from control panel menu ,and disable registry editing.

To disable right click on my computer go to Group Policy.
Navigate to  User Configuration>Administrative templates>Desktop
Locate “Remove Properties from the My Computer context menu” and set it to “Enable”

You should check also How disable  Right Click Properties on my computer on windows 7/Vista

Than navigate to User Configuration>Administrative templates>Control PanelLocate “Hide specified Control Panel applets”Set it to “Enabled” and add Sysdm.cpl to the list of disallowed Control Panel applets.

To block Sysdm.cpl  from executing

Navigate to User Configuration>Administrative Templates>System

Navigate to “Don’t run specified Windows application” set it to “Enabled” and add Sysdm.cpl  to the list of disallowed applications

• Open Group Policy Editor:
• Link Policy to relevant OU
• Navigate to User Configuration>Administrative Templates>Start menu and taskbar.
• Edit “Prevent Changes to Taskbar and Start Menu Settings”
• Set it to enable
  
• Pres OK

Note: To enforce group policy: Navigate to Start>Run type gpupdate /force and hit Enter

Recently I installed 2 2008 terminal servers , and when I started configuring them I realized that I can’t use lot of new features that are available only via 2008 Group Policy . The network was 2003 , and adding or upgrading current DC to 2008 domain controller rises project costs ( 2008 CAL’s for entire domain ) I had to look for other solution .

Since windows 2008 GPO templates changed their format from ADM to ADMX I couldn’t import windows 2008 templates to windows 2003 DC.

So here how you solve this.

You must use Vista +sp1 Desktop

First , you need to extend your schema to 2008
The first schema updates need to be applied to the Active Directory Forest. In order to apply them you need to run the adprep application from the domain controller that holds the schema role master. To run the forest schema updates use the following command: adprep /forestprep

Once the forest updates have been updates, the next step is to run the adprep for each domain in the forest. This should be run on the domain controller that holds the Infrastructure operations master role. The command to run is: adprep /domainprep

After you finish with with schema expansion

Go to your Vista desktop.
Download RSAT tool for vista x64 and for vista x86 and install it

After instalation is completed.

• Go to Control Panel click on Program & Features
• Locate and click on Turn Windows features on or off
• Install relevant Feature Administration and Role Administration tools (For group policy install Group Policy Management Tools)

Now you can use all Windows 2008 and Vista  GPO goodies on your windows 2003 domain .