I have been planning to move my desktop on to the cloud for years, now it’s the right time as cloud technology has finally matured.
There has always been a need for me to print documents via Remote Desktop on my locally attached laser printer. Today, I finally got time to try this out, I thought it was as simple as enabling the Printer in Local Resources under Remote Desktop options, but it turns out no printer was found in the RDP session PC. In additional, Windows 7 or W2K8 doesn’t have this problem as printer drivers were loaded by default, only Windows XP or W2K3 needs to install printer drivers.
After Google a bit, I was able to locate the answer that all you need is to install the printer driver on the remote PC as well. Soon after I’ve done that, the remote printer showed up magically. Besides, I was also able to tested out the local drive letters and USB disks on demand, they all worked flawlessly, so no need to use VPN and Shared Folder function any more. Worried about RDP’s security? It’s encrypted, if you need much higher level, then use Windows 7 or Windows Server 2008 R2 will do the trick.
Now it’s time for me to Acronis my 13 years old desktop (Dual PIII 850Mhz,1GB Ram and 120GB IDE, amazingly it’s still running and can play HD MKV!) and send it to the cloud by using vCenter Converter, then I can connect with any thin client (e.g., iPhone) as long as it has Remote Desktop, I can finally open my huge Excel way faster now! Yeah!
It shouldn’t be classified as hack-in incidence at all, as the hacker didn’t break into their system but rather jammed HKSE’s pipe. Btw, no body dares to say the truth that there is no way to prevent bandwidth type of DDOS attack, as bandwidth is limited, but DDOS bot is unlimited, so even the biggest gun will be brought down to its knee including FBI site last year. That’s why HKSE senior is so afraid to disclosure the bandwidth they had.
and Guess Who’s that security expert in DDOS from Iseral? Well, there is only one, my guess is Radware!
對於有激動股民認為他應該辭職，李小加不以為然，他表示，「若做錯了當然要負責……（但停牌）已是最好的選擇」，他強調決定是具有良好目的（in good faith），並強調港交所關鍵的清算及交易系統，採高保安封閉式運作，未有受黑客攻擊。
海外黑客前日癱瘓了港交所「披露易」網站，所發動的「分散式阻截服務攻擊（DDoS, distributed denial of service attack）」攻擊法，即是在背後發出遙控指令，令全球數以百計已中電腦病毒的傀儡電腦，同時向目標網站發出大量攻擊信息，耗盡其頻寬及伺服器能力使之癱瘓，事件揭出披露易網站事發前欠缺強力保安設施，無法抵擋黑客攻擊。
I noticed both the latest Equallogic firmware v5.05/v5.07 STILL contains a bug that a failed disk won’t be indicated in group manager. What’s worst is that soon you will discover all your VM starts to BSOD/Panic and thinking it’s either related to your switch/VMWare/ESX Host, until you found out it is actually caused by Equallogic firmware. This bug causes volume corruption and excessive disk latency, killing all your VMs at the end, both scenarios have been preciously reported by actual EQL users in VMTN.
This is VERY SERIOUS! Users who bought Equallogic supposed to have a 99.999% reliability (what they called Five 9s), but a fail disk won’t show up in the error windows nor it flashes the amber light to alert you is a very scary experience and plain stupid!
I read from VMTN that a bad luck EQL users has no way to find out which drive has failed, finally he asked EQL support to WebEx into his console, spent hours to figure out the one.
Simply NOT ACCEPTABLE for this kind of high-end SAN!
Yes, that’s why I am still holding off my upgrade to v5.0.7 (currently at v5.0.2), I was told once by Dell consultant this: “DON’T UPGRADE ANY OF YOUR FIRMWARE if you are not having any problem.” I guess he meant for something by then, now I fully understood!
After the heavy 99.9% negative comments in VMTN, VMW finally surrendered sort of! Why did you do that in the first place? Stupid $$$ driven decision! You have hurt many loyal followers heart deeply this time. Now I finally see why Monopoly is a bad thing!
Finally ESXi Free Edition is able to use 32GB compares to 8GB previously and I also found VSSP actually encourages use of the reserved ram model that allows memory over-commitment, but isn’t that contradict to what vRam model is used for enterprise? Seem VMware has confused everyone including itself.
As you are probably aware, when VMware announced our new Cloud Infrastructure Suite, we also introduced changes to the vSphere licensing based on a consumption and value-based model rather than on physical components and capacity.
While we believe this model is the right long-term strategy as we move into the cloud-computing era, the announcement generated a great deal of passionate feedback from partners and customers that led us to examine the impact of the new licensing model on every possible use case and scenario – and equally importantly, taking into consideration our partners’ and customers’ desire to broadly standardize on VMware. We’ve listened to your ideas and advice, and we are taking action with the following three updates to the vSphere 5 licensing model:
•We’ve increased vRAM entitlements for all vSphere editions, including the doubling of the entitlements for vSphere Enterprise and Enterprise Plus. Below is a comparison of the previously announced and the new vSphere 5 vRAM entitlements per vSphere edition:
•We’ve capped the amount of vRAM we count in any given VM, so that no VM, not even the “monster” 1TB vRAM VM, would cost more than one vSphere Enterprise Plus license. This change also aligns with our goal to make vSphere 5 the best platform for running Tier 1 applications.
•We’ve adjusted our model to be much more flexible around transient workloads, and short-term spikes that are typical in test & development environments for example. We will now calculate a 12-month average of consumed vRAM to rather than tracking the high water mark of vRAM.
Finally, we introduced the vSphere Desktop Edition to address vSphere licensing in a desktop environment. vSphere Desktop is licensed on the total number of Powered On Desktop Virtual Machines allowing customers to purchase vSphere for VDI use case on per user basis. Our price books are being updated and will be available on Partner Central shortly.
Update Sep-14
There is an interesting article about how enterprises in Taiwan responded to the vRam change, it seemed 99% are still against the change.
I always wonder what Hot-add means in Veeam’s term as it’s always mentioned in their forum, now I understand after reading the blog post, but again I never use virtual appliance mode as it’s for small enviornment say if you have 30 or less VM to backup.
Hot-add – This is frequently used when referring to virtual appliance mode backups within Veeam Backup & Replication. Basically, once the virtual machine backup is underway; the associated VMDK files are added dynamically to the Veeam backup server. This dynamic procedure can only happen when the virtual machine has a snapshot in place, and then the VMDK files of the source virtual machine are disconnected from the Veeam backup server once the backup steps are completed. Further, this option is only available when Veeam Backup & Replication is installed on a virtual machine. Veeam Backup & Replication has supported Hot-add mode since version 4, released in 2009.
Comments (0) 
