windows server
2196 TopicsIdle time out GPO for Remote Desktop Services sessions not working in Windows 2019 servers
I have configured GPO to Set time limit for active but idle Remote Desktop Services sessions. Policy has been set to disconnect sessions which are idle for more than 3 hours. But I am getting warning after 30 minutes itself. This GPO has been applied at OU level. Issue occurs only with Windows 2019 servers. Session time limits on Windows 2016 servers which are in the same OU works well. I ran gpresult /h on the affected servers. I could see session time limit policy is applied properly still sessions are getting disconnected after 30 minutes. Anyone came across this issue? Please assist me355KViews1like23CommentsWindows Server 2019 and .NET 4.8?
Hello, On a fully updated Windows Server 2019, roles and features allow me to install only .NET 4.7. One of the solution we are using require .NET 4.8 (Adaxes). When I install .NET 4.8 using the installer available here https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0 It works, I can install Adaxes, but it break ServerManager as well as Azure AD Connect. What's the correct procedure to install .NET 4.8 on Server 2019 without breaking anything else? Thanks a lot204KViews5likes38CommentsHow to download windows server 2019 update to 1903
I just want to download the full 1903 patch for Windows server 2019 and can't find it anywhere. It keep redirecting to Window 10. I am sure they are based of the same OS, but there should be a way to download it manually or force a server to use it.Solved192KViews0likes8CommentsCleaning up WinSxS Directory to reduce space Windows Server 2012 R2
Hi I'm trying to reduce the amount of drive space taken up by Windows on my servers C Drive - currently the entire drive is taking up 28GB of a 30GB drive... I've used the disk clean up tool that ships with Windows but it didn't identify anything that could be removed (really!)... The Windows Directory is taking up 17.5GB of the 30GB drive so a big chunk. I've seen that you can reduce the size of the WinSxS directory within Windows which is currently taking up about 8GB, and this director (given it's size) seems a likely candidate for size reduction. I found this tool - but it is not compatible (won't install stating incompatible) - see: https://support.microsoft.com/en-us/help/2852386/disk-cleanup-wizard-addon-lets-users-delete-outdated-windows-updates-o Perhaps there's another tool I can use? Alternatively - perhaps there is something else I can do to reduce the data on my drive...? I'm working an a Windows 2012 R2 Server running off an EC2 Instance on AWS. Any help most appreciated? Thanks Mark191KViews0likes3CommentsDCOM was unable to communicate with the computer
i ran dcdiag on all my for dc 2,3,4,5 dc2 = windows 2016 dc3 = windows 2012 dc4 = windows 2012 dc5 = windows 2016 I get the following error DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:20:39 Event String: DCOM was unable to communicate with the computer 10.10.0.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:21:57 Also, note that 10.10.0.1 IP does not exist and its not configured in nic or forwards Please assist170KViews0likes14CommentsHostname Character Limit
Still being limited to 15 characters for hostnames in 2019 is very upsetting. In an age where we are deploying servers in multiple data centres, whether that be on premise or in the cloud and having multiple environments as well means trying to come up with sensible hostnames in just 15 characters is basically impossible. Iām sure I am not the only person who is frustrated by this limit and would very much like it if Microsoft was to revisit this limit and increase it to bring it in line with the wonderful limit our Linux friends enjoy.170KViews6likes6CommentsRemote Desktop users have access to shutdown/restart, how disable these ?
Hi I am learning windows server 2019 and i have a problem about RD: i have a user (test_1) in an OU and this user have access to Remote Desktop, locally this user have access to "Sign out" option only but when using Remote Desktop this user have access to: 1. Disconnect 2. Shutdown 3. Restart how can i disable shutdown/restart options for remote users ? i tried this ways: - apply a GPO to Related OU (...start menu and taskbar > enabling "remove and prevent access to the shutdown...) - checking user (test_1) "Member Of tab" and the only groups are: Domain users and Remote desktop users - Local group policy > local policy > user right assignments > shutdown the system policy is unavailable ("The setting is not compatible with computers running Windows 2000 SP 1 or earlier. Apply Group Policy Objects containing this setting only to computers running a later version of the operating system.")Solved166KViews0likes19CommentsHOW-TO: Import Out of Band Updates to WSUS using Microsoft Edge Chromium IE Mode and PowerShell
----- I recommend using https://www.powershellgallery.com/packages/Import-WSUSUpdate Full instructions to install the module are located here - https://www.ajtek.ca/blog/the-new-way-to-import-updates-into-wsus/ ----- History: 09/12/2023 - adding PowerShell method to the OP 07/30/2023 - please follow the latest comments for the updated approach using PowerShell. The method in the OP has become obsolete 01/13/2022 - update links and clarification to prevent an error "This update cannot be imported into Windows Server Update Services, because it is not compatible with your version of WSUS", added Troubleshooting and Q&A section. 02/11/2021 - initial version PREREQUISITES: Windows 10 / 11 / Windows Server 2016 or later with WSUS RSAT Tool installed. latest Microsoft Edge installed, version 97 as of time of writing. Internet Explorer (mode) is installed in Settings > Apps > Optional Features or equivalent location in Windows 11 HOW-TO: - Open Edge 97 or later - Open Microsoft Edge Options > Default Browser - Change "Allow Sites to be reloaded in Internet Explorer Mode" to 'Allow' - Add links to add to Microsoft Edge IE Mode - Remove all other links in the scope of *.catalog.update.microsoft.com, only these shall remain for the catalog.update.microsoft.com page. https://catalog.update.microsoft.com/ https://catalog.update.microsoft.com/v7/site/Home.aspx see screenshots below for better illustration. - Close Edge and all catalog tabs if there were any open, especially if you use "Open tabs from the previous session" feature - Open WSUS MMC and right click Updates from the tree > Import Updates - The link in Edge should open in IE mode, there are several indicators on this the open tab to point to https://catalog.update.microsoft.com/v7/site/Home.aspx?SKU=WSUS&Version=10.0.xxxxx.xxxx&ServerName=YOURSERVER.CONTOSO.LOCAL&PortNumber=8531&Ssl=True&Protocol=1.20 NOTES 1.When the link opened in importing updates from WSUS MMC does not contain the "v7/site/" part or does contain a https://www.update instead of https://catalog.update your configuration is wrong. 2. The "Default" setting will not be sufficient to allow the installation and use of the ActiveX plugin. Go back to your update catalog tab, Install the ActiveX if you have not done on this box already. Check if you have not setup restrictions to execute or install ActiveX plugins in IE directly or via group policy. 3. Edge now has the ability to an IE Mode button. Also it has a new feature to automatically add pages to the exception list. Do not use this ability as shown in the picture for this use case as it might add wrong exceptions to the list. 4. When there are wrong exceptions in the exception list for IE mode it might not work correctly and cause a missing but very important redirection, which ultimately cause the import to fail. More troubleshooting assistance below. LINKS STARTING FROM DECEMBER 2021 / JANUARY 2022: Links to add to Microsoft Edge IE Mode https://catalog.update.microsoft.com/ https://catalog.update.microsoft.com/v7/site/Home.aspx TROUBLESHOOTING: Q 1: Microsoft Edge does not allow me to configure any IE Site Mode links (greyed out). A: Either you have not enabled "Allow Sites to be reloaded in Internet Explorer Mode" to 'Allow', or your enterprise has set policies to prevent that. This should be clearly indicated by a lock and message in the Edge settings tab. Q 2: I have followed this guide or a previous version. I can see the cart to import into WSUS but cannot import any or just specific updates. Others fail with a message "This update cannot be imported into Windows Server Update Services, because it is not compatible with your version of WSUS". A: This is a "known" issue and the guide has been updated to reflect this issue and a potential change on the server-side. Please make sure only the two links are included in your IE mode list. They may not include www in the link name. You need to include both links, not just one or the other as in the previous version of this guide. Q 3: May I use the new Edge feature in Settings > Appearance > Internet Explorer Mode button A: I would recommend to refrain using this feature, as the mechanism between WSUS update import and the browser is extremly picky. It would not work if you just copy the same link into a browser tab. The feature of the cart to import into WSUS will be likely missing and you can just download to the Download folder instead. Q 4: Edge offers me to restart this tab in IE mode next time. A: you should not receive this message, otherwise the exceptions as stated in the guide are invalid or you have more than the stated links in place. Go through the guide again and double-check. Do not use this otherwise nice feature. It will cause to add more catalog links to the exception list which will cause an issue to import updates to WSUS, as described in Q #2. Thanks for the hint Eric_VanAelstyn, thanks to abbodi1406 for additional hints after this guide got invalid a redirection change in December 2021 / January 2022. cc AriaUpdated MissyQ cc for the other teams as I did not want to repost it in Edge and Servicing communities, unless you insist šSolved161KViews8likes40CommentsBest practices: sharing folders, NTFS+share permissions and the Everyone permissiion
Hi! Trying to follow best practices on sharing data folders using security groups instead of users, I rolled down the hill and I can't go any further. I have a data folder shared on the network. The data is on my Server 2016 (I tried this on a Server 2012R2 and it does the same). Inside that folder, there is a subfolder that I want to give permissions. So I created a security group and give permission to that security group (following https://social.technet.microsoft.com/Forums/office/en-US/c6242159-d15d-417e-91f8-eb19c0da3a35/best-practices-for-basic-ntfs-permissions-on-a-share?forum=winserverfiles) and put a user into that group. Then I tried to use it to no avail. The user can't access the folder. If I directly put the user in the permission list instead of using the security group, it works as expected. If I analyze the effective permissions, I get X everywhere for the group, with "Share" on the "Access limited by" column. But the network share is Everyone - Full Control (and no other in the list). As you can see https://superuser.com/questions/1276744/windows-file-permission-access-limited-by-share https://social.technet.microsoft.com/Forums/ie/en-US/b58a08ee-7d7c-4d73-a8e3-587a89f0d67a/domain-users-recieve-access-denied-errors-for-folders-they-have-permissions-to-access?forum=winserverfiles, https://social.technet.microsoft.com/Forums/windows/en-US/d1248276-3955-4c68-9027-c8f1a82185b4/quotaccess-limited-by-sharequot-unable-to-access-files-via-security-group-membership?forum=winserverfiles or https://social.technet.microsoft.com/Forums/en-US/7ee5e34c-bbfa-41c9-a08b-49e3eca7353c/access-limited-by-share-for-effective-permission-on-assigned-group-if-the-group-doesnt-have?forum=winserverfiles, I'm not alone. The last post has the correct identification of the problem: the security group that I use is not included in the definition of Everyone for Microsoft, so I have to manually add the security group to the root share permission. But having dozens of security groups, adding all of them to the root share folder's permission list is not a funny thing to do. So, what's the correct way of doing this?Solved159KViews1like5Comments