Mengkonfigurasi Outlook anywhere di Exchange 2007 dan Outlook 2007

Cerita ini berawal dari mulai banyaknya order Microsoft Exchange 2007 dari kostumer. Al hasil, aku jadi kebagian juga deh ngoprek si Microsoft ini (padahal dah agak anti sama microsoft gara2 sering ngoprek Linux ). Yah, klo bos dah ngomong apa boleh di kata … hehehe.

Ok, langsung aja ke intinya. Untuk para pengguna setia Microsoft Outlook, dan selalu mengikuti tren dengan menggunakan versi Outlook yang up-to-date (walaupun kadang nda tau bedanya ). Mungkin akan menemukan sedikit perbedaan pada Outlook 2007 ini. Selain format email yang lebih lengkap, Outlook 2007 ini juga bisa langsung membuka applikasi Ms. Office langsung pada saat meng-”compose” atau membaca email. Eits, tapi bukan itu yang mau saya bahas. Yang akan di bahas disini adalah “Outlook anywhere” yang memudahkan customer mengkonfigurasi email client tanpa repot2 tanya ke provider email mereka.

Konfigurasi “Outlook Anywhere” di Exchange 2007

Ada tiga langkah yang harus di jalankan supaya Outlook anywhere bisa berjalan dengan baik :

1) Buat komputer client “trust” SSL certificate yang di “issued” oleh Exchange Server.

Agak males niy nulisnya, di baca aja di sini dl klo sempet saya translate ke bahasa indonesia deh

2) Install RPC Proxy component, langkahnya sebagai berikut

“Add/Remove Programs” > “Add/Remove Components” > “Network Services” > “RPC over HTTP Proxy”

3) Enable Outlook Anywhere in Exchange server

Pada “Exchange Management Console (EMC)” > “Server Configuration” > “Client Access” > Pilih “<machine name>”, pada Actions panel klik “Enable Outlook Anywhere”. Untuk “External hostname” penamaannya harus sesuai dengan “CN” dari SSL certificate yang di buat untuk “Default Web Site” di IIS.

jika menggunakan EMS, perintahnya kurang lebih seperti di bawah :

enable-OutlookAnywhere -Server ‘<Machine-name>’ -ExternalHostname ‘<external URL for Outlook anywhere>’ -ExternalAuthenticationMethod ‘Basic’ -SSLOffloading $false

Konfigurasi Outlook 2007

Supaya mudah, saya buatkan screen shoot untuk setiap langkahnya

1) Start > klik kanan pada icon “Outlook 2007″ > “Properties”2) Klik “E-mail Accounts…”3) Klik “New…”4) Pilih “Microsoft Exchange, POP3, IMAP. or HTTP”, lalu “Next”5) Isi informasi yang di butuhkan, untuk email address menyesuaikan dengan “accepted domain” yang di set pada Exhange server itu sendiri. (yang dibawah cuma sample ). Lalu “Next”.6) Langkah terakhir tinggal tunggu outlook 2007 terkoneksi dengan Exchange server.

Yups sekian dl, ngantuk niy mau bobo

Plesk disaster!!!

Another day in another week of plesk disaster! This plesk change us to a silly persons who didn’t know how all this processes running…

A lot of issues recently, force us to work very hard every weeks just to find out what goes wrong with the server. And end with conclution that plesk causing all this troubles.

Arggg… I think that management has enough patient to go through all this issues, with all customers always complaining about their email server performance, domainkey issue, or some missing emails on that Plesk.

Other thing that get me frustated with this plesk. It seems plesk make everything easier, but in fact something really bad happened. When i use Plesk Migration Manager (PMM) on expand, the website was successfully migrated, but the emails missing somewhere??? Who knows? where i can find those emails?

It is not easy to inform customer, especially when they rely everything on emails. They will get mad and crazy when they know all the emails are gone. And there is no way to recover it.

Plesk is mistery for me, only the developer can tells what is the true story about it. We can provide better services when we were use our traditional architecture before we implement this Plesk for all our customers. We can solved all issue on the servers.

It is a nightmare you know, we have to migrate a batch of domains from that problematic server to the new server only on 2 days. How many domains you think? only us know

I only can say, i have to get enough sleep and rest after that disaster happened!

^_^

Alternative script to clone VPS on OpenVZ

Silahkan di modifikasi sesuai kebutuhan pembaca

#!/bin/bash

## script name : vzclone.sh

OLDVE=$1
NEWVE=$2
vzctl stop $OLDVE
mkdir /vz/root/$NEWVE
echo “copying……”
cp /etc/vz/conf/$OLDVE.conf /etc/vz/conf/$NEWVE.conf
cp -a /vz/private/$OLDVE /vz/private/$NEWVE
echo “Starting old VPS …”
vzctl start $OLDVE;

echo -n “Start new VPS ? [Y/n] : “
read opsi

if [[ -nz $opsi ]]; then
if [ $opsi == "Y"  ]; then
vzctl start $NEWVE;

##== change hostname
CurHostname=`vzlist -a | grep $OLDVE | tr -s ‘ ‘ | cut -d” ” -f6`
tmpHostname=$CurHostname”_clone”

echo -n “New VPS Hostname ? [ "$CurHostname"_clone ] : “
read NewHostname
if [ -nz $NewHostname ]; then
vzctl set $NEWVE –hostname $NewHostname –save
else
vzctl set $NEWVE –hostname $tmpHostname –save
fi
##== chane hostname

fi
fi
NewIP=”"
echo -n “New VPS IP Address? [Empty] : “
read NewIP

CurIP=`vzlist -a | grep $OLDVE | tr -s ‘ ‘ | cut -d” ” -f5`
if [ $CurIP != '-' ]; then
vzctl set $NEWVE –ipdel $CurIP –save
fi

if [[ -nz $NewIP ]]; then
vzctl set $NEWVE –ipadd $NewIP –save
fi

echo “done.”

Cara menjalankan script:

# ./vzclone  [Old VPS ID]  [New VPS ID]

Contoh :

# ./vzclone  999 1005

Semoga bermanfaat