Wednesday, October 14, 2009

BES - Activation / Message Issues

Dealt with a rather annoying issue today regarding BES access: 4 users were unable to receive email while others were fine. I was able to figure it out with a little digging and some help from the Blackberry Technical Solution Center.

The Behavior:

- Certain Blackberry users are unable to send/receive email
- In the Application Event logs, you will see this:

1 user(s) failed to initialize

{} MAPIMailbox::Construct - Open Root Folder failed

OpenRootFolder - Mailbox::m_pMDB->OpenEntry (0x80004005) failed

- if you try to remove/add the affected user, you will get the "user(s) failed to initialize) error while still being able to add a new user

Here is what you do:

1) Ensure that the BB Service account (by default, it should be called BES Admin) has all the required permissions according to the setup documentation
2) Use IEMSTest.exe to confirm that BESAdmin has access to the users mailbox
3) Right-click the user in BlackBerry Manager and click "Reload User"
4) If the logs return that the user failed to initialize, restart BES

Note that these steps apply to BES v4.1.6MR and prior. Not sure if the steps are the same in version 5


(From BB KB01150)

Friday, June 5, 2009

Boot Images and OS's

A little tidbit that I learned while researching the 760/E6400 issue (This is from Michael Kelley [MSTF] over at the Technet Forums):

"You can deploy an x64 operating system from a 32-bit WinPE. This combination allows you to use a 32-bit WinPE, run various hardware tools (such as doing BIOS configuration, configuring a RAID controller, etc.) as task sequence actions, and still deploy an x64 operating system. Many of these tools are 32-bit executables. x64 WinPE does not include the WOW layer that full x64 Windows has, so it can't run 32-bit tools.

Deploying a 32-bit operating system from x64 Windows PE is not supported..."

Link to Post:

Optiplex 760 and Latitude E6400 / OSD Issues

This has been one of the most frustrating driver builds i've ever had to do. After adding the 760 to our driver standard, functionality became broken for the E6400 (it restarts as soon as WinPE loads). After struggling for a day to figure out what is going on, I learned something new!

One thing that I can't seem to find is some good documentation as to what command line options are available in WinPE 2.1 (Vista). A useful command that I learned in my travels is drvload:

1) Make sure you enable Command Line support in your boot image
2) Load all of your NIC driver candidates onto a USB Memory Stick
3) Boot your reference machine, when you get into WinPE, press F8 to bring up a command prompt
4) Use the following syntax: drvload inf [Path to INF]
Example: drvload e:\folder\driver.inf
5) Once it reports that the driver loaded successfully, run ipconfig to see if any IP info is listed (if you only get "Windows IP Configuration" then the driver is not correct, move onto the next one)

Once you find the driver that works in WinPE, import it into your Boot Image.

Wednesday, February 11, 2009

Adding Updates too Office 2007 Products

While this may seem like a mundaine task, the initial documentation from MS isn't very clear about how to add updates too a deployment of a 2007 product. Yes, you can find it in the technet documentation, but we don't always have time to go searching. Here is how you do it:

For initial deployents, the installer looks too a folder called "Updates" for any updates that need to be installed for the product. Sounds simple enough, however you can't just download the full file patch and save it there, it has to be extracted.

The Updates folder is limited too MSP installs, the full file patches that you get from Microsoft are .exe, however you can extract the .MSP files by using the following command:

filename.exe /extract:"pathtoupdatesfolder"

If you do not type in the path, you will get prompted for the location to save the updates too. Don't worry about duplicate files.

Info taken from: