StrictTimeWaitSeqCheck setting on Windows Server 2016
I would like to know if StrictTimeWaitSeqCheck needs to be set to 1 for TcpTimedWaitDelay value as mentioned in https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.solarwinds.com%2FSuccessCenter%2Fs%2Farticle%2FTweaking-Windows-Server-performance-to-prevent-port-exhaustion-when-using-Orion-modules%3Flanguage%3Den_US&data=04%7C01%7CVishwesh.Sharma%40wolterskluwer.com%7C5aa83e8d3fa04b7746f708d881b5699d%7C8ac76c91e7f141ffa89c3553b2da2c17%7C0%7C0%7C637401963454946520%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BsutuGoKNaX4cNdBBTTT1u81j993Sx0HNMUc%2F0c2Nhc%3D&reserved=0
WinHTTP Proxy Service Stopping on Server 2019
I am having an issue with a few of our Windows server 2019 VMs. Every week weeks one of the boxes would suddenly be unable to send HTTP requests. Upon further investigations into the Event Viewer, we found this entry around the start of the issue. The WinHTTP Web Proxy Auto-Discovery Service service terminated with the following service-specific error: The endpoint mapper database entry could not be created. Has anyone ever had this issue or knows a fix? We need to restart the VM for it to rectify as the WinHTTP Service refuses to start using the services control panel. The services on those box support 24/7 products and we don't have anyone on call to restart the box at a moments notice.
Microsoft RD client Android app url scheme is not working
I've been using a legacy URL scheme in my Android app to open the RD Client app via a deep link and initiate an automatic connection with a remote server. It used to work fine, but now it's no longer functioning. Is there a change in the URL scheme that hasn't been documented, or perhaps an update that affects this functionality? Can someone guide me on this issue?Azure VM Agent Status not ready
I have created a red hat openshift private cluster but the VMS are stuck in the state of "agent status not ready." I have followed these troubleshooting steps: Linux Virtual Machine Agent Status "Not Ready" - Microsoft Community Hub However, all of them seem to point to trying to check and see what is on the VM itself. I am unable to do this because I can't SSH into the machine. Has anyone else ran into this issue and been able to resolve it? I am deploying it via CLI as I was not able to do it via GUI for some reason. This is my script: #az login az account set --name "accountnamehidden" #az provider register -n Microsoft.RedHatOpenShift --wait #az provider register -n Microsoft.Compute --wait #az provider register -n Microsoft.Storage --wait #az provider register -n Microsoft.Authorization --wait $LOCATION= "eastus" # the location of your cluster $RESOURCEGROUP= "sample-rg" # the name of the resource group where you want to create your cluster $CLUSTER= "K8sDev1test" # the name of your cluster $arovnet= "sample-vnet" $mastersubnet = "k8sDev1-master-ue-snet" $workersubnet = "k8sDev1-worker-ue-snet" az aro create --resource-group "samplerg" --vnet-resource-group "sample-vnet-rg" --name $CLUSTER --vnet $arovnet --master-subnet "k8sDev1-master-ue-snet" --worker-subnet "k8sDev1-worker-ue-snet" --apiserver-visibility Private --ingress-visibility Private --fips true --outbound-type UserDefinedRouting --client-id hidden --client-secret hiddenIntegrate with SharePoint online API through console application which hosted on onprem windows VM
I have the below console application which is hosted on a local windows VM, which integrates with SharePoint Online. the console application authenticates with SharePoint using ClientId, TenantID & Certificate, as follow:- using Microsoft.Extensions.DependencyInjection; using Microsoft.Extensions.Logging; using PnP.Core.Auth; using PnP.Core.Model.SharePoint; using PnP.Core.Model.Teams; using PnP.Core.QueryModel; using PnP.Core.Services; using PnP.Core.Services.Builder.Configuration; using System; using System.Collections; using System.Collections.Generic; using System.Globalization; using System.Runtime.CompilerServices; using System.Security.Cryptography.X509Certificates; using static Microsoft.ApplicationInsights.MetricDimensionNames.TelemetryContext; using static System.Net.Mime.MediaTypeNames; namespace ConsoleApp4 { internal class Program { static async Task Main(string[] args) { var tenantId = "b***c"; var clientId = "7*****9"; var certificatePath = @"c:\CERT\SPDashBoardIntegration.pfx"; var certificatePassword = "***"; // Initialize a new service collection var serviceCollection = new ServiceCollection(); // Load the certificate var certificate = new X509Certificate2(certificatePath, certificatePassword, X509KeyStorageFlags.Exportable); // Configure logging serviceCollection.AddLogging(builder => { builder.AddConsole(); }); // Add and configure PnP Core SDK serviceCollection.AddPnPCore(options => { options.PnPContext.GraphFirst = true; // Set true if you prefer to use Graph over CSOM when possible // options.HttpRequests.UserAgent = "ISV|Contoso|ProductX"; options.Sites.Add("SiteToWorkWith", new PnPCoreSiteOptions { SiteUrl = "https://********.sharepoint.com/sites/********-******", AuthenticationProvider = new X509CertificateAuthenticationProvider(clientId, tenantId, certificate) }); }); Now my question is if this is a secure approach? I mean when the VM sends the ClientID, Client Secret & Certificate to SharePoint Online, will that info be secure on the network? i mean will the console application communicate with SharePoint in a secure way when it sends the credentials (ClientID, Client Secret & Certificate)? If not, then how we can secure this? Thanks
Why the api NdisMEnableVirtualization returns NDIS_STATUS_RESOURCES?
In Windows Server 2022, when creating a Hyper-V VMSwitch, the NDIS miniport driver will use the api NdisMEnableVirtualization. But sometimes, the function returns NDIS_STATUS_RESOURCES. There is still a lot of remaining memory and cpu resources. Why the api returns NDIS_STATUS_RESOURCES? In the case, I restarted the operating system, this problem has disappeared. Is there a solution that does not require restarting the operating system?Why NDIS miniport driver' RSC capability is disabled by OID_TCP_OFFLOAD_PARAMETERS?
In Windows Server 2019 and Windows Server 2022, sometimes OID_TCP_OFFLOAD_PARAMETERS is received to set NDIS miniport driver's RSC as disabled, after reporting RSC (Receive Segment Coalescing) enable in the miniport driver initialization phase. What specific operations or scenarios can trigger this situation? How to ensure that NDIS miniport driver's RSC is finallly enabled?Wish me Luck
If I were Achilles, Networking would be my Heel. If My Machine Learning Better, A.I would already understand how they feel. If my attitude toward Data Analysis embodied more Zeal, Meta Verse would look less like Roblox and resemble something real. If I had listened to Mr. P my O'l Physic's Teach, I might have founded OpenAI and had more time at the beach. If I Applied myself this Tech Race wouldn't seem so outta reach. If I hadn't been so mediocre I wouldn't be me, not here to Preach, my gift is lifting people with me, solving the problems not glamorous enough to claim, and when a team member is down and out, shoulder the blame. I can't do that from the top or the front or the beach. If I missed those opportunities, life would have been bland and its colors Bleached. (Don't let that fool ya that was born of procrastination and the availability of fruit snacks)
