How to mount /system folder for write access

$ adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

when you finish whatever you need to do just run this

# mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system

VPNC on adnroid

1. Download latest version of VPNC from here
2. Find the tun.ko file for you kernel version (this is for the version 2.6.32.21-gd2764ed) Link and copy it on the sdcard.
3. Download vpn-script from here and copy it on the sdcard
4. Go to the market and download VPNC Widget
5. Open the terminal and type:
insmod /mnt/sdcard/tun.ko
(If you get any error means that the file is not for your kernel version)
6. Open VPNC and create new vpn connection.
7. Open VPNC Widget and set the preferences as needed.
8. Open the terminal and type:
cp vpnc-script /data/data/com.gmail.mjm4456.vpncwidget/files/
9. Tap on the screen, go to the Widgets and add VPNC Widget.

That's it...

How to root HTC Desire Z

1. Get theses 3 files:
https://github.com/tmzt/g2root-kmod/raw/scotty2/scotty2/psneuter/psneuter (right click > save as...)
http://www.multiupload.com/A9PNGVBWBE
http://www.multiupload.com/9L618DJVR6

2. Extract misc_version_01.zip (only misc_version is needed)
3. Get the PC10IMG.zip from here or download the full RUU from here. If you already downloaded the 1.34 RUU somewhere else you can skip this step.
4.

adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb  shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter adb shell

5. Check if you have the '#' sign instead of the '$' If you see the '#' sign you got root!


6.

/data/local/tmp/misc_version -s 1.33.405.5 exit

7. If you have downloaded the 1.34.405.5_PC10IMG.zip copy it to you SD-Card and rename it to PC10IMG.zip.

If you downloaded the full RUU or had it already execute the exe file (mine is called RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe), start explorer and type %temp% in the adress bar.
Look in all the folders starting with a { sign and also in the sub directories if it also starts with a { sign, in one of the subdirectories there should be a rom.zip file with 298.442.206 bytes and the MD5 sum 2ff42897cd27e0db425a2cf36c8bd078.
Copy this rom.zip to your SD-Card on the phone and rename it to PC10IMG.zip


8.

adb reboot bootloader

(or turn your phone of and on again while holding the trackbad).

9. Select bootloader (vol +/- buttons for navigation and power button for select).

10. Enable USB-Debugging on your phone

11. Extract root.zip

12.

adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/

13. Start the Terminal app on your phone and type:

/data/local/tmp/rage

14. Wait until you see the message "Forked #### childs.", reset Terminal (menu > Reset Term). The Terminal app will close, launch it again. It will force close, launch it again.
You should see the magic '#' sign again.


15. Type in the terminal

/data/local/tmp/gfree -f

16. Last step in terminal app on your phone is to execute these commands.

/data/local/tmp/root sync

Migrate from Mdaemon to Exchange

Configure Exchange 2010 to Route Messages for a Shared Address Space

Applies to: Exchange Server 2010 SP1

Topic Last Modified: 2009-09-30

An organization may have to share the same SMTP address space between two or more different e-mail systems. For example, you may have to share the SMTP address space between Exchange and a third-party e-mail system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each e-mail system have the same domain suffix as part of their e-mail addresses.

You can use the EMC or the Shell to configure a Microsoft Exchange Server 2010 Hub Transport server to route messages for a shared address space.

Looking for other management tasks related to managing message routing? Check out Managing Message Routing.

Step 1: Create an internal relay domain

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Accepted domains" entry in the Transport Permissions topic.

To support routing messages for a shared address space, you must create an accepted domain that's configured as an internal relay domain. When you configure an accepted domain as an internal relay domain, Exchange first tries to deliver to a recipient in the Exchange organization. If the recipient isn't found, the message is routed to the Send connector that has the closest address space match.

Use the EMC to create an internal relay domain

1. In the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Accepted Domains tab.
   
2. In the action pane, click New Accepted Domain. The New Accepted Domain wizard appears.
   
3. On the New Accepted Domain page, complete the following fields:
   
   • Name Use this field to identify the accepted domain in the user interface. You can type any name that you want. We recommend that you select a meaningful name that helps you easily identify the purpose of this accepted domain. For example, you may want to use a name that identifies this as a subsidiary domain or as a hosted domain. You must use a unique name for each accepted domain.
     
   • Accepted Domain Use this field to identify the SMTP namespace for which the Exchange organization will accept e-mail messages. You can use a wildcard character to accept messages for a domain and all its subdomains. For example, you can type *.contoso.com to set Contoso.com and all its subdomains as accepted domains.
     
4. After you complete these fields on the New Accepted Domain page, select the following option: Internal Relay Domain.
   
5. Click New.
   
6. On the Completion page, click Finish.
   

Use the Shell to create an internal relay domain

This example creates the internal relay domain Contoso for the SMTP domain contoso.com.

New-AcceptedDomain -Name "Contoso" -DomainName contoso.com -DomainType InternalRelay

For detailed syntax and parameter information, see New-AcceptedDomain.

Step 2: Create a Send connector to route e-mail to the shared domain

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Send connectors" entry in the Transport Permissions topic.

You must also add a Send connector that's sourced on a Hub Transport server and configured to send e-mail to the shared address space.

Caution:
To achieve the correct routing behavior, you must specify a Hub Transport server as the source server for the Send connector. If the Edge Transport server is specified as the source server for the Send connector, a routing loop will occur.

Use the EMC to create a Send connector to route e-mail to the shared domain

1. In the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Send Connectors tab.
   
2. In the action pane, click New Send Connector. The New Send Connector wizard starts.
   
3. On the Introduction page, follow these steps:
   
   • In the Name field, type a meaningful name for this connector. This name is used to identify the connector.
     
   • In the Select the intended use for this connector field, select one of the following usage types for the connector. The usage type determines the default permission sets that are assigned on the connector and grants those permissions to trusted security principals:
     • Internal Select this usage type if the e-mail system with which Exchange 2010 shares an address space is another Exchange 2010 organization.
     • Internet Select this usage type if the e-mail system with which Exchange 2010 shares an address space is a third-party e-mail system.
     
4. Click Next.
   
5. On the Address space page, click Add. In the SMTP Address Space dialog box, enter the domain name to which this connector will send mail, for example, contoso.com or *.contoso.com. You may select the Include all subdomains check box to use this connector to send e-mail to all subdomains of the address space. If necessary, you can also provide a specific cost for this connector. When you're finished, click OK. Leave the Scoped send connector check box cleared, and then click Next.
   
6. On the Network settings page, select Route mail through the following smart hosts. Click Add.
   
7. In the Add Smart Host dialog box, select IP Address or Fully qualified domain name (FQDN) to specify how to locate the smart host. If you select IP Address, enter the IP address of the smart host. If you select Fully qualified domain name (FQDN), enter the FQDN of the smart host. The sending server must be able to resolve the FQDN. When you're finished, click OK. To add more smart hosts, click Add, and repeat this step. If you want to use a specific list of external DNS servers instead of the DNS servers specified in the adapter settings, select the Use the External DNS Lookup settings on the transport server check box. When you're finished, click Next.
   
8. On the Configure smart host authentication settings page, select the method that's used to authenticate to the smart host. The following smart host authentication methods are available:
   
   • None
     
   • Basic Authentication
     
   • Basic Authentication over TLS
     
   • Exchange Server Authentication
     
   • Externally Secured (for example, with IPsec)
     
9. Click Next.
   
10. On the Source Server page, click Add to add a source server. By default, the Hub Transport server that you're currently working on is listed as a source server. In the Select Hub Transport or Subscribed Edge Transport dialog box, select the Hub Transport servers that will be used as the source server for sending messages to the shared address space. When you finish adding source servers, click OK. Click Next.
    
11. On the New Connector page, review the configuration summary for the connector. If you want to modify the settings, click Back. To create the Send connector by using the settings in the configuration summary, click New.
    
12. On the Completion page, click Finish.
    

Use the Shell to create a Send connector to route e-mail to the shared domain

This example creates a Send connector with the following settings:

• Configures the connector as an Internet usage type
  
• Assigns the address space contoso.com
  
• Routes messages to the smart host smarthost.contoso.com
  
• Uses the Externally Secured authentication mechanism
  
• Sets the maximum message size to 20 megabytes (MB)

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


Set exchange MX record as a higher priority then Mdaemon.

Disable Recipient Filtering on the edge server.

Set unknown email to deliver to the edge server on Mdaemon server

-------------------------------------------------------------------------------------

New-ExchangeCertificate -FriendlyName "SelfSigned Cert" -SubjectName "cn=mail.domain.com.au" -DomainName SERVERNAME, SERVERNAME.DOMAIN.local, mail.domain.com.au,autodiscover.domain.com.au -PrivateKeyExportable $True

Extend partition in windows 2003/xp

cmd
diskpart
list volume
select volume
extend
exit

Microsoft Lync Server installation Step-By-Step

http://imaucblog.com/archive/2010/09/15/step-by-step-microsoft-lync-2010-consolidated-standard-server-install-guide/

How To Export SSL Certificate from Linux to Windows IIS

How To: Export SSL Certificate from Linux to Windows IIS

I just had to figure this out by myself because the title of this thread returned no relevant results in Google. This

is the quick and dirty. Hope you can follow along.

Step 1: pem file
You will need to log into your linux box and create a .pem file that contains your private key and your certificate

hash. Your private key is usually in a .key file and your certificate is usually in a .crt file. Just paste the

content of your key and certificate files into the same file (in that order, separated by a line break) and save it as

"whatever.pem".

Step 2: p12 file
The p12 file is what IIS wants. To create it, use the following command in linux:

openssl pkcs12 -export -in whatever.pem -out whatever.p12 -name "Whatever Certificate"

You'll be asked to provide a password for the file. Remember it for the next step. After you've done this, transfer

whatever.p12 to your windows server (FTP, anyone?).

Step 3: Import the p12 file in IIS
Go to the properties of your website in IIS, then into the Directory Security tab. Click on "Server Certificate" and

select the "Import" option. When it asks you to find the file, make sure to change the scope to "All files" to find

the p12. When you select the file, you'll be asked to enter the password you selected in step 2. Et voila!

Successfully transferred SSL Certificate from Linux to Windows.

Don't forget to install a valid CA Root Certificate while you're at it. You can actually find a tutorial for that

online though.