Windows 365 and Azure Virtual Desktop sessions at the Microsoft Technical Takeoff
The next iteration of the Microsoft Technical Takeoff is coming up quick. Four days of in depth sessions, demos, roadmap and Q&A are coming up on Monday March the 3rd to Thursday the 6th. This is a great learning event where we in the Microsoft engineering and product groups go deep on a whole host of topics, from Windows, Azure Virtual Desktop, Intune and Windows365. For those specifically interested in Windows 365 and Azure Virtual Desktop then this is the ultimate short list of sessions. Please click on the link for the session below and then click on the Attend button, (times below are in PST). To access the full site with the entire agenda and session list just visit: aka.ms/TechnicalTakeoff Windows 365 and Azure Virtual Desktop Monday, March 3, 2025 8:30 AM - The path ahead: The roadmap for Windows in the cloud 10:30 AM - Understanding security and management on Windows 365 Link 11:00 AM - Unlocking productivity on the frontline with Windows 365 Tuesday, March 4, 2025 10:30 AM - Skill up! Cloud PC management and reporting 11:00 AM - Get to know Windows security and resiliency in the cloud Wednesday, March 5, 2025 9:30 AM - Enhancing resiliency with Windows 365 10:30 AM - Delivering like-local Windows experiences from the cloud Thursday, March 6, 2025 7:00 AM - Azure Virtual Desktop app management 7:30 AM - Azure Virtual Desktop hostpool management at scale 11:00 AM - Windows cloud migration and deployment best practices
Kerberos KDC Errors
Hello, I have been testing Windows Server 2025 with AD DC role and sometimes in event log I can see error. The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was and lookup type 0x108. Just a note - I did not remove the account name; it is not just there, not even once. I'm unable to connect it to some "action", so it looks a bit random. In data field there is only C000000D (in words) which is every time the same. Event ID is 7. Is this okay or anything to worry about?
RAM Memory Leak Issue
Good morning. I am experiencing issues with an updated installation of Windows Server 2016. The task manager reports 8.1GB of memory used (which normally tends to grow indefinitely), and I can't figure out what is using this memory. The growth is about 1GB per day. However, no processes appear that justify the 8GB of RAM used. Even using RAMMAP, I can't find anything significant... On the server, additionally, we have SentinelOne as antivirus and Apache-Tomcat. Thank you for your help.Windows 365 now supported in Japan West
Today I am pleased to announce that we have enabled a second region in Japan to deploy Windows 365 Cloud PC’s. You can now deploy your Cloud PCs into the Japan West Azure region in addition to the existing Japan East region. Within a provisioning policy if you select the Japan geography, you can then select Japan West. This increases the number of regions available to the Windows 365 service when you select the “Automatic” region option of Japan. We always recommend using the Automatic region option when using the Microsoft Hosted Network network type. In the future we will be making some exciting improvements to the provisioning of Cloud PCs by simplifying the region and network selection within your provisioning policies. This expansion increases the number of Azure geographies that Windows 365 supports, giving you more choices for locating your Cloud PCs. This means you can place them closer to your user estate, reducing latency for users in these locations. We are committed to providing more choice and flexibility for your Cloud PCs by enabling new Azure regions over the coming years. This ongoing expansion demonstrates our dedication to evolving the service into a truly global service by growing into existing and new Azure geographies, ensuring you can provide the best service to your organization. Stay tuned for more updates as we continue to enhance Windows 365 and bring it to more locations worldwide.
Remove, Hide, or Relocate the Connection Bar in Windows App when in Full Screen on Cloud PC
When using Cloud PC in full screen mode the connection bar always pops up. It's not Pinned so it auto hides. This issue is the bar pops up anytime the mouse is on top of screen. When using a browser, for example, to navigate to a different tab the user has to mouse to top of the screen. This mouse movement pops up the Connection bar which is VERY invasive and blocks a large portion of the top screen which blocks the browsers tabs. Users have to shift this left/right every time or move the mouse away (wait till it disappears) then hope they have better aiming to click on tab without bringing curser to top of screen... or else the annoying Connection bar pops up. Is there ANY method to be able to any of the these Relocate the connection bar to left side screen (right side interferes with up/down scroll) Delay the connection bar popup for few seconds (mouse on top of screen few seconds to show connection bar) Or permanently remove it and use Windows hotkeys to break out of Full Screen mode Any other idea...
Teams addin missing in Classic outlook in Azure virtual desktop
Hello Everyone! We have both classic and new teams installed. Since we have updated our AVD machines with the new image, we noticed that it does not have the Teams add-in in classic Outlook. We already checked in com-addins, but Teams was not listed there. Can you please explain how we can get the Teams Addin back in the classic Outlook? We are using the source image plan "win11-23h2-avd-m365," which has this issue. Do any of you also face the same issue?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.
