TheBernharts.com » computers

Having trouble running an executable through RDP?

Neil — Thu, 04 Dec 2008 19:17:51 +0000

Today I needed to install a utility on a remote Windows 2003 server. Thinking this would be a breeze, I copied the .exe installation file over the network to a directory on the server. I then logged in through RDP as local administrator on the server, located the file, and when I went to run it, I was given this error spat out to me: “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

Huh? I’m the local admin on this here system… the hell you say I don’t have permissions to access this file!

A quick search found that if you copy an executable to a remote system and try to run it via RDP, you get this message because the file is blocked by the operating system since it was copied from another computer. Apparently this is done to try and ‘protect’ the destination computer.

Here’s the quick fix for it: Right-click on the executable file. On the General tab, you will see at the bottom (under the Attributes area) a section for “Security” that has an explaination for you. It says “This file came from another computer and might be blocked to help protect this computer”. (good lookin out, windows) Just click on the “Unblock” button, then click the “OK” button and try running the .exe again.

Boom! You’re done. Now, wasn’t that simple?

Force Users to auto log-off of Windows XP

Neil — Fri, 07 Dec 2007 16:34:19 +0000

I had a friend recently ask me how to get XP to log off a user automatically after a certain amount of inactivity. So, I figured I would take a look around and find the solution for him.

Windows 2003 Resource Kit has a screen saver that does just what he needed. Check out the Microsoft KB article that describes how to set it all up.

Disable screen saver properties on a stand-alone XP workstation

Neil — Fri, 07 Dec 2007 15:55:55 +0000

If you’re ever in the need to keep users from changing their screen saver, for whatever reason, follow these steps:

Go to START, then RUN. Enter this command: gpedit.msc
This opens the local system policy, and you’ll find the options you require under:
Local Computer Policy > User Configuration > Administrative Templates > Control Panel > Display

Then change the following four options to set a specific screensaver and lock it:

Change the option “Screen Saver” to Enabled
Change the option “Screen Saver Executable Name” to Enabled, and enter the file name of an .scr file (from the Windows directory) in the box labeled “Screen Saver executable name”. For example, to set the screen saver to the logon screen saver, enter “logon.scr”.
Change the option “Password Protect the Screen Saver” to Enabled (to password protect the screen saver and lock it) or Disabled (to keep password protection from applying to the screen saver and lock it), as necessary.
Change the option “Screen Saver Timeout” to Enabled, and enter the number of seconds in the box labeled “Seconds”. (10 minutes = 600 seconds)

This will lock changing the screen saver, and set the screen saver options and lock them from being changed.

Vista screen saver w/wireless laser mouse

Neil — Sun, 01 Apr 2007 01:06:09 +0000

I’d been racking my head for a couple of days over why my screen saver won’t kick in on my new PC running Microsoft Vista Ultimate.

After trying several modifications to my screen saver properties, I stumbled upon a Windows Update that was listed under the “Windows Ultimate Extras”. It’s listed as Microsoft – Other Hardware – HID Non-User Input Data Filter. After installing that update (no reboot required), the screen saver worked fine.

Check the KB article here.

Problem importing into Lightroom 1.0 on Vista

Neil — Fri, 30 Mar 2007 00:54:52 +0000

After getting my new PC, loaded with Vista Ultimate, I’ve experience trouble importing some photos from my Nikin D70s camera. I did some research and discovered the resolution.

Vista does not like the forward slash that Lightroom uses when importing using “by date” organization. You can simply double-click on the path within the “organize” box (with the check mark on it), you can modify it and replace it with a backslash. The import should work fine after that.

Cheers! Happy importing!