ADCS Notification bug in Server manager
Hi, i'm coming here for some help on the server manager. Has anyone ever had a persistent notification problem on the server manager after a role deployment despite the correct configuration of the role in question? And did you find a solution to remove the notification? On my side, I have a problem with an ADCS that has been installed, configured, ... But a notification asks us to configure the role, and it is already configured. We've set up : Certification Authority Certification Enrollment Policy Web Service I tried to edit a registry key : Set-ItemProperty ` –Path registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager\Roles\16 ` –Name ConfigurationState ` –Value 2 But nothing happened, same with a reboot. I find that we could uninstall and reinstall the role but that's not really a solution because the ADCS is actually in production. Does anyone have any idea ? env: Windows Server 2016 up to date
Remote App strange behavior with saved credentials
This problem has confused me for awhile now, and I haven't been able to find any solution. I'm not sure if this is an issue with the mstsc.exe on the client, or if it's an issues server side at this point. The bottom line issue, is that the "Remember me" checkbox for the remote app credentials will stop showing up, preventing the user from saving his or her credentials for the remote app connection. So, here's the scenario. I have a Windows Server 2016 environment, with it's own domain that provides access to applications to remote clients via Remote App services. Joining the clients to the domain isn't an option. We have a publicly trusted certificate deployed in our Remote App servers. When we setup a client machine, we do so through the Remote App and Desktop Connections control panel app, and enter the RDweb url. The client machines are a mix of Windows 7 machines to Windows 10. When we give the users their credentials, it's always in the format of <username>@<domain name> not <domain name>\<username> When we initially setup the client machine, usually the user will save his credentials. Which is fine. However, when their password expires, or when they want to change it through the web interface, things get weird. When everything is working fine, in the windows credential manager there are two entries, both in the Windows Credentials section. 1) <public FQDN of remote app collection> with the username in the format of <username>@domainname> 2) TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> When the users change their passwords via the RDWeb portal page, obviously it doesn't update their saved credentials. The expectation would be that the remote desktop client would prompt them for their new password, with the option to save it, as how it was when it was originally setup. And this is what happens, some times. They get prompted for their password, with a screen that shows them their username in the <domain>\<username> format, with the remember me box. Eventually though, it will break. And this is 100% repeatable by changing the password on the AD side, and trying to conenct again from the client. At some point, one of those times they change their password, they will be prompted for their new password with a credential screen with no remember me box. When it does this. if you look in the credential manager, there will be 3 entries. Windows Credentials: TERMSRV/<RDSessionHost FQDN> with username in <domain name>\<username> format TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> Generic Credentials: TERMSRV/<public FQDN of remote app collection>with username in <domain name>\<username> format After this happens, the users will never get the remember me box again, unless they completely delete the session from their control panel, and re-add it. Manually fixing the credentials in the credential manager to make them match how they were when it was working fine works temporarily, but will break again next time they reboot their computer, or the session disconnects from the servers. I’m not sure what to do with this next. If anyone has any ideas, it'd be greatly appriciated.
KB4580346 download - Windows Server 2016 no feature installation possible 0x80073701
When I try to install a new feature one of our Windows Server 2016 I get the following error in cbs.log: Failed to pin deployment while resolving Update: Package_7513_for_ KB4580346 I resolved a simmilar issues on other systems with installing again the failing KB again. But for that I need theupdateKB4580346. Microsoft removed it from the Windows Update Catalog: October 13, 2020—KB4580346 (OS Build 14393.3986) - EXPIRED - Microsoft Support here the way I used succesful for the other systems: Resolve 0x80073701 – ERROR_SXS_ASSEMBLY_MISSING - Windows Server - Spiceworks Is there any way to download theKB4580346 for Windows Server 2016?
Scheduled reboot that should run every second Sunday, doesn't seem to run on the correct dates/days
As far as I know the second Sunday in August is the 14th. The job seems to have run on the 7th. Next job is scheduled to run on the 11th of September, which seems to be correct according to the "Run on the Second Sunday" trigger I've setup. Is there any good explanation why the job ran on the 7th instead of the 14th of August?Microsoft Windows Server 2016 License tracker
I have a client who currently has 50 Windows 2016 datacenter virtual machines and 10 SQL 2017 installations licenced under the Service Provider Licence Agreement, each of which has a Per Core licence (SPLA). The virtual machines run on five hosts, each of which has two physical CPUs and 18 cores per socket for the virtual machines. The question now is, does Windows come with a tool that I can use to track the licence utilisation (core-based licensing)? Since I am required to provide this to my SPLA team on a monthly basis, I believe that automating this process is preferable to doing it manually.Anyone using Essential Role on Windows server 2016 Datacenter?
Hi, I have been try to integrate Office 365 add in on Windows server 2016. But I am getting the following error repeatedly. Server: Windows server 2016 Datacenter with Essential role Installed. I tried to create multiple VMs in Azure withWindows server 2016 Datacenter, when I try to integrate all of them are showing the same above error. Later I installed the Windows Server 2016 datacenter on local computer, here also getting the same above integration error? Does Windows server 2016 support integration with O365 and Azure? kindly helpCorrupted Mainfests/Payloads Windows Updates Server 2016 0x80073712
I have tried dism, sfc scans to no avail. Cumulative updates have been failing since january. I tracked the update (KB4530689) related to the corruptions by looking at the registry (components hive). From what I understand, you can get the manifests/payload in their respective KB by extracting them. Sadly, I cannot download this particular KB in Microsoft's catalog site. I'd like to avoid reinstalling ang migrating stuff as much as possible. any ideas?
