VMWare Virtualization Forum 2008

Looking for a conference to learn a little more about VMWare and Virtualization? Check out the VMWare Virtualization Forum 2008. They probably have one coming near you!


Exchange 2007 – How to Remove the Last Legacy Exchange Server from an Organization

UPDATE: April 23, 2008

Today I used the MS Technet Article on “How to Remove the Last Legacy Exchange Server from an Organization”.  There is one section that is very confusing.  Under the “To remove the last Exchange 2003 or Exchange 2000 server…” section, number 5 gives a Command Shell command to run.  They put “dc=<domain>” but it’s actually “dc=<domain>,dc=<ext>”.  I don’t think “ext” (domain extension) is the correct term, but here’s the example:

My domain name is scc.com, so my command shell will look like this:

Remove-ADPermissions “dc=scc,dc=com” -user “scc.com\Exchange Servers” -AccessRights WriteDACL – InheritedObjectType Group

If you do not have your “dc” correct, then you will get errors!  Copy and paste the code above and change it to match your domain name. 

Thanks to my good friend and volunteer, John S., for spending the time and research to get through this issue on his own Exchange 2007 Server, and for immediately passing it on to me! (We both did our Exchange 2007 Upgrades/Migration at the same time)  Hope this helps!

Blogging with Office 2007

Not only can you have your Outlook 2007 pull your favorite RSS feeds directly into Outlook, you can also use Word 2007 to create and post blogs directly to your blog from your Word document…

“How do I get started?”, you may be thinking!

  • First you’ll want to open Word 2007. Once you have Word opened, simply click your “Office Button” and then click “New”.
  • Once you click new, you’ll be prompted do you want to create a new document or a new Blog. Select Blog.
  • Then you’ll need to register your Word 2007 with your blog. I use WordPress, so I simply chose “WordPress” in the drop-down menu.
  • You’ll be prompted for your Blog link, as well as your user name and password. Once you have typed this information in, your computer will be registered to publish directly to your blog. Images and all!

Try it out!

Dameware Mini Remote Control

Dameware Mini Remote Control is a Remote Desktop software that I’ve been using for almost 6 years now. Dameware is an application that will allow you to interactively remote control another workstation on your network. When you log into your users computer, you can see their desktop and they can also see you on their desktop. This is great for those who support multiple buildings, or even a single building with employees spread out. If your user has an issue on your network, simply log into their computer and see exactly what’s going on. You can then reconfigure, or fix the problem however you need to without leaving your desk.

Dameware is licensed per technician, so one technician can log into an unlimited number of computers. The best part, Mini Remote Control is only $89.95!

What are you using to provide remote assistance to your users? If you are currently not using anything, I would highly recommend downloading a 30 day trial from www.dameware.com. You will not be disappointed.

SCC installs first Linux Server

This week we installed our first Linux Server. It’s a CentOS box that is being used as a Web Development Server in-house. Our Production Server will be a RedHat box Dedicated Server hosted offsite. So far so good. We have a few volunteers that are great with Linux who helped with the installation and on going support. I am interested in learning as much as I can, since I am ultimately responsible for the server.

All you Linux users, post some “must have” or “must know” comments that will help with managing and maintenance of this new server. I’m all ears (or “all eyes” I guess I should say, since I’ll be “reading” them) 🙂

BES – Message Status: Desktop email program unable to submit message.

BES – Message Status: Desktop email program unable to submit message.

Windows 2003 SBS with Blackberry Professional Software Server installed in the SBS server.

I ran into this problem at a side job/contract job, that I worked last weekend.  Although we don’t use SBS at the church, and this particular problem didn’t happen at the church, I wanted to post it on my blog for anyone doing a google search on the same problem.  Hopefully you’ll find this blog sooner than later and save time troubleshooting.

You can install Blackberry Professional Software on Windows 2003 SBS.  You’ll need to create your BESAdmin account in AD and be sure the account is a member of Domain Users (not admins).  You’ll also need to make sure that BESAdmin has Send As rights on your Exchange Server.  Then log into the SBS as BESAdmin.  Once you have BES running correctly, you can log out and log back in as Administrator to mange your SBS server.  If you need to do anything to BES, log back out and back in as BESAdmin.

Here’s the problem we ran into: the user could receive e-mail, and the calendar, contacts, etc seem to sync.  But when the user tried to send an e-mail, he would get:  Message Status: Desktop email program unable to submit message.  We checked the users Security in AD and had to add the BESAdmin to the Security with Send As rights.  Within 30 minutes later, the BESAdmin had disappeared from the Security on the account.  Ultimately, our problem was that this particular user was part of the “domain power users” group.  This is a privileged group.  We removed the user from the group and all is well.

Check out this link for a more detailed and official explanation of the problem:


BES – Message Status: Service Blocked

Out of 11 Blackberry’s on our Blackberry Professional Server that I manage onsite at our church, I had trouble with two.  They both could not Activate wirelessly.  When I plugged in the cable, I could successfully activate via Desktop Manager. However, once I unplugged the cable, I could not send/receive e-mail, nor sync with Calendar, Contacts, Tasks, etc. When I tried to send an e-mail, I received a Message Status: Service Blocked.  When I called the service provider, the moment I told her I had a BES online, they said “I’m sorry, there’s nothing we can do since you have your server you’ll need to go through Blackberry.  I can help you wipe the phone as a troubleshooting step, but from there, I’ll have to transfer you to RIM.”  So they transfered me.  After spending almost an hour on hold, I spoke with RIM.  I gave him the PIN numbers of both Blackberry phones and sure enough, they said that neither phone had the service provisioned on their phones to allow them to connect to a Blackberry Enterprise Server.  He told me to call back the service provider and ask them to be sure that the phone has the correct plan to work with a Blackberry Enterprise Server.  After doing this, we found out that the phone had a service plan that allowed for Blackberry Internet Mail (not BES).  They upgraded the plan, reprovisioned the phone, and all is working.

So… if you are receiving  Message Status: Service Blocked, call your service provider and ask them to verify that your account is provisioned to work with a Blackberry Enterprise Server.  Once they change the plan and re-provision the account, you should be all set to Activate Wirelessly.