Earlier this month I posted Why Move to the Public Cloud?, outlining the thinking behind choosing a public cloud implementation. As you may recall, it described why organizations choose public, private or hybrid cloud implementations and also why some choose traditional, on-premises applications.
What about those who have already made the move to the public cloud? How did they approach their work and what best practices are emerging? I guest blogged last week on the Microsoft Enterprise Viewpoints blog, describing the importance of selecting, validating and securing the right workload, and of preparing to manage services. Be sure to take a look at Top Considerations in Moving to the Public Cloud, and please provide your thoughts on how these approaches could apply to your cloud rollout.
I like the quote
"Nathan McBride, AMAG Pharmaceuticals who is building an IT infrastructure wholly in the cloud:
“Security is my favorite topic because I’ve yet to meet a single person who can show me specifically in some legitimate, substantive, concrete way that the cloud is less secure.”"
As for
"Take an inventory of your assets to adequately assess ROI for cloud solutions"
In cloud migrations I've been involved with, the costs associated with maintaining IT assets is generally much higher than any fees from cloud technologies. For instance, in the case of evaluating InTune, the cost of maintaining a PC through traditional means (I used WSUS server maintenance + time used for user to connect to VPN to do software auditing + OS upgrade cost + time spent for IT as the formula) is about $125/month per machine. In contrast, $11 is such a tiny figure that it makes little sense not to subscribe. InTune spreads out the cost of IT as well as every machine can be handled from a single interface regardless of geographic location. Especially in the case of laptop computers, the ROI on InTune is realized immediately.
For email, the loss of email connectivity associated with unpredictable events (i.e. server crashes, sustained loss of electricity) can be quite costly. In one formula we used, we took the actual additional time employees must spend conducting business away from email. Lost time due to having to fall back to phone calls (across time zones) added up to one years worth of cloud service being equal to 1/2 day worth of email loss.
Managing the systems turned into a learning experience rather than being a well-planned project. As employees became more accustomed to cloud services, other tasks were pushed to the cloud. For instance, expense tracking, quality assurance, and preventative maintenance were moved to cloud applications which created unexpected challenges. I would highly recommend any business considering a cloud migration to anticipate department heads wanting to migrate things to the cloud that aren't obvious at a glance.
Interior jakarta on http://maxinteriorjakarta.blogspot.com
Situs buka jasa dan promosi jasa on http://www.bukajasa.com
cara flashing android on http://a-ndroid.com
cara flashing samsung on
http://a-ndroid.com/category/flashing/samsung
cara flashing tool on http://a-ndroid.com/category/flashing/tool
cara flashing acer on http://a-ndroid.com/category/flashing/acer
berita bola on http://berita-prediksibola.com
prediksi bola on http://berita-prediksibola.com
berita prediksi bola on http://berita-prediksibola.com
Tempat wisata di singapore on
http://tempatwisatadisingapore2.blogspot.com
Tempat wisata di singapura on
http://tempatwisatadisingapore2.blogspot.com
Wisata singapura on http://tempatwisatadisingapore2.blogspot.com
uber gratis on http://www.ubergratis.com/
uber coupon code on http://www.ubergratis.com/
http://www.uber.com/invite/ubergratis.com
Dompet pria kulit pari on http://www.paridjogja.com
Dompet wanita kulit pari on http://www.paridjogja.com
Dompet kulit ikan pari on http://www.paridjogja.com