After you install your Linux OS from the Microsoft HyperV terminal access do the following:
- Click "Media", "DVD Drive" > "Insert Disk..."
- Choose LinuxIC-4.2.5.iso
- Login to the server and do the following:
#mount /dev/cdrom /media
mount: /dev/sr0 is write-protected, mounting read-only
After doing this you will be able to setup networking and use kvm via HyperV on linux.
So you go to login to via RDP to a server, workstation or remote PC and you get this error:
Not to worry, here is the fix as well as the why.
First run windows update on your local system and try again.
Quick fix: (not secure)
- Use the Windows+R key to open the Run Command. (If you keyboard lacks the windows key you can use Ctrl+Alt+DEL, open task manager, then click file and "Run".)
- In the run command type in gpedit.msc which will open the Local Group Policy Editor.
- Expand Computer Configuration > Administrative Templates > System > Credentials Delegation.
- Update the Encryption Oracle Remediation policy to Enabled, then change Protection level to Vulnerable.
- After doing this it is advisable to update your remote system and switch these settings back.
Proper fix: (secure)
Update the remote server, in some cases the remote server may show that is it up to date in which case you may have a compromised system and will need to follow the following steps in order to force the update after which you should do a full scan on the system for potential malware.
After the May 2018 update RDP no longer connects by default to a remote system that is not running the CredSSP update.
After installing exchange 2013 and migrating clients over to the server you may notice Microsoft® SharePoint® Search Component or noderunner.exe running multiple instances with high memory usage. This is because Microsoft has integrated parts of sharepoint into exchange 2013. This process runs when accounts are first migrated and periodically to index email data stores for OWA in order to make search results fast, very fast.
You can disable Microsoft Exchange Search Host Controller service if it is causing an issue. In some cases it can consume an extremely high amount of memory causing the "Microsoft Exchange RPC Client Access" to fail and get stuck in a starting state. In which case the best solutions are to:
- Increase the amount of RAM on the server.
- Set the server to restart when "Microsoft Exchange RPC Client Access" fails.
- Disable the "Microsoft Exchange Search Host Controller service".
This is an obvious flaw in the design of exchange 2013 server.