.NET Framework Cleanup Tool User’s Guide Introduction This .NET Framework cleanup tool is designed to automatically perform a set of steps to remove selected versions of the .NET Framework from a computer.  It will remove files, directories, registry keys and values and Windows Installer product registration information for the .NET Framework.  The tool is intended primarily to return your system to a known (relatively clean) state in case you are encountering .NET Framework installation, uninstallation, repair or patching errors so that you can try to install again. There are a couple of very important caveats that you should review before using this tool to remove any version of the .NET Framework from…

Collecting system events for a specific source # Store the current System log in the variable TempSystemLog$TempSystemLog = (Get-WinEvent -LogName System) Then pipe the variable to the appropriate filter($TempSystemLog | ? {$_.ProviderName -eq "NTFS" }) ($TempSystemLog | ? {$_.ProviderName -eq "Volsnap"}) ($TempSystemLog | ? {$_.ProviderName -eq "Disk" }) Add “FT –Autosize” it will display more of the message text on the screen | FT –Autosize For users of the iSCSI Initiator, the following events sources are interesting: iSCSI iSCSIPrt MSiSCSI For users of MPIO: MPIO MSDSM Other Storage events of interest: Partition Manager (partmgr) Volume Manager (volmgr) ClassPNP

We can find the installed dot net version from registry or using power shell script, refer below detail. Registry path: Find .NET Framework versions 4.5 and later in the registryFrom the Start menu, choose Run, enter regedit, and then select OK.You must have administrative credentials to run regedit.In the Registry Editor, open the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full. If the Full subkey isn't present, then you don't have the .NET Framework 4.5 or later installed. NoteThe NET Framework Setup folder in the registry does not begin with a period.Check for a DWORD entry named Release. If it exists, then you have .NET Framework 4.5 or later versions installed. Its value is a release key that corresponds to a particular version of the .NET Framework.…

Link1Link2 Basic Disk: Basic disks are the most common type of partition used in Windows operating systems. This disk uses primary partitions and logical drives that are formatted with a file system, typically NTFS.Basic disks support two styles of partitions — master boot record (MBR) and GUID partition table (GPT). MBR partition style uses a partition table that contains the location where partitions are stored on the disk. This is the only partition style available on x86-based computers prior to Windows Server 2003, so it is used automatically.In MBR, you can create up to four partitions — three primary and one extended or all four primary. The extended partition, in turn,…

Today we see how to map network drive manually and troubleshoot. Steps to add in network drive with CMD net use Z: \\remotepc\sharename /persistent:yes net use z: \computer name\sharename /user username password /persistent:yes Delete the respect drive mapped: net use Z: /delete To delete all mapped drives: net use * /delete Check whether the server using SMBv1,v2 LinkCheck the port open between the servers. 137,138,139 4451. Start the Local Security Policy manager by running secpol.msc and check "Local Policy\User Rights Assignment\Access this computer from the network"2. Check the firewall settings or disable. 3. Network Access Right is controlled by policy so it might be set for your server at a domain…

Open the run and type the cmd as “control keymgr.dll” or Go to Start / Control Panel / User Accounts and Family Safety / Credential Manager

Error Value: 2147943645

Starting in Windows Vista and Windows Server 2008, we added an Event Trace for Windows (ETW) provider for Winsock (AFD). ETW provider: Microsoft-Windows-Winsock-AFD ETW provider GUID: E53C6823-7BB8-44BB-90DC-3F86090D48A6 Method 1: Enable AFD logging using the perfmon GUI Note: The benefit, it’s built-in to the O.S. 1. Open Perfmon 2. On the left under “Data Collector Sets” 3. Right-Click “Startup Event Trace Sessions” 4. Choose “New”->”Data Collector Set” 5. Type “Winsock-AFD” and click Next 6. Click Add 7. Wait for the dialog to populate and choose “Microsoft-Windows-Winsock-AFD” and click ok 8. In the Properties Dialog select each item and click edit 9. Enable all check boxes and for the level type 4 10.…

1. To get this working for my Windows 7 client PC’s, I ran this PS Script on the server:  Set-SmbServerConfiguration -RejectUnencryptedAccess $false 2. Go to “gpedit.msc” to configure “local security policy” on the Win7 client, change “LAN Manager authentication level” to “send LM & NTLM -use NTLMv2 session security if negotiated”. Local computer policy > Computer configuration > Windows settings > Security settings > Security options > Network security: LAN Manager authentication level > send LM & NTLM -use NTLMv2 session security if negotiated 3. If the issue persists, please also check if there’s any error message in the event viewer regarding SMB on server side. Event viewer > Applications…