Wednesday, October 27, 2010

DROID X Won't Ring, Vibrate Only? Tried Everything?

I rarely post because I am busy. But this might help someone.
Anyway, one of our new DROID X users could not get his phone to ring anymore after using "SMART PROFILE: FACE DOWN" option. It worked as it was supposed to, but the phone remained in "vibrate" mode ever since. We tried everything.

The Motorola forums are filled with the problem, and one in particular had a thread with a Motorola Rep named "Matt" presenting a fix "without a hard reset." It is obvious why people would not want to hard reset their phones. It's not about the applications (they can easily be redownloaded from the Market), and it is not about email or anything hosted in Google. It is not wanting to reconfigure the damn thing!

I have 20 DROID X users, each I had to configure to communicate with Exchange, and personalize to secure them, and make them the most effecient. I don't want to have to do that all over again.

Anyway, here is the solution, it was brought out by a user on the Motorola forums as an afterthought, which turned out to be the solution. Thanks for the tip "Salsero."

SOLUTION:

Calibrate your compass in the Settings > Location & Security. Do it slowly and patiently, not too fast. Continue doing the motions until it turns green. It is frustrating within itself I know, because it can be difficult to calibrate the compass.

Once it became Green for a successful calibration, I called the phone and it rang. I then went to the settings for Sounds and disabled (unchecked) Smart Profile: Face Down.
Hope it works out for anyone still having that same issue. This specific DROID X was on Froyo 2.1.

Friday, February 26, 2010

Monitor User Email with Exchange 2007

Since I'm on, let me briefly explain how to monitor your user's email, both incoming and outgoing. I used to do this in a similar way in Small Business Server 2000.

In Exchange 2000, I simply created a Distribution group with me being the member. Then I placed the group into the Exchange server's properties for "Archiving." Then simply create a rule in Outlook to organize all this email your inbox is going to get flooded with.

Of course there was another way, by using a journal type feature which I believe was more demanding on the server, but that is just my opinion.

In Exchange 2007 you can still "archive" the same way using the Journaling feature but unless I find a reason not to, I will be doing it by using Transport Rules instead. Some references mentioned performance degradation using Journaling. At the same time I've also read that the transport rules take a dump after a handful of them. In any case, that's what I've read and not what I've experienced, at least not yet.

Here are the simple steps:

Using Exchange 2007 Transport Rules to 'Monitor' Users Emails Inound/Outbound

  1. Organization Configuration > Hub Transport > Transport Rules
  2. Create a New Transport Rule
  3. Step 1 Select Condition(s): [x] Sent to a member of distribution list
  4. Specify the distribution list that all your users belong to
  5. Select Action(s): [x] Blind carbon copy (bbc) the message to addresses
  6. Select the email address, for example your own
  7. Select Exception(s): [x] Except when any of the recipients in the To field is people
  8. Select yourself again. This should prevent redundancy if you belong to the distribution list too.
  9. Finish
Then create a rule in Outlook that filters this email to a subfolder in your "Inbox." You can use "Where my name is not in the TO box" rule to accomplish this.

Hope this helps better manage email monitoring. Remember to keep in mind the legalities and invasion of privacy when it comes to email interception. In most cases a detailed email policy can inform all employees of such monitoring which would release you of liability, however check with your own state laws to be sure.

Using Exchange 2007 to Add Email Disclaimers & Prevent Redundancy

While I have not been too talkative as of late (mainly due to being tired and stressed and busy,) I wanted to make this brief post in case anyone was looking for a simple solution.

If you want to add a disclaimer to outbound emails there are plenty of tutorials out there that show you how to do it already. Google Search: Exchange 2007 Email Disclaimers

However just for giggles, here is the quick run down:

Adding Disclaimers at the Organizational Level

  1. Organization Configuration > Hub Transport
  2. Transport Rules Tab
  3. New Transport Rule
  4. Step 1 Condition: [x] From a member of distribution list (Select a distribution list with members you wish this rule to apply to) HIT NEXT
  5. Step 1 Select Action(s): [x] Append disclaimer text using font, size, color (etc)
  6. Here of course enter the text you wish your disclaimer to say, or simply use a common/generic one and edit it. At emaildisclaimers.com you can find useful information regarding these legal notices. HIT NEXT
  7. Step 1 Select Exception(s) if necessary:
  8. [x] Except when the message is SENT to users inside or outside the organization
  9. Choose "Inside." (Steps 7 and 8 are optional, depending how you want it to work. I personally didn't want a disclaimer attached to incoming messages but only to those going outside.)
  10. [x] Except when the TEXT PATTERN appears in the subject or body message
  11. Here simply copy and paste some of your disclaimer, a sentence or less, preferrably less, but choose a portion that seems unique enough to the Disclaimer. So don't choose something like "and the" as this will appear in most emails and the disclaimer will fail to apply. This rule is what will prevent your system from applying the disclaimer to emails that already contain disclaimers. This is useful especially in conversation-type emails where there are a lot of replies. It will prevent clutter.
That's it! Of course test it a few times with an external email and reply back and forth; there should only be one disclaimer from your domain. Hope this helps.

Monday, January 25, 2010

AdminAlive finally went to sleep: this why you thoroughly test migrations, I just pulled a 64hr shift. :-/ and 98% complete. There still needs to be a lot of configurations and tuning done. Goodnight, you know it's been a long day when you start dreaming with your eyes open...

Thursday, January 21, 2010

Days Before the Migration

Here I am sitting with anxiety just a day away before I actually begin the real migration of the server. Up to this point I have mainly been focusing on fine tuning all client machines for performance, security, updates and just plain fine tuning.

Today I had to make sure I brought the network cameras back online. They had been offline for a couple of days (2 of them) because of there being no slack in the CAT5 cables. While there is slack I wasn't able to pull it. The reason being was when the holes in the attic floor and drywall were being plugged with expanding foam, the slack was left behind the foam thus locking it at its shortened state. So I had to climb up there and do some dungeon crawling. Here are a few pictures of the adventure in First-Person-View action:







Tuesday, January 12, 2010

Small Business Server 2008 R2 Anyone?

Yeah, you looking for it too eh? Well you won't find it because it doesn't exist. Seriously, considering we just purchased SBS 2008 for our network, I am disappointed that it does not come with several features I was hoping it would come with since Server 2008 R2 has been out for a while now. For example, AppLocker and DirectAccess support, but there isn't any "R2" for SBS 2008!

At this time, until they release a new version or I purchase another server for this purpose only, we will not be able to utilize any Windows 7 features that are actually new and useful. So what does this actually mean? Well, purchasing any Ultimate or Enterprise editions of Windows 7 is pretty useless. Unless you want to play with BitLocker, but if you stand back a bit, the price increase for such a feature doesn't really feel that great. It'd be another thing if you'd be able to utilize all the other features, but if you cannot, what's the point?

Anyway, I just received an email this morning, the server is finally on its way, about 2 months later! At the moment I am finishing up the accounting department's migration to a new version of their software to new machines. And since I currently do not have the resources or space to carry out a lab on Windows 7 64, I am going to run it on a guinea pig user. Least critical machine I could find, see how it works out.