Proactive private share #microsoft
Many comapanies is part of my job last two year. I desade to implement and create new public communty group at microsoft, with public share. Like universal patch insade giant org and partner companes ,microsoft deside lead postiton. Proacticve and future plan is constructed to grow on world network with client and our partners[server 25314] External SET Team to Internal after Reboot.
I have created SET Teaming on Windows Server 25314 (actually from a previous build) using External and 3 Intel i350-T4 ports, configured for Hyper-V and external access. New-VMSwitch -Name SETSwitch -NetAdapterName "i350t4_1","i350t4_2","i350t4_3" -AllowManagementOS $true -EnableEmbeddedTeaming $true -EnableIov $true Set-VMSwitchTeam -Name SETSwitch -LoadBalancingAlgorithm Dynamic In that case, the Hyper-V VM and OS can be accessed normally, but when I restart Windows Server, all Adapters disappear from SET Teaming and are changed to the Internal setting, and network access is lost. The above logs were obtained at WPR with Profile in Network. Since the file is large, I will post a link to OneDrive. setTeamingTrouble.etl https://1drv.ms/u/s!AoGvAA_XXMTH-dJ2gkOa6E5hP4QhLg?e=7hPgLQ In addition, if the EnableIov option is set to $false, a BSOD (KMODE_EXCEPTION_HANDLED) will occur after the Switch is created. VMSWITCH.SYS 0x0000007e (0xffffffffc0000005, 0xfffff80643a95c61, 0xffffb28989f2a6d8, 0xffffb28989f29ef0) Addition 2: LBFO Teaming is working properly. I tried to send it through the Feedback Hub and could not get it to work, so I have included it here. Addition 3: Server 25324 LBFO Teaming with New-VMSwitch failed.
Windows Server 2022 or 2025 Data Centre edition- concurrent editing of Microsoft office documents
Does Windows Server 2022 or 2025 Data Centre edition provide real time collaboration or concurrent editing (through workspaces etc) by multiple users on Microsoft office documents hosted on it locally. So for the sole purpose of having concurrent editing feature of office documents, can Windows Server 2022 or 2025 Data Centre edition become an alternative to using Sharepoint server hosted locally or on premise.
Problems to join Debian/Ubuntu machines to a domain
Is not posible to join Debian/Ubuntu machines to a domain based on Windows Server 2025 (using realm at least) this is the error: ! Couldn't set password for computer account: XXXX$: Message stream modified adcli: joining domain xxxx.local failed: Couldn't set password for computer account: XXXX$: Message stream modified ! Failed to join the domain realm: Couldn't join realm: Failed to join the domain Domain is discoverable vía realm: root@lnms01:/home/administrator# realm discover xxxx.local xxxx.local type: kerberos realm-name: XXXX.LOCAL domain-name: xxxx.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss Tested on WS2025 build 26227 and Linux 6.1.0-21-amd64 x86_64, Linux 6.6.31+rpt-rpi-v8 aarch64 and Linux 6.8.0-31-generic x86_64. Those 3 versions of Linux joined to another doman based con Windows Server 2022 without issues.WAC - Server not addable from AD
Hi, i installed actual WAC public preview with my domain account (local admin) on a Server 2025 (26257). When i start WAC and i want to add window Server i can´t search Active Directory, because it says: "We can’t search Active Directory because the Windows Admin Center computer isn’t joined to an Active Directory domain. It’s also possible that your account doesn’t have permission to read from Active Directory." Can you help, because server is domain joined. SPN is also set on AD Computer Account with http/admincenter.domain.internal.
[Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
I have installed 20303.1 and added the SMTP Service and add the management tools. Install-WindowsFeature SMTP-Server -IncludeManagementTools After the installation, I bring up the IIS 6 Management Console. If I right-click the [SMTP Virtual Server] node and select properties, I get an error like this: Clues?b26085 - Windows Server 2025 Domain Controller fail to deploy via DSC
Hi there, I am trying to deploy mslab using Windows Server 2025 preview VM using Windows Server 2025 OS as a Hyper-V platform. I believe Jaromir as maintainer of mslab opened an SR. In result he updated the code, plus PS DSC Modules. edit: this issue is unrelated to the running SR. Still the deployment of the domain controller template will fail during first boot. This is not specific to b26085, this one is troubling for since WS2025 insider, so it never worked with this branch. Repro steps Install Windows Server 2025 b26085.1 on a physical machine and enable Hyper-V Download and extract mslab https://github.com/microsoft/MSLab/releases/tag/v24.04.1 run the mslab scripts in order 1_Prereq 2_CreateParentDisks > select Windows Server 2025 ISO b26085 (WS 2022 ISO will work) > skip the MSU dialogue Domain Controller VM gets created from parent disk image First boot will fail with following error Creating DC VM Applying Unattend and copying Powershell DSC Modules PSPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir PSParentPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp PSChildName : MountDir PSDrive : J PSProvider : Microsoft.PowerShell.Core\FileSystem PSIsContainer : True Name : MountDir FullName : J:\mslab_v24.04.1\Temp\MountDir Parent : Temp Exists : True Root : J:\ Extension : CreationTime : 21.04.2024 13:20:16 CreationTimeUtc : 21.04.2024 11:20:16 LastAccessTime : 21.04.2024 13:20:16 LastAccessTimeUtc : 21.04.2024 11:20:16 LastWriteTime : 21.04.2024 13:20:16 LastWriteTimeUtc : 21.04.2024 11:20:16 Attributes : Directory Mode : d----- BaseName : MountDir Target : {} LinkType : Path : J:\mslab_v24.04.1\Temp\MountDir Online : False Path : J:\mslab_v24.04.1\Temp\MountDir Online : False PSPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir\Windows\Panther PSParentPath : Microsoft.PowerShell.Core\FileSystem::J:\mslab_v24.04.1\Temp\MountDir\Windows PSChildName : Panther PSDrive : J PSProvider : Microsoft.PowerShell.Core\FileSystem PSIsContainer : True Name : Panther FullName : J:\mslab_v24.04.1\Temp\MountDir\Windows\Panther Parent : Windows Exists : True Root : J:\ Extension : CreationTime : 21.04.2024 13:20:22 CreationTimeUtc : 21.04.2024 11:20:22 LastAccessTime : 21.04.2024 13:20:22 LastAccessTimeUtc : 21.04.2024 11:20:22 LastWriteTime : 21.04.2024 13:20:22 LastWriteTimeUtc : 21.04.2024 11:20:22 Attributes : Directory Mode : d----- BaseName : Panther Target : {J:\Windows\Panther} LinkType : Creating DSC Configs for DC LastWriteTime : 21.04.2024 13:20:23 Length : 1206 Name : DC.meta.mof LastWriteTime : 21.04.2024 13:20:25 Length : 32600 Name : DC.mof Copying DSC configurations (pending.mof and metaconfig.mof) Applying changes to VHD LogPath : C:\WINDOWS\Logs\DISM\dism.log ScratchDirectory : LogLevel : WarningsInfo Starting DC Configuring DC using DSC takes a while. Initial configuration in progress. Sleeping 250 seconds Question: What could be reasons it keeps failing? We have no clue / pointers and imho it would be expected and necessary that mslab works with WS2025, despite being preview, too. Who at Microsoft could afford time to repro and looking into that? As mslab is also used by Microsoft, I hope anyone could spare time to investigate (with Jaromir and/or me). I personally can spare time for that investigation. Thank you very much in advance!
