MachPanel Knowledgebase

SOP Creating a Sealed Image of Windows Server with Microsoft SQL Server 2022

rehan_waseem — Wed, 17 Jun 2026 08:49:50 GMT

Summary

This article provides information about preparation of sealed images for Windows Virtual Machines with MS SQL Server 2022.

Applies To

Applies to MachPanel v8 and onward.

Procedure for creating Windows VM Sealed Images with MS SQL Server 2022

STEP-1: CREATE VM

Minimum Disk Space 10-12 GB: Create a VM to host the operating system of your choice with minimal disk space i.e. from 10 to 12 GB, as the purchased storage will then be added to respective VM later based on Service Plans.

Required Partition Settings:

Proper disk partitioning is critical for successful deployment. The recommended partition order is:

EFI System Partition (ESP) - SYSTEM
Recovery Partition (WinRE) - MSR (Reserved)
Windows (C:) - Primary

Hint : Create the Windows (C:) partition first (by selecting "New" in the Windows Setup dialog), Windows Setup automatically creates the required UEFI/GPT partitions in the correct order behind the scenes.

STEP-2 SCHEDULED TASK

In order to set Machine Name, Password and IP Address of VM, a "Scheduled Task" in sealed image must be created. Please review details below to create a scheduled task to allow MachPanel to "Set Password" and process other OS initialization steps in Gen1 & Gen2 VM: Creating Scheduled Task

Note: There is a difference between creation of scheduled task for Gen1 and Gen2 type virtual Machines. Please check details in above KB and create task accordingly.

STEP-3 Installing Microsoft SQL Server 2022 as Built-in part of Windows Sealed Image

Perform these steps on your reference Windows Server 2022 machine before running Windows SysPrep

Mount or attach the SQL Server 2022 Standard installation media to VM.
Launch setup.exe to open the SQL Server Installation Center
In the left navigation menu, click Advanced
Select Image preparation of a standalone instance of SQL Server

Accept License terms
Select the desired Features
Give Instance ID , (e.g. MSSQLSERVER, SQL2022STD)

Complete rest of steps, click prepare

STEP-4: SEAL THE IMAGES / PREPARE WINDOWS VM SEALED IMAGES

Download the sample / generic sysprep.xml file provided in download section in this article (adjust it if required per your requirements).
Copy sysprep.xml to C:\Windows\System32\sysprep inside the VM that needs to become your sealed image / OS template.
Open Command Prompt as Administrator
Navigate to SysPrep Directory: CD C:\Windows\System32\sysprep>
Run command: sysprep.exe /generalize /oobe /shutdown /unattend:sysprep.xml
On completion, you will find the VM in shutdown state.
Your sealed image is ready. You can copy this <name>.VHD / <name>.VHDX file to MachPanel's Sealed Image repository directory and specify the path to the prepared file in MachPanel configuration.

STEP-5: After VM Provisioned

On Each VM deployment

Use the “Image completion of a prepared stand-alone instance” from start menu

During SQL Complete Image, provide:
- Product key (for Standard edition)
- Instance name (can differ from Instance ID)
- Service accounts (e.g., NT Service\MSSQLSERVER or domain accounts)
- SQL Server administrators (Add current user)

Domain Split & Migration Procedure

mudesira.munir — Wed, 22 Apr 2026 21:34:40 GMT

Summary

This article provide a summary on how to split domain of an organization into two customers/tenants.

Applies To

This article applies to MachPanel build v8.2.50 and above

Scenario Overview

Existing Setup:

Customer-A
- OrgA
  - Domains:
    1. DomainA.com
    2. DomainB.com
- Users exist in both domains

Required Target Setup

Existing Customer (Customer-A)
- OrgA
  - Domain: DomainA.com only
  - Mailboxes: All users should belong to DomainA.com

New Customer (Customer-B)
- OrgB
  - Domain: DomainB.com only
  - Mailboxes: Users migrated from OrgA (DomainB.com users)

Solution Steps

Step-1: Create New Customer

Create Customer-B with Organization Name as “OrgB” but with dummy domain “DomainC.com” since the panel already has domain DomainB.com.

Assign a temporary (dummy) domain (e.g., DomainC.com) 
Reason: DomainB.com is already associated with OrgA in the panel.

Step-2: Move Users on Backend

Move users of DomainB.com from OrgA to OrgB:
- OrgA OU → OrgB OU
Ensure:
- There should not be any permissions/settings from DomainA.com user on DomainB.com user and vice versa.

Step-3: Update Database Records

Modify the MachPanel Database table:
Table Name: HB_tblExchangeOrganizationDomains

Required Changes:
- Update OrganizationID for DomainB.com to associate it with OrgB i.e. 24 in given example.
- Set IsDefaultDomain = True for DomainB.com
- Remove the dummy domain (DomainC.com) entry

Record Before:

Record After:

Ensure database backup is taken before making changes.

Step-4: Update UPN Suffixes in Active Directory

Ensure each organization (OU) has only its valid domain:

OrgB OU
- UPN Suffix: DomainB.com

OrgA OU
- UPN Suffix: DomainA.com

Step-5: Perform Backend Synchronization

OrgA
- Perform Sync from backend for OrgA, check DomainB.com users (Mailbox and AD Users) get removed form OrgA.

Result:

OrgB
- Perform Sync from backend for OrgB, verify DomainB.com users are part of OrgB Exchange Security Group, AL, GAL, OAB etc.

After:

Hotfix for MachPanel Build v8.2.50 HF8 Updated (August 19, 2026)

rehan_waseem — Mon, 13 Apr 2026 08:41:46 GMT

Summary

This article provides 8.2.50 HF8 and information about how to apply this fix on your servers.

Applies To

This article applies to MachPanel

Important Note

Prior to performing any update take backup of your MachPanel Database and files from Control and Remote servers. See below Kb article for more details on how to take backup. http://kb.machsol.com/Knowledgebase/Article/50248
MachPanel Control Panel and all MachPanel Remote Servers need to be on Build v8.2.50 and then Hotfix can be applied.
Please follow the steps given below in sequence and execute instructions in the KB articles to complete the update:
- Update to Latest MachPanel
- Update to Latest MachPanel Remote Server

Latest Issues Fixed

Build: 8.2.50 HF8 Updated: August 19, 2026

1. Added method in REST API to change Mailbox type.
2. Added methods in REST API to manage Mailbox calendar permissions.
3. Fixed VPS IP only addon not getting provisioned.
4. Fixed VPS disk options in Add VPS.
5. Optimized/Enhanced Exchange Distribution Group Members management.
6. Dynamic IP allocation handled for Linux VMs.
7. Fixed edit VPS addon throwing an exception due to missing Natted IP record.
8. Added Export AD users CSV option in Update Bulk AD User.
9: Added Copy to Clipboard option in Selectable/Select control.
10:Option added to manage Snashots on VMs using Cluster setup.
11:Optimized Exchange and AD management to avoid deadlocks and faster load and processing time.
12:Add NIC in Linux VM fixed for PFSense integration.
13:Added feature to reset Firewall rules to default for an Interface.
14:Fixed Mailbox created on Synced ADUser does not appear in listing when the Country is Null on Customer AD by Setting Country = Customer Profile Country.
15:New Audit Logging implemented for S4B module.
16:Handled User mailbox changed to O365/Remote Mailbox in Exchange Organization Sync from Backend.
17:Handled auto add mailbox primary email on ADUser UPN change.
18:New permissions related for reports added in Staff role and Access permissions.
19:Improved VM management UI/UX.
20:Added method in REST API to update Customer Linked Ad User.
21:Updated REST API Mailbox features method.
22:Added method in REST API to manage Mailbox Calender permissions.
23:Snapshot management handled for Cluster based VM management.
24:REST API search using domain alias fixed.
25:Added VPS Server to Customer mapping in Hyper-V module.
26:Option added to change OS type of existing VM.
27:Added method in REST API to change mailbox type.
28:Send connector management updated.
29:Fixed AD Organization Domain Edit issue not getting updated on backend AD.
30:Fixed Automatically Add Users in Security Group of AD Organization.
31:Updated Resource/Room Mailbox Full Access manager auto-update.
32:Fixed Mailbox connect/recreated issue through MachPanel Recovery interface.
33:Fixed Exchange DL LDAP Issue after setting Email Alias as Primary.
34:Updated Mailbox listing having different UPN and Primary Email for better understanding.
35:Fixed Shared Mailbox permission violation issue.
36:Fixed VPS Disk Move operation.
37:Updated KeyCloak handling, added to match authenticated user against panel login.
38:Added Cluster support in VPS import, now all VMs on cluster get listed for import.
39:Added default settings in VPS import to make it easy to pre-select settings and import bulk VMs for a customer in one go.
40:Enhancement: In VM import no need to do NIC settings, it is auto handled and if a match is not found then message appears to set the settings manually.
41:Added feature to map Servers to Customer in Hyper-V, it updates Owner nodes in Cluster setup on backend too.
42:Added feature to manage Trunk port Config in NIC management for Provider.
43:Added feature to schedule email for Over Quota usage report.
44:Added function for Over Quota usage report in REST API.
45:Permissions added for Staff and Customer/Reseller access permissions to manage different sections in Hyper-V and Exchange section.
46:Updated VM import handled Cluster resource name containting SCVMM VMName Resources.
47:Updated VM Disk management, optimized speed and option added to skip disk format commands. Need to run script "Update HB_tblSystemSettings Set AutoConfigureDisk = 0", to disable the format and reboot handling.
48:Updated NIC management for Dynamic Pool and SDN case, no need to reboot in Windows VM case.
49:Updated logging in VM creation. Run button disabled for Customers.
50:Fixed Expand disk shows wrong disk type.
51:504 Error in VM operations cause is found to be HTTP/HTTPS Gateway connection timeout needs to be increased to 1800 seconds.
52:VM account listing view updated.
53:VM account name link corrected.
54:Logging added to find cause of wrong disk consumed value in Disk management.
55:Wrong ServerId set in imported VM in Cluster setup is fixed.
56:Fixed error "The INSERT statement conflicted with the FOREIGN KEY constraint "FK_HB_tblVPSAccounts_HB_tblVPSHosting". The conflict occurred in database "MachPanel_Db", table "MachPanel_Db.HB_tblVPSHosting", column 'VPSHostingID'. The statement has been terminated." in VM import.
57:Fixed VM management get freezed when Memory tab is opened.
58:IP handling and UI updated in Hyper-V Module.
59:Export forwarding report error in Customer side fixed.
60:Handling done to import VM without IP being read automatically when Dynamic Pool is used.
61:VM reboot message updated.
62:Exchange Recycle bin, Recovery hidden when Exchange module is Off.
63:Enhancement: The VM subscription resources used does not include resources assigned to VMs in recycle bin.
64:Hyperlinks added for easy navigation where needed in VPS module.
65:In Add/Expand disk "Apply changes inside" VM checkbox added in Windows case. If checked, reboot is needed else not.
66:Patch actions added in REST API for Mailbox management.
67:Added option to install OS using ISO in VM creation. Import and management has also option to change Sealed Image/ISO option for provider.
68:Added more filters and State and refresh State data in VM listings.
69:VLan listing added for assigning Dynamic pool to Customer Subscription.
70:Mailbox usage info corrected in REST API.
71:Select reseller hidden if resellers are not used in Subnet Pools.
72:Fixed wrong time VM schedule processing issue.
73:Fixed Custom quota values not displayed in mailbox advanced tab.
74:Updated display of banner in Login, Forgot password page.
75:Updated Vlan handling in Hyper-V module.
76:Updated VPS import, error is given if NIC name are duplicate.
77:Fixed error in sync Hyper-V VM stats reading routine.
78:Handled Custom input in Mailbox Archive settings.
79:Fixed Public Folder Mailbox not automatically removed from Exchange after associated subscription is cancelled.
80:Hyper-V VM Management User Interface Improvements.
81:Bulk AD User create issue when country not mentioned in CSV file is fixed.
82:Issue of missing data for AD user fields when creating AD User enabling Exchange mailbox from AD user interface is fixed.
83:Fixed get mobile device using Identity fails when LDAP of mailbox is changed.
84:Fixed error in mailbox add when selecting existing AD User.
85:Fixed error in adding NIC when NIC Name has apostrophe in NIC name.
86:Release locked thread from crashed machine in load balanced deployment.
87:Fixed user attributes missing when creating mailbox from Ex interface.88:Fixed error in removing VPS subscription.

Procedure

Go to MachPanel configuration studio.
Shut down all the MachPanel services and also exit the configuration studio. Make sure no instance to MachPanel Configuration Studio is running under any user.

Download the hotfix MachPanel_HF_8.2.50_HF8_August_19_2026.zip file from the link at bottom of this page.
Stop IIS Admin Service, please make sure that all the services are STOPPED from MachPanel Configuration Studio. Verify from "Task Manager" that the following services are not running.

MachSol.MachPanel Provisioning Service.

MachSol.MachPanel.ConfigurationStudio.exe.

MachPanel Billing Service.

MachPanel Helpdesk Service.

MachPanel Network Service.

MachPanel License Service.

MachPanel O365 Service.

Replace files from MachPanel folder on MachPanel control server (Path: C:\Program Files\MachSol\MachPanel Control Server) and Replace files from Remote server folder of hotfix folder on MachPanel remote server (C:\Program Files\MachSol\MachPanel Remote Server) keeping the folder hierarchy same as it is in hotfix. (you should get message to overwrite files, if not you are not doing it right).
Execute script.txt from zip file on MachPanel_Db after logging in to SQL management studio as MachPanel_Db user.

Once all files are replaced properly from hotfix folder Restart all services related to MachPanel on Control as well as Remote Servers.

Download Link

https://www.machsol.com/updates/8250/MachPanel_HF_8.2.50_HF8_August_19_2026.zip

Note: Please Unblock the files before replacing in installation directory if the downloaded Zip folder is blocked.

Logging on Hyper-V Remote Server

rehan_waseem — Fri, 10 Apr 2026 15:12:36 GMT

Summary

This article provides a summary on MachPanel Hyper -V Logs files for Remote servers.

Applies To

This article applies to MachPanel build v8.2.50 and above.

Enable Extensive Logging via MachPanel:

AttachVHDLog_<date>

Is for all operations related to attaching a VHD to a virtual machine including initialization, configuration validation, disk attachment on the SCSI controller, and final status. Any exceptions encountered during execution are also recorded.

BandWidthMonitering_<date>:

Records network bandwidth utilization metrics for virtual machines within the Microsoft Hyper-V environment. This file is generated when bandwidth monitoring is enabled for a virtual machine and is used to track network activity over time.

It captures both upload and download traffic separately, providing visibility into inbound and outbound data transfer for each monitored VM. The recorded data helps in understanding network consumption patterns, identifying high-traffic workloads, and ensuring fair usage of shared network resources.

JobProcessingLog_<date>

Is for the virtual machine provisioning process on the Microsoft Hyper-V server. It captures a detailed, step-by-step record of all operations performed during VM creation, like creation of the virtual machine directory and storage path, selection and configuration of the VM generation, attachment of the sealed image (VHD/VHDX), allocation of compute resources, and network configuration such as virtual switch assignment and NIC setup.

Any warnings, exceptions, or failures encountered during execution are also recorded.

Overall, this log file provides end-to-end traceability of the VM creation lifecycle.

ProvSvc-RemoteConfigurationStudio_<date>

This indicates that the Provisioning Service (ProvSvc) has initiated a process. Typically, this log appears when the service starts up, or task/job (such as configuration, deployment, or sync) is triggered.

Prov_SVC_<date>

This usually logs when the system attempts to process a job. For e.g. The process is already stopped, or process was never running, or process ID/name could not be found.

Remote_<date>

This log shows that a remote PowerShell command was executed. The command queries the Windows Management Instrumentation (WMI) to collect CPU (processor) details from the target machine. It is typically used by monitoring/provisioning systems (like MachPanel) to gather system resource information.

Remote configuration Studio_<date>

These logs indicate a MachPanel Remote Server update process initialization. It shows the version to which it is updated. The update was successful or failure. In case of update failure it will show the error or cause of failure.

VPS_<date>

Provides an abstracted, high-level view of the processing status for individual virtual machine files (XML) within the provisioning workflow on the Microsoft Hyper-V environment.

VMUsageStateLog

Maintains a structured, time-series record of resource utilization metrics for virtual machines hosted on the Microsoft Hyper-V environment. The data is stored in JSON format, where each entry corresponds to a specific virtual machine identified by its unique VMID and VMName.

For each virtual machine, the log captures a collection of UsageStats entries recorded at periodic intervals. These entries include key performance indicators such as CPU usage, memory (RAM) consumption, and disk (HDD) utilization, along with an associated UTC timestamp (DateStamp) indicating when the metrics were collected.

This log enables historical tracking of VM resource consumption over time, facilitating performance monitoring, capacity planning, and trend analysis. It also supports identifying usage patterns, detecting anomalies (e.g., sudden spikes in CPU or memory), and correlating system behavior with operational events.

This structured JSON format allows easy integration with monitoring tools, reporting systems in MachPanel for both real-time observation and retrospective analysis of virtual machine performance.

VMUsageState

Is for the virtual machine resource monitoring process within the Microsoft Hyper-V environment. It records the execution details of the ReadVMStatsAndSaveInFile() routine, which is responsible for collecting and persisting VM usage statistics.

This log captures timestamped entries that document both successful operations and runtime exceptions encountered during the data collection process. Common logged activities include reading VM resource metrics, calculating virtual disk consumption, and writing aggregated statistics to the VMUsageState data file.

VMDownTime (folder)

Contains the VMDownTime file that maintains a record of virtual machine downtime events within the Microsoft Hyper-V environment. It captures essential details for each instance where a virtual machine is identified as unavailable or not running.