Blog Archives

Sansa to IPOD conversion

I have been using an 8GB Sandisk Sansa for my mobile media needs…that is up until last night.  I traded a new graphics tablet I bought at a CompUSA closeout for a 4GB IPOD nano with video.  At first I was going to give it to Liz, but after tinkering with it for a while I decided to keep the IPOD and give her the Sansa.  There are several reasons for this..

1. She won’t use the IPOD to its fullest extent (I will)
2. The Sansa has more storage space so she can put more photos on it and use it for client demos for her photography clients
3. I already have accessories she would need such as the carry case with clip so that she can take it with her more easily.
4. I would use the video playback more than she would.

So it worked out great for us both, she got a device she can use to store her favorite music, use in her photography business and its easily portable and easy to use.  Plus the Sansa has a built in FM radio so she can listen out and about. 

So now I have to convert all my WMA files to mp3, since some of them were DRM protected, I have to obtain the non-DRM protected versions so that I can import them into my itunes library.  I use both Rhapsody and Itunes now, I think Rhapsody has a nicer interface, but itunes is definately easier to get podcasts and audiobooks, etc. 

Advertisements

FIOS customers – better DNS solution

If you have Verizon FIOS, and haven’t already customized your router to use better DNS Servers, do yourself a favor and do so asap.  By default Verizon uses “DNS assistance” on their *.*.*.12 DNS servers.  Set your router to use custom DNS servers and change the ending .12 to a .14.  Alternatively, using any of the other official Verizon DNS Servers in the range of 4.2.2.1 through 4.2.2.5 is also a good bet. 

If you don’t customize your DNS, the Verizon DNS assistance configuration can potentially cause issues for Tech Savy users who do VPN, host monitoring, etc.  You are also helping Verizon make more money by being served ads on their DNS assistance page. 

I came across this help link on the Verizon website that will guide you through changing your router config to optomize your DNS settings…

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.

Help and Support service missing in Server 2003

I ran into a situation in which the Help and Support service in server 2003 dissappeared.  I had no idea why, and for a long time left it alone.  I then did some digging and found a KB article from Microsoft describing how to re-install the service.  Follow these instructions (taken from MS KB article 937055):

To resolve this problem, reinstall the Help and Support service. To do this, follow these steps:

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, locate the following folder:

%windir%PCHealthHelpCtrBinaries
3. At the command prompt, type the following commands, and then press ENTER after each command:

HelpSvc.exe /regserver /svchost netsvcs /RAInstall
HSCUpd.exe -i hscmui.cab
HSCUpd.exe -i hscsp_s3.cab

Note The following commands do not apply to some language versions of Windows Server 2003:

HSCUpd.exe -i hscmui.cab
HSCUpd.exe -i hscsp_s3.cab

The reason is that the Hscmui.cab compressed file is not included in some language versions of Windows Server 2003, such as the Japanese version of Windows Server 2003.

Goodlink 5 deployment issue

I have been working on deploying multiple Goodlink 5 messaging servers recently, and came across a problem with the user migration feature in Goodlink 5.  Normally if you have more than one Good messaging server, you have the option to “change good messaging server” when you right-click on a user account.  So in my deployment when I didn’t see this option enabled, I had to call Goodlink support.  What I found out made sense, but is definately irritating. 

I called Goodlink support before deploying Goodlink version 5 to ask about deployment options and get some advice on my project.  I asked about the user migration feature and using multiple GoodAdmin mailboxes, and was told that it should work fine.  Now here is where the issue comes in.  In my deployment scenario, I wanted to deploy multiple individual Goodlink 5 servers in various locations/offices around the world.  The limitation here is network bandwidth and latency, due to the fact that the offices getting these Goodlink 5 servers are spread across the globe on various speed networks, and some of the offices in Asia for example, have very high network latency and bandwidth is limited.  To help with this situation, I asked if it would be advisable to use multiple GoodAdmin mailboxes, one for each new Goodlink 5 server, that way, each location that got a Goodlink 5 server and had a local Exchange server, would get its own GoodAdmin mailbox homed on the local Exchange server.  This would increase performance, reduce the time it takes to re-connect all the mailboxes in the event of a reboot, and provided a better solution for my deployment project. 

When you use a single consolidated GoodAdmin mailbox, and you have more than one Goodlink server which is connected to the network on a low bandwidth link or one that has high latency, it is a good idea to have separate GoodAdmin mailboxes, to keep network traffic local to the office in question.  Its faster, more reliable, and if the central Exchange server that houses the consolidated GoodAdmin mailbox were to go down, all your Good Messaging servers would be rendered useless until the Exchange server is back online and the GoodAdmin mailbox is available again. 

So my scenario of using more than a single consolidated GoodAdmin mailbox was a good idea, still works well and does help with performance and all the other reasons I mentioned above.  The drawback is that in this configuration, from within the Good Messaging console, you only see the server you are connected to under the “Good messaging servers” folder.  This also means that the “change good messaging server” option is grayed out and unavailable.  The fact is that the GoodAdmin mailbox is what keeps track of how many servers you have, but they all have to be configured to use the same GoodAdmin mailbox in order for the server to “know” about the other Good Messaging servers you have in your network.  This basically means that the user migration option is not going to work for us. 

This is not a problem, its just an inconvenience.  And it would have been nice to have known this initially when I talked with Good support eariler.  Lately no matter what company I deal with, I usually end up getting conflicting information about their products and features based on who you talk to.  The first time I call and get info on something, I hear one thing, then when I am working on the deployment and have a question or problem and call back, I hear something completely different.  This is irritating and can cause some major problems for large projects. 

RPC over HTTP(S) for Exchange 2003 – single server

I’m pleased to announce that I’m now able to access my exchange mailbox from anywhere in the world using RPC over HTTP(s).  This was a lot easier to setup than I thought it would be, and following the steps provided by Daniel Petri helped a lot!  I also utilized the RPCFrontend tool that he mentions in the link.  This made things very easy and I got it working the first time I attempted the configuration. 

What this means is that I can now access my mailbox on my Exchange server, from anywhere with the only requirement being an internet connection.  I can just open Outlook, and go straight to my mailbox as if I were on my home network.  I highly recommend this for anyone with Exchange servers, it makes remote connectivity so much easier and can be fully secured with SSL and other security options. 

Now where will I eat?

I just found out that the nearest T.G.I. Fridays to my office just closed down.  No warning at all, and I was just there last week and there was no indication that they were closing the store.  This was the last one in close proximity to my office.  Last year we had one right across the street in the mall that we would frequent for special occasions, but alas it closed as well sometime last year.  With this most recent closing, that makes the closest location borderline too far from my office for regular use.  I guess I’ll have to pick out a new favorite preferred restaurant close by for future events or special occasions.  Not that there is any shortage of good restaurants, but Fridays had my favorite sandwich and recently improved it even better than the old version. 

Vista image resizer

I used to use the Windows XP powertoy “image resizer” which added a quick context menu resize ability to any image file. This was handy if I needed to quickly adjust or resize my images. Now in Vista, that ability is missing, and the powertoy from XP won’t work in Vista. So I found this Vista Image Resizer which is a free alternative. It also adds a context menu option to resize photos. And while it does work ok, I found it has a bug when resizing multiple images, if you leave the option set to resize the originals, it fails to do anything, but if you set it to make copies, then the copied images actually get resized.  This is only an issue if you have multiple photos selected and attempt to resize the originals.  Overall it’s a good replacement, and I recommend it as a replacement for the old XP powertoy.

Pasting links from OWA

I deal with Good support now and then for various technical issues with their mobile e-mail solution (Goodlink).  Today it appears they sent out a survey request to all of their customers, but I had to chuckle a little when I read the message and found they had pasted in the survey link through OWA.  If you read below, you will find the actual URL is missing the first h in the (http), and the actual linked URL is an Exchange OWA redirect link.  This happens when you copy a link from OWA and paste into another message.  By default in OWA, links point to the Exchange redirector and then take you to the link specified at the end of the redirect URL. 

I run into this issue myself from time to time and forget about this until I get a reply back to something I sent out with a complaint that the URL I sent does not work.  To get around I usually paste the link into notepad so I Can get a plain text copy of the link, and then I remove the Exchange redirector part.  I then paste in the plain text link which most e-mail programs and even OWA convert to a hyperlink automatically for you. 

I’m not trying to gripe about this flub, but find it humorous that such a mistake can be made by anyone and its nice to know I’m not the only person out there who forgets about this from time to time and sends out links that don’t work.  Now naturally a technically apt person could easily extract the correct link and get where they need to go, but the average person is going to reply and complain that you sent them a bad link.  Not just that, but now we all have the OWA logon link to their Exchange mailboxes.  (Don’t worry Good (motorola), I’ve hidden the actual OWA Link for your privacy) 🙂  (NOTE: I did receive a correction email from them shortly after receiving the message below).

Dear Valued Motorola Good Technology Group Customer:

Thank you for your recent inquiry into our support team. We appreciate the opportunity to serve you, and help you and your company meet your mobile messaging needs. To gauge the level of support you, and other customers are receiving, and to better understand where our strengths and weakness are, we are asking for your help.

By clicking on the following link and taking a brief six question survey, you will help us gauge the level of support we are providing our customers. This will allow us to know where our strengths are, and where we need improvement:

ttp://www.zoomerang.com/recipient/survey-intro.zgi?p=maskedsurveyidforprivacy <https://nosy.notmotorola.com/exchweb/bin/redir.asp?URL=http://www.zoomerang.com/recipient/survey-intro.zgi?p=maskedsurveyidforprivacy>

Please spend the two minutes it will take to respond to the survey questions so we will know how to better serve you in the future.

Sincerely,

The Good Technology Group Technical Support Team

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: , , , , , ,