El conocimiento al alcance de todos.

Thanks to:  https://www.netwoven.com/ INTRODUCTION A remote code execution vulnerability exists in the Credential Security Support Provider protocol (CredSSP). An attacker who successfully exploited this vulnerability could relay user credentials and use them to execute code on the target system. CredSSP is an authentication provider which processes authentication requests for other applications; any application which depends on CredSSP for authentication may be vulnerable to this type of attack. As an example of how an attacker could exploit this vulnerability against Remote Desktop Protocol, the attacker would need to run a specially crafted application and perform a man-in-the-middle attack against a Remote Desktop Protocol session. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. The security update addresses the vulnerability by correcting how Credential Security Support Provider protocol (CredSSP) validates re

Thanks to:  https://www.petenetlive.com/ Problem Seen on Exchange 2010 (with or without service packs) when you access the internet through a proxy server.  Note : Exchange does  NOT  take its proxy settings from Internet Explorer. Solution 1. To prove that the proxy is the problem drop to command line and issue the following command: netsh winhttp show proxy If it says “Direct Access (no proxy server)” and you have a proxy server then that’s your problem. 2. Issue the following command: netsh winhttp set proxy proxy-server=”http={proxy IP}:{port};https={proxy ip}:{port}” bypass-list=”*.YourDomain.com” 3.  Note : If at this point it all goes wrong (If you get it wrong, then the Exchange Management Console wont open! test it to make sure). To revert back to “no proxy”, issue the following command: netsh winhttp set proxy proxy-server=”http={proxy IP}:{port};https={proxy ip}:{port}” bypass-list=”*.YourDomain.com” You only do this if it’s broken someth

Thanks to: https://winteladmin.com/ error: Port enc0:iobay1:d3 pause-flood detected and automatically disabled Host was not reachable on network. When checked on ILO server is up and running. When I try to ping the server its unresponsive.Host is a blade server, hence suspected an issue with the network module. Therefore, connected virtual connect. Found one of the virtual connect module was degraded. When analysed the HP Virtual connect found an error message stating “Port was disabled because a pause flood was detected” Further to this when validated the server port assigned to the bay1/bay2 found the status “Not Linked/Pause Flood Detected”. It confirms the issue was caused by pause Flood. In some cases, a flex-10 port can enter into disabled state due to the triggering of “pause-flood”, or network-loop. You can confirm the same port status using Virtual Connect Manager CLI. Connect to Virtual connect using SSH and Execute the below command: Show port-protect This would sh

Thanks to:  https://www.faqforge.com When you apply a group policy on a container or OU, it applies on all users or computers in that container. However, you can exclude a single or multiple users or containers from the policy applied. This tutorial is written to show you how to exclude a single user from a group policy object. Exclude a user from group policy object Step 1 . Open server manager dashboard. Click  Tools -> Group policy management Step 2 . In the group policy management editor, open the group policy object you want to apply an exception on (Located in Group Policy Objects). Step 3 . Click  Delegation tab -> Advanced Step 4 . Click  Add  and choose the user whom you want to exclude from group policy enforcement. Step 5 . Choose the user you entered in step 4. Step 6 . Locate  Apply group policy in permissions  and check mark deny. Step 7 . Click  Apply  and then  OK . Step 8 . Link the group policy to a container or OU (If you haven't do