Skip to main content

Smaller is More Beautiful -- Virtualization in Government Data Centers

Government information technology managers are warming to server virtualization as a means to save money, reduce energy consumption, and simplify management of servers. New products and technologies are bringing virtualization to large and small data centers.

Prior to virtualization, servers were dedicated to particular tasks. Every new application would require the acquisition of one or more new servers. In a large data center, this would ultimately lead to proliferation of servers, and the models and configurations of the hardware would change over time. There was no easy way to scale up applications which needed more hardware horsepower, short of migrating to a new server, and, more commonly, no easy way to take advantage of unused horsepower for servers that largely sit idle.

Every new server demands more resources to keep it alive, including power, connectivity, backup, and management. As the number of servers grow, so does the need for more racks, more floor space and more air conditioning in the server room.

Virtualization means the end of one-to-one mapping of servers and services. A server can hold multiple operating systems on the same hardware, and multiple instances of applications to facilitate management.

The collapse rate is the ratio of servers before and after virtualization. Government Computer News claims a ratio of 20:1, that is the retirement of 19 out of 20 servers when virtualization is implemented. Your mileage may vary, but the ongoing operations savings could be significant.

Virtualization also offers more portability. Once you are operating in a virtual server environment, your applications are less tightly bound to your particular physical servers and easier to move to a new server or even a new hosting facility.

Microsoft has launched new virtualization products, including Windows Server 2008 Hyper-V.

Here is a video introduction of the product.

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

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

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