1. Open the GPMC.msc.
2. Create or open a GPO which will be applied to your server(s).
3. Navigate to Computer Configuration\Policies\Administrative Templates\Network\Network Connections.
4. Enable the “Do not show the “local access only” network icon” setting.
5. Close the GPO and GPMC.msc.
6. Run C:\>gpupdate on the server(s) to apply the new policy.

The “No Internet Access” notification should be disabled now.

• You have a computer that has Outlook 2003 (SP2) or 2007, Exchange 2007 Management Tools (32-bit version), PowerShell and .NET Framework installed
• Logon with an account that has Exchange Server Administrator and Local Administrator rights
• You have full access to the users’ mailbox on both servers. See the note below on how to do it.

1. Start the Exchange Management Shell and type the following:[PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Export-Mailbox –PSTFolderPath C:\PSTFiles to export all users mailbox to a PST file. Press A for Yes to All. Depending on the size of your database, the export procedure could take a long time to complete.
2. Now the mailboxes are exported to the PST files, make sure that the PST file name matches the alias of the users’ account in the other domain.
3. Next, import the PST files to the other Exchange Server by typing the following: [PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Import-Mailbox –PSTFolderPath C:\PSTFiles and press A for Yes for All. Wait until the import operation completes.

Note:
To grant the Administrator Full Access rights on the database type the following command:
[PS] C:\>Get-Mailbox -Database “<Exchange Server FQDN>\<Database Name>” | Add-ADPermission -User Administrator -AccessRights GenericAll

Follow these steps to change the text on a Windows Server 2008 (R2) machine:

1. Logon to your server with the Administrator account.
2. Start RegEdit and navigate to the following key: HKCR\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}
3. If necessary, take the ownership of this key, grant yourself full control rights and then edit the LocalizedString value.
4. In the edit window type: %UserName% on %ComputerName%. Click OK and close RegEdit.
5. Press F5 somewhere on the desktop and the text on the Computer icon should now display the logged on user name.

Tested on Windows Server 2008 R2 Build 7600.

Before you begin, don’t forget to open the default UDP 123 port (in- and outbound) on your firewall.

1. First, locate your PDC Server. Open the command prompt and type: C:\>netdom /query fsmo
2. Log in to your PDC Server and open the command prompt.
3. Stop the W32Time service: C:\>net stop w32time
4. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org”
5. Make your PDC a reliable time source for the clients. Type:C:\>w32tm /config /reliable:yes
6. Start the w32time service: C:\>net start w32time
7. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
8. Check the Event Viewer for any errors.

Tested on Windows Server 2008 R2 (Build 7600).

Key to press	Action
Windows logo key + Plus Sign or Minus Sign	Zooms in or out
Ctrl+Alt+Spacebar	Preview the desktop in full-screen mode (you have to be zoomed in first)
Ctrl+Alt+F	Switch to full-screen mode
Ctrl+Alt+L	Switch to lens mode
Ctrl+Alt+D	Switch to docked mode
Ctrl+Alt+I	Invert colors (Probably my favorite feature)
Ctrl+Alt+arrow keys	Pan in the direction of the arrow keys
Ctrl+Alt+R	Resize the lens
Windows logo key + Esc	Exit Magnifier

And then, I FORGOT to add the new Port to the so called ‘Windows Firewall with Advanced Security’ .. it was like a lighting strike in my body when I clicked ‘restart Server’

So, I used putty to open an SSH connection to the server. Easy I thought, REG ADD “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp” /t REG_DWORD /v PortNumber /d d3d /f

noooo, Access Denied .. ok, UAC is enabled .. tried to figure out if there’s a way to elevate the prompt .. but didn’t find a route/solution .. so I decided to reboot the server in Windows Recovery Mode, started regedit.exe and used load hive to load the SYSTEM Hive (found under C:\Windows\System32\Config). entered a name for the temporary hive, changed the PortNumber (always use CurrentControlSet1 – it’s the last successful config) and unloaded the hive.. then I remembered that I read an article about editing the registry ‘offline’ using reg.exe .. just to verify if the changed values have really been written in the SYSTEM Registry I used:

reg load HKLM\Win_SYSTEM C:\windows\system32\config\system
reg query "HKLM\Win_SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp"
reg unload HKLM\Win_SYSTEM

and see what I got:

another option is to disable the Firewall completely using this bat/cmd file:

@echo off
:start
echo ****************************************************************
echo *                                                              *
echo *             1 : Disable Windows firewall on server           *
echo *                                                              *
echo *             2 : Enable Windows firewall on server            *
echo *                                                              *
echo ****************************************************************
 set /p choice= choose What to do:
 if not %choice%=='' set choice=%choice:~0,1%

 if %choice%==1 goto Menu1

 if %choice%==2 goto Menu2

 echo %choice% WRONG option, choose 1 or 2
 goto start

 :Menu1
reg load HKLM\Win_SYSTEM C:\windows\system32\config\system
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile" /v "EnableFirewall" /t REG_DWORD /d "0" /f
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile" /v "EnableFirewall" /t REG_DWORD /d "0" /f
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile" /v "EnableFirewall" /t REG_DWORD /d "0" /f
reg unload HKLM\Win_SYSTEM
@echo on
@echo Firewall Disabled !
@echo off
goto end

 :Menu2

reg load HKLM\Win_SYSTEM C:\windows\system32\config\system
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile" /v "EnableFirewall" /t REG_DWORD /d "1" /f
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile" /v "EnableFirewall" /t REG_DWORD /d "1" /f
reg.exe add "HKEY_LOCAL_MACHINE\Win_SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile" /v "EnableFirewall" /t REG_DWORD /d "1" /f
reg unload HKLM\Win_SYSTEM
@echo on
@echo Firewall Enabled !
@echo off
goto end

:end
pause

maybe this is of help for someone..

Windows command line:

C:\> tasklist /FI "modules eq vstoee.dll"

PowerShell

PS C:\> Get-Process | ? { $_.Modules -like "*(vstoee.dll)*" }

Here is a PowerShell script to read the Last Write Time for a registry key.

Usage:

Get-RegKeyLastWriteTime.ps1 <Key> <SubKey>

Example:

Get-RegKeyLastWriteTime.ps1 HKLM SOFTWARE\Microsoft\Windows\CurrentVersion

Output:

Key                         LastWriteTime
—-                         ——————-
AdminDebug                  10/28/2009 7:50:51 PM
App Management              7/14/2009 4:41:12 AM
App Paths                   1/22/2010 2:07:18 PM
Applets                     7/14/2009 4:41:12 AM
Audio                       7/14/2009 4:41:12 AM
Authentication              7/14/2009 4:41:12 AM
BitLocker                   7/14/2009 4:41:12 AM
...

Get-RegKeyLastWriteTime.ps1 Script:

param (	[string] $Key, [string] $SubKey )

switch ($Key) {
    "HKCR" { $searchKey = 0x80000000} #HK Classes Root
    "HKCU" { $searchKey = 0x80000001} #HK Current User
    "HKLM" { $searchKey = 0x80000002} #HK Local Machine
    "HKU"  { $searchKey = 0x80000003} #HK Users
    "HKCC" { $searchKey = 0x80000005} #HK Current Config
    default {
        #throw "Invalid Key. Use one of the following options HKCR, HKCU, HKLM, HKU, HKCC"
    }
}

$KEYQUERYVALUE = 0x1
$KEYREAD = 0x19
$KEYALLACCESS = 0x3F

$sig1 = @'
[DllImport("advapi32.dll", CharSet = CharSet.Auto)]
  public static extern int RegOpenKeyEx(
    int hKey,
    string subKey,
    int ulOptions,
    int samDesired,
    out int hkResult);
'@
$type1 = Add-Type -MemberDefinition $sig1 -Name Win32Utils `
    -Namespace RegOpenKeyEx -Using System.Text -PassThru

$sig2 = @'
[DllImport("advapi32.dll", EntryPoint = "RegEnumKeyEx")]
extern public static int RegEnumKeyEx(
    int hkey,
    int index,
    StringBuilder lpName,
    ref int lpcbName,
    int reserved,
    int lpClass,
    int lpcbClass,
    out long lpftLastWriteTime);
'@
$type2 = Add-Type -MemberDefinition $sig2 -Name Win32Utils `
    -Namespace RegEnumKeyEx -Using System.Text -PassThru

$sig3 = @'
[DllImport("advapi32.dll", SetLastError=true)]
public static extern int RegCloseKey(
    int hKey);
'@
$type3 = Add-Type -MemberDefinition $sig3 -Name Win32Utils `
    -Namespace RegCloseKey -Using System.Text -PassThru

$hKey = new-object int
$result = $type1::RegOpenKeyEx($searchKey, $SubKey, 0, $KEYREAD, [ref] $hKey)

#initialize variables
$builder = New-Object System.Text.StringBuilder 1024
$index = 0
$length = [int] 1024
$time = New-Object Long

#234 means more info, 0 means success. Either way, keep reading
while ( 0,234 -contains $type2::RegEnumKeyEx($hKey, $index++, `
    $builder, [ref] $length, $null, $null, $null, [ref] $time) )
{
    #create output object
    $o = "" | Select Key, LastWriteTime
    $o.Key = $builder.ToString()
    $o.LastWriteTime = (Get-Date $time).AddYears(1600)
    $o

    #reinitialize for next time through the loop
    $length = [int] 1024
    $builder = New-Object System.Text.StringBuilder 1024
}

$result = $type3::RegCloseKey($hKey);

Just open up a cmd.exe and change the ip range..

C:\>FOR /L %x in (1,1,255) do ping -n 1 192.168.2.%x | find /I "reply" >> c:\temp\pingresult.txt

The above command uses a FOR loop to ping each device and looks for "Reply" in the output. If there is a "Reply" then the host is up.. Results will be written to C:\temp\pingresults.txt

Or the PowerShell version:

C:\> 1..255 | foreach-object { (new-object System.Net.Networkinformation.Ping).Send("192.168.2.$_") } | where-object {$_.Status -eq "success"} | select Address

Address
——-
192.168.2.1
192.168.2.5
192.168.2.10
192.168.2.11
192.168.2.12

At first glance the results are very similar and you would think, "Why all the extra typing? The second command is 2.5 times longer!" The big difference between the standard windows command line and powershell is that the latter uses objects, which gives a lot of power…in our shell. Not let’s see how it works…

In the above command the range operator (..) generates a list of the numbers 1 through 255. The cool thing is you don’t have to use just a single range, you can string them together like this (1..5),7,(9..10) which would give you the numbers 1-10 skipping 6 and 8.

foreach-object { (new-object System.Net.Networkinformation.Ping).Send("10.10.10.$_") }

The foreach-object takes the numbers fed into the pipeline and operates on them one at a time. First, it creates a new ping object and then calls the send method. The parameter given to the send method is a string concatenation of 10.10.10. and the number from $_, which is the "current pipeline object." The $_ variable in our example will contain the numbers 1-255.

where-object {$_.Status -eq "success"}

The output of the send method is the PingReply object which contains a status. We can filter the results only successful pings reply objects will be sent further down the pipeline.

Select Address
Finally, all we care about is the address so that is the only piece we have displayed.

Now that we know how it works, let’s pimp out our powershell version.

First, we don’t have to just use a contiguous set of numbers. If we wanted to scan all ip address before 10.10.10.100, after 10.10.10.200 and 10.10.10.155 we could use this:
(1..99),(200..255),155 | foreach-object ….
We can use the results to feed into other commands. You can ping sweep an entire subnet and have it automatically do an nslookup, attempt to list the contents of the c$ share, and tell you that you are doing a good job (a little positive reinforcement never hurts).

PS C:\>1..255 | foreach-object { (new-object System.Net.Networkinformation.Ping).Send("10.10.10.$_") } | where-object {$_.Status -eq "success"} | foreach-object { nslookup $_; gci "\\$($_.Address)\c$"; echo "Good Job" }

The ping sweep can be sped up by setting a timeout value (in milliseconds). In the example below we set the timeout value to 100ms.

… (new-object System.Net.Networkinformation.Ping).Send("10.10.10.$_", 100) …