How to suppress IE enhanced security prompt

How to suppress below kind of prompt?


The detailed description is shown in the below video.


It can be set through registries also as below.

Reference: StackOverFlow




Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A7-37EF-4b3f-8CFC-4F3A74704073}]

[HKEY_CURRENT_USER\Software\Microsoft\Active Setup\Installed Components\{A509B1A8-37EF-4b3f-8CFC-4F3A74704073}]



virtualbox to vmware conversion

The below video shows how to convert virtualbox format to vmware.

Command to convert Virtualbox vdi to generic vhd format:


vboxmanage clonehd "source vdi file path" "Destination vhd file path" --format VHD

GitHub Desktop for other providers

GitHub Desktop can be downloaded from GitHub Desktop.

It is provided by GitHub and supposed to use only for

Other providers like BitBucket can’t be used directly with GitHub Desktop.

If we need desktop client for BitBucket, we can use directly the Git software available at Git website, this is the most recommended one and have both command line and GUI versions.

But for people, who are acquainted with GitHub Desktop, they can follow below instructions to use BitBucket and other service providers with GitHub Desktop.

  1. Clone the Bitbucket repo locally via command line.
  2. Add Cloned Repository to Your GitHub Desktop App.

Video Tutorial:

Reference: Main Link


How to connect to Remote Hyper-V in a workgroup network

We can access Hyper-V server and its machines through Hyper-V manager on a different machine if it is connected in Active Directory network.It will pickup the AD credentials we logged in with and provide access based on the rights the logged-in user have.

Prior to server 2016 and windows 10, we don’t have below option to connect with Remote Hyper-V.


So we don’t have option to use Hyper-V server on the previous OS of windows.

From the OS mentioned above (from windows 10), we can connect to remote Hyper-V server or client machines and access/control their VMs.

Before doing that, we need to configure some settings on the remote machine and on the local machine to create a trust between both the machines.

To do that, run below scripts on respective machines.


CommandLine : Set-ExecutionPolicy Unrestricted

CommandLine : Get-ExecutionPolicy

CommandLine : Start-Service WinRM

CommandLine : Enable-WSManCredSSP -Role "Server"

CommandLine : .\Configure-SMRemoting.exe -Enable

CommandLine : Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true

CommandLine : Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -Passthru

CommandLine : Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -PassThru

CommandLine : Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true -PassThru

CommandLine : Set-NetFirewallRule -DisplayName 'File and Printer Sharing (Echo Request - ICMPv4-In)' -Enabled true 

CommandLine : .\cscript.exe C:\Windows\System32\SCregEdit.wsf /AR 0

CommandLine : Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru

CommandLine : get-history | Format-List CommandLine | out-file c\server.txt


CommandLine : Enable-WSManCredSSP -Role "Client" -DelegateComputer "chellangi-2016"

CommandLine : Enable-WSManCredSSP -Role "Client" -DelegateComputer "chellangi-2016"

CommandLine : Connect-WSMan -ComputerName "chellangi-2016"

CommandLine : set-item wsman:\localhost\Client\TrustedHosts -value *

CommandLine : set-item wsman:\localhost\Client\TrustedHosts -value "chellangi-2016"

CommandLine : $current=(get-item WSMan:\localhost\Client\TrustedHosts).value

CommandLine : $current=(get-item WSMan:\localhost\Client\TrustedHosts).value

CommandLine : get-command *winrm*

CommandLine : get-command *remote*

CommandLine : get-command *winrm*

CommandLine : get-command *win*

CommandLine : get-command *remote*

CommandLine : winrm quickconfig

CommandLine : winrm quickconfig

CommandLine : clear

CommandLine : winrm quickconfig

CommandLine : winrm quickconfig

CommandLine : $Profile = Get-NetConnectionProfile -InterfaceAlias Ethernet1

CommandLine : Get-NetConnectionProfile 

CommandLine : $Profile = Get-NetConnectionProfile -InterfaceAlias ERWIN-AP01

CommandLine : $Profile = Get-NetConnectionProfile -InterfaceAlias "vEthernet (wifi)"

CommandLine : $Profile.NetworkCategory = "Private"

CommandLine : Set-NetConnectionProfile -InputObject $Profile

CommandLine : winrm quickconfig

CommandLine : winrm set winrm/config/client @{TrustedHosts="Name of the Server"}

CommandLine : winrm set winrm/config/client @{TrustedHosts="chellangi-2016"}

CommandLine : winrm set-winrm/config/client @{TrustedHosts="chellangi-2016"}

CommandLine : winrm set winrm/config/client @{TrustedHosts="chellangi-2016"}

CommandLine : winrm set winrm/config/client @{TrustedHosts="chellangi-2016"}

CommandLine : Enable-WSManCredSSP -Role "Client" -DelegateComputer "chellangi-2016"

CommandLine : Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru

CommandLine : get-history

CommandLine : get-history | format-list

CommandLine : get-history | format-list CommandLine


After that, add below settings on the local machine, to add remote machine to the trusted zone.

add to trusted.png


How to reset windows password

In the windows operating system, the credentials are stored in the registered in encrypted format at [HKEY_LOCAL_MACHINE\SAM]

This location won’t be visible once the OS is loaded.

This can be accessed during the boot time and we can access it by launching the command prompt during boot time and can clear or reset the password.

To make it simpler, below third party vendors provide bootable media or application to create that bootable media.

List of softwares to create the bootable media to reset windows password.

You can comment on the post if you need any details.

How push or sync commits to a different branch

Let’s say we have created a branch yesterday and committed some changes to master branch.

If we want to make both the branches even.

  1. Option 1 -> is to delete and recreate the branch again from master.
  2. Option 2 -> checkout to master branch and run below command.
    git push origin master:<new_branch>

All the commits are identified by a unique ID.So we don’t need to mention the parent branch of the commit if we know its ID.So, If we want to add only a specific commit, then run below command from the target branch checked out.

git checkout -b new_branch origin/new_branch -> If branch never checked out locally.
git checkout new_branch -> If already checked out locally.

git cherry-pick <commit-ID>


How to add windows node to Jenkins

Login to Jenkins portal and click on Manage Jenkins link.

Scroll down and click on Manage Nodes.

Click on new node link left side.


Provide node details and press OK.


Click on save after providing below details.



Now login to the Jenkins portal on the machine which we want to add as node.

And then go to the nodes section and click on the node we added.

Click on the launch button.




Select the below window and hold alt key to get the options enabled.



Click on refresh, so you can see the node added successfully.


Download document: Add windows node to jenkins

How to disable auto launch of server manager

On the windows server machines, I am taking 2012 as an example, server manager launches automatically once we login to the machine.

To disable that we need to set below option.

  1. Open the “Server Manager”.
  2. Select “Manage” on the top bar.
  3. Select “Server Manager Properties” from the drop down menu.
  4. Select the option “Do not start Server Manager automatically at logon”.



This can also be set using the below registry.


And the reverse option is


You can set the same key in HKLM to set it for all users.But we should not keep this registry value “DoNotOpenServerManagerAtLogon” in HKCU at that time as the User key will be given preference.

Temporary Directories for RDP sessions on windows

By default, In windows server machines, when you login to the machines using Remote Desktop Session, it will create a temporary sub directory in the temp folder and redirects to this when we tried to access temp folder using %temp%


As you see the number marked at the end.


We can disable this behavior using the below setting in group policy.

For server 2003:

group policy:  Administrative Templates\Windows Components\Terminal Services\Temporary folders . If you don’t select Do not use temporary folders per session, then these TEMP subdirectories are created.


For server 2008 and above:

group policy:  Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Temporary folders




The following tool, from Microsoft TechNet, allows management of Group Policy via the command line, and thus scripting as well:

Local Group Policy Object Utility, v1.0


The registry used is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]


Create a free website or blog at

Up ↑