Found this online: ClickYes software. Don't install!
It's supposed to automatically click Yes when a program uses Outlook to send e-mail. In my opinion, it's a very useless piece of software as one could simply disable the prompt in Outlook, or better, install a proper antivirus.
If you're running Internet Explorer 10 or later, you may get this error when trying to log on to a computer using RDP through Remote Web Workplace:
You can resolve the issue by adding RWW to the Compatibility View list in Internet Explorer.
You can add RDS servers to the list of computers in Remote Web Workplace, making them available to anyone with access to RWW. The process is simple, requires no reboot and is immediately active.
Note that this will only work if your RDS server is inside the SBSServers OU or a sub-OU (i.e. you're allowed to create other OU's inside the SBSServers OU).
To get this card running on Windows Server 2012 and 2012 R2, you need this driver:
Newer versions no longer seem to support this card.
Run this command in an elevated Powershell to enable remote WMI access:
Enable-NetFirewallRule -Name WMI-RPCSS-In-TCP,WMI-WINMGMT-In-TCP,WMI-WINMGMT-Out-TCP,WMI-ASYNC-In-TCP
A handy tool to edit file associations, default program handlers, and autoplay handlers:
And best of all, it's free!
The Debugging tools for Windows (a.k.a. Windbg) for Windows 8.1 can still be downloaded separately. Although it's now part of the Windows Driver Kit (WDK), you can still download the Windows 8.1 SDK Installer and select only the debugging tools. It's an about 180MB download (without the symbols).
The NETLOGON folder is in fact a subfolder of the SYSVOL directory. Unless this location is changed, you can find it here:
(replace *yourdomain* with the DNS name of your Windows domain)
To allow an Exchange user to send from an external e-mail address, perform the following steps:
Get-MailContact MyUser@MyExternalDomain.com | Add-ADPermission -User MyUser@MyLocalDomain -AccessRights ExtendedRight -ExtendedRights "Send As"Replace the first e-mail address with the external one, the second part contains the user you wish to assign the permission to.
When performing RDS shadowing, by default, the user whose session is being shadowed has to consent to viewing and/or controlling his/her session. This behaviour can be changed with a group policy.
In your group policy (local or through domain), navigate to:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
Find the policy called Set rules for remote control of Remote Desktop Services user sessions and configure it:
By default, only users with local admin rights on an RDS server can do session shadowing on that server.
To allow a particular user or group to allow shadowing, run this from a command prompt on the RDS server:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TSPermissionsSetting WHERE (TerminalName="RDP-Tcp") CALL AddAccount "domain\group",2
In the command, replace domain\group with settings of your own. It's recommended to create a group specific for the job (e.g. RDS Shadowing) so you can run this command only once, and then add users to the group to allow them to shadow.