Blog Archives

Vista SP1 removes search from start menu

I find this highly annoying as a user who frequently has to search for files.  It seems Microsoft removed the search button from the start menu in Vista SP1.  In my case, I couldn’t even use the (windows key + F) to launch the search dialog.  I had to search around and found this registry hack which restores search to the context menu when you right-click on a folder, adding “search” as an option.  This is the only way I can currently access windows search.  Use the following information to restore the search contact menu item…

Open Regedit and navigate to
HKEY_CLASSES_ROOTDirectoryshellfind

Rename the REG_SZ: ‘LegacyDisable’ value to something else like, say, ‘LegacyDisablex’

Exit registry editor and try right-clicking on a folder. You will see that “Search” appears again. You can now use this to access the windows search application. I still can’t get search back in my start menu just yet, but a little more google searching and I’m sure I’ll find a solution.

Black logon screen for Server 2003

This is the first time I’ve run across this issue, but what was happening is I’d see a black screen both through RDP and from the actual server console.  You could see a little bit of the windows logon box, but it was cut off where the username and password fields would be.  If you can fumble your way through the logon screen you’d be able to logon but everything was still black, the only color you’d see would be in the desktop icons.  This makes it virtually impossible to do anything on the server.  This situation does not cause a work stoppage, as all the background services ran fine, you just can’t logon and do anything. 

So I started searching around and ultimately ran across a MS KB article 906510.  I’ll paste in the information below, but the KB said it was an issue with the color scheme, and the registry values were all set to “0”.  At least that is whats listed as the cause of the black screen symptom, but it does not offer an explanation of what would cause the numbers to get set to “0” in the first place. 

To resolve this I had to do the following:  (NOTE: the drive mapping step was only needed for my solution as the server was not on the domain and not using internal DNS, so I could not authenticate on the domain).

1. Map a drive from another network machine to this server using local admin credentials.
2. Open regedit and connect remote registry to the server in question. (this will not work unless you map the drive first – see above note)
3. Use an export from a working server of the registry key noted in the MS KB and import that into the remote server.
4. Attempt logon through RDP or at the console, the color issue should be resolved. 

I wish I knew what caused this issue, but I can’t find much as to the actual cause.  I heard talk that maybe it was a disk space issue, but my server had 10GB of free space, so that wasn’t it.  Hope this information helps someone in the future.

My favorite registry hack

Do you know how annoying it is to try to quickly open a file in Windows that should be all text and naturally you want to open it with a text editor right?  Instead of being an easy process sometimes you have to go through a few steps to pick the program you want to open the file in.  Well here is a quick registry hack that will let you import all the settings necessary to add a context menu (right click menu) item called “open with notepad” when you right click on a file.  I personally like notepad better than wordpad (out of the build-in options in Windows), however, you could substitute your own text editor of choice here and save yourself a lot of trouble.  Just copy the code below into a new notepad document and save the file (to your desktop for example) with a .reg extension.  Then double-click on the resulting .reg file and click “ok” to add the registry information to your computer (NOTE: this only works on Windows operating systems). 

Now when you right click on a file, notice you have a new option in the context menu to open with notepad.  You can customize this as I mentioned to use your own text editor, just replace the name of the menu item and the executable name of your text editor in the code below.  Naturally you need to make sure the .exe is in a set user path so Windows knows where to get it. 

———————— (Copy below this line)————————————

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT*shellOpen with Notepad]
@=""

[HKEY_CLASSES_ROOT*shellOpen with Notepadcommand]
@="notepad.exe %1"

————————-(copy above this line)—————————-——-

Enjoy!

Tags: , ,

Ran into issue with LCS 2005 and OCS 2007

LCS 2005 (Enterprise Edition) is installed on a single server with SQL 2005 server for the backend database. ?There is no warning or indication that this would cause any problem and up until now it?hasn’t.? The software does allow for this type of deployment and works fine in this configuration.? OCS 2007 server was recently installed and configured.? During initial testing it was observed that users on the 2005 LCS server could not see presence data and communicate with users on the OCS 2007 server (and vice-versa).??After searching online for solutions it was found that there are two critical hotfixes for LCS 2005 that were said to correct this issue.?

Installing the hotfixes:
Following the instructions on the first hotfix documentation, I installed hotfix 911996.? The installer completed successfully and there was no indication of a problem.? Next I installed the second hotfix 921543, again the installer ran successfully and there was no indication of a problem.? I then checked the services for LCS and found that the LCS Server services would start, but then stop on its own with an error:

Event ID: 12299
Source: Live Communications Server
Details: The service is shutting down due to an internal error.
Error Code: 0xC3EE78F8.

The hotfix documentation mentioned this error as a possibility if you install the patch on the front-end server before the backend patch is installed.? However, since this was a single server deployment with both the back-end database and front-end server components on the same physical server, the hotfix only installed the update for the front-end components.? Again, there is no documentation saying this is not a supported configuration and the installer will gladly allow you do install both components together without a problem in the LCS 2005 setup.? (NOTE: OCS 2007 server prevents this configuration in the installer and will not install both components on the same box when using Enterprise Edition).? There is also no warning in the hotfix documentation not to install the update if you have both components on the same physical box.?

For a resolution, I called Microsoft support services ticket number SRX080212602272 and spoke to an afterhours support specialist.? After some initial troubleshooting and research the technician was able to review a similar case they had a few months ago.? He attempted the resolution listed in their issue history which did ultimately fix the issue.? To resolve, a string value must be deleted from the LCS 2005 registry branch (HKLMSoftwareMicrosoftReal-Time Communications{Your GUID}.? This key “role=EE” ?had to be deleted from the registry in order for the hotfix to install on the back-end database.? Once this was done, the LCS 2005 server service started successfully and we tested connectivity with a test account to verify that the server was working normally.? Basically this tricks the installer into thinking that the server is the backend database only, and it will allow the hotfix to install the back-end components.?

This issue could have been avoided completely if Microsoft had updated their documentation for the hotfix, especially since they had issues with this months ago and should have updated the documentation.? I am recommending to the technical support manager that the documentation be updated since this is a known issue and others have experienced the same problem.? Hopefully this will get done and prevent others from having the same issue.?

Tags: , , , , , ,

FIOS Update

So now that I’ve had FIOS for several months, I thought I would post an update. Here are my observations so far…

1. I love the ActionTec wireless router that comes with the service. It is a very flexible and fully featured with a firewall, MAC address filtering, port forwarding, and more. I took a little while to adjust to the settings on the router, as you have to click save in more than once place for your settings to be saved and applied, which is a little different, but once you figure out the little neuances of the router, you are good to go! It will do anything and everything I need and more.

2. My only gripe so far, is something that happened when my IP address changed. I had the service for probably over 2 months before my IP changed for the first time. When it did change, my home network lost internet connectivity and my dynamic DNS client was unable to connect to the internet to update my IP. This caused several hours of outage for my home e-mail and internet connectivity. I have not yet had another IP change, so I’m hoping the first time was just a fluke. (NOTE: This won’t be an issue for most people, unless you run DNS for accessing services on your home network like I do).

3. The speeds are consistent and fast, every time I run the Verizon speed test, it comes out over 20MBps down, and nearly 5MBps up, with only slight variations. The bandwidth is exceptional, very fast, and reliable. I have had not real service outages at all and am very pleased with the quality of service I am receiving.

4. In order to optomize the speed your computer will see on the FIOS network, it may be necessary to run the FIOS connection optomizer. This basically changes some TCP/IP settings in the registry to optomize throughput on the FIOS system. These are the same type of settings people have been adjusting since the internet was created, I’ve done it with dialup before, and this is just the most modern way to optomize the connection. Its no big deal, but you will see lower than advertized speeds unless you run the optimizer.

5. The price of the service is comperable to service with other providers in the area, but the speeds are much faster without increasing the cost of the service.

I am overall very pleased with Verizon FIOS service. I highly recommend it to anyone currently using a cable provider. I’ve been a cable user for years, and took a long time to make the decision to switch. I am happy that I did, and will never go back to cable. I would also point out that Verizon offers a 30 day money back guarantee, so you can always give it a try and test it out to see what you think. You can cancel at the service if you don’t want to keep it. Plus then your home will be wired for the service should you decide to use it again in the future.

McAfee mini-firewall issue

I had a server a few weeks ago that suddenly started experiencing blue screens of death for no aparent reason. It tooks a week or troubleshooting and digging to finally determine from a crash dump file, that the cause of the issue was the mini firewall component of McAfee viruscan 8.0i. I was able to disable the component in the registry and havn’t had a problem since. This server was an Iomega NAS p435m. So FYI – if anyone has any similar unexplained problems, check the mini firewall in McAfee, as it may be the cause, although in our case it took a memory dump file analysis to find out the cause.