SigmaSystemCenter 3.1 Update Module (SSC0301-0002-update1.zip) Patch Name : SSC0301-0002-update1 Patch Description : A module to improve functions and problems considered in SigmaSystemCenter 3.1. Release Date : Apr/26/2013 File Name : SSC0301-0002-update1.zip Target Product : SigmaSystemCenter 3.1 Target Versions of Components *1: SigmaSystemCenter Version: 3.1-20825, SystemProvisioning 6.1.0010, 3.1-21185, SystemProvisioning 6.1.0011 DeploymentManager Version: 6.1, 6.11 System Monitor - Performance Monitoring Services Version: 5.1.1027.0 NEC ESMPRO Manager Version: 5.31-5.62 Necessary Patch : SigmaSystemCenter: N/A DeploymentManager: N/A System Monitor - Performance Monitoring Services: N/A NEC ESMPRO Manager: N/A Reboot: Required Patches Contained in This Patch *2: SSC0301-0001 *1) How to check target versions of components - SigmaSystemCenter and SystemProvisioning A version is displayed at the bottom of the Web Console. Target Version: One of the followings "Version: 3.1-20825, SystemProvisioning 6.1.0010" (SigmaSystemCenter 3.1) "Version: 3.1-21185, SystemProvisioning 6.1.0011" (SigmaSystemCenter 3.1 SSC0301-0001 is already applied.) - DPM Server 1) Start the DPM Web Console. 2) Check that "DeploymentManager 6.1" or "DeploymentManager 6.11" is displayed at the bottom of the DPM Web Console. 3) After checking, end the DPM Web Console. - System Monitor - Performance Monitoring Services 1) Click the [Start] button, select [All Programs]. From [All Programs], select [SigmaSystemCenter]. From [SigmaSystemCenter], select [System Monitor Management Console] to start the management console of System Monitor - Performance Monitoring Services. 2) The Logon window appears. Click [Cancel]. 3) Click the [Help] menu, select [Version Information] to display the Version Information window. 4) The version is displayed at the Version. Target Version: 5.1.1027.0 - NEC ESMPRO Manager 1) Click the [Start] button - [All Programs] -[NEC ESMPRO Manager] - [About NEC ESMPRO] - [Version Detector] dialog. 2) Select [Manager] tab and check Current Version. Target Versions of Components: 5.31-5.62 *2) This update module contains fixes and improvements in the following previously released patches. For the fixes and improvements in each patch, see the following files. - SSC0301-0001.txt This update module incorporates the following fixes and improvements in SigmaSystemCenter 3.1. 1. Fixed Problems 1.1. Fixed Problems in SystemProvisioning (1) The Delete VM command fails (#5480) Phenomenon: The command to execute Delete VM (pvmutl vmdelete) fails to delete a virtual machine if you specify the category that has the lower-priority physical or virtual machine server group than the virtual machine group. Problem Explanation: When a category is provided in the command to execute Delete VM, the command searches the group in the category first, and then searches the virtual machine to be deleted from the group. If the lowest priority group is a physical or virtual machine server group, the command cannot find the target virtual machine and its process fails. Solution: Fixed the command so that it excludes the groups to which the virtual machine to be deleted does not belong from the searching targets. (2) The cancellation of the software distribution may fail (#10865) Phenomenon: When you execute the software distribution for multiple machines and then immediately cancel it, the job is not cancelled in some machines and the software may be distributed to those machines. Problem Explanation: If you execute the software distribution for multiple machines and immediately cancel it, the cancellation may be executed before the software distribution process has been started in all of the target machines. The cancellation for the software distribution process cannot be executed for machines on which the process has not started yet, and the software may be distributed to those machines. Solution: Fixed the cancelation of the software distribution so that it retries until the software distribution process has been cancelled in all of the target machines. (3) Move VM with Quick Migration does not function in the predictive event (#12619) Phenomenon: When the [Action for VMS / Move all VMs on the VM Server (Quick Migration, Failover)] action in the standard policy template for ESXi is executed, it skips Quick Migration. Problem Explanation: The [Action for VMS / Move all VMs on the VM Server (Quick Migration, Failover)] action is defined to the standard policy template for ESXi contains as an action for the predictive event. When this action is executed, it skips Quick Migration and executes only Failover. However, the action properly functions if you do not use the standard policy template as is and manually specify the action from the Action list, or if you redefine the action. Solution: Fixed the [Action for VMS / Move all VMs on the VM Server (Quick Migration, Failover)] action in the standard policy template for ESXi so that both Quick Migration and Failover function when the action is executed. (4) When unassigning an LUN from a host in CLARiiON, other LUNs may be also unassigned from the same host (#12495) Phenomenon: When unassigning an LUN in CLARiiON, LUNs which should not be unassigned may be unassigned if the LUN is already assigned to the host but the [Storage] tab does not have its settings. Problem Explanation: If there is the assigned LUN (displayed as a red checkmark) but it is not configured in the [Storage] tab, other LUNs also may be unassigned when you attempt to unassign an LUN. So, when you intend to assign an LUN to a machine, you must configure the LUN in the [Storage] tab, too. Solution: Fixed so that other LUNs than the specified one keep their connection statuses on actual machines regardless of whether it has been configured in the [Storage] tab or not when unassigning the LUN. Also, fixed so that, if the unnecessary connection has been found, it will be released and then the specified connection will be established. (5) Unable to specify groups in the placement information commands (#12589) Phenomenon: When using the ssc placement information commands, if you specified the group in a root folder with its full path, you may receive the warning "GroupName is duplicated." and an error may occur. Problem Explanation: When you specify the group in a root folder when specifying a group name, the ssc placement information commands search elements with the specified name from all categories, groups, models, and resources. If multiple elements which share the specified name are found in categories, groups, models, and resources, the commands cannot identify which element is that you specified and the command execution results to an error. Solution: Fixed the ssc placement information commands so that they search the group in the root folder from the elements within the root folder when its full path is provided. (6) The sub-pool-consumption notification events are named improperly. (#13000) Phenomenon: If the consumption notification events for both root resource pools and sub-pools are monitored, duplicated event names may be detected when adding those events to a policy if you use their default event names. Problem Explanation: The standard event name of the sub-pool consumption notification event share the same name with that of the root resource pool consumption notification event, which causes name duplication between a resource pool and sub-pool if you add the event with the standard event name. So you must change one of those event names manually. Solution: Modified event names for a sub-pool. (7) Incorrect virtual disk information may be displayed in the Hyper-V virtual machine (#13079) Phenomenon: A bad virtual disk name is displayed on [Virtual Disk List] which appears in details of a Hyper-V virtual machine. Problem Explanation: This issue occurs, for example, when you directly provide the virtual disk file path in manually settings of a virtual machine. When this issue occurs, nothing is displayed on the area where host names and cluster names should be displayed, although file paths are displayed properly. Solution: Fixed [Virtual Disk List] so that it properly displays disk names. (8) Named machine profiles are deleted (#13452) Phenomenon: When you specify the host settings on the [Portal] view to create a virtual machine, named machine profiles may be deleted. Problem Explanation: The machine profile already set to the host setting is deleted because a virtual machine will be created based on the specified machine profile in [Create VM] from the [Portal] view. If you execute [Create VM] from the [Portal] view when a named machine profile is set to the host setting, the named profile is deleted. Solution: Fixed [Create VM] in the [Portal] view so that it does not delete a named machine profile. 1.2. Fixed Problems in DeploymentManager (1) The Windows parameter file creation fails (#13108) Phenomenon: Restoration such as N+1 Recovery for a Windows operating system from SigmaSystemCenter fails under the following condition: [Condition] You attempt to restore the image that has been created with the generation management enabled (the number except zero is set to [The Number Of Backup Image File Generations To Be Managed] in [Backup/Restore] tab). [Error message] Failed to create a parameter file for Windows while executing the scenario (xxxxxxxx) for the server (xxxx). A backup image file does not exist. Problem Explanation: The DPM restoration process creates a parameter as its internal process when it is executed from SigmaSystemCenter. The process obtains the backup image name from the restore scenario during the parameter creation. However, if the image is created with the generation management enabled, the process fails to obtain the image name with the actual date and the process fails to create a parameter file, which causes the restoration process to fail. Solution: Fixed so that the DPM restoration process can properly handle the image name to which the date is attached. (2) An application error occurs in DeploymentManager API Service (apiserv.exe) (#13247) Phenomenon: If the DeploymentManager API Service logging level in the "apiserver.ini" is 16 (LEVEL=16) or higher, an application error occurs when you specify the Sysprep answer file on SigmaSystemCenter and attempt to register a virtual machine to DPM. -File location \apiserver.ini - Description [TRACE] LEVEL=xx Problem Explanation: The DeploymentManager API Service logging function malfunctions. Due to this, the Sysprep answer file information is not logged properly and an application error occurs. Solution: Fixed the logging function. (3) Search for the management server does not function (#13303) Phenomenon: Search for the management server might fails on a managed machine. This issue applies only to the managed machine running a 64-bit Windows operating system. Problem Explanation: DPM Client temporally disables a WOW 64 file system redirector in order to access the native system directory (%windir%\System32) on a 64-bit Windows operating system. It must be enabled after accessing the native directory, but the process to enable it is not executed and this issue can occur. Solution: Added the process to re-enable a file system redirector. (4) In Image Builder (Remote Console), an application error occurs (#13327) Phenomenon: When you do the following operation in Image Builder (Remote Console), an application error occurs. 1. On the [Create Setup Parameter File] screen, click [File]. Then click [Create new disk copy information files for 2008/Vista or later] (clicking [Create new information files] is alternative to this operation.) 2. After clicking [Cancel], click [File] menu and click [Create new disk copy information files for 2003/2000/XP] on the [Create Setup Parameter File] screen. Problem Explanation: If you perform the procedure above in Image Builder, its internal doubly releases a resource, which causes an application error. Solution: Fixed the process not to doubly release a resource. (5) Obtaining logs in DPM fails in the environment that has no database (#13428) Phenomenon: An error might occur when you attempt to obtain DPM logs in the environment that has no databases. Problem Explanation: The log tool asynchronously iterates the database access even though the environment has no database. If the log tool proceeds to the process to compact the collected data during the database access retry, an error occurs because it tries to compact the file that is being accessed. Solution: Fixed the logging tool not to try to access a database if there is no database in the environment. (6) Some services may fail to start when starting the management server (#13440) Phenomenon: The following services may fail to start when starting the management server: - DeploymentManager Backup/Restore Management - DeploymentManager PXE Management - DeploymentManager PXE Mtftp - DeploymentManager Remote Update Service - DeploymentManager Transfer Management Problem Explanation: The internal process fails when the DeploymentManager service starts during the start-up process of the network service, which causes an error. Solution: Fixed the DeploymentManager services so that they can delay their execution timing if a service is in process. (7) The DPM Server installation fails (#13442) Phenomenon: The DPM Server installation may fail when you use the SSC installer to install it. Problem Explanation: If you system require to reboot after the silent installation of DPM Server, the installation fails, which is expected design behavior. Solution: Fixes the installation process so that the process is not terminated even if your system requires reboot, and that the process returns the code that reboot is required to the higher process. 1.3. Fixed Problems in System Monitor - Performance Monitoring Services (1) Graph is not displayed in the specified scale (#12972) Phenomenon: Graph is not displayed in the specified scale when starting the System Monitor - Performance Monitoring Console even though the value of [Automatic Scale Setting] in [Graph Setting] is set to "OFF". Problem Explanation: The graph data to be displayed is initialized after starting the console. At this time, the value of the scale is set to its default "1.0" regardless of the [Automatic Scale Setting] value. This is why the graph is not displayed in the specified scale even though the value of [Automatic Scale Setting] is "OFF". Solution: Graph plotting is fixed so that it uses the specified scale in [Graph Setting] if the value of [Automatic Scale Setting] is "OFF" when initializing graph data. 1.4. Fixed Problems in NEC ESMPRO Manager (1) A SNMP trap port conflict occurs (#12330) Phenomenon: SNMP trap port conflict occurs. Problem Explanation: SNMP trap port conflict occurs between NEC ESMPRO Manager and PVM service when "Method of receiving SNMP Trap" is set to "Use own method" on the ESMPRO Manager. Solution: The default setting of "Method of receiving SNMP Trap" is now "Use SNMP Trap Service" if SNMP trap service is installed on the management computer. 2. Functional Enhancements 2.1. Functional Enhancements in SystemProvisioning (1) Enhanced network management Support Overview: - The firewall control is now supported for Linux iptables (#11878) - You can check the usage of IP address pools on the [Resource Pool] screen and the [Details of the logical network] screen. Also, you can check the VLAN usage on the [Network List] screen. (#8843) (2) Support for VMware vSphere 5.1 (#12281) Support Overview: - You can use the vSphere 5.1 VM console. (#10906) - The following limitations have been removed: - You can now create a virtual machine using EFI firmware in a Standalone ESXi environment. (#12716) - HW Profile Clone from a master VM which is the virtual machine using EFI firmware is now supported. (#12994) This update includes the following limitation: (a) VMware does not support guest operating system customization of Windows 8 and Windows Server 2012 at the time of release of this update. (#12281) (3) Enhanced virtual environment management Support Overview: - You can view and delete folders/ files on a datastore. (#2373) - You can create a virtual machine without using templates. (#8682) - You can edit the optical drive information and mount an ISO file on [Edit VM]. (#8683) The ISO file must be located on a datastore. - You can create a virtual machine with a larger system disk than that of a template by providing the system disk size in [Machine Profile]. (#12843) You cannot specify the system disk when you use a Differential Clone template. - If a failure occurs on a virtual machine server and its status becomes [Faulted] or [Degraded], the hardware parts status "The virtual machine server" of the virtual machine managed on the virtual machine server is updated to [Faulted] or [Degraded]. (#12752) You can check it on the [Resource] view or the [Virtual] view. - The "/mode:vm" option is now available when running a Sysprep (deleting the machine-specific information) for virtual machines running Windows 8 or Windows Server 2012. (#12855) - The following required tasks to create an template in Differential Clone / Disk Clone has been automated: (#12859) - Preparing a sysprep for a master virtual machine - Creating software (scenario) to run a sysprep - Setting the software for a master VM - You can specify a template and network when creating a virtual machine on the [Portal] view. (#12665) (4) Enhanced collaboration with VMware Support Overview: - The license can be applied for the ESXi 5 provisioning. (#12032) You must provide the license in [Host Profile]. - You can change the root password when creating a virtual machine for a Linux guest operating system in the VMware environment. (#12656) You must set the root password for a master VM to a template or image. (5) Enhanced collaboration with KVM Support Overview: - Red Hat Enterprise Linux 6.3 is now supported in SigmaSystemCenter. (#12422) (6) Enhanced collaboration with Hyper-V (#12648) Support Overview: - The following Windows Server 2012 Hyper-V features are available in SigmaSystemCenter: - Migration in a non-cluster environment - SMB 3.0 file share - The new virtual disk file format (VHDX) (7) Enhanced user management Support Overview: - The user account information has added the following items: Certification Type, Last Login, User Status, and E-Mail address (To - Recipient). (#13004) - You can login to SigmaSystemCenter with a user authenticated by an LDAP (Lightweight Directory Access Protocol) server. (#11793) - You can create a user group which enables you to set roles to multiple users at one time. Also, if you add a user to a user group that has been already created the roles for the group can be automatically assigned to the user. (#12013) (8) Enhanced e-mail notification Support Overview: - You can specify the recipient of the e-mail notification in operation group basis or host profile basis. (#12043) - The action "Notification / E-mail Reporting" has been added to the policy action. With this action specified in the policy setting, the notification e-mail can be sent at any timing you want. Also, you can specify the subject and content of the notification e-mail. (#12996) (9) Enhanced operation management Support Overview: - You can specify how long to retain operation logs. (#11714) Provide the maximum output days on the [Environment Setting] window. - If a failure occurs in a machine and the details of its hardware status on the [Resource] view and the [Virtual] view has been changed, the target machine icon on a tree in those views is highlighted. The highlighting is turned off when you click [Details] to check the status. (#12998) - The "Reset of an Action Execution Result" action has been added to the policy action. You can set this action to the policy to specify the waiting interval before the next action is executed. (#13003) (10) Enhanced storage management Support Overview: - You can use the ssc command to view the topology information which helps you to determine the range affected if the failure of storage devices and physical disks has occurred or physical disks have been exhausted during thin provisioning. (#12130) - You can bind the 2 terabytes or more LD in NEC Storage (available with the ssc command only), although you could not do in the earlier NEC Storage. (#12255) - The created LD name was not explicitly identified in the previous SigmaSystemCenter, if you omitted to specify it when binding an LD (available with the ssc command only). But it has been modified to be emitted in the operation log. (#12311) - You can view the information of hybrid pools in NEC Storage. (#13323) (11) Enhanced VM Placement Rule Support Overview: - The VM Placement Rule feature has been improved so that it checks the placement rule when you intend to move a virtual machine with the explicitly specified destination virtual machine server. (#12870) If you want to ignore the placement rule in moving a virtual machine select the [Ignore placement rules] option. - The VM Placement Rule feature has added the Hold rule which is a rule to associate a particular machine with the virtual machine server to which it currently belongs. (#7435) By using this rule, you can associate a virtual machine with a particular virtual machine server and exclude the virtual machine from the target virtual machines to be moved in Optimized StartUp / Optimized Placement. Also, the virtual machines with this rule are not checked for errors due to the restriction for its moving when executing Move Virtual Machine for a virtual machine server in case of the failure. - The functionality of the VM Placement Rule settings has been improved. (#12780, #13077) - The GUI screen for the VM Placement Rule setup has been added to the property screen of the model (VM server). - The concept of [the restriction group] has been added, which improves the VM Placement Rule capability so that it helps you to set the rule for multiple virtual machines / virtual machine servers at one time. - When you set the EQ rule in the existing environment, you need to do the operation to validate the placement rule settings (the ssc vmop verify-rule command). Some edit operations are unavailable before this operation has been completed. (Other operations / functions except edit are not affected by this.) (12) Support for IPv6 Support Overview: - You can use a static IPv6 address when creating a virtual machine or reflecting a machine-specific information during configuring a physical machine using the OS installation by disk duplication of DPM. (#9875) 2.2. Functional Enhancements in DeploymentManager (1) Support for Windows Server 2012 / Windows 8 (#12247, #12743) Support Overview: - (a) Windows 8 is supported as the operating system for a managed machine. And the following limitations for Windows Server 2012 have been removed: - OS installation by disk duplication - Installation of Service Packs, hotfixes, and applications (b) Window Server 2012 and Windows 8 are now available as the operating systems for Image Builder (Remote Console), DPM Command Line, the package Web server, and Package Describer. (2) Support for the UEFI booting (#9151) Support Overview: - You can manage and operate machines booting in the UEFI (Unified Extensible Firmware Interface) mode. (3) Support for the LDAP authentication (#12356) Support Overview: - The directory server in which Lightweight Directory Access Protocol (LDAP) has been implemented can perform the authentication for the login user entered from the Web console. (4) Simplified master image creation in the OS installation by disk duplication (Windows) (#12769) Support Overview: - In the OS installation by disk duplication (Windows), the following tasks, which you need to do on the master machine, can be executed automatically by the pre-installed scenarios. - Preparing a Sysprep - Running Sysprep.bat (5) Support for Red Hat Enterprise Linux 6.3 (#12651) Support Overview: - Red Hat Enterprise Linux 6.3 is now supported as the operating system for a managed machine. (6) Support for IPv6 (#11950) Support Overview: - In the following DPM features, you can use IPv6 addresses to: - Set an IPv6 address for the managed machine during the OS installation by disk duplication - Collect the IPv6 address information through the DPM Client (7) Support for SQL Server 2012 (#13144) Support Overview: - SQL Server 2012 is now supported as a database engine. Also, the included SQL Server in the product has been changed from SQL Server 2008 R2 Express Edition to SQL Server 2012 Express Edition. (8) Support for JRE7 (#13192) Support Overview: - The version of JRE included in the product has been changed from version 6 to 7. (9) Enhanced management server search (#13132) Support Overview: - In this version, it is possible to search for a management server in the environment where the management server and the managed machine are on the different segment if only you configure the regular DHCP Relay Agent, although, in the earlier DPM versions, port forwarding on the port 4011 had to be enabled on a network device to do this. (10) The data root directory can be changed during the database (DPMDBI instance) installation (#12959) Support Overview: - You can specify the following parameters when you directly use the SQL Server installer to install the retail version of SQL Server. - Instance root directory - Data root directory You had to specify the same folder for them in the earlier DPM versions, however, you can specify a different folder for each of them and install the database. (11) The dpmcmd execution is no more halted by Ctrl + C input (#12545) Support Overview: Ctrl+C input is disabled so that it does not halt the dpmcmd execution if it is pressed. 2.3. Functional Enhancements in System Monitor - Performance Monitoring Services (1) Enhancement in Monitored Infrastructures Support Overview: - You can specify a performance counter as you like in collecting the performance information of VMware ESX / ESXi virtual machine servers and virtual machines on VMware ESX / ESXi. (#7071) - Collecting performance information can be customized by executing batch files or scripts such as Windows Script Host (WSH), PowerShell and Linux Shell on a managed machine running Windows or Linux. (#12624) - The network speed of Linux machines is calculated based on physical interfaces only from this release.(#12615) - Improved so that the information of the available storage pool and network speed of the KVM server can be obtained properly. (#11331) (2) Enhanced Platform Support Support Overview: - Windows Server 2012 is supported for a management server. (#13057) - The following platforms are available as monitored targets: - Windows 8 (#12046) - Red Hat Enterprise Linux 6.3 (#12697) - The following platforms are no longer supported as monitored targets: (#12993) - VMware ESX 3.5 - VMware ESXi 3.5 (3) Support for IPv6 Support Overview: - An IPv6 address is available in data collecting of monitored machines running Windows or Linux (SSH connection). (#12048) (4) Support for SQL Server 2012 Support Overview: - SQL Server 2012 is supported as a database engine. (#12695) (5) Released the 64-bit version of System Monitor - Performance Monitoring Services Support Overview: - The 64-bit version of System Monitor - Performance Monitoring Services has been released. (#12572) (6) Enhanced logging capability Support Overview: - The threshold monitoring event logging of System Monitor - Performance Monitoring Services is improved to record the event [ID] and [Event Category] adding to the existing items. (#12540) 2.4. Functional Enhancements in NEC ESMPRO Manager (1) Support of .NET Framework 4.0 Support Overview: - Installer adds NEC ESMPRO Manager services to the exception list on the Windows Firewall if .NET Framework 4.0 is installed. (#12926) =============================================================================== Installation Procedures and Release Modules List =============================================================================== For the procedures to unzip and install this software, other information regarding installation, and release modules list, see Install.txt. In addition, if you set up SigmaSystemCenter components in a clustering environment, see Clustering.txt for the installation procedures in a clustering environment. =============================================================================== Notes on Unzipping a .zip File =============================================================================== [Notes 1] Before unzipping the zip file of this software, confirm and delete the ZoneID information with the following procedure. If you unzip the zip file and install the software with the ZoneID information, the module after installing the software will not work properly. The information called "ZoneID" has been added to a file downloaded from a site in a zone configured other than [Intranet] on Internet Explorer of Windows Vista, Windows XP Service Pack 2 or later, or Windows Server 2003 Service Pack 1 or later. If ZoneID is added to the zip file, the ZoneID information is succeeded to a deployed file and a warning of security is displayed when executing the file, consequently, services or processed may not start. (1) Checking and changing the policy setting (Hide mechanisms to remove zone information): 1) Click the [Start] button, and click [Run]. 2) Enter "gpedit.msc", and click [OK]. 3) The Group Policy Object Editor dialog box appears. Click [User Configuration], click [Administrative Templates], double-click [Windows Components], and double-click [Attachment Manager]. 4) Check the [State] of [Hide mechanisms to remove zone information]. If it is "Enabled," click [Disabled] on the Hide mechanisms to remove zone information Properties dialog box, and click [OK]. If it is "Disabled" or "Not Configured," you do not need to change the setting. (2) Deleting the ZoneID information of the zip file: 1) Open the properties dialog box of the zip file, and click the [General] tab. 2) If the following message is displayed, click [Unblock], and click [OK]. Security: This file came from another computer and might be blocked to help protect this computer. (3) Changing the policy setting (Hide mechanisms to remove zone information): If you changed the policy setting (Hide mechanisms to remove zone information) from "Enabled" to "Disabled," configure it to "Enabled" with the same procedure. [Notes 2] When unzipping the zip file of this software, specify a path whose length is not over 80 bytes as the path to extract. If you specify a path whose length is over 80 bytes, the zip file might not be extracted properly. -------------------------------------------------------------------------------- [Trademark and Copyright Information] All rights reserved. Copyright in this software is owned by NEC Corporation. * All other brands and products used in this document are the trademarks or registered trademarks of their respective trademark holders. -------------------------------------------------------------------------------- Copyright NEC Corporation 2013