I was trying to assist another admin with a login issue on a Windows Server 2008 terminal server when I encountered a slightly different login error than the one he was describing. When attempting to connect to the terminal server with a user not in the Domain Administrators security group I received the following message:

“The requested session access is denied”

The problem, it turns out, was me. When connecting, I used a desktop shortcut for Remote Desktop Connect that had the “/admin” switch applied, which instructs Remote Desktop to connect to the Console session, which is restricted to administrators only. Using a regular shortcut without said switch solved the problem.

D’oh.

MSI Wind U123I’ve been updating the BIOS on my MSI Wind U123 religiously since I got it, hoping each time that the latest update will finally allow me to boot, well, anything other than DOS from my class 6 SDHC card (so far, no dice). Went I went to apply the latest update, though, I was greeted with a slightly different message than normal:

ERROR: BIOS has no flash information available

As it turns out, this message doesn’t actually state than the end of the world is near, or that you’ll never be able to update your BIOS. In fact, all it means is that the laptop isn’t connected to AC power and is running off the battery. Simply plug in your laptop and the update will run without issue.

Now why couldn’t they have just said that in the first place?

To the person who found my blog by searching “what command to run on terminal emulator“, I’d probably suggest the following:

help

Important! This article assumes that your phone is rooted. If you don’t know what that is or how to do it, this article won’t be able to help you. If your phone isn’t rooted, this won’t work.

I love my Android phone, but the root side of it still has some quirks. The default shell, for example, is pretty bare-bones. Fortunately, there are ROMs out there like CyanogenMod that help with that side of things by providing little extras like, for example, the BASH shell. BASH is incredibly handy on an Android phone as the default shell doesn’t allow you to scroll back through your command history using the track ball.

So while BASH is included in some ROMs, it’s not the default shell. Typically, I’ve been using ConnectBot (available on the Android Market) which works well, however I’d usually end up starting out every session like this:

su -c bash

It’s only one line, but really, it’s annoying to have to type it out every time. I’m in the IT field, so my nature is to be lazy and automate everything. Enter Terminal Emulator.

Available for free from the Android Market, Terminal Emulator is very basic. It doesn’t allow you to SSH to remote systems or anything like that – instead, it just immediately opens a local shell. As an added bonus, the preferences let you specify the Command Line to the shell executable.

I thought this was my answer. I set the Command Line preference to “/system/xbin/bash -” (the location on CyanogenMod 5.x.x — this may differ depending on your ROM. Make sure the path is correct before hand, as if you set it incorrectly it’s nearly impossible to get Terminal Emulator back up and running) and re-launched it.

Success! I was in the BASH shell! However, I wasn’t root, and this did cause a problem. As soon as I typed su to become root, my shell was changed back to the default one. After doing a little more digging, though, I found my solution.

In the Terminal Emulator preferences, there’s another option for Initial Command - Terminal Emulator will execute this immediately on open. So, I inserted the line I was using in ConnectBot (su -c bash) and voilĂ ! Terminal Emulator now immediately opens with a BASH shell as root.

The TL;DR version: Install Terminal Emulator from the Android Market, open it, hit the Menu button, then Preferences. Tap Initial Command and enter “su -c bash” — now it will always open with BASH running as root.

Extra Note: If you are using an Android phone without a physical keyboard, simply hold the Menu button on your phone for a few seconds in Terminal Emulator to force the virtual keyboard to appear.

UPDATE: As it turns out, you can do this in ConnectBot as well. Tap-and-hold on the local connection, then choose ‘Edit Host’ and ‘Post-login automation’. Note that if you do this, though, ConnectBot will enter the command, but you still have to press enter to active it.

To the person who found my blog by searching “does intel quad q6600 work with windows“:

Yes. Yes it does.

When it comes to naming conventions, everyone will give you a different answer. Some people will say the names should be based on location, like “LIVINGROOM”, “BEDROOM”, “SHOWER”, etc…. Others will say they should be named based on what they do, as in “WEBSERV1″, “PRINTSERV3″, “PRONSTOR99″, etc…. A lot of people tend to name their machines after asset tags, or the people who use them.

Myself? I like to name machines after comic book characters. My current lineup is: “CALVIN”, “HOBBES”, “SATCHEL”, “BUCKY”, “OPUS”, “BILL-THE-CAT”, and this server, “STEVE-DALLAS”.

What can I say?

A few weeks ago, my Exchange Server had a series of unfortunate problems, and in the end the planar board had to be replaced (I’ll eventually get around to doing a blog post about that gong show). When the (first) replacement board arrived, I had to take a picture of the asset labeling on the box. In light of the whole situation, ‘C0KZUP’ was certainly appropriate.

The entry for 'Loc-emplacement', whatever that is.

The entry for 'Loc-emplacement', whatever that is.

After pushing out Google Desktop Search to a few departments, I received scattered complaints that searches were coming up with nothing, even if the exact document name was being mentioned (eg, search terms “Policy Manual” and the document is named “Policy Manual”).

I did a little digging and found that although all of the XP systems were working, none of the Vista computers (32 bit or 64bit) were. Huh. At first I thought that maybe the GPO hadn’t hit some of the computers, but then found that all of the effected Vista computers were in the same OU as the working XP ones (also evidenced by GDS being installed in the first place).

Checking the GDS options, all of them reported that the network location (\serversharenamehere) had a status of ‘Crawl not yet started’. Now, before you jump down my throat screaming “GDS doesn’t search network drives”, let me clear this up: it does. All of the XP systems had happily indexed the same network location, just none of the Vista systems had.

After playing around a little bit, I found the answer.

GDS waits until the computer is idle before attempting to crawl it’s list of allowed locations. The problem is, in Vista, Windows Search (which is built-in) does the same thing, and seems to always do so before GDS gets a chance to start. Therefore, because Windows Search is indexing, the system is no longer idle and GDS won’t crawl.

To fix this, I simply stopped and disabled the Windows Search Service and left the computer to idle. Sure enough, no more ‘Crawl not yet started’ message. Success!

Source: http://xkdc.com

Source: http://xkcd.com

I ran in to an issue the other day at work. We have three tape backup units serving ten servers, two Seagate DDS4 DAT-72 drives that are around four years old, and an HP Ultrium 2 purchased earlier this year.

Over the last three weeks, the cleaning lights on the Seagate drives started lighting up on a daily basis. I tried running the cleaning tapes three times in a row for a few days, and even replaced the cleaning tapes, but there was no difference.

A little Googling suggested that the drive heads were likely wearing out, but I wasn’t ready to give up on the drives yet. Taking a page out of my NES repair guide, I lifted the flap on the front of the drive and blew in. After getting a mouthful of dust, I repeated the action and then did the same on the other drive.

Since then both drives have gone back to only requiring a weekly cleaning. Who says the Nintendo Generation has contributed to troubleshooting?