Some people recommend using ….control + alt + end on a RDP session to bring up that Windows Security screen, but it does NOT work on nested RDP sessions.
This procedure is the only one which worked for me on a Windows 2012 R2 RDP session:
- Click Start
- Type osk (to bring up the on screen keyboard)
- Hit enter
- Once the on screen keyboard is open, hold ctrl+Alt on your physical keyboard, then click on the del key in the on screen keyboard.
- Minimize the on screen Keyboard
- Click Change a password.
PS: Thanks a ton for the tip, Bill!
While setting up a new network for iSCSI operation here are the things we need to check and configure:
Check the general notes here: http://technet.microsoft.com/en-us/library/ee338480%28v=ws.10%29.aspx especially the “Networking best practices section” there.
The most relevant parts are:
- Use a a separate LAN or setup VLAN for iSCSI traffic
- Use CHAP (at least)
- Configure Jumbo Frame size
- Use multiple NICs
- Configure MPIO, use vendor’s DSM if available.
Here is a quick and dirty way of finding out the binding order of your multi-homed server (meaning a server with multiple NICs or multiple network ports).
On a command prompt run ipconfig. All active connections will be shown in the current binding order. The first entry is the one in the top of the binding order and so and so forth. The ports which are not connected are not shown here.
This is especially useful if you are running server core (without GUI) and quickly want to find out this info.
While trying to connect from a Windows 8 Enterprise client machine to my Windows Server Hyper-V 2012 server via the Hyper-V Manager, I kept getting this error message:
“Access denied. Unable to establish communication between Client and Server”.
I found a way to fix this. Here is how:
- From the command prompt of the client open a command prompt and type DCOMCNFG
- Go to: “Component Services > Computers > My Computer”.
- Open Properties for “My Computer” and select the COM Security tab.
- In “Access Permissions” area click the “Edit Limits” button.
- Select the “Anonymous Logon”-group and make sure the “Remote Access” is set to Allowed.
Now your client will connect successfully to the server.
Note that for server management “Server Manager >> Computer Management” you still need a firewall rule on the server or simply disable the firewall completely [not recommended] using this command:
netsh firewall set opmode mode=disable