Grid Ultimate Edition System Requirements

[Geraldine Ferraiz]

NoteThese system requirements are for SAS Grid Manager using SAS Workload Orchestrator and SAS Job Flow Scheduler. The solution formerly known as SAS Grid Manager that used Platform Suite for SAS has been renamed SAS Grid Manager for Platform.

To keep pace with changes to third-party technologies, SAS has adopted a general policy of supporting one or more baseline major versions, subsequent minor updates, and subsequent major versions for each officially supported operating system. Only the supported baseline major versions are listed in this document. The full SAS Support policy governing third-party software can be found at _plus.html.

SAS recommends that you deploy SAS Metadata Server on a 64-bit host system. The SAS Metadata Server is multi-threaded and multi-core server hardware (typically quad core or higher is recommended). A dedicated machine for the SAS Metadata Server is recommended to simplify tuning, management, and diagnostics, but is not required. The disk I/O performance of any server-class system should be sufficient. Memory requirements are highly dependent on the product mix and usage, but 8 GB of RAM are sufficient for most large deployments. For many deployments, 4 GB of RAM are sufficient and should be considered a minimum, unless the specific deployment is tested and verified to require less memory.

Note: These system requirements are for SAS Grid Manager using SAS Workload Orchestrator and SAS Job Flow Scheduler. The solution formerly known as SAS Grid Manager, which used Platform Suite for SAS, has been renamed SAS Grid Manager for Platform.

To keep pace with changes to third-party technologies, SAS has adopted a general policy of supporting one or more baseline major versions and subsequent minor updates for each officially supported operating system. For example, if the baseline for SAS x is Red Hat Enterprise Linux 8.4, SAS x will also support Red Hat Enterprise Linux 8.9 under this policy.

The full SAS Support policy that applies to third-party software can be found at -party-software-reference/baseline-and-higher.html. As part of this policy, SAS strongly encourages customers to install the latest operating-system service packs.

The disk I/O performance of any server-class system should be sufficient. Memory requirements are highly dependent on the product mix and usage, but 8 GB of RAM are sufficient for most large deployments. For many deployments, 4 GB of RAM are sufficient and should be considered a minimum, unless the specific deployment is tested and verified to require less memory.

SAS software may be provided with certain third-party software, including but not limited to open-source software, which is licensed under its applicable third-party software license agreement. For license information about third-party software distributed with SAS software, refer to

The system requirements in this document were valid when this product version was released. Updates are made periodically. System requirements for components not covered here (such as host systems, Citrix Workspace app, and Citrix Provisioning) are described in their respective documentation.

Except where noted, the component installer deploys software prerequisites automatically (such as .NET and C++ packages) if the required versions are not detected on the machine. The Citrix installation media also contains some of this prerequisite software.

RAM and disk space values are in addition to requirements for the product image, operating system, and other software on the machine. Your performance varies, depending on your configuration. Your configuration includes the features that you use, plus the number of users, and other factors. Using only the minimum can result in slow performance.

Specific recommendations cannot be provided because of the complex and dynamic nature of hardware offerings, and every deployment has unique needs. Generally, sizing a Citrix Virtual Apps VM is based on the hardware and not the user workloads. The exception is RAM. You need more RAM for applications that consume more.

Local Host Cache considerations: Microsoft SQL Server Express LocalDB is a feature of SQL Server Express that Local Host Cache uses on a standalone basis. Local Host Cache does not require any components of SQL Server Express other than SQL Server Express LocalDB.

When installing a Controller, Microsoft SQL Server Express LocalDB 2019 with Cumulative Update 15 is installed for use with the Local Host Cache feature. (This installation is separate from the default SQL Server Express installation for the site database.)

When upgrading a Controller, the existing Microsoft SQL Server Express LocalDB version is not automatically upgraded. For replacement requirements and procedures, see Replace SQL Server Express LocalDB.

Microsoft Internet Information Services (IIS) 7.0 and ASP.NET 2.0. Ensure that the IIS server role has the Static Content role service installed. If this software is not already installed, you are prompted for the Windows Server installation media. Then, that software is installed for you.

Several multimedia acceleration features (such as HDX MediaStream Windows Media Redirection) require that Microsoft Media Foundation be installed on the machine on which you install the VDA. If the machine does not have Media Foundation installed, the multimedia acceleration features are not installed and do not work. Do not remove Media Foundation from the machine after installing the Citrix software. Otherwise, users cannot log on to the machine. On most supported Windows single-session OS editions, Media Foundation support is already installed and cannot be removed. However, N editions do not include certain media-related technologies; you can obtain that software from Microsoft or a third party. For more information, see Prepare to install.

Several multimedia acceleration features (such as HDX MediaStream Windows Media Redirection) require that the Microsoft Media Foundation be installed on the machine on which you install the VDA. If the machine does not have Media Foundation installed, the multimedia acceleration features are not installed and do not work. Do not remove Media Foundation from the machine after installing the Citrix software; otherwise, users will not be able to log on to the machine. On most Windows Server versions, the Media Foundation feature is installed through the Server Manager. For more information, see Prepare to install.

The following host/virtualization resources (listed alphabetically) are supported. Where applicable, the major.minor versions are supported, including updates to those versions. Knowledge Center article CTX131239 contains current version information, plus links to known issues.

The following clients are supported for Windows Media client-side content fetching, Windows Media redirection, and real-time Windows Media multimedia transcoding: Citrix Workspace app for Windows, Citrix Workspace app for iOS, and Citrix Workspace app for Linux.

To use Windows Media client-side content fetching on Windows 8 devices, set the Citrix Multimedia Redirector as a default program: in Control Panel > Programs > Default Programs > Set your default programs, select Citrix Multimedia Redirector and click either Set this program as default or Choose defaults for this program. GPU transcoding requires an NVIDIA CUDA-enabled GPU with Compute Capability 1.1 or higher; see -gpus.

For virtualized graphics acceleration using the NVIDIA GRID API, you can use HDX 3D Pro with all the NVIDIA GRID GPUs supported by the NVIDIA Virtual GPU (vGPU) software version 13 and up, see For a detailed list of supported Hypervisors and supported hardware, see the NVIDIA vGPU software documentation.

The Universal Print Server comprises client and server components. The UpsClient component is included in the VDA installation. You install the UpsServer component on each print server where shared printers reside that you want to provision with the Citrix Universal Print Driver in user sessions.

When using Citrix Provisioning (formerly Provisioning Services) with this release, version 7.x is covered by the XenApp and XenDesktop 7.x lifecycle and the Citrix Virtual Apps and Desktops lifecycle. See the Product Matrix for more information about version compatibility.

The Microsoft Group Policy Management Console (GPMC) is required if you store Citrix policy information in Active Directory rather than the site configuration database. If you install CitrixGroupPolicyManagement_x64.msi separately (for example, on a machine that does not have a Citrix Virtual Apps and Desktops core component installed), that machine must have Visual Studio 2015 runtime installed. For more information, see the Microsoft documentation.

The Commission initiated Rulemaking (R.) 17-07-007 on July 13, 2017 to consider refinements and, if necessary, revise the rules and regulations governing the interconnection of generation, distributed energy resources (DERs) and storage facilities to the electric distribution systems of the Large IOUs. The proceeding is divided into three phases.

Phase 2:Expected to begin in mid-2024, this phase will cover rate setting issues, including distribution upgrade cost sharing and rate setting issues resulting from the implementation of Phase 1.Phase 2 may also include other topics needing that are yet to be determined.

The Interconnection Discussion Forum (IDF) provides an informal venue for utilities, developers, and other stakeholders to explore a wide variety of issues related to interconnection practices and policies. The forum meets at least twice a year in person and/or through online conferencing. Visit the Energy Division's IDF page for more information, including how to join the mailing list and to view previous presentations. For questions related to the IDF e-mail IxF...@cpuc.ca.gov.

On October 12, 2017, the Commission approved Resolution ALJ-347 establishing an Expedited Interconnection Dispute Resolution Process as authorized by Assembly Bill 2861 (Ting, 2016). The expedited dispute resolution process will issue binding determinations to electric distribution grid interconnection disputes based on the recommendations of a technical panel within 60 days of the Commission receiving the Application regarding a particular dispute. For a detailed description of the adopted process, please see Exhibit A of Resolution ALJ-347.

3a8082e126