Ideas

✅ Proposal: Standard VM Template for MAX2 PIVOT (Central Fill / PCMS Deployments)

🔹 Objective

Reduce deployment time and eliminate environment-related delays by providing customers with a pre-built, validated VM template for MAX2 PIVOT 7.4.x.

🔹 Current Challenge

Although installing MAX2 PIVOT is typically a ~2-hour process, real-world deployments are taking 3–4 days due to customer-controlled environments.

Most common blockers:

1. Remote Access Constraints

   • Provided accounts lack local admin rights

   • Install manager requires ability to create local accounts (e.g. ParataSupport, ParataDatabase)

   • Delays: 1–2 days waiting on IT to grant proper access (RDP/local admin)

2. Incorrect OS Version

   • Customers deviating from spec (e.g., Windows Server 2025 instead of 2022)

   • Not discovered until late in the process

   • Requires rebuild from scratch

👉 Impact: 2–3 days lost

3. Pre-configured Group Policies / Domain Issues

• • Machines pre-joined to domain or previously domain-managed

  • Restrictions prevent:

    • Local user creation

    • Permission assignments

  • Requires customer IT intervention

4. 3rd Party Antivirus / Security Controls

• • AV deletes or blocks:

    • Installer files

    • Batch execution steps

  • Requires exemptions or temporary disablement

🔹 Business Impact

• 3–4 days per deployment

• Increased:

  • Support effort

  • Customer frustration

  • Coordination overhead with IT teams

• Inconsistent deployments and higher risk of misconfiguration

🔹 Proposed Solution

Provide a standardized VM template pre-built by us (BD):

✔ Pre-installed components:

• Windows Server 2022 (clean, non-domain joined)

• MAX2 PIVOT Server 7.4.x

• Verified local accounts:

  • ParataSupport

  • ParataDatabase

• Required roles, features, and dependencies

• No domain policies applied

• No third-party AV installed

🔹 Delivery Format Options

Recommendation:

• Maintain a master image

• Export into:

  • .OVA → for general distribution

  • .VHDX → for Hyper-V customers

🔹 Deployment Workflow (Future State)

1. Customer downloads VM template

2. Imports into their hypervisor

   • VMware → Deploy OVA

   • Hyper-V → Attach VHDX

3. Powers on VM

4. Performs minimal configuration:

   • IP / hostname

   • Domain join (if required AFTER install)

5. System is ready

👉 Total time: 1–3 hours instead of 3–4 days

🔹 Key Benefits

✅ Time Reduction

• From 3–4 days → few hours

✅ Eliminates Known Issues

• No OS mismatch

• No domain conflicts

• No GPO restrictions

• No AV interference

✅ Consistency

• Every deployment is identical

• Easier troubleshooting

• Easier escalation to R&D

✅ Reduced Customer Dependency

• Less reliance on:

  • IT teams

  • Security approvals

  • Access provisioning

🔹 Implementation Strategy

Step 1: Build Gold Image

• Create VM in Hyper-V or VMware

• Install:

  • Windows Server 2022

  • MAX2 PIVOT 7.4.x

• Validate full functionality

Step 2: Generalize (Optional but Recommended)

PowerShell

sysprep /oobe /generalize /shutdown

This allows:

• SID reset

• Customer-specific configuration post-deployment

Step 3: Export Formats

• VMware:

  • Export to OVA

• Hyper-V:

  • Provide:

    • .VHDX

    • Or full VM export

Step 4: Hosting / Distribution

Options:

• Internal BD portal

• Secure file transfer (SFTP / SharePoint / Azure Blob)

• Version-controlled repository

🔹 Optional Enhancements

• ✅ Pre-configured SQL instance (if applicable)

• ✅ Pre-created service scripts

• ✅ AV exclusion recommendation file

• ✅ Post-deployment checklist for customers

🔹 Risks / Considerations

🔹 Summary

Providing a standard VM template:

• Eliminates the most common deployment blockers

• Reduces install time from days to hours

• Improves consistency and reliability

• Significantly lowers support overhead for Product Support Engineers

** Even though a new version of MAX2 PIVOT Server is released, it is much easier to upgrade from a previous version than installing everything from fresh. Say MAX2 7.5 PIVOT Server is released, the upgrade from 7.4X to 7.5.x should take around 1 hour to complete.