These astute people have described a very super process to restrict exchange messaging to internal messaging only for a user…
Using Transport Rules to Restrict Users from Sending Email to External Recipients
The windows root
These astute people have described a very super process to restrict exchange messaging to internal messaging only for a user…
Using Transport Rules to Restrict Users from Sending Email to External Recipients
Kali Linux 2.0 Top 10 Post Install Tips
Kali Linux Tools Listing – Penetration Testing Tools
Make sure SSH service always restarts on reboot in Kali Linux
update-rc.d -f ssh enable 2 3 4 5
Some other service boot notes:
~# service open-vm-tools start
~# update-rc.d -f open-vm-tools enable 2 3 4 5
~# reboot
~# service open-vm-tools status
Edit /etc/ssh/sshd_config
, and comment out the following line:
PermitRootLogin without-password
Just below it, add the following line:
PermitRootLogin yes
Then restart SSH:
service ssh restart
Step 1 is to setup SSH on Linux host as directed by this wonderful earthling:
Step 2 is Using PuTTY and keyfiles to SSH into your Ubuntu 12.04 server as provided by this spectacular human:
Using PuTTY and keyfiles to SSH into your Ubuntu 12.04 server
This works super awesome on Surface devices. Have confirmed mstsc.exe works!!!
Use PSExec to launch command on remote PC:
ENABLE:
psexec \\ComputerName cmd /c “netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes”
DISABLE:
psexec \\ComputerName cmd /c “netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=no”
When using Computer Management to manage a hyper-v server, trying to connect to Disk Management shows the following error dialog:
Disk Management could not start Virtual Disk Service (VDS) on SERVER-NAME. This can happen if the remote computer does not support VDS, or if a connection cannot be established because it was blocked by Windows Firewall.
For additional information about diagnosing and correcting this problem, see Troubleshooting Disk Management in Disk Management Help.
Where SERVER-NAME in the above is the name (or IP address) of the hyper-v server you are trying to manage.
Possible causes that I am aware of are:
netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes
If you just do this on the server and not on the local client computer then when you next try to connect to Disk Management you will most likely (instead) see the error:
Virtual Disk Manager
The RPC server is unavailable
So be sure to configure the firewall on the client as well as the server.
You will need to restart “Computer Management” before trying to connect to Disk Management, otherwise it will remember that it was unsuccessful last time and not try to reconnect.
For versions of Windows other than Hyper-V-Server (or Server-Core) another work around is to use Remote Desktop Connection (RDC) to connect to the server and then run Disk Management on the server directly.
SOURCE = this dude: