User Profile
JimGaynor
Brass Contributor
Joined 9 years ago
User Widgets
Recent Discussions
Re: Support for M365 Apps (O365) on Windows 2022
Deleted AVD on Stack HCI is in preview, and has been for a while, so Product Terms and finalized pricing aren't available. Currently available details are here: https://learn.microsoft.com/en-us/azure/virtual-desktop/azure-stack-hci-overview#pricing3.2KViews1like5CommentsRe: Support for M365 Apps (O365) on Windows 2022
It's rather important to note that "Azure Stack HCI for on-prem AVD support" is support for running the session host VMs on Stack HCI, but the management layer and other AVD supporting services remain in Azure. It's not AVD hosted entirely on-premises.3.3KViews0likes0CommentsRe: RDS - How relevant?
For all intents and purposes, RDS has remained unchanged in Windows Server 2019/2022. Microsoft's focus is on Azure Virtual Desktop, and it's unlikely that RDS will see meaningful changes in future LTSC versions of Windows Server. The company's answer for customers that want to host virtual desktop infrastructure (VDI) on-premises is Azure Virtual Desktop deployed on Azure Stack HCI, currently in public preview. It's important to note that Remote Desktop Modern Infrastructure (RDmi), originally previewed in late 2017, was intended to be the long-due update to RDS. However, the technology of RDmi was instead used as the basis of Azure Virtual Desktop (originally announced as Windows Virtual Desktop in late 2018.) Given that their previous effort at modernizing RDS turned into a hosted service, I think it's unlikely that they will put any further effort into RDS other than security, bug fixes, and compatibility. Azure Virtual Desktop (and Windows 365) are Microsoft's focuses for virtual desktop infrastructure. Those services are where new features and capabilities will be delivered, like it or not, and are where you should look for your long-term planning. Similarly, as Harm_Veenstra noted, Microsoft is making it very difficult to support Office running on Windows Server (such as in a Windows Server hosted terminal server or session-based desktop environment). If you're using the Office 365 apps, they will no longer be supported on Windows Server after late 2025. If you're using the perpetual (LTSC) versions of Office, it get more complicated depending on what (if any) Office 365 services you're using. In VDI environments, Microsoft is using a combination of licensing benefits and Office end-of-support to push users away for session-based Windows Server desktops to the multi-session versions of Windows 10 and Windows 11 - which, unsurprisingly, can only be licensed for use with Azure Virtual Desktop.3.5KViews1like0CommentsRe: Window Server Standard Hyper-V licensing
Windows Server Standard, when properly licensed for the cores of the physical host upon which it is installed, includes virtualization rights for up to two Windows Server OSEs (operating system environments) running on the same host server. This includes full Hyper-V VMs or Windows Server Containers running in Hyper-V Isolation. Linux Server VMs do not count against this limit, and require only licensing from their respective vendor (if it is a commercial Linux distribution). This is part of why Hyper-V Server (which is not being updated past Hyper-V Server 2019) was popular among shops that also ran Linux VMs. Hyper-V Server includes no Windows Server virtualization rights, but can run Linux VMs without additional licensing. Similarly, Azure Stack HCI does not include Windows Server virtualization rights, and any Windows Server OSEs must be licensed separately (through application of Windows Server licenses, or the in-preview Windows Server license subscription program). In most cases, when running more than two Windows Server VMs on a host, it's advantageous to license Windows Server Datacenter instead of Standard as Datacenter includes rights for unlimited OSEs.77KViews0likes1CommentRe: OK, so how do we get the RTM version?
amaldevv - Windows Server 2019/1809 went directly to General Availability on Oct 2nd; the RTM phase was skipped. However, Windows Server 2019 LTSC and 1809 SAC as well as Windows 10 1809 SAC and Windows 10 2019 LTSC were pulled from availability on Oct 6th after reports of a data-deletion bug in the upgrade process, and some Intel driver issues. The bits are currently not available for download, and users are advised not to install from media they may have downloaded previously. https://support.microsoft.com/en-gb/help/4464619/windows-10-update-history3.1KViews0likes3CommentsRe: Upgrading windows server 1709 to 1803?
Lars Andersen, in-place upgrades from Windows Server 1709 to Windows Server 1803 were part of the initial Insider previews, and were promoted as a feature of that version early on. https://redmondmag.com/articles/2018/01/23/windows-server-in-place-upgrades.aspx However, it looks like they dropped that feature when they announced, in late March, that the SAC versions would be focused entirely on "modern applications and innovation scenarios such as containers", and would drop most of the infrastructure roles. https://cloudblogs.microsoft.com/windowsserver/2018/03/29/windows-server-semi-annual-channel-update/ Accordingly, 1803 has even fewer infrastructure services than 1709 (which dropped Storage Space Direct just as it was released). So an in-place upgrade would have likely stripped out features from a 1709 installation, causing issues for administrator who (rightfully) expect an in-place upgrade to maintain roughly the same feature set. I haven't seen any indication if 1809 will offer an in-place upgrade, since all the attention has been focused on the LTSC Windows Server 2019 version.38KViews0likes1CommentRe: Server-insider Build
TLDR: No GUI version of 1803 is coming; it'll be Server Core and Nano Server (container base OS image) only. Windows Server with the Desktop Experience (GUI) is only available on the Long Term Servicing Branch, with releases expected every 2-3 years (and supported for 5 years of Mainstream and 5 years of Extended support). The current version is Windows Server 2016. Windows Server 2016 is required for almost all Microsoft enterprise software (Exchange Server, SharePoint Server, and so-on). Semi-annual Channel (SAC) releases (such as 1709 and the pending 1803 version) only provide Server Core and Nano Server (container base OS image only). Server Core and Nano Server do not provide the Desktop Experience (aka Windows Shell, aka GUI). SAC versions of Windows Server are only available to customers with Software Assurance, and are only supported for 18 months from time of release. The current version is Windows Server 1709. I've written more about this https://www.directionsonmicrosoft.com/research/secured/2017/09/comparing-windows-server-installation-modes, although I'm afraid it's behind a paywall (guy's gotta make a living).3.4KViews1like1CommentRe: Confused about Semi-Annual Channel (Pilot) and Semi-Annual Channel (Broad) Timing
This is what I'm hearing: 1709 is released in September 2017. It's dubbed "Semi Annual (Pilot)", and the 18 month clock starts ticking immediately. A few months later (January 2018, if we're matching the Office Pro Plus timeline), 1709 is declared ready for Semi Annual (Broad). The 18 month clock is now at 15 months. 15 Months later (March 2019), 1709 is no longer supported. There is no 60-day "grace period", as that was removed with implementation of this new servicing schedule. Would that be an accurate life for 1709, under the new model?30KViews0likes1Comment
Recent Blog Articles
No content to show