User Profile
-_RH_-
Steel Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: WAC 2211 Error: Cannot read properties of undefined (reading 'toLocaleLowerCase')
MHinloopenI'm seeing the same as well. I've used this previously, so I'm not sure when this started (possibly with the June Windows updates?). Enabling/disabling CredSSP has no impact. The issue seems to be present in all of the following versions: WAC 2211 WAC 2306 Cluster Manager extension 2.251.0 Cluster Manager extension 2.263.01.9KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
MI5-AgentI hear you, especially on not being able to upgrade to the latest OS until 1-2 years after release, so 5 years is reduced to 3-4 in the real world. In fairness to Microsoft, 5 years mainstream support has been their standard for quite some time, though software support has usually continued into the extended support period rather than dropping once mainstream support ends. However, 5 years support is better than none at all and being forced to W365 or AVD. I think as customers we're caught between the waterfall/traditional licensed OS and ~agile/subscription licensed application worlds. I could be wrong, but I get the impression that, while Microsoft dogfoods their own software, they don't dogfood their own licensing and experience the same licensing conundrums their customers face. Perhaps a more continuous upgrade model OS like Azure Stack HCI could resolve the issue in the long run, though that doesn't help much today.3.3KViews1like0CommentsRe: Support for M365 Apps (O365) on Windows 2022
greatquuxEldenChristensenBernd DauschNote only2302or later is supported on Server 2022. The latest Semi-Annual Enterprise Channel release is 2208 and is NOT supported (at this time). The latest Monthly Enterprise Channel (2303) and Current Channel (2304) are supported.3.3KViews1like3CommentsRe: Support for M365 Apps (O365) on Windows 2022
HelloDeleted🙂 I think I follow what you're describing/speculating. It sounds like the forked management model plan is Client for customers, and Server primarily for... Microsoft itself (for Azure). Customers now also have access to those same Azure management tools (including on-premises via Azure Stack HCI and Arc), but while these controls may make sense for Microsoft's use, they don't really map that nicely to how customers managetheir servers. They are a subset of GPO/SCCM/CSP controls, and unless this is some hidden thing I've not yet stumbled across, some things simply can't be done because of that gap, such as applying Conditional Access controls based on Compliance status.4.4KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
DeletedThat misses the point: Microsoft could simply choose to provide CSP support in anything they want: they make all the Windows versions, including the LTSC versions. I don't think it's that simple anyway, as I'm pretty sure the non-LTSC versions of Server they've released don't have CSP support either.4.6KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
DeletedThat view seems to see it almost exclusively from the provider (software and hardware) side. From the customer side, the binding isn't technical, it's practical: e.g., small businesses running a single cluster for the majority of their workload simply can't upgrade that production system in place. It's far too risky.4.6KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
EldenChristensenThank you for asking for feedback here, Elden! Regarding the 5-year support cycle, one reason it's problematic is because by the time the hardware is certified for the new release, procured, shipped, and schedules align for the install, it's often already 18-24 months after the release. For smaller companies on a 5+ year replacement cycle, this puts a system out of support for about half of its life. When they have only one cluster, another challenge is migrating to Azure Stack at all. Realistically, it means new hardware (very difficult and risky to update their one cluster in production), but when the replacement cycle is 5+ years and given the hardware certification/procurement/etc. cycle, this new support uncertainty really puts them in a bind. They just can't afford to keep on the schedule Microsoft has in mind here, and for their use, there is little justification for new hardware otherwise.3.2KViews1like2CommentsRe: Support for M365 Apps (O365) on Windows 2022
Bernd Dausch Until now, yes, but it was only recently that Server support for O365 was in question. 100% agreed regarding cost vs. VDI. There are some workloads for which terminal server is a better solution. The alternative seems to be multi-user client, but as server and client still use the same core and the process of modularization of the OS has gone far, the main difference from Microsoft's standpoint seems to be licensing. However, from a customer's standpoint, as many here have pointed out, there are many practical implications (or perhaps more to the point, many impractical implications).3.1KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
It is unclear to me why multi-user client is significantly different from terminal server, other than licensing. However, one thing that is sorely lacking in Server is Intune support, and this isn't really answered by Azure Stack HCI, either (Azure Security Center/Defender for Cloud =/= Intune, and it makes little sense to spin up/maintain/skill up on a non-cloud Config Manager for cloud-first orgs). Want to apply Conditional Access Compliance policies for Server? Can't do it. The technical answer I've heard is "CSP support doesn't exist in Server," but that kind of skirts the question, as it's coming from the company that could easily choose to add it.3.2KViews1like4CommentsRe: Support for M365 Apps (O365) on Windows 2022
Günter Born Update: I tried updating to Current Channel today (previously was using Semi-Annual Channel; I tried the Semi-Annual Jan 10 update as well with no luck), and it appears to go blank (white for the whole content window) sometime after the first run, and as you mention, if you move/click or interact with Word it displays the content again. However, unlike Semi-Annual Channel version, it only seems to do this once, and then never again. I tried both 1920x1080 and 4k. It seems like it might be related to the "See what's coming soon" first launch stuff. However, unlike the DisablePreviewPlace reg value for Outlook, unfortunately there doesn't seem to be a corresponding value for Word.3.5KViews0likes0CommentsRe: Support for M365 Apps (O365) on Windows 2022
Günter, you wrote a follow-up to your blog post saying that disabling H.264/AVC 444 ultimately did not resolve the Word issue where all the characters disappear. Did you find a resolution? I'm seeing the *exact* same issue and thought I was going crazy. I tried Googling the issue, but that returned a bunch of garbage results... I know Word was named decades ago, but trying to craft queries that filter out useless results when product names are super-common words--like "word" or "teams" (a practice Microsoft continues...)--makes the products nearly immune from finding actually helpful info like your post. If not for stumbling across your comment here, I would not have found it.3.5KViews0likes0Comments
Groups
Recent Blog Articles
Re: Further simplifying the Microsoft Defender for Endpoint onboarding experience with Microsoft Int
Please, please, please drop the ConfigMan requirement for servers in Intune. I've supported SMS/SCCM/ConfigMan for many years (SMS 2.0) and have since decommissioned. In this SaaS/Intune era, I just ...