Skip to main content

Top Ten CIO Checklist for Cloud Computing

Once you've made the decision to move your servers to the cloud, be sure to read the fine print. 

Here are some factors that CIOs and other buyers should look for:
  1. Understand your data security needs.  What form of encryption is provided?  Are there government security rules or standards you must follow?
  2. Don't take virtualization for granted.  Make sure that all your servers can be virtualized.  Some older systems such as mainframes and AS/400 may require co-location instead unless you want to migrate to a more modern system.
  3. Start small and prioritize your cloud migration.  Start with less essential services so you can learn how to transition from your data center to the cloud without as many angry users.  Running for a month or more with limited services will give you a better idea of actual costs.
  4. Watch pricing for data in and out.  Many services don't charge for moving data to the virtual server but charge for moving it off the server.  So if you have ten server images to move, you may get a different bill if you move to each from your office server than if you move to one in the cloud and copy from it to another.
  5. Track your return on investment. Keep checking your costs.  One of the main motivations for moving to the cloud is to save money, so keep track after you migrate and make sure that you are succeeding in this goal.  Report back to stakeholders so they know that the change has been worthwhile.
  6. Check the specs on your servers carefully.  Review all the performance parameters for the servers to be sure you are comparing apples to apples in choosing a cloud vendor.
  7. Test your backup and restore.  Backup and restore capabilities are essential, but worth nothing if you can't do them when you need them.  So put them through their paces.
  8. Find out the speed limit.  See if your provider sets a maximum speed for your servers.
  9. Learn about shared and dedicated servers, single and multi-tenancy.  Find out what is right for you.
  10. Standardize your platform.  The more you rationalize your servers and move them to a standard platform, the easier it makes migration and management.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan