ARMC126-ARMC-6287 - Citrix Hardware Refresh Addendum 1 QA.pdf
PDF 179 KB Posted
- Attached to
- Citrix Hardware Refresh - RFP
- Solicitation number
- ARMC126-ARMC-6287
- Issued by
- San Bernardino County, California
About this file
This is Addendum No. 1 to Request for Proposals ARMC126-ARMC-6287 issued by San Bernardino County on behalf of Arrowhead Regional Medical Center (ARMC), a 456-bed acute care facility located in Colton, California. The addendum provides a comprehensive Q&A document addressing 16 questions submitted by potential bidders regarding the Citrix Hardware Refresh project. The project scope encompasses replacement of the existing Citrix VDI server and storage environment without upgrading or migrating to newer Citrix versions. ARMC anticipates hardware setup and configuration to occur within 6 to 8 months, with preference for expedited completion due to existing hardware being out of support. The organization currently operates AHV Version 20220304.441 with VDA version 2402.0.2150.2566 and intends to migrate to the latest AHV version. The environment includes two MCS golden images, one per cluster, with plans to transition from Ivanti/Res One Workspace to Citrix WEM for profile management. ARMC utilizes Citrix DaaS for management with on-site Virtual Apps and Desktops, alongside Nutanix Prism and Citrix UberAgent monitoring solutions. The organization maintains a monthly downtime window for cutover activities and expects proposed VDI configurations of 8-16 CPU and 16-32 GB RAM to address current login time performance bottlenecks.
Successful project completion is defined by full hardware and hypervisor installation with updates, new VDI and VApp desktop builds communicating with Citrix Cloud, and readiness for end-user deployment. ARMC conducts annual security audits through third-party vendors and requires encryption at rest and micro-segmentation features to remain outside this project scope. The addendum confirms that no NetScaler VPXs or non-Citrix workloads requiring migration are included in the scope, which is limited to Virtual App Servers and VDI environments only. No specific pricing information, set-asides, or incumbent contractor details are disclosed within this addendum document. The proposal submission deadline was April 10, 2026 at 3:00 PM PST, with presentations and demonstrations scheduled for the week of April 20, 2026.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP - ARMC - 3-9-26 - Citrix Hardware Refresh~1.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
400 N. Pepper Avenue, Colton, California 92324-1819 | Phone: 909.580.1000
Addendum No. 1 BID No. ARMC126-ARMC-6287
Request for Proposals Citrix Hardware Refresh
Citrix Hardware Refresh - Q&A
Question
Question Answer
1 What are the project timelines?
A. We would like the hardware and set up of the hardware to take place in the next 6 to 8 months.
2 Are there any deadlines that affect when this migration must be completed by? (e.g.
hardware/software end of support/life, contract expiration, etc.)
The sooner the better. Some of our existing hardware is already out of support.
3 Is the goal of Citrix portion of the project to result in like for like? (i.e. Citrix will not be upgraded nor migrated to newer versions or new farms)
Correct. This project is just to replace our existing VDI server/storage environment. Our existing Farm will remain as it is in the Citrix Cloud Control Plane.
4 What is your existing hypervisor and version?
(e.g. vSphere 6.5, AHV 10.3, etc.)
AHV Version 20220304.441 and VDA version 2402.0.2150.2566
5 What is your target hypervisor and version? (e.g.
vsphere 9.0, AHV 11.0, etc.)
Whatever the lates AHV version is.
6 What your image management solution and version (if applicable)? (MCS 2507, PVS 2407 CU3, standard image build with no image management, etc.) a. If yes, how many base or gold master images are used today? b. If leveraging PVS, where is the cache stored? c.
Per image, how many servers/desktops are being deployed? d. Will all images remain on their current operating systems, or are any operating system upgrades/rebuilds expected as part of this effort?
We are leveraging MCS. Version We have two golden images, one per cluster.
7 What profile management solution are you using? (e.g. Citrix UPM/File based, Citrix UPM/Container based, FSlogix container, other or no profiles are used) a. If yesIf so, are you planning on leveraging Nutanix Files for storing profiles or windows file server?) b. Has the performance and storage impact of this approach been evaluated?
We currently are using Ivanti/Res One Workspace and are looking to make the jump to Citrix WEM.
We are open to using Nutanix Files and no to questions b.
8 Are you using Citrix Virtual Apps and Desktop/On-prem or have you completed a migration to Citrix Cloud/DaaS?
We are using Citrix Daas to manage our environment, however, all VApps and Desktops remain onsite.
9 Are you leveraging any monitoring solutions that must remain integrated? (Citrix uberAgent, ControlUp, Nexthink, Nutanix Prism, etc.)
B. We have UberAgent and are using Nutanix Prism.
10 Are there any NetScaler VPXs on the existing
Nutanix hardware that must be migrated also?
What firmware version are those VPXs?
C. No.
11 Will other non-Citrix workloads VMs be migrated as part of this scope from the old Nutanix cluster to the new Nutanix cluster? (e.g. domain controllers, certificate servers, virtual appliances, Windows file server, Citrix Cloud
Connectors/Delivery Controllers, NetScaler
VPXs, etc.)
None. We just have Virtual App Servers and VDI’s in this environment.
12 For servers that must be migrated from the old cluster to the new cluster, what outage window is available? Note: Citrix workloads using image management can be built and tested in parallel, then put into UAT or production when ready.
We will be able to build net new and move over slowly. We have a monthly downtime that we can use to the cut over.
13 Is there a performance bottleneck in the current environment and if so what is it today? CPU, memory, disk? a. And has that bottleneck (if any) been addressed in the new hardware request?
I would say login times could be better.
Would also like to provide more CPU and RAM to the VDI’s if possible. Thinking 8/16 CPU and 16 to 32 for RAM
14 With the Nutanix Security add-on, are you planning on leveraging Encryption at rest and/or Flow (micro-segmentation) as part of this project and should be scoped?
Encryption at Rest and Flow (micro-segmentation) are not included in the scope of this project. Vendors should not include these features in their proposals unless they are explicitly required by the RFP.
15 Are there any audit or security assessment that will be performed against the new cluster? Is that same audit or security assessment already performed against the existing cluster? If an audit or security assessment, can you share detail on what the requirements are?
Yes we do audit the cluster on an annual basis. This is done by a third parting vendor that will scan the infrastructure.
16 What defines successful completion of the Citrix portion of the project (functional access, performance validation, stability period) and how it will be measured?
All hardware/hypervisors is fully online, installed and updated. New VDIs/VApp desktops are built and communicating to Citrix Cloud and a fully deployable to our end users.
File details come from the government source that posted it. Updated .