Windows 8 doesn’t mean anything to the Virtual Desktop Strategy

Posted on September 8th, 2012 in Announcement, Industry News, Operating Systems, Virtual Desktop Infrastructure, Virtualization | No Comments »

I had been over excited by the public news been covered on Windows 8 official release. Of course, my buddies who are die hard fans to Microsoft had convinced myself to take a try on windows 8. My new DELL inspiron just arrive yesterday and I immediately loaded the windows 8 enterprise edition to the machine.

I would like to share some of the finding from my 1 day experience on windows 8.

Microsoft disable the start button on desktop is a major disastor. For task workers and power users, I will say the startup button with application shortcut is a MUST. The fancy new generation start button are too much into the tablet world and multi touch devices.

Read more »

Database requirement in Citrix Xendesktop

Posted on October 13th, 2011 in Tips, Virtual Desktop Infrastructure, Xen, Xen Desktop | No Comments »

I had gone through few days of hands on training for Citrix Xendesktop. The experience of the training is good and it went through technical deep dive. 1 of the key thing we discussed during the training was about the databases requirements to support the Xendesktop and Xenapp infrastructure. Microsoft SQL will be 1 of the key component, and you will require to plan for the high availability architecture to support the production environment.

The best approach may just consider to build an independent Active/Passive or Active/Active SQL cluster to support the infrastructure. A backup for the SQL is always recommended to create recovery point in the event of data corruption. Most data on the SQL databases is the configuration changes, log and etc. Similar to VMWare vCenter Database.

Read more »

Microsoft 2008 Cluster Bugs

Posted on August 17th, 2011 in Operating Systems, Server, Tips | No Comments »

Went through a marathon troubleshooting with my client for the past 1 week to figure out the reason why a cluster failed in place and it could not easily rebuild back after 1 of the node evicted. We had gone through the process to re image both nodes and rebuild from scratch. Follow exactly the best practices and run through the cluster validation without any error. While we try to form the cluster, the system keep provide an unknown error which do not share much information from log. It just keep telling you that the node is not reachable or unauthorized due to security setting.

After few nights of troubleshooting, I was running out of clue. Came to the sudden, I accidentally search the computer name in AD under the category of Users object group, and I found an user account been created in AD with the same name as we define on the cluster name. I was wondering whether this could caused the confuse to the system. Therefore, I was suggesting to remove the user name temporally as it was not use at the moment and tried to reform the cluster. Guess what, the cluster form up as it needed to be in less than 1 minutes. We were so happy to end the marathon troubleshooting every night well and we were also very pissed off with the bugs we face here.

Read more »

Microsoft Cluster on VMware ESX 4.1

Posted on January 6th, 2011 in Server, Storage, Tips, Virtualization, vSphere | 6 Comments »

To deploy Microsoft Cluster on VMware ESX 4.1 is not new thing, you may need to choose the right storage protocol in this case. According to VMware best practices, on Fiber Channel SAN will be supported with the current version. You will need to present the Share Storage via FC LUN to build the microsoft cluster in VMware environment. ISCSI & NFS both are not supported in this case.

You can view the Official VMware Documentation from here.

Read more »

Bugs on Virtual to Virtual Migration from Microsoft to VMware

Posted on October 9th, 2010 in Tips, vSphere | No Comments »

Recently had found some weird issue while we tried to migrate virtual to virtual from Microsoft Virtual Server 2005 to VMware vSphere 4. The import process done successful by the VMware converter, but we realized the network packets get delay while we performed the continues ping test to the virtual machine. the Ping respond had been delayed more than 1000ms in the LAN environment.
Read more »