Forum Widgets
Latest Discussions
Nested 23H2 cluster deployment stuck in "Resolve requirement"
Hi all, I'm breaking my head over this. Every time I deploy new cluster it's always stuck in Resolve requirement. It was fine before but there is no way now to move from it. Host 1 restarts after 15min of deployment and then all goes quiet and finally cluster deployment fails. Anybody any idea?
Feature Request: Azure Stack HCI / Windows Admin Center - Pinning CSV / Align VMs
I would like to propose an idea for a new feature that could be Azure Stack HCI exclusive. Pinning / preferred location for CSV to Hosts via WAC / PowerShell The idea is sourced by the behaviour of VMfleet where "move-fleet" does it for you. Also sourced by the idea of the exclusive feature to assign VMs to a certain Clusternode. Moving VMs to the hosts will break the logic of dynamic resource movement and Azure Stack grouping of VM to hosts or separated. Currently pinning CSV to hosts is a manual task via PowerShell, to improve performance and reduce redirected IO / RDMA traffic. The new feature do not have to be implemented in Failover MMC, since it doesn't regularly receive improvements. Does it make sense to you, or am I missing / misunderstanding something?Feature Request: Azure Stack Storage and Sizing Tools
I would like to bring up that, despite Azure Stack HCI is a growing solution with outstanding features, the current situation for customers and partners is odd to sizing the solution. What we got is in preview everything and not touched for long time, not keeping up with the technology Introducing the all-new azure stack HCI sizing tool (preview)! - Microsoft Community Hub / https://azurestackhcisolutions.azure.microsoft.com/ https://s2dcalc.blob.core.windows.net/www/index.html I hope that the tool will be united. Also the sizing tool requires a Microsoft account instead of a business account which is odd for a business faced solution. It would be amazing, to see more attention. One thing I would wish the most, is a possibility to import LiveOptics data into the sizer tool.Reproducible issue with CAU Kernel Soft Reboot - cluster is in mixed mode but isn't
When trying to enable Kernel Soft Reboot on Customer Hardware or reproduced in MSLab, setting the CAU according to https://learn.microsoft.com/en-us/azure-stack/hci/manage/kernel-soft-reboot I receive the error message that the cluster is in mixed mode but this is not the case, Cluster Feature Level and UBR Level are the same on all nodes. Can anyone produce this? CAU with KSR works fine when used by WAC, so I wonder why the output from the PowerShell Set-CAUClusterRole on Azure Stack HCI 22H1 and 22H2 throws this message. Get-Cluster | Set-ClusterParameter -Name CauEnableSoftReboot -Value 1 -Create PS C:\Users\Administrator.Corp> Set-CauClusterRole -AttemptSoftReboot Are you sure? Do you want to set parameters for the Cluster-Aware Updating clustered role on cluster "ASClus01"? [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y WARNING: Ignoring SuspendRetriesPerNode as it is not supported on specified cluster. Cluster is in mixed mode, not all nodes support SuspendRetriesPerNode WARNING: Ignoring WaitForStorageRepairTimeoutMinutes as it is not supported on specified cluster. Cluster is in mixed mode, not all nodes support WaitForStorageRepairTimeoutMinutesAzure Stack HCI, 2306 Supplemental Package (preview) - WAC Lite no longer accessible aft. deployment
As mentioned in the other posting, how the output of WAC Lite and XML based output could be improved in the future. The idea of using WAC Lite for the deployment progress seems to get a bit odd after the Azure Stack "cloud deployment" has finished successfully. progress output on the seeding node VERBOSE: Action plan execution completed for action plan 'CloudDeployment'. - 9/8/2023 5:45:18 AM VERBOSE: Action: Action plan reached terminal state due to one of the steps. Finish running all remaining steps that may still be currently in progress before exiting. - 9/8/2023 5:45:18 AM VERBOSE: Action: Action plan 'CloudDeployment' completed. - 9/8/2023 5:45:18 AM XML based progress output 0.35.1.1 Success Disable Remote DeskTop on hosts 2023-09-08T03:40:54.658214Z 2023-09-0... 0.35.1.2 Success Rename built-in Administrator on hosts 2023-09-08T03:42:15.8314445Z 2023-09-0... 0.36 Success [Security] FinalizeHostEncryption 2023-09-08T03:43:36.0574408Z 2023-09-0... 0.36.1 Success Parallel per-node operation top step 2023-09-08T03:43:36.0705138Z 2023-09-0... 0.36.1.1 Success Finalize Bitlocker Encryption on host boot volume 2023-09-08T03:43:36.1313787Z 2023-09-0... 0.36.1.1 Success Finalize Bitlocker Encryption on host boot volume 2023-09-08T03:43:36.1110164Z 2023-09-0... 0.37 Success Clean up temporary content 2023-09-08T03:44:56.4865401Z 2023-09-0... 0.37.10 Success MarkNodeProvisioningStatus 2023-09-08T03:44:56.5174646Z 2023-09-0... 0.37.10.1 Success MarkPhysicalMachineStatusComplete 2023-09-08T03:44:56.5335751Z 2023-09-0... 0.37.10.2 Success MarkPhysicalMachineStatusComplete 2023-09-08T03:44:56.6596832Z 2023-09-0... 0.37.20 Success CleanUpSeedNodeSpace 2023-09-08T03:44:56.7857443Z 2023-09-0... 0.37.40 Success ResetECEStoreCredentials 2023-09-08T03:45:02.064136Z 2023-09-0... 0.37.50 Success ResetLocalAdminAccount 2023-09-08T03:45:10.3813749Z 2023-09-0... WAC Lite Dev Tools view issue: the user is not able to view the final status and overview, nor having the ability to download the things, previously provided in WAC Lite. I believe this behaviour is not intented, is it?Azure Stack HCI, 2306 Supplemental Package (preview) - discrepancy between progress
Fetching the deployment status via XML file is much more readable and precise compared to what you'll see on WAC Lite. Example of how to fetch the status from a management host using the seeding node: Invoke-Command -ComputerName $SeedNode -ScriptBlock { >> ([xml](Get-Content C:\ecestore\efb61d70-47ed-8f44-5d63-bed6adc0fb0f\086a22e3-ef1a-7b3a-dc9d-f407953b0f84)) | Select-Xml -XPath "//Action/Steps/Step" | ForEach-Object { $_.Node } | Select-Object FullStepIndex, Status, Name, StartTimeUtc, EndTimeUtc, @{Name="Duration";Expression={new-timespan -Start $_.StartTimeUtc -End $_.EndTimeUtc } } | Format-Table -AutoSize >> } Deployment Status as seen in WAC Lite: Deployment Status as seen with given PowerShell XML output: FullStepIndex Status Name StartTimeUtc EndTimeUt c ------------- ------ ---- ------------ --------- 0 InProgress Cloud Deployment 2023-09-08T02:25:08.8344395Z 0.1 Success Before Cloud Deployment 2023-09-08T02:25:11.4559195Z 2023-0... 0.1.1 Success EnvironmentValidatorFull 2023-09-08T02:25:11.5027893Z 2023-0... 0.1.1.0 Success Azure Stack HCI Connectivity 2023-09-08T02:25:11.5183762Z 2023-0... 0.1.1.1 Success Azure Stack HCI Bitlocker 2023-09-08T02:25:47.2214407Z 2023-0... 0.1.1.2 Success Azure Stack HCI External Active Directory 2023-09-08T02:25:48.2371459Z 2023-0... 0.1.1.3 Success Azure Stack HCI Hardware 2023-09-08T02:26:27.5758371Z 2023-0... 0.1.1.4 Success Azure Stack HCI Network 2023-09-08T02:26:29.2164686Z 2023-0... 0.1.1.5 Success Azure Stack HCI Observability 2023-09-08T02:26:30.294631Z 2023-0... 0.1.1.6 Success Azure Stack HCI Software 2023-09-08T02:26:36.5457993Z 2023-0... 0.1.1.7 Success Azure Stack HCI MOC Stack 2023-09-08T02:26:41.2576857Z 2023-0... 0.1.1.8 Success Azure Stack HCI Arc Integration 2023-09-08T02:26:50.2757153Z 2023-0... 0.1.2 Success SetPrerequisitesForDeployment 2023-09-08T02:27:18.9414396Z 2023-0... 0.1.3 Success SetPrerequisitesForDeployment 2023-09-08T02:27:27.249078Z 2023-0... 0.1.4 Success DisableWindowsUpdateServiceOnAllHosts 2023-09-08T02:27:35.6241222Z 2023-0... 0.1.4.1 Success Parallel per-node operation top step 2023-09-08T02:27:35.6552969Z 2023-0... 0.1.4.1.1 Success DisableWindowsUpdateService 2023-09-08T02:27:35.6552969Z 2023-0... 0.1.4.1.1 Success DisableWindowsUpdateService 2023-09-08T02:27:35.6709951Z 2023-0... 0.1.5 Success SetCloudEnvironmentVariablesOnAllHosts 2023-09-08T02:27:44.5330797Z 2023-0... 0.1.5.1 Success Parallel per-node operation top step 2023-09-08T02:27:44.5487005Z 2023-0... 0.1.5.1.1 Success SetCloudEnvironmentVariables 2023-09-08T02:27:44.5799769Z 2023-0... 0.1.5.1.1 Success SetCloudEnvironmentVariables 2023-09-08T02:27:44.5642973Z 2023-0... 0.1.6 Success Parallel per-node operation top step 2023-09-08T02:27:53.1893504Z 2023-0... 0.1.6.1 Success InstallOSCustomization 2023-09-08T02:27:53.2205614Z 2023-0... 0.1.6.1.0 Success LiveUpdateRegistryKeys 2023-09-08T02:27:53.2518641Z 2023-0... 0.1.6.1.1 Success Install windowsfeatures with restart 2023-09-08T02:28:03.5906765Z 2023-0... 0.1.6.1.2 Success Install windowsfeatures without restart 2023-09-08T02:28:30.9098956Z 2023-0... 0.1.6.1.3 Success LiveUpdateWindowsFeatures 2023-09-08T02:29:08.5907581Z 2023-0... 0.1.6.1 Success InstallOSCustomization 2023-09-08T02:27:53.2049765Z 2023-0... 0.1.6.1.0 Success LiveUpdateRegistryKeys 2023-09-08T02:27:53.2362201Z 2023-0... 0.1.6.1.1 Success Install windowsfeatures with restart 2023-09-08T02:28:03.0595019Z 2023-0... 0.1.6.1.2 Success Install windowsfeatures without restart 2023-09-08T02:28:29.9880426Z 2023-0... 0.1.6.1.3 Success LiveUpdateWindowsFeatures 2023-09-08T02:29:14.318046Z 2023-0... 0.1.7 Success Flush Progress Before Reboot 2023-09-08T02:30:32.6716905Z 2023-0... 0.1.8 Success Restart host node 2023-09-08T02:30:32.6716905Z 2023-0... 0.1.9 Success Flush Progress Before Reboot 2023-09-08T02:31:39.2342427Z 2023-0... 0.1.10 Success Restart host node 2023-09-08T02:31:39.2497477Z 2023-0... 0.1.11 Success Parallel per-node operation top step 2023-09-08T02:34:51.8859374Z 2023-0... 0.1.11.1 Success ValidateWindowsFeatureInstallation 2023-09-08T02:34:51.9170717Z 2023-0... 0.1.11.1 Success ValidateWindowsFeatureInstallation 2023-09-08T02:34:51.9015009Z 2023-0... 0.1.12 Success InstallOSUpdates 2023-09-08T02:36:08.4943378Z 2023-0... 0.1.12.1 Success PrepareOsUpdatesFromSeedNode 2023-09-08T02:36:08.525665Z 2023-0... 0.1.12.2 Success Parallel per-node operation top step 2023-09-08T02:36:12.8105575Z 2023-0... 0.1.12.2.1 Success CopyOsUpdatesFromSeedNode 2023-09-08T02:36:12.8417176Z 2023-0... 0.1.12.2.2 Success InstallOsUpdatesFromNode 2023-09-08T02:36:15.6232297Z 2023-0... 0.1.12.2.3 Success CleanupOsUpdatesFromNode 2023-09-08T02:42:46.1372654Z 2023-0... 0.1.12.2.1 Success CopyOsUpdatesFromSeedNode 2023-09-08T02:36:12.8260575Z 2023-0... 0.1.12.2.2 Success InstallOsUpdatesFromNode 2023-09-08T02:36:16.4201Z 2023-0... 0.1.12.2.3 Success CleanupOsUpdatesFromNode 2023-09-08T02:42:40.6974386Z 2023-0... 0.1.12.3 Success RestartHostNode 2023-09-08T02:42:49.5129135Z 2023-0... 0.1.12.4 Success RestartHostNode 2023-09-08T02:43:53.8356468Z 2023-0... 0.1.13 Success Parallel per-node operation top step 2023-09-08T02:47:09.0400405Z 2023-0... 0.1.13.1 Success Expand Live Update Content 2023-09-08T02:47:09.1180454Z 2023-0... 0.1.13.1 Success Expand Live Update Content 2023-09-08T02:47:09.0867606Z 2023-0... 0.1.14 Success Install Role Nugets 2023-09-08T02:52:42.3352209Z 2023-0... 0.1.15 Success Setup Observability Volume 2023-09-08T02:55:17.8476392Z 2023-0... 0.1.15.0 Success Register Observability EventSource 2023-09-08T02:55:17.8632574Z 2023-0... 0.1.15.1 Success Setup Observability Volume 2023-09-08T02:56:46.1241375Z 2023-0... 0.1.15.2 Success Create Observability Subfolders and Volume Pruner 2023-09-08T02:57:02.1051668Z 2023-0... 0.1.15.3 Success Setup UTC Exporter Feature 2023-09-08T02:57:12.4645786Z 2023-0... 0.1.15.4 Success Install VC Redistributable 2023-09-08T02:57:30.4020852Z 2023-0... 0.1.15.5 Success Setup uptime scheduled task 2023-09-08T02:57:40.4802871Z 2023-0... 0.1.15.6 Success Setup census event scheduled task 2023-09-08T02:57:49.8597304Z 2023-0... 0.1.15.7 Success Setup registration events task 2023-09-08T02:58:01.109813Z 2023-0... 0.1.15.8 Success Set DeviceType Registry Key 2023-09-08T02:58:12.6163635Z 2023-0... 0.1.16 Success Installs Bootstrap Observability 2023-09-08T02:58:17.9757357Z 2023-0... 0.1.16.0 Success Set DeviceType Registry Key 2023-09-08T02:58:17.991366Z 2023-0... 0.1.16.1 Success Set GMATenantJsonRegistryKeys 2023-09-08T02:58:23.2726161Z 2023-0... 0.1.16.2 Success Install Arc for server agent and extensions 2023-09-08T02:58:32.1021905Z 2023-0... 0.1.17 Success EnableFirewallPortsOnAllHosts 2023-09-08T03:05:39.7284057Z 2023-0... 0.1.17.1 Success Parallel per-node operation top step 2023-09-08T03:05:39.7753087Z 2023-0... 0.1.17.1.1 Success EnableFirewallPorts 2023-09-08T03:05:39.8221865Z 2023-0... 0.1.17.1.1 Success EnableFirewallPorts 2023-09-08T03:05:39.7908975Z 2023-0... 0.1.18 Success ResizeSystemDriveOnAllHosts 2023-09-08T03:05:52.3366318Z 2023-0... 0.1.18.1 Success Parallel per-node operation top step 2023-09-08T03:05:52.3522608Z 2023-0... 0.1.18.1.1 Success ResizeSystemDrive 2023-09-08T03:05:52.3991337Z 2023-0... 0.1.18.1.1 Success ResizeSystemDrive 2023-09-08T03:05:52.383508Z 2023-0... 0.1.19 Success AddDSCCertificateOnHost 2023-09-08T03:06:03.0663753Z 2023-0... 0.1.20 Success UpdateStampInformation 2023-09-08T03:06:10.3188924Z 2023-0... 0.1.20.1 Success Parallel per-node operation top step 2023-09-08T03:06:10.3345329Z 2023-0... 0.1.20.1.1 Success Update Stamp Information 2023-09-08T03:06:10.3814005Z 2023-0... 0.1.20.1.1 Success Update Stamp Information 2023-09-08T03:06:10.365804Z 2023-0... 0.2 Success Validate network settings for servers 2023-09-08T03:06:16.287882Z 2023-0... 0.2.1 Success ValidateEceHostNetworkSettings 2023-09-08T03:06:16.3033268Z 2023-0... 0.3 Success Configure settings on servers 2023-09-08T03:06:27.3136903Z 2023-0... 0.3.1 Success ConfigureAzureStackHostsPreConfig 2023-09-08T03:06:27.4388217Z 2023-0... 0.4 Success AutoScale VirtualMachines 2023-09-08T03:06:30.5793357Z 2023-0... 0.5 Success Apply security settings on servers 2023-09-08T03:06:30.7668229Z 2023-0... 0.5.1 Success Parallel per-node operation top step 2023-09-08T03:06:30.7824524Z 2023-0... 0.5.1.1 Success Prepare SecurityBaseline Metadata 2023-09-08T03:06:30.829403Z 2023-0... 0.5.1.2 Success Enforce SecurityBaseline 2023-09-08T03:06:33.9699516Z 2023-0... 0.5.1.3 Success Enforce SecuredCore 2023-09-08T03:06:44.8491817Z 2023-0... 0.5.1.4 Success Configure OSConfig DriftControl 2023-09-08T03:06:48.7241873Z 2023-0... 0.5.1.1 Success Prepare SecurityBaseline Metadata 2023-09-08T03:06:30.8137493Z 2023-0... 0.5.1.2 Success Enforce SecurityBaseline 2023-09-08T03:06:33.8606136Z 2023-0... 0.5.1.3 Success Enforce SecuredCore 2023-09-08T03:06:43.411684Z 2023-0... 0.5.1.4 Success Configure OSConfig DriftControl 2023-09-08T03:06:47.0367128Z 2023-0... 0.6 Success Flush Progress Before Reboot 2023-09-08T03:06:51.5836192Z 2023-0... 0.7 Success Join servers to a domain 2023-09-08T03:06:51.5991867Z 2023-0... 0.7.1 Success Deploy AD and domain join physical machines 2023-09-08T03:06:51.6304755Z 2023-0... 0.7.1.1 Success Add host to domain 2023-09-08T03:06:52.567935Z 2023-0... 0.7.1.2 Success Add host membership to security groups 2023-09-08T03:10:35.9829234Z 2023-0... 0.8 Success Deploy JEA endpoints on the host 2023-09-08T03:10:42.1090313Z 2023-0... 0.8.1 Success Parallel per-node operation top step 2023-09-08T03:10:42.1558589Z 2023-0... 0.8.1.1 Success Update Baremetal JEA endpoints 2023-09-08T03:10:42.202733Z 2023-0... 0.8.1.2 Success Update Baremetal JEA endpoints 2023-09-08T03:10:48.953369Z 2023-0... 0.8.1.2.1 Success Update Baremetal JEA endpoints 2023-09-08T03:10:49.0626434Z 2023-0... 0.8.1.1 Success Update Baremetal JEA endpoints 2023-09-08T03:10:42.187093Z 2023-0... 0.8.1.2 Success Update Baremetal JEA endpoints 2023-09-08T03:10:50.5939981Z 2023-0... 0.8.1.2.1 Success Update Baremetal JEA endpoints 2023-09-08T03:10:50.7191111Z 2023-0... 0.9 Success ConfigCluster 2023-09-08T03:11:31.2731412Z 2023-0... 0.9.1 Success ConfigCluster 2023-09-08T03:11:31.3826336Z 2023-0... 0.9.2 Success ConfigWitness 2023-09-08T03:14:13.3245004Z 2023-0... 0.10 Success Configure cluster networking requirements 2023-09-08T03:14:16.824566Z 2023-0... 0.10.1 Success Start ATC tracing 2023-09-08T03:14:16.8562837Z 2023-0... 0.10.2 Success Configure host networking requirements 2023-09-08T03:14:20.2627417Z 2023-0... 0.10.3 Success Configure hosts adapter IP addresses 2023-09-08T03:18:20.497262Z 2023-0... 0.10.4 Success Validate ATC service 2023-09-08T03:18:23.8653905Z 2023-0... 0.10.5 Success Validate Host Reachability 2023-09-08T03:18:41.2113366Z 2023-0... 0.10.6 Success Stop ATC tracing 2023-09-08T03:18:49.7291644Z 2023-0... 0.11 Success Register with Azure 2023-09-08T03:18:54.5427914Z 2023-0... 0.11.1 Success RegisterStamptoAzure 2023-09-08T03:18:54.5740379Z 2023-0... 0.12 Success UnlockVirtualDisks 2023-09-08T03:25:46.2502502Z 2023-0... 0.12.0 Success Enable S2D for repair 2023-09-08T03:25:46.3283738Z 2023-0... 0.12.1 Success Unlock Enctypted VirtualDisks 2023-09-08T03:25:51.8598104Z 2023-0... 0.13 Success ConfigStorage 2023-09-08T03:25:53.7191889Z 2023-0... 0.13.1 Success ConfigStorage 2023-09-08T03:25:53.7503781Z 2023-0... 0.14 Success RepairCSVsExternalKeyProtectors 2023-09-08T03:27:34.5590147Z 2023-0... 0.14.0 Success Repair Encrypted CSVs External Key Protectors 2023-09-08T03:27:34.6058889Z 2023-0... 0.15 Success EncryptCSVs 2023-09-08T03:27:36.8558855Z 2023-0... 0.16 Success EncryptHostsOSVolumes 2023-09-08T03:27:40.5121677Z 2023-0... 0.17 Success MitigateForClusterGenericService 2023-09-08T03:27:42.0435738Z 2023-0... 0.18 Success Set up certificates 2023-09-08T03:27:51.2019195Z 2023-0... 0.18.0 Success Install ASCA and Set Up External Certficates 2023-09-08T03:27:51.2487492Z 2023-0... 0.18.0.0 Success StageAndGenerateCertificates 2023-09-08T03:27:53.4987664Z 2023-0... 0.18.0.0.0 Success Generate certificates 2023-09-08T03:27:53.5300089Z 2023-0... 0.18.0.0.1 Success Publish artifacts 2023-09-08T03:28:00.4055286Z 2023-0... 0.19 Success Copy Artifacts 2023-09-08T03:28:03.9995672Z 2023-0... 0.20 Success Refresh Active Directory permissions 2023-09-08T03:28:13.8277691Z 2023-0... 0.20.1 Success Parallel per-node operation top step 2023-09-08T03:28:13.8433192Z 2023-0... 0.20.1.1 Success PurgeLocalMachineTicket 2023-09-08T03:28:13.9058177Z 2023-0... 0.20.1.1 Success PurgeLocalMachineTicket 2023-09-08T03:28:13.8901953Z 2023-0... 0.21 InProgress Switch Observability Watchdog to Listener mode 2023-09-08T03:28:21.5785007Z 0.21.0 InProgress Evaluate GMA Configuration type 2023-09-08T03:28:21.5940174Z 0.21.0.1 InProgress Parallel per-node operation top step 2023-09-08T03:28:23.2660084Z 0.21.0.1.1 InProgress Switch Observability Watchdog to Listener mode 2023-09-08T03:28:23.4065185Z 0.21.0.1.2 Stop Arc Extension Observability Agent 0.21.0.1.3 Stop Env Checker and Arc Extension Remote Support Agent 0.21.0.1.1 InProgress Switch Observability Watchdog to Listener mode 2023-09-08T03:28:23.3753356Z 0.21.0.1.2 Stop Arc Extension Observability Agent 0.21.0.1.3 Stop Env Checker and Arc Extension Remote Support Agent 0.22 Install Agent Lifecycle Manager Nuget 0.23 Deploy Agent Lifecycle Manager 0.24 Migrate deployment orchestrator service 0.25 SeedSBE 0.26 Apply WDAC on hosts 0.27 Configure UpdateURI in Update service 0.28 CloudDeployment Expand 0.29 UpdateSBE 0.30 PreCheck for DeployMOCStack 0.31 EnvironmentValidatorReplayResult 0.32 Send Telemetry from cached files 0.33 Enable SMB Encryption 0.34 Migrate deployment orchestrator service 0.35 [Security] FinalizeHostSecurity 0.36 [Security] FinalizeHostEncryption 0.37 Clean up temporary content I would love if WAC Lite would simply just do the same fetching the XML output and render it in HTML, rather than having its own style of output on the deployment progress, especially since the XML based output is more precise and quite more verbose and gives a better UX to the user in terms of current steps and steps remaining in the process. Secondly, I believe this would make future changes obsolete in the WAC Lite progress view. In the XML view the column "description" could be added as done in WAC Lite with the user-friendly description each task.verbose spam in Azure Stack HCI, 2306 Supplemental Package (preview) - 'Networkhelpers'
I am deploying Azure Stack HCI in a lab using MSlab using the Supplemental Package 2306 preview. using this MSLab configuration Not looking for support, rather sharing feedback on my experience with this release. Everything runs as expected. When starting the script on the AzNode1, Task 5 - Step 3 https://github.com/DellGEOS/AzureStackHOLs/tree/main/lab-guides/08-DeployAzureStackHCICluster-DeploymentTool The verbose output first indicated a problem with importing of module az.accounts but no error just that it is in use and cannot be updated. Later the verbose output is spamming this, which is apparently an issue that occours because the import of a module did not use allow clobber? expectation: MSFT team please try to replicate and see if you find the issue for this, so the verbose output could be drastically reduced. WARNING: 2> [BareMetal:EnableWindowsFeaturesWithRebootRequirement] The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. - 9/8/2023 4:28:08 AM OR SIMILAR such as The names of some imported commands from the module 'NetworkHelpers' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. - 9/8/2023 4:43:47 AM
Panel Discussion on Azure Stack Hub Billing
Hi All, Are you interested in exploring our client's achievements in optimizing Azure Stack Hub billing with Hybr® and overcoming billing challenges during our scheduled panel discussion on September 28th, 2023? Additionally, are there specific topics or areas related to Azure Stack Hub billing that you'd like us to address during the panel? We're keen to understand if this discussion aligns with the interests of you and your clients. Please share your thoughts and preferences; we're looking forward to your input! https://www.cloudassert.com/Resources/Webinar/azure-stack-hub-billing-with-hybrSurvey/sweepstakes for Windows Admin Center & Azure Stack HCI
If you have experience using Windows Admin Center to manage Azure Stack HCI clusters, the HCI team would like to hear your feedback about the tools you use to manage your clusters! Take this survey: https://aka.ms/hcitc for a chance to win one of three $350 USD virtual gift cards. Microsoft and public sector employees, and residents of a few countries are not eligible to receive gift cards. Must be 18 or older. Survey ends January 22, 2023. Rules: https://aka.ms/AzSHCISweepstakesRules Your feedback will influence the roadmap for Azure Stack HCI management in WAC and Azure. Survey link -> https://aka.ms/hcitc Thanks! -The Azure Stack HCI Team
Linux with Db2 cluster on Azure Stack Limitation
We are using Linux based IAAS compute service with 2 or more Db2 and GPFS nodes setup in Active / Standby mode. Here the cluster fail-over mechanism needs a VIP which I assume is not available on Azure Stack Hub. In the Azure public cloud, the backend cluster uses the automatic script via Azure CLI to update private DNS zone and A record with CNAME to promote the Master / Active node during the fail-over process. Is that correct that the Private DNS zone services unavailable on Azure Stack Hub hence we can't form a cluster like this. I read on the Azure Stack Hub DNS article that we have an internal zone as azurestack.local that's used for infrastructure services in Azure Stack Hub. It's Directory Service-integrated and private (not reachable from outside the Azure Stack Hub deployment). But this recursive server is used to resolve names of everything except for the "internal private zone" and the external public DNS zone for that Azure Stack Hub deployment. What is the workaround or solution to resolve our issue for private DNS zone.
