Abstract: Administering a remote session between a target computing device and a remote computing device, including: identifying, by a remote session administration module, a confidentiality level of content displayed by a target computing device, the target computing device engaged in a remote session with remote computing device, the remote session carried out by software executed by the target computing device, software executed by the remote computing device, and an active data communication link between the target computing device and the remote computing device; and controlling, by the remote session administration module, the remote session in dependence upon the confidentiality level of content displayed by the target computing device.

Abstract: Administering a remote session between a target computing device and a remote computing device, including: identifying, by a remote session administration module, a confidentiality level of content displayed by a target computing device, the target computing device engaged in a remote session with remote computing device, the remote session carried out by software executed by the target computing device, software executed by the remote computing device, and an active data communication link between the target computing device and the remote computing device; and controlling, by the remote session administration module, the remote session in dependence upon the confidentiality level of content displayed by the target computing device.

Abstract: An apparatus, system, and method are disclosed to failover to a standby server when a primary server is under broadcast storm or denial-of-service (“DoS”) attack. A primary attack sensing module is included to monitor a rate of incoming data from a computer network to a primary server and to determine if the rate of incoming data is above a primary data rate threshold. A standby contact module is included to request a standby data rate status from a standby server in response to the primary attack module determining that the rate of incoming data to the primary server is above the primary data rate threshold. The standby server is connected to the primary server over a private network. The standby data rate status includes a determination by the standby server of whether a rate of data received by the standby server is above a standby data rate threshold. A standby receiver module is included to receive a standby data rate status from the standby server over the private network.

Abstract: Migrating port-specific operating parameters during blade server failover including querying, by a system management server of a data center, a switch for port-specific operating parameters of a first port, the data center comprising blade servers coupled for data communications to one another and to the system management server by a network, the system management server comprising a computer subsystem that automates server management processes in the data center, the switch comprising a data communications component of the network, the switch comprising ports, the ports comprising physical points of connection between the switch and blade servers, each port having associated port-specific operating parameters, the switch connected at the first port to a failing blade server; and assigning, by the system management server, the port-specific operating parameters to a second port in a same switch or another switch connected at the second port to a replacement blade server.

Abstract: Migrating port-specific operating parameters during blade server failover including querying, by a system management server of a data center, a switch for port-specific operating parameters of a first port, the data center comprising blade servers coupled for data communications to one another and to the system management server by a network, the system management server comprising a computer subsystem that automates server management processes in the data center, the switch comprising a data communications component of the network, the switch comprising ports, the ports comprising physical points of connection between the switch and blade servers, each port having associated port-specific operating parameters, the switch connected at the first port to a failing blade server; and assigning, by the system management server, the port-specific operating parameters to a second port in a same switch or another switch connected at the second port to a replacement blade server.

Abstract: Migrating port-specific operating parameters during blade server failover including querying, by a system management server of a data center, a switch for port-specific operating parameters of a first port, the data center comprising blade servers coupled for data communications to one another and to the system management server by a network, the system management server comprising a computer subsystem that automates server management processes in the data center, the switch comprising a data communications component of the network, the switch comprising ports, the ports comprising physical points of connection between the switch and blade servers, each port having associated port-specific operating parameters, the switch connected at the first port to a failing blade server; and assigning, by the system management server, the port-specific operating parameters to a second port in a same switch or another switch connected at the second port to a replacement blade server.

Abstract: Methods, apparatus, and products for managing virtual addresses of blade servers in a data center are disclosed that include storing by a blade server management module (‘BSMM’), in non-volatile memory of a blade server, a parameter block, the parameter block including one or more virtual addresses for communications adapters of the blade server and one or more action identifiers, each action identifier representing a type of address modification; detecting, by a basic input-output system (‘BIOS’) module of the blade server upon powering on the blade server, the parameter block; and modifying, by the BIOS module of the blade server in dependence upon the one or more action identifiers of the parameter block, an address of at least one communications adapter of the blade server.

Abstract: Failover of blade servers in a data center including powering off a failing blade server by a system management server through a blade server management module (‘BSMM’) managing the failing blade server, the failing blade server characterized by a machine type, one or more network addresses, and one or more storage addresses, the addresses being virtual addresses; identifying, by the system management server from a pool of standby blade servers, a replacement blade server, the replacement blade server managed by a BSMM; assigning, by the system management server through the BSMM managing the replacement blade server, the one or more network addresses and the one or more storage addresses of the failing blade server to the replacement blade server, including enabling in the replacement blade server the assigned addresses; and powering on the replacement blade server by the system management server through the BSMM managing the replacement blade server.

Abstract: Applying firmware updates to servers in a data center, the servers including one or more active servers and a standby server, each server mapped to separate remote computer boot storage, including applying the firmware updates to the standby server; selecting an active server for firmware updating; powering off the selected active server by the system management server; remapping the standby server to the remote computer boot storage for the selected active server; rebooting the standby server from the remote computer boot storage for the selected active server, designating the standby server as an active server; remapping the selected active server to the remote computer boot storage formerly mapped to the standby server; and rebooting the selected active server from the remote boot storage formerly mapped to the standby server, designating the selected active server as a standby server.

Abstract: Migrating port-specific operating parameters during blade server failover including querying, by a system management server of a data center, a switch for port-specific operating parameters of a first port, the data center comprising blade servers coupled for data communications to one another and to the system management server by a network, the system management server comprising a computer subsystem that automates server management processes in the data center, the switch comprising a data communications component of the network, the switch comprising ports, the ports comprising physical points of connection between the switch and blade servers, each port having associated port-specific operating parameters, the switch connected at the first port to a failing blade server; and assigning, by the system management server, the port-specific operating parameters to a second port in a same switch or another switch connected at the second port to a replacement blade server.

Abstract: Methods, apparatus, and products for managing virtual addresses of blade servers in a data center are disclosed that include storing, by a blade server management module (‘BSMM’) in non-volatile memory of a blade server, a parameter block, the parameter block including one or more virtual addresses for communications adapters of the blade server and one or more action identifiers; detecting, by a BIOS module of the blade server upon powering on the blade server, the parameter block; disabling, by the BIOS module, in dependence upon the one or more action identifiers of the parameter block, an original address of at least one communications adapter of the blade server; and setting, by the BIOS module, an address of the communications adapter to a virtual address included in the parameter block.

Abstract: Failover of blade servers in a data center including powering off a failing blade server by a system management server through a blade server management module (‘BSMM’) managing the failing blade server, the failing blade server characterized by a machine type, one or more network addresses, and one or more storage addresses, the addresses being virtual addresses; identifying, by the system management server from a pool of standby blade servers, a replacement blade server, the replacement blade server managed by a BSMM; assigning, by the system management server through the BSMM managing the replacement blade server, the one or more network addresses and the one or more storage addresses of the failing blade server to the replacement blade server, including enabling in the replacement blade server the assigned addresses; and powering on the replacement blade server by the system management server through the BSMM managing the replacement blade server.

Abstract: Methods, apparatus, and products for managing virtual addresses of blade servers in a data center are disclosed that include storing by a blade server management module (‘BSMM’), in non-volatile memory of a blade server, a parameter block, the parameter block including one or more virtual addresses for communications adapters of the blade server and one or more action identifiers, each action identifier representing a type of address modification; detecting, by a basic input-output system (‘BIOS’) module of the blade server upon powering on the blade server, the parameter block; and modifying, by the BIOS module of the blade server in dependence upon the one or more action identifiers of the parameter block, an address of at least one communications adapter of the blade server.

Abstract: Applying firmware updates to servers in a data center, the servers including one or more active servers and a standby server, each server mapped to separate remote computer boot storage, including applying the firmware updates to the standby server; selecting an active server for firmware updating; powering off the selected active server by the system management server; remapping the standby server to the remote computer boot storage for the selected active server; rebooting the standby server from the remote computer boot storage for the selected active server, designating the standby server as an active server; remapping the selected active server to the remote computer boot storage formerly mapped to the standby server; and rebooting the selected active server from the remote boot storage formerly mapped to the standby server, designating the selected active server as a standby server.

Abstract: An apparatus, system, and method are disclosed to failover to a standby server when a primary server is under broadcast storm or denial-of-service (“DoS”) attack. A primary attack sensing module is included to monitor a rate of incoming data from a computer network to a primary server and to determine if the rate of incoming data is above a primary data rate threshold. A standby contact module is included to request a standby data rate status from a standby server in response to the primary attack module determining that the rate of incoming data to the primary server is above the primary data rate threshold. The standby server is connected to the primary server over a private network. The standby data rate status includes a determination by the standby server of whether a rate of data received by the standby server is above a standby data rate threshold. A standby receiver module is included to receive a standby data rate status from the standby server over the private network.

Abstract: The present invention facilitates the management of blade server information handling systems by providing a non-disruptive indication signal for power management to a Management Module or similar. By providing said functionality and method, the power available to power the management module at a particular instance, in relationship to the power state of the chassis may be determined, such that power may be configured in a non-disruptive manner for the management module. Said functionality and method also provides for both the safe and efficient powering of a server from cold start or the hot-plugging of a management module into an active, powered chassis.

Abstract: A method and system for managing a computer system including a plurality of servers and at least one shared peripheral device is disclosed. The method and system include performing communications between the plurality of servers and the at least one shared peripheral device using a shared bus. The communications include providing data for a first server of the plurality of servers from the shared peripheral device(s). The data is provided to the servers over the shared bus. The method and system also include caching the data in the plurality of servers and utilizing the data only in the first server in response to receipt of the data.

Abstract: The present invention facilitates the management of blade server information handling systems by providing a non-disruptive indication signal for power management to a Management Module or similar. By providing said functionality and method, the power available to power the management module at a particular instance, in relationship to the power state of the chassis may be determined, such that power may be configured in a non-disruptive manner for the management module. Said functionality and method also provides for both the safe and efficient powering of a server from cold start or the hot-plugging of a management module into an active, powered chassis.