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

While performing maintenance to Exchange 2010 DAG server you should first remove the DAG member from DAG group.Other wise you may have unwanted DB failovers and many other unexpected issue that may affect company mail services availability

Shutting Down DAG Members

The Exchange 2010 high availability solution is integrated with the Windows shutdown process. If an administrator or application initiates a shutdown of a Windows server in a DAG that has a mounted database that’s replicated to one or more DAG members, the system attempts to activate another copy of the mounted database prior to allowing the shutdown process to complete.

However, this new behavior doesn’t guarantee that all of the databases on the server being shut down will experience a lossless activation. As a result, it’s a best practice to perform a server switchover prior to shutting down a server that’s a member of a DAG.

The correct way to perform any maintenance is to run first  StartDagServerMaintenance.ps1 script that is located under “C:Program FilesMicrosoftExchange ServerV14scripts”
This script moves all the active databases to next preferred DAG server and prevents active databases from moving to that server during the maintenance.
In addition the script ensures that all critical DAG support functionality that may be on this server has been moved to next proffered server

To run the script open EMC
Type:
cd $exscripts
StartDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Suspend-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Pauses the node in the cluster, which prevents the node from being and becoming the PAM.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to blocked
• Moves all active databases currently hosted on the DAG member to other DAG members.
• If the DAG member currently owns the default cluster group, the script moves the default cluster group (and therefore the PAM role) to another DAG member.

If any of the preceding tasks fails, all operations, except for successful database moves, are undone.

After the maintenance is complete and the DAG member is ready to return to serve clients you need to run the following script:

cd $exscripts
StopDagServerMaintenance.ps1 -server YourServername

The script performs the following tasks on the background:

• Runs the Resume-MailboxDatabaseCopy cmdlet for each database copy hosted on the DAG member.
• Resumes the node in the cluster, which enables full cluster functionality for the DAG member.
• Sets the value of the DatabaseCopyAutoActivationPolicy parameter on the DAG member to Unrestricted

I highly recommend using  Start/StopDagServerMaintenanceInstalling maintainance scripts before any action that requiers server Reboot/ShutDown or Update Rollups instalation.

Most of the material has been taken from Managing Database Availability Groups MS article

Get Quota report
Get-Mailbox | Format-Table alias, *quota

Delete message from Mailbox
get-mailbox -resultsize unlimited | search-mailbox -SearchQuery “Subject:ABDCEV’” -DeleteContent

Turn Off firewall on all profiles
netsh advfirewall set allprofiles firewallpolicy allowinbound,allowoutbound

Exchange 2007 – check DB copy status.
Get-StorageGroupCopyStatus -StandbyMachine mtvmail01

Message Tracking log to csv (| Select Sender, Recipients, TimeStamp, MessageSubject)
Get-MessageTrackingLog -Server servername-ResultSize Unlimited | Where { $_.Sender -like “username*” } | Export-CSV “c:username.csv”

Put Exchange DAG cluster member to Maintainance
cd $exscripts
StartDagServerMaintenance.ps1 -server servername

Get Exchange DAG cluster member from Mainatainance

cd $exscripts
StopDagServerMaintenance.ps1 -server servername

Set Distribution group owner
Set-DistributionGroup groupname -ManagedBy “User Name” -BypassSecurityGroupManagerCheck

Access rights to all mailboxes in DB or All
Get-Mailbox | Add-MailboxPermission -User “Username” -AccessRights FullAccess -InheritanceType All
Get-MailboxDatabase –identity “DBNAME” | Add-ADPermission -User “UserName” -AccessRights GenericAll

Move Mailbox
New-MoveRequest -Identity user@mail.com -TargetDatabase DBNAME -BadItemLimit 100 -AcceptLargeDataLoss

Add permition to send as
Add-ADpermission -Identity “DatabaseName” -user “username”  -ExtendedRights Receive-as

Some times we need to use PS script to send email, script can be used in Task Scheduler or any other program

BatchFile to run script: Create *.bat file

C:WindowsSystem32WindowsPowerShellv1.0powershell.exe -PSConsoleFile "C:Program FilesMicrosoftExchange Serverbinexshell.psc1" -noexit -command ". C:scriptslocationscriptname.ps1"

PS Script to send mail: Create  .ps1 file

$filename = “c:filelocationHtmlFIleyouwant torecieve.html”
$smtpServer = “SMTP Servername”

$msg = new-object Net.Mail.MailMessage
$att = new-object Net.Mail.Attachment($filename)
$smtp = new-object Net.Mail.SmtpClient($smtpServer)

$msg.From = “sendername@domainanme”
$msg.To.Add(“recipient_address@domainanme”)
$msg.Subject = “Subject”
$msg.Body = “Body ”
$msg.Attachments.Add($att)
$smtp.Send($msg)

You can update OAB by 2 ways via EMS or using Power Shell

1 To update via  EMS

Open EMC>Organizational Configuration>Mailbox>Offline Address Book tab.

Right click on desired Address Book and press update.

2. Via Power Shell

Type: Update-OfflineAddressBook –Identity “Address List Name”

To update all Address Books type : Get-OfflineAddressBook | Update-OfflineAddressBook

Finding Disabled Users:

get-qaduser –disabled

Create a new Active Directory user:

new-QADUser -name '<User CN>' -parentContainer '<Parent DN>' -UserPassword
'<Password>' -FirstName '<User First Name>' -LastName '<User Last Name>'
-UserPrincipalName '<User UPN>'

Create multiple users in Active Directory:

$parentDN = “<ParentDN>" $strPass = “userPaswd” For ($i = 1; $i -le 1000; $i++) { $strUserName = “User” + $i New-QADUser -name $strUserName -parentContainer $parentDN -UserPassword $strPass }

Modify Attributes for several users:

$strfileServer = "\Servername"
$objOU = [ADSI] "LDAP://<OU DN>"
$objOU.psbase.Children |% {
    $uac = [int](($_.userAccountControl).ToString())
    if (($_.objectClass -eq "user") -and (($uac -band 2) -eq 0))
    {
        $_.put("homeDirectory", $strFileServer + $_.sAMAccountName)
        $_.SetInfo()
    }
}

Delete user in Active Directory

remove-QADObject -identity <User DN>

Set user profile in Active Directory

get-QADUser -identity "<User DN>" |
set-QADUser -HomeDirectory '\ServernameKatrin' -HomeDrive
'H:' -ProfilePath '\server1profilesjsmith'
-scriptpath '\dcnamenetlogonlogonscript.vbs'

Move User to other OU

move-QADObject -Identity <UserDN> -NewParentContainerName <New OU DN>

Find Locked User Accounts

Get-QADuser -locked

Unlock User Account

Unlock-QADUser -Identity <UserDN>

Retrieve Password lockout policy

Get-QADObject domainname.com | format-list Name, *password*, *lockout*

$dcname = <DomainDNSName>
$newSite = "NewSite Name"
$context = New-Object
System.DirectoryServices.ActiveDirectory.DirectoryContext(‘DirectoryServer’, $dcname)
$dc =
[System.DirectoryServices.ActiveDirectory.DomainController]::getDomainController ($context)
$dc.MoveToAnotherSite($newSite)

Where DomainDNSName – Enter your DNS domain name

$VSMgtSvc=Get-WmiObject -ComputerName localhost
-NameSpace "rootvirtualization"
-Class "MsVM_virtualSystemManagementService"
get-wmiobject -computername localhost -Namespace rootVirtualization
-query "Select * from MSVM_Computersystem where Description like
'%Virtual%' " | foreach-object {$VSMgtSvc.psbase.invokeMethod
("CreateVirtualSystemSnapshot",@($_,$Null,$null)) }

Creating a Group Using a graphical user interface

1. Open the Active Directory Users and Computers .
2. In the left pane, browse to the parent container of the new group, right-click on it, and select New Group.
3. Enter the name of the group and select the group type (global, domain local, or universal) and group type (security or distribution).
4. Click OK.

Using dsadd in command-line interface

dsadd group “<GroupDN>” -scope <GroupScope> -secgrp yes|no -desc “<GroupDesc>“

Where <GroupDN> replace with DN of the group ,

Where <GroupScope> use one of the above

• l – for domain local
• g – for global
• u – for universal

Where –secgroup

• yes if the group is a security group
• no for any other

Where desc fill group description

Using dsadd in command-line interface

> admod -b “<GroupDN>” objectClass::group groupType::
“<GroupType>” sAMAccountName::”<Pre-Windows2000Name>” -add

Example: We will create global security group called “Accounting” in Accounting OU in testdomain.com

> dsadd group "cn=Accounting,ou=Accounting,dc=testdomain,dc=com"-scope global-
secgrp yes

> admod-b "cn=Accounting,ou=Accounting,dc=testdomain,dc=com" groupType::-2147483646
sAMAccountName::"Finance Users" -add

When using AdMod, you need specify the numeric value for group type, These values are predefined in Active Directory

Universal Distribution Group Value – “8”

Universal Security Group Value – “–2147483640”

Domain Local Distribution Group Value – “4”

Domain Local Security Group Value – “–2147483644”

Global Distribution Group Value – “2”

Global Security Group Value – “–2147483646”

Create Group Using VBScript

Example bellow shows how to create a global security group.

' ------  CONFIGURATION ------
strGroupParentDN = "<GroupParentDN>" ' e.g. ou=Groups,dc=testdomain,dc=com
strGroupName     = "<GroupName>"     ' e.g. Accounting
strGroupDescr    = "<GroupDesc>"     ' e.g. Accounting group
' ------ END CONFIGURATION ---------

' Constants taken from ADS_GROUP_TYPE_ENUM
Const ADS_GROUP_TYPE_GLOBAL_GROUP       = 2
Const ADS_GROUP_TYPE_DOMAIN_LOCAL_GROUP = 4
Const ADS_GROUP_TYPE_SECURITY_ENABLED   = -2147483648
Const ADS_GROUP_TYPE_UNIVERSAL_GROUP    = 8

set objOU = GetObject("LDAP://" & strGroupParentDN)
set objGroup = objOU.Create("group","cn=" & strGroupName)
objGroup.Put "groupType", ADS_GROUP_TYPE_GLOBAL_GROUP _
                         Or ADS_GROUP_TYPE_SECURITY_ENABLED
objGroup.Put "sAMAccountName", strGroupName
objGroup.Put "description", strGroupDescr
objGroup.SetInfo

Create Group Using PowerShell

To create a group using the Quest cmdlets, use the following syntax:

Where <Parent OU DN> – Fill OU DN

Where <GroupName> – Fill Group Name

After –grouptype – set group type (Distribution or Security)

After –groupscope – set if (Universal, Domain Local)