Exchange 2007, increasing e-mail rule limit

Exchange 2007 rule sizes by default is set to 64kb (rather than 32kb for Exchange 2003).
You may change this using Exchange 2007 Management Shell (PowerShell) to max 256kb

To check setting on specific account: (to display RulesQuota : xxKB)
get-mailbox userlogin | fl rulesquota



To change setting to 256kb for specific account:
set-mailbox userlogin -rulesquota 256kb



To change setting to 256kb for all account:
get-mailbox | set-mailbox -rulesquota 256kb

VPN to remote network on same subnet as local network

Symptoms: 
You need to connect using VPN connection to remote client site and realize that you both using same IP subnet. You connect fine but can't access any resources on the remote subnet. Some people may suggest you to change one of the subnet, but you can't do that because both of subnet are office environment.


Cause:
It's network and route thing. Your PC think the remote IP is locally.


Solution:
You need to manually add routing for remote IP at your PC. You can do that using command ROUTE.
1. Connect to VPN site.


2. From command prompt run ROUTE PRINT to show status. In my case:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 09 26 33 75 ...... VIA Rhine II Fast Ethernet Adapter - Packet Scheduler Miniport
0x60004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0       10.10.10.1      10.10.10.9  21
          0.0.0.0          0.0.0.0      10.10.10.79     10.10.10.79  1
        10.10.8.0    255.255.252.0       10.10.10.9      10.10.10.9  20
       10.10.10.9  255.255.255.255        127.0.0.1       127.0.0.1  20
      10.10.10.79  255.255.255.255        127.0.0.1       127.0.0.1  50
   10.255.255.255  255.255.255.255       10.10.10.9      10.10.10.9  20
   10.255.255.255  255.255.255.255      10.10.10.79     10.10.10.79  50
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1  1
  2xx.2xx.2xx.2xx  255.255.255.255       10.10.10.1      10.10.10.9  20
        224.0.0.0        240.0.0.0       10.10.10.9      10.10.10.9  20
        224.0.0.0        240.0.0.0      10.10.10.79     10.10.10.79  1
  255.255.255.255  255.255.255.255       10.10.10.9      10.10.10.9  1
  255.255.255.255  255.255.255.255      10.10.10.79     10.10.10.79  1
Default Gateway:       10.10.10.79
===========================================================================
Persistent Routes:
  None

3. From here, we get information:

   - 10.10.10.9      my current IP

   - 10.10.10.79     my assigned VPN IP

   - 0x60004               my VPN interface

   - 2xx.2xx.2xx.2xx  I need to hide my client public IP

4. To manually add route run:

ROUTE ADD <TargetIP> MASK <Mask> <GatewayIP> METRIC <Metric> IF <InterfaceID>

so for my case if I want to add route to single IP 10.10.10.18 on remote site:

ROUTE ADD 10.10.10.18 MASK 255.255.255.255 10.10.10.79 METRIC 1 IF 0x6004

5. Run ROUTE PRINT again to make sure the new route listed

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 11 09 26 33 75 ...... VIA Rhine II Fast Ethernet Adapter - Packet Scheduler Miniport

0x60004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

===========================================================================

===========================================================================

Active Routes:

Network Destination        Netmask          Gateway       Interface  Metric

          0.0.0.0          0.0.0.0       10.10.10.1      10.10.10.9  21

          0.0.0.0          0.0.0.0      10.10.10.79     10.10.10.79  1

        10.10.8.0    255.255.252.0       10.10.10.9      10.10.10.9  20

       10.10.10.9  255.255.255.255        127.0.0.1       127.0.0.1  20

      10.10.10.18  255.255.255.255      10.10.10.79     10.10.10.79  1

      10.10.10.79  255.255.255.255        127.0.0.1       127.0.0.1  50

   10.255.255.255  255.255.255.255       10.10.10.9      10.10.10.9  20

   10.255.255.255  255.255.255.255      10.10.10.79     10.10.10.79  50

        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1  1

  2xx.2xx.2xx.2xx  255.255.255.255       10.10.10.1      10.10.10.9  20

        224.0.0.0        240.0.0.0       10.10.10.9      10.10.10.9  20

        224.0.0.0        240.0.0.0      10.10.10.79     10.10.10.79  1

  255.255.255.255  255.255.255.255       10.10.10.9      10.10.10.9  1

  255.255.255.255  255.255.255.255      10.10.10.79     10.10.10.79  1

Default Gateway:       10.10.10.79

===========================================================================

Persistent Routes:

  None

Or You can use Portable GUI Application NetRouteView from nirsoft.net to show and manipulating your windows routing table.

Find Old Network Card not show under Device Manager

Symptoms: 

Popup error while setting IP

The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

But cannot find this old hidden device to remove even you already enabled show hidden device in Device Manager

Cause:

Show hidden devices option in the Device Manager (View > Show hidden devices) does not always show the old NIC (ghosted adapter) to which that IP Address is assigned.

Solution:

From cmd prompt:

    set devmgr_show_nonpresent_devices=1

After that make sure in Device Manager:

    View > Show Hidden Device        Checked

Should show dimmed network adapter under network manager group.

Note:

For Some old OS, you may doing by add System Variable:

- In the System variables section, click New.

- Set the Variable name to devmgr_show_nonpresent_devices and set the Variable value to 1 to enable the parameter

FTP command line problem from Windows Server 2008 R2

Symptoms: 

Using FTP.exe server command prompt will allow you to connect out to an FTP site, but no response from ls or get commands

Cause: 

Windows Server 2008 R2 has a strict firewall by default

Solution:

1. Go to: Administrative Tools > Server Manager > Configuration > Windows Firewall with Advanced Security

2. Right click on Windows Firewall with Advanced Security on Local Computer to pop-up Windows Firewall Properties

3. On the Domain Profile tab, settings, click customize

4. Change Display a notification to yes

5. Click ok twice for changes to take effect

For now, at first you run ftp.exe and login, Windows security Alert will pop-up. You check Domain Networks and click Allow Access

Opening Port for FTP and SQL

FTP: 21
sometimes need to open incoming port 20

SQL: 1433

SYSVOL and NETLOGON location

SYSVOL and NETLOGON are the shared from \\DOMAIN.NAME


Share name     SYSVOL
Path              C:\WINDOWS\sysvol\sysvol
Remark            Logon server share
Maximum users     No limit
Users
Caching           Manual caching of documents
Permission        Everyone, READ
                  BUILTIN\Administrators, FULL
                  BUILTIN\Authenticated Users, FULL


Share name        NETLOGON
Path              C:\WINDOWS\sysvol\sysvol\DOMAIN.NAME\SCRIPTS
Remark            Logon server share
Maximum users     No limit
Users
Caching           Manual caching of documents
Permission        Everyone, READ
                  BUILTIN\Administrators, FULL

fSMORoleOwner location on ADSIedit

- Domain []
   -- DC (properties)

- Domain []
   -- DC
       --- CN=Infrastructure (properties)

- Schema []
   -- CN=Schema (properties)

- Configuration []
   -- CN=Partitions (properties)

Ncomputing over windows 2003 server problem and solution

Symptom

Error “Server yet not ready, try again a bit later” an error where the hpvcard.dll failed to initialize.

Solution 1

Add the following key to the host:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
“SessionImageSize”=dword:00000020

Solution 2

Remove Security Update KB956572 also remove update KB958690

Symptom

Error "to log on to this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Remote Desktop Users group have this right. If you are not a memeber of the Remote Desktop Users group or another group that has this right , or if the Remote Desktop Users group doesn not have this right, you must be granted this right manually"

Solution 1 

Add user to Remote Desktop User Group

Solution 2 

Configure the security setting in Default Domain Controller Policy GPO:

1.    Run gpmc.msc  to open the Group Policy Management console.
2.    Expand  Domain Controllers, right-click Default Domain Controller Policy, and click Edit.
3.    In the Group Policy Management Editor window, expand Computer Configuration\Windows Settings\Security Settings\Local Policies\User Right Assignment\Allow log on locally
4.    Add User or Group and click OK three times to apply the settings.
5.    Run gpupdate /force to apply the policy.