Event banner
Event details
126 Comments
- I am asking about firewall because if the firewall is weak, it will be a problem for the server. It should be strengthened, because firewall is important for protection against hackers. Is there a hacking of the Mac? I study or not.
Hello! This event happened over a year ago so no one will be monitoring questions asked here.
If you have Windows Server questions, feel free to ask them in the Windows Server discussion space: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bd-p/WindowsServer
- Thanks for having this, what an overwhelming exchange!
- Thanks for joining us for this Windows Server AMA! The event is now over, but we'll be posting a summary of the questions and answers here soon.
- Is there a way to disable NTLM per user? kinda like "Protected Users" do, but without other limitations
- Hi. No, it's per client or server. We have a lot of NTLMless plans in motion for the future though, stay tuned.
- What's the scenario? What's the end goal of doing this?
- Are there any plans for adding Azure AD to Windows Server for on-prem, and I know there is ADFS device registration and workplace join.
- Thanks for your question. Yes, the team is aware of this request, and they're considering it. At this time there are no firm plans or commitments, however.
- Any alternative to add windows 2003 as domain member server for a 2016 Domain Controllers in an azure environment ? since 2003 requires smb 1.0 and that feature is disable for all windows server images from market places, could someone tell any work around for this ? thanks
- Hi. There's no way to run a 32-bit guest OS in Azure, including Windows Server 2003. https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/run-win-server-2003. You'll need at least Windows Server 2008 R2
- I am sorry I didnt describe all the scenario, domain controllers with windows server 2016 are running in azure, but there are some others workloads running in skytap for azure, which has 2003 , this 2003 servers run in this platform as a Disaster Recovery Site for some legacy application
Cliff_FisherMicrosoft
1. Why would you want to? We'd be curious why you'd want to deploy 2003 in 2023. 2. Server 2003 is not supported anywhere, including Azure.- If you had an application written many years ago that only ran on that Legacy OS, and it would cost your organization a vast amount to replace it, then you might just want to keep that XP based OS running... But definitely in a walled garden, not exposed to the Internet. We have several clients in the manufacturing and precision measurement business still running VFP 7 apps.
- Just ten minutes left - get your questions in!
- Any issue with upgrading 2012r2 Hyper-V hosts
- Jeff-Woolsey
Lots of questions about in place upgrades. Keep in mind that we invested time and resources in Windows Server 2019, and even more in Windows Server 2022, to make in place upgrades "just work." The Windows Server team support in place upgrades (up to N+2), but in place upgrades is more than the operating system. Ask yourself two questions:
What is the app you are upgrading?
Is this an inbox app (role) like file server, Hyper-V (see my important note about HW below), IIS, print? It should just work. (NOTE: Domain controllers are a special case. For DCs, install new DC, sync with old, promote new and demote old.)
Is this an app installed on the OS? SQL Server? Exchange? SharePoint? 3rd Party App? Consult their documentation. Some apps may support it, some may not. The support decision is up to the app owner. For example, if you have some Oracle app running on Windows Server and Oracle states they don't support in place upgrades, that's their support decision.
What is the underlying platform?
Is this app running in a virtual machine or on hardware?
If the app is running in a VM, things are easier because the virtualized hardware will likely look the same. For Hyper-V, the guest drivers are automatically updated, so it's EASY. For third party virtualization, see them and don't forget to update the guest drivers. A common support issue is that folks are running ancient 3rd party VM guest drivers.
If the app is running on hardware, proceed with caution especially in the N+2 scenario. For example, imagine you have hardware originally running Windows Server 2012 R2 and now you want to in place upgrade to Windows Server 2019. That's a big span.
- Is the new hardware certified for the new OS?
- Are there drivers for the new OS? Be sure to look at I/O. Storage controllers, Network Adapters.
Backups
Finally, always have backup before performing in place upgrades. If you're virtualized this is easy. If you're on hardware make sure you perform an appropriate backup.
- Are there any plans to add a linux like FUSE ability to Windows Server. Kinda like https://github.com/winfsp/winfsp but an official option from Microsoft?
- Rob-HindmanHi John, this is an interesting question - what scenarios would having this capability in Windows Server enable? Are you blocked by not having this capability? Please let me know, we want Windows Server to be as capable as possible, and use the storage systems that customers want to use. Many Thanks, John!!! -Rob.
- We have code that was written for linux, but want to port it over to windows server that needs fuse capability. This is for healthcare applications.
