A place for info I've learnt in IT & stuff. (I get a little kick back from affiliate ads & links, just so you are aware)

Browsing Posts published in January, 2011

You’ll have an mmc on the desktop or a shortcut to AD where you RUN AS and get the “The directory name is invalid”.

Here is a fix for the AD shortcut issue

Right click on the AD shortcut in properties and in the Start In put


Fix for the MMC is to give the RUNAS user account permissions to the location of the MMC. If it’s on your desktop, then give permissions there. Not just to the icon, but the whole desktop folder or even the whole profile folder.

The message basically means that RUNAS user doesn’t have permissions to that location. Shit error message but that’s what it means.

Also see

Remote Desktop Dual Monitor Support tip
remote-desktop-general-tab.jpgYou’re probably wondering if there is dual monitor support for Remote Desktop Connection. There is indeed, but there are some caveats and issues you should be aware of, as well as some solutions to these issues.

First, as of Microsoft Remote Desktop client version 6.0, support was added for spanning across multiple monitors. Only some configurations are supported by Remote Desktop client in span mode. According to the Remote Desktop help file Remote Desktop Connection supports high-resolution displays that can be spanned across multiple monitors. The monitors must be the same height and aligned side by side. Go here for more details:

To have the remote computer’s desktop span two monitors, simply type ‘mstsc /span’ at a command prompt (i.e. Start, Run, cmd.exe, mstsc /span). This feature is sometimes called continuous resolution. To toggle in and out of full-screen spanned mode, press Ctrl+Alt+Break.

If you know the resolution you want for the virtual desktop, you can now state explicitly the dimensions you want using the /w and /h switches. This is useful for when you wish to have a less than full screen window span two monitors.

Example: mstsc /w:2048 /h:768 /v:”server”

The above would create a full screen spanned virtual desktop on two 1024×768 resolution displays.

So what are the limitations or requirements for span mode to work correctly?

* Equal resolution monitors
* Total resolution of all monitors not exceeding 4096 x 2048
* Top-left monitor being the primary

A software app from SplitView lets you make the remote desktop show up as two separate desktops when using RDP with dual monitors in span mode. SplitView automatically repositions dialog boxes and windows so they do not appear in the middle of the two monitors. Additionally, it lets you maximize to the left or right monitor, while preserving the ability to restore to the previous size. This tool adds a left and right button to the top right corner of system windows in the title bar area. Simply press left or right button to send the window to the left or right display.

If you do not have SplitView installed on the remote computer, here are some issues you will discover with span mode with just Remote Desktop 6.0 installed:

* The Windows taskbar will cover both monitors
* Applications will maximize across both monitors
* Popup dialogs and windows will appear in between the two monitors, half on one monitor and half on the other
* The Windows log on dialog will also appear cut off by the monitor bezels in between the two monitors

Perhaps most importantly, Splitview makes sure that when windows are maximized, they get maximized to either the left or the right monitor, and not across both monitors. While SplitView is not a free utility, it resolves all the above issues, making it a valuable app for power Remote Desktop users. It’s only $39 for the personal edition. They also have a Terminal Services edition and a virtual desktop edition worth checking out.

In any event, one of the first things you’ll want to do is Save your /span configuration so you can quickly connect to your PC in the future. To do this you need to save the .rdp file. I like to save my RDP files to the Desktop for quick access. Unfortunately, for some reason the mstsc program doesn’t save the /span option into the .rdp configuration file, which is simply a text file. So here’s how you solve the problem.

* Open Windows Explorer, and browse to the folder containing the .rdp file you want to edit. (C:\myworkpc.rdp).
* Right-click the file > Open With > Choose Program > Notepad or on my PC I can right-click > Send To > Notepad since I added Notepad to the Send To function
* Once the file is open in Notepad go to the very bottom of the file and add the following command: span monitors:i:1
* Save the file and you’re done! (Note: there are some other config settings in this file you might want to play with)

Enjoy your dual monitor Remote Desktop experience!

If you are unable to resume a virtual machine that had been suspended:

1. Navigate to the directory where the virtual machine’s files are located.
Delete the file that ends in .vmss as well as any files or folders that end in .lck.

Note: The suspend state of the virtual machine will be lost. This operation will replicate a physical machine having had its power unplugged.

Sometimes you can corrupt Windows’ MBR (Master Boot Record) unintentionally, through installation of another operating system for instance, and you need to repair it before Windows can boot again. The error message that you usually get is “Operating System not found”. Under Win 95, 98 and ME, you could have used a standard MS-DOS utility called FDISK in the Command Prompt console. However, FDISK is not distributed with Win NT, 2000, XP, Vista, and 7. So you either have to resort to finding an alternative utility called MbrFix.exe and run it from floppy, optical or USB drive or follow these direction from the installation DVD to repair your MBR. While these directions are specific to Win 7, you maybe able to use the knowledge gained to apply to your particular Win install.
Difficulty: Moderate
Things You’ll Need:

* Win 7 DVD installation


Insert Win 7 installation DVD and boot from DVD drive. While in some older systems you may have to change boot order through system BIOS, most newer systems allow booting from DVD without changing boot order by simply clicking on any key when prompted to doing so.

Choose your default “Language”, “Time”, and “keyboard Input” on the first window and click next.

You’re now presented with 3 choices. Click on “Repair Your Computer” to gain access to the System Recovery window. Now choose “Command Prompt” in order to run the desired utility which is called “bootsect.exe”. Bootsect is located inside the boot folder so change your directory to boot. Now run “bootsect /nt60 C: /mbr” if you had Win 7 initially installed in the C partition. Alternatively, you can run “bootsect /nt60 SYS” or “bootsect /nt60 ALL” to repair the system partition or all partitions. Eject the DVD, and restart computer. Your computer should now boot Win 7 again.

.snp to PDF

Get Snapshot viewer

Then get CutePDF or whatever PDF Writer you want.

Then open the file in Snapshot viewer and save as .PDF

Most people have a PDF reader, most people don’t have the snapshot viewer.

As the snapshot is uneditable anyway, putting it into PDF shouldn’t be a problem. And you might even be able to edit the PDF if you have a full PDF package.


If you put the sysvol on a separate drive when AD was setup, that will be there. Otherwise it should be in the Windows directory in path above.

Register loads of .dlls in a directory
Create a txt file. Stick this in it

@echo off
echo registering files….

if not test%1==test goto run
goto end

echo registering: %1 …..
regsvr32 “%1” /s
goto check


Name it whatever you want. It needs to be a cmd file so lets say
Then drag the .dlls to that file and it should run and open its own cmd window and start registering.