You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.163.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 17:28, 10 March 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.163.179.242. The blocked range is 54.163.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Form of personal computer))
((Multiple issues|
((original research|date=April 2010))
((More citations needed|date=July 2009))
))

A '''blade PC''' is a form of [[Client (computing)|client]] or [[personal computer]] (PC). In conjunction with a client access device (usually a [[thin client]]) on a user's desk, the supporting blade PC is typically housed in a rack enclosure, usually in a datacenter or specialised environment. Together, they accomplish many of the same functions of a traditional PC, but they also take advantage of many of the architectural achievements pioneered by [[blade server]]s.

==Description==

Like a traditional PC, a blade PC has a [[central processing unit|CPU]], [[RAM]] and a [[hard drive]]. It may or may not have an integrated graphics sub-system. Some can support multiple hard drives. It is in a “blade” form that plugs into an enclosure. Enclosures offered by current blade PC vendors are similar but not identical. Most have moved the power supplies, cooling fans and some management capabilities from the blade PC to the enclosure. Up to 14 enclosures can be placed in one industry standard [[19-inch rack|42U rack]].

Blade PCs support one or more common operating systems (for instance Microsoft has created a “blade PC” version of their XP and Vista Business operating systems and many Linux distributions are installable). Importantly, these solutions are intended to support one user per discrete device. This is a major difference from server-based computing, which supports multiple users simultaneously using an application hosted on one discrete server (be it a discrete piece of hardware or a discrete [[virtual machine]] on a server).

Access to the device is usually achieved via various [[Virtual Network Computing]] (VNC), which allows users to log on to the blade PC via a client device (usually a [[thin client]]). Once logged on the end user experience is largely the same as if they were logged on to a local PC. It is less effective at delivering multimedia, in part because the audio and video are not synchronized, so in circumstances where there is increasing latency, there is a proportional decrease in the quality of the end user experience. All protocols are negatively impacted by increasing latency between the end user’s access device and the blade PC. One of the biggest challenges the blade PC vendors have experienced is how to minimize the impact of latency and deliver an end user experience comparable to that offered by a traditional PC, and there has been a number of new entrants in this sub-category of the blade PC in 2007.

[[International Data Corporation]] recognizes blade PCs as a category separate from other types of PCs and has begun issuing forecasts for blade PCs.

==History and vendors==
[[ClearCube]], a small privately held company based in [[Austin, Texas]], gets credit for creating and popularizing the category.<ref name="Start-up brings 'blades' to the desktop, September 20, 2002, by Michael Kanellos">((cite web
 | url=http://news.cnet.com/Start-up-brings-blades-to-the-desktop/2100-1003_3-958819.html
 | title=Start-up brings 'blades' to the desktop, September 20, 2002, by Michael Kanellos 
 | accessdate=2009-12-31
 | publisher=CNet
 ))</ref> Started in the late 1990s, they have been very aggressive promoting the concept especially in the United States and in vertical markets such as financial traders, hospitals and national defense organizations.<ref name="ClearCube Extends Market Leadership with Record Growth in 2007, May 6, 2008">((cite web
 | url=http://www.paladincapgroup.com/portal/index.php?option=com_content&task=view&id=71&Itemid=2
 | title=ClearCube Extends Market Leadership with Record Growth in 2007, May 6, 2008
 | accessdate=2009-12-31
 | publisher=Paladin Capital Group
 ))((dead link|date=July 2017 |bot=InternetArchiveBot |fix-attempted=yes ))</ref>

[[Hewlett-Packard|HP]] was second to the category with the 2004 announcement of their “Consolidated Client Infrastructure” in North America.<ref>http://www.hp.com/go/cci ((Dead link|date=February 2022))</ref>  In contrast to ClearCube, HP emphasized density while minimizing power consumption, which resulted in the ability to put far more blade PCs in an industry standard 42U rack (up to 280). HP’s first offering, however, was a Transmeta-based solution, which offered only a marginal end user experience.((Citation needed|date=October 2009)) HP has since migrated to AMD-based blade PCs. Like the other blade PC vendors, HP offers MS RDP with their solutions, and they have announced availability of another protocol called [[Remote Graphics Software]] that has some advantages over MS RDP, especially in regard to delivery of three-dimensional and streaming content.

[[Hitachi]] offers a blade PC of their own in Japan. It is reportedly only available in Japan. There does not seem to have been any enhancements since it was first introduced in 2005. Though more like the CCI solution than the ClearCube solution, it is less dense and has all cabling out of the front of the unit.

==Comparison==
Common value proposition of blade PCs relative to traditional PCs:

* Enhanced data security because all data can be maintained in the datacenter and can more easily be saved to a mass storage device, so if the access device is stolen or destroyed the data is not compromised
* Reduced Total Cost of Ownership due to consolidation, standardization, and more redundancy
* Better disaster tolerance for end users because with MS RDP end users can log in from anywhere to  their blade PC, so even if their office is quarantined (due to a contagious disease outbreak, for instance), they can continue to have access to their blade PC and their data files so they remain productive

==Design considerations==

As an alternative to traditional PCs, the blade PC solutions offered by the various vendors are effectively competing with PCs, albeit they are based in datacenters. Therefore some of the more important design considerations in this category include:
* Maximizing the end user experience (this is a “ticket” to entry – end user experience must be comparable to at least low-end traditional PCs)
* Minimizing acquisition cost (as a result traditional PC components are frequently used rather than more expensive server components)
* Maximizing density (because if these devices are to replace millions of traditional PCs by moving into datacenter they must minimize the amount of expensive datacenters space they require)
* Minimizing power consumption (minimizing power input and heat output in a datacenter is critical to keeping data centers properly cooled and datacenter costs down - see [[HVAC]])
* Similar to traditional PCs to deploy and integrate (ease of integration is critical, or the barriers to adoption will prohibit widespread success for the category)
* Easy to manage with the same tools used for other datacenter based HW and SW (otherwise it becomes onerous extra work)

==Related client solutions==

* [[Blade workstation]]: These solutions tend to be much more expensive than the traditional blade PCs, and befitting their more high-end specs, they are much more capable.
* [[Virtual PC]]: Unlike blade PCs, some vendors of virtualization software (such as [[VMware ESX Server|ESX]] from [[VMware]]) have recently popularized the idea of using a [[hypervisor]] such as ESX to create multiple [[Virtual Machine]]s (VM) that sit on top of the hypervisor, and load a client operating system in each VM. The goal then is to maximize the number of users per server to minimize acquisition cost while not so compromising the end user experience to make it too poor to use. So unlike the blade PC solutions described above, in a virtualized model all end users share the underlying hardware resources.

==See also==
* [[Nettop]]
* [[Remote Graphics Software]]
* [[Blade server]]
* [[PCoIP]]

==References==
((reflist))

((Computer sizes))

((DEFAULTSORT:Blade Pc))
[[Category:Microcomputers]]
[[Category:Thin clients]]
[[Category:Personal computers]]

Pages transcluded onto the current version of this page (help):

Blade PC (edit)
Template:Ambox (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite web (view source) (protected)
Template:Computer sizes (edit)
Template:Dead link (view source) (template editor protected)
Template:Delink (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (template editor protected)
Template:Hlist/styles.css (view source) (protected)
Template:Icon (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Original research (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (template editor protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Icon (view source) (template editor protected)
Module:Icon/data (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (template editor protected)
Module:Pagetype/setindex (view source) (template editor protected)
Module:Pagetype/softredirect (view source) (template editor protected)
Module:SDcat (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (template editor protected)
Module:Yesno (view source) (protected)

Return to Blade PC.

Retrieved from "https://en.wikipedia.org/wiki/Blade_PC"