All posts in Uncategorized

Enabling RDP Remotely

Need remote access and forgot to turn RDP access on? Argh, how to get to that server (or workstation)?

PSExec comes to the rescue in four easy steps! PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console applications, without having to manually install client software. For those of you not familiar with Sysinternals I highly recommend you check out the suite of tools freely available from Microsoft –

  1. Download PSExec –
  2. Copy to your Windows System 32 folder. This way its always available straight up when you fire up an administrative command prompt – c:\windows\system32
  3. Open a command line and type the following command (ensure you swap out ‘remote-machine-name’ for the hostname of your remote server):

    This command adds a registry entry that enables RDP connections.
  4. Still in the command line enter the following commands, again swapping out ‘remote-machine-name’ for the hostname of your remote server:

    These commands set the firewall to enable remote administration and then allows remote desktop connections through the firewall.

And that’s it. You should now have remote access to that server (or workstation).


Exchange Offline Help Files

Hey Guys, here are some must have downloads and reading for you Exchange Admins.

Preferred Architecture,

Download Offline Help Files,

Download Architecture Posters,

Exchange Server Tools Documentation

This tools documentation provides detailed information about tools that can help you plan, install, manage, and troubleshoot Exchange Server.



[ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plug-in unity.

An error while logging in through RDP onto a Windows Server 2008R2, a VM under ESX 5.5  –
[ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plugin unity.

Here is an example of the error captured with a quick PowerShell one-liner.

The issue here lies in that the tools.conf file failed to be created during upgrade of VMTools during a recent ESX upgrade. Strange as this error is meant to be fixed in VMTools version 9.05, and yet this is the installed version. No matter, easily rectified.

Open your favourite text editor (tell me your in the comments).

  • Open your favourite text editor (tell me your in the comments).
  • Copy and paste the text from below into the newly created text file.

  •  Save your new text file as tools.conf, see the table below for the location of the file.

Linux, Solaris, and FreeBSD/etc/vmware-tools/tools.conf
Windows Server 2008C:\ProgramData\VMware\VMware Tools\tools.conf
Windows Server 2003C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf

  • Restart the VMTools service and you should be good to go ;-)



Exchange “Send As” Permissions

Ok, someone asked me the other day how to allow a user to send email as if they were the owner of another mailbox. This can be done by granting the user Send-AS permissions said mailbox – or you can even grant rights to send as a distribution group, very handy for members of a team.

One thing to note here is that Add-ADPermission cmdlet uses -Identity to classify the user who is assigned the permissions. You cannot use the mailbox alias for the -Identity and must use a unique display name or the distinguished name.

#Same as before but this time we know the display name is not unique so we are going to use the distinguished name:

Nice and easy. The process is the same for adding permission to a distribution group.

#Grant user Jane Doe permission to send from ALL distribution groups:

And lets say Jane changes roles and no longer needs to send on behalf of John…