After yet another delayed flight, this time from Ho Chi Minh City to Bangkok, we eventually made it to Chaing Mai without having to reschedule any flights. The 5hr break between flights that we put in came in handy! Also managed to squeeze in my first meal in Thailand – Pad Thai at Bangkok Airport.
Eventually reached the Holiday Inn in Chaing Mai (this is one very nice hotel!). Crashed in the hotel for a bit before heading out to the Night Markets. Many things on sale here, mostly low quality goods and souvenirs. The other thing you can do here is book a tour from the many stalls. We did exactly this, and booked an Elephant Ride for the next day before returning home.
Woke up nice and early for the journey back to Ho Chi Minh. It is a very long drive (8hrs) with rest stops, covering only 400km. This is mainly due to traffic and road conditions. You get use to the constant darting around on the road while trying to get around slower cars and avoiding oncoming traffic.
By the time we got there, we checked into our hotel and went to a very classy/westernised restaurant. The food and atmosphere was great (address details in pic)! Highly recommended.
Spent most of the day on a private beach (pay to enter). This beach was beautiful and rivaled the beaches of Australia. It was untouched to the point that you see little crabs running around digging holes on the beach and burrowing. I’d recommend anyone travelling to Nha Trang to check out this beach. You may need to be part of a tour to access it, as it’s location is quite isoloated.
On the way home we saw a truck rollover. No surprise considering how they drive on these roads…
Our last stop for the day was to see the old relics of the native tribes that used to live in Nha Trang. These buildings had great structure and shape and well worth a visit.
What an interesting day this turned out to be.
The day started off at Monkey Island, a place where scientists kept monkeys for research. This is now a thing of the past, and the island is now a resthaven for monkeys and tourists. Caught a cruise over to Monkey Island from Nha Trang, and had the opportunity to feed the monkeys and lie on the beach.
At this point I got attacked by a killer monkey (joking)! I ended up getting bitten by a monkey while trying to save my possessions from being raided by a monkey, and he retaliated and bit me on the arm. The locals fixed me up on the spot and reassured me that the monkeys here do not carry viruses or infectious diseases. I watched a monkey circus where monkeys were trained to perform tricks. This was very ammusing to watch!
The beach here on the island is nothing special. The Australian beaches are much cleaner and nicer. There is soft sand leading up to the beaches back at home, rather than coarse pebbles and stones.
Last event for the day was to get a mud bath and sit in a hot spring. The mud bath felt great, but the mud is extremely hard to wash off your swimwear afterwards! This is something you must try in Nha Trang. The location is tucked away, so you may need a guide.
Got picked up from my hotel in Ho Chi Minh City to be driven to Nha Trang.
Had breakfast at a place overlooking the river before hitting the road. The road to Nha Trang was only about 400 kms but it took over 8 hours to travel. There were stops, but it was mainly due to the crowded roads and the condition of the road. You’ll be lucky to hit 80km/hr, and it’s more typical to be coasting along at 60km/hr.
Had lunch at a beautiful resort. We sat literally meteres from the ocean. Pictures and resort name are below for those interested.
Once we arrived, we checked into the hotel and had dinner later on that evening. That was it for the day, the majority spent on the road.
Arrived in Ho Chi Minh City after a stop over in Bangkok overnight (and after a 4hr delayed flight out of Australia). Stayed in the Novotel Airport hotel in Bangkok, which was decked out beautifully. Ashame that it was only a stop over.
First impressions of Vietnam after landing at the airport was that everything was very very quiet. I later found out that family/friends were not allowed into the airport for pickup. They needed to wait outside behind a fence. The atmosphere inside the airport felt lifeless.
It was quite a cultural shock once we hit the roads of Vietnam. Soooo many motorbikes, and everyone ignores all the road rules. Everyone is darting around everywhere, and most traffic signals are ignored. The weather was also extremely hot and humid (37C that day).
I ended up making my way to the market which was in District 1. I also stayed at a hotel in District 1. Many things are cheap at the market, but as a travelling foreigner you get earmarked for sales. You will notice a lot of people trying to sell you practically anything. They will probably tug your shirt if you get close enough to them!
After getting dinner at a restaurant in District 5 (suckling pig is cheap!), we called it a night.
This will generally occur if you need to install a printer driver that is not approved by Microsoft.
You will find it either fails or asks for the administrator username and password.
There are various Group Policy Adjustments that need to be made.
On Windows XP, follow this article -> http://support.microsoft.com/kb/888046
On Windows 7, you need to disable this GPO (same policy as that for XP in the article above, but different location):
Computer Configuration/Policies/Admin Templates/Printers/Point and Print Restrictions
Make sure you apply Computer Configuration Policies to OU’s with Computers, and User Configuration Policies to OU’s with Users in it (or lump them both into one policy and appy them to both Computer and User OU’s). Then everything should work find once the policy refreshes on the PC.
Now I know there are articles out there, but I wanted to write one that had enough detail for anyone attempting this to follow, but with as few steps as possible.
Obviously make sure you Exchange 2003 server is working well before moving to 2010.
- Check Default SMTP Virtual Server to ensure you do not have any smarthosts in there on the Exchange 2003 server (Under First Administrative Group – Servers – Servername – Protocols – SMTP). This will prevent mailflow between 2003 and 2010 servers.
- Install Exchange 2010 on the new server (I’m assuming single server here – not recommended by Microsoft). Plenty of articles on how to do this.
- Disable Linkstate on Exchange 2003 and reboot (or restart Exchange 2003 services) (Command Prompt to x:ExchSvrBin and type Regsvr32 -u xlsasink.dll)
- Move/create a mailbox onto the 2010 server. Connect Outlook or log into webmail on that server to conduct some tests. Test the following: Email flow between 2003 and 2010 mailboxes (both directions) and email flow from 2003 -> external and 2010 -> external
- If there are issues with mailflow between 2003 and 2010 delete and recreate the connectors. The connectors are setup automatically when you installed Exchange 2010.
- Replicate Public Folders and other instructions as per article (do everything but decommision the Exchange 2003 server): http://support.microsoft.com/default.aspx?kbid=822931
Do not change Replication Schedule or Replication Priority when replicating the Public Folders. You could end up bogging down the connectors with excess traffic and grinding the Exchange servers to a halt.
- Move mailboxes. You will have to do this with the Exchange 2010 ESM (not the 2003).
- For seamless transition with Outlook 2003 clients, you need to disable the requirement for encrypted connection.
Run this in the Exchange Powershell on the 2010 server:
Set-RpcClientAccess –Server <servername> –EncryptionRequired $False
Otherwise in Outlook 2003, you will need to choose the Encrypt Connection between Outlook and Exchange server option. This is not hard, however in migration scenerios, it will prevent seamless handover between legacy Exchange 2003 servers and Exchange 2010 servers when you are moving mailboxes.
- I would leave the Exchange 2003 server running for 2 weeks before removing to ensure there is a automatic handoff to the new Exchange 2010 servers when users connect in with Outlook for the first time. Otherwise you will be running around reconfiguring Outlook to point to the new 2010 server
- Rehome Receipient Update Services. Use the Exchange 2003 System Manager to do so. Point it to the other Exchange Server, and the correct Domain Controller.
- Remove Exchange 2003 server as per article above from Microsoft.
- It’s not unusual that during a process/migration like this to have errors with the Offline Address Book to Global Address List. If you are getting such errors during Sending/Receiving in Outlook, you may have to rebuild/recreate the Offline Address Book after all the above steps have been completed. Symptoms of a faulty OAB/GAL are that newly created users do not appear. A temporary workaround is to get your users to type in their full email address for the time being.
Are you using the administrator account to test with activesync? You shouldn’t be!
If you are getting these messages in Event Log: User “domainnameadministrator” cannot synchronize their mobile phone with their mailbox because Exchange ActiveSync has been disabled for this user.
And on your Windows Mobile phone have error code 0x85010004
It’s probably because you’re trying to use the administrator account to test with! This is not supported under Exchange 2007/2010 as the administrator does not inherit permissions in AD which makes it hard to give it activesync rights. Use a user’s account instead!
If this is not the case, then try one of two things (I found this normally happens when migrating from 2003 -> 2007/2010 – never seen it with a fresh install)
- Remove and recreate ActiveSync Directory (use Exchange Powershell)
Remove-ActiveSyncVirtualDirectory -Identity “Microsoft-Server-ActiveSync (Default Web Site)”New-ActiveSyncVirtualDirectory -Server “xxx” -WebSiteName “Default Web Site” -ExternalURL “http://www.xxx.com/Microsoft-Server-ActiveSync”
or for a single server deployment
New-ActiveSyncVirtualDirectory -WebSiteName “Default Web Site” -ExternalURL “http://www.xxx.com/Microsoft-Server-ActiveSync“
- Use the powershell to give the user ActiveSync rights
Set-CASMailbox -Identity <username> -ActiveSyncEnabled $true
Also, more specifically for error 85010014
Make sure you check that the user does Inherit permissions from the parent. Load up ADU&C – Make Sure View -> Advanced Options is ticked – Find User – Properties – Security – Advanced – Tick Allow Inheritable Permissions from the Parent… Ok all the way back out.
Other than that, make sure you check the obvious. Are you using SSL on both the Exchange and device side, or are you turning it off? It must match up.