[sems]

Originally Posted by RipThorn

Hi Gary

I think i found out what the problem is

when adding permission you use the following line
get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

the line that works for me is
get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights Genericread, GenericWriteExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

only after adding Genericread and genericwrite my MAPI errors went away

thank you

On a test bed we have, I keep on getting MAPI error, "Bookmark is not valid". I checked besadmin user's global address list priviliges via ADSIEdit, I tried apply what RipThorn has written, still no dice. The error occurs when I try to run Blackberry Manager or edit MAPI profile for Blackberry Server.

Any suggestions?

[tassiehawk]

Originally Posted by MtnHermit

Thanks for the great post. I followed your howto (ignoring one line) and installed BES Express 4.1.4 directly on a brand new Win2K3 64 / Exchange 2007 and had no problems running it in the 64bit environment. As far as I can tell, everything is functioning perfectly.

Thanks again for your post.

What step did you miss, as every time i install 4.1.4 onto my 64 bit 2007 exchange machine, exchange stops as it cant handle 32 bit .net 1.1 and 64 bit .net 2 (which exchange 2007 needs)?

[tonywall]

Anyony getting the "could not open default message store" with MAPI and Exchange 2007 installations probably took the default (recommended) option in Exchange Setup to NOT support older MAPI clients. This means there is no "Public Folders" database. Follow the MS KB article on how to create them, basically create a new Public Folder database in your First Storage Group called "Public Folders". Once this was done BES Manager was able to connect without error Enjoy!

[tonywall]

This helped thanks, but also I found I needed to:-

1) Enable MAPI access in Exchange 2007 by creating the Public Folders database (the setup routine suggests you sould not support Outlook 2003 clients by default, so does not create it - but that causes BES to fail on MAPI connect).

2) Add the Mailbox (not just AD) permission to the blackberry user mailboxes for BESAdmin to have AccessRights (not just ExtendedRights) of FullAccess. See the MS KB: How to Allow Mailbox Access

Cheers! If this really works I take a holiday, this should not be so difficult!

[sems]

Originally Posted by sems

On a test bed we have, I keep on getting MAPI error, "Bookmark is not valid". I checked besadmin user's global address list priviliges via ADSIEdit, I tried apply what RipThorn has written, still no dice. The error occurs when I try to run Blackberry Manager or edit MAPI profile for Blackberry Server.

Any suggestions?

I fixed my issue by:

I opened ADSIEdit, went to

CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=HMC 40 Green Field Test,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=dom ain,DC=biz

And add Read and Open List permissions, voila it seems to work now

See my other thread at: http://www.blackberryforums.com/bes-...-2007-bes.html

[teklach]

Hi!

I'm pretty new at all this, so I'll try to be as clear as I can!

I installed BES on an actual working Exchange 2007 X64, and the installation went fine.

I had to add the blackberry user in the list, and it worked. I configured everything for this user, but there's one thing I don't understand: when I try to use Enterprise Activation on the blackberry, acter 2-3 minuts, the blackberry says: Activation failed, please contact your administrator.

So I tried with the USB cable, plugged in the user's computer and when I look in the device manager, I see that it's trying to connect to the server, but with the wrong adress...

The adress should be boumboum.no-ip.info but instead it's activationbb.boumboum.com

Where can I tell the blackberry the right address to connect to?

Thank you!

[Inphektion]

Just to add to this, BES 4.0.x runs fine in an exchange 2007 environment. you simply need to remove esm if you have on bes server and install the new mapi and cdo files as referenced in this thread then change some permissions in exch 07 and works fine. I only ran it for a week before upgrading to 4.1.4 so can't post anything else about it now.

[teklach]

Originally Posted by Inphektion

Just to add to this, BES 4.0.x runs fine in an exchange 2007 environment. you simply need to remove esm if you have on bes server and install the new mapi and cdo files as referenced in this thread then change some permissions in exch 07 and works fine. I only ran it for a week before upgrading to 4.1.4 so can't post anything else about it now.

Anywho, even if the "Enterprise Activation" didn't work, the BES catched the PIN of the user and everything works fine...exept it's only one way: from exchange to the phone, and not from the phone to exchange.

Any ideas?

[teklach]

Hi! Everytime I try to add the BESAdmin with these commands:

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

I get that error:

[PS] C:\Documents and Settings\Administrator>get-mailboxserver exchange | add-ex
changeadministrator BESAdmin -role ViewOnlyAdmin
Add-ExchangeAdministrator : The input object cannot be bound to any parameters
for the command either because the command does not take pipeline input or the
input and its properties do not match any of the parameters that take pipeline
input.
At line:1 char:55
+ get-mailboxserver exchange | add-exchangeadministrator <<<< BESAdmin -role V
iewOnlyAdmin
[PS] C:\Documents and Settings\Administrator>

Thank you for your help!!!!!

[Inphektion]

Just follow this:
KB12483
worked perfectly for me.

[teklach]

Thank you! I'll try it later!

Bye!

[garycutri]

Originally Posted by teklach

Hi! Everytime I try to add the BESAdmin with these commands:

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

I get that error:

[PS] C:\Documents and Settings\Administrator>get-mailboxserver exchange | add-ex
changeadministrator BESAdmin -role ViewOnlyAdmin
Add-ExchangeAdministrator : The input object cannot be bound to any parameters
for the command either because the command does not take pipeline input or the
input and its properties do not match any of the parameters that take pipeline
input.
At line:1 char:55
+ get-mailboxserver exchange | add-exchangeadministrator <<<< BESAdmin -role V
iewOnlyAdmin
[PS] C:\Documents and Settings\Administrator>

Thank you for your help!!!!!

After you have created the BESadmin account then manually go to delegate control and add BESadmin as a Admin View Only Administrator. Then just run the second script.

[brinaht]

Good Afternoon. My organization is running a mixed platform for 4 Exchange Servers until we migrate to 2007 within the month. (2 2000 Servers, 1 2003 Server, and a test 2007 server).

Until we get the other 3 set up as 2007 servers, do we need to move the besadmin account to the new 2007 test server? I read that we really can't run a 2003 and 2007 together because of calendar synchronizing problems. We want to update to 2007 as swiftly as possible, but there is going to be days when the servers will be running mixed until all servers are updated.

What would be your suggestions?

[hdawg]

You don't need to move your besadmin account, but rather you need to make sure you have the most up to date MAPI / CDO dll's on your BES. That said, you only need to worry about mailbox servers ... you can get the MAPI Client and CDO dlls from Microsoft

[zartar]

Is there a work around for the calendar synchronization for a 2000/2003/2007 exchange environment yet?

Or am I out of luck and will have to do a Exchange & BES upgrade all at once?

[hdawg]

What do you need a work around for?

[sems]

Originally Posted by zartar

Is there a work around for the calendar synchronization for a 2000/2003/2007 exchange environment yet?

Or am I out of luck and will have to do a Exchange & BES upgrade all at once?

What calendar sync issue are you refering to? Calendar sync works fine for us with Exchange 2003 and 2007, running BES 4.1.4. (Has been fine with 4.0 as well)

[zartar]

Originally Posted by garycutri

Re: "does this mean you can't support 2003 and 2007 with the same BES server"

If you have Exchange Systems Manager 2003 installed on the BES server it will fully support Exchange 2003 but won't fully sync with Exchange 2007 (e.g. Calendar sync doesn't work). If you remove Exchange System Manager and install "MAPI Client and Collaboration Data Objects 1.2.1" it will fully support Exchange 2007 but will have sync issues with Exchange 2003 (e.g. Calendar sync doesn't work).

Sorry what I mean was Is the above still an issue or has it been fixed?
I'm planning on migrating from Exchange 2000 to 2007 while keeping the existing BES server.

From what I understand I would have to remove the ESM and install the MAPI client and cdo up date for it to sync with Exchange 2007. But doing so would cause issues with older Exchange.

[mitchelrl]

[PS] C:\Documents and Settings\mlewis.WPI>add-adpermission -user besadmin -acces
srights ExtendedRight -extendedrights Send-As, Receive-As, ms-exch-store-admin

cmdlet add-adpermission at command pipeline position 1
Supply values for the following parameters:
Identity: besadmin
Add-ADPermission : The operation could not be performed because object 'besadmi
n' could not be found on domain controller 'WPI-ARCHIVE.internal.blah.com'.
At line:1 char:17
+ add-adpermission <<<< -user besadmin -accessrights ExtendedRight -extendedri
ghts Send-As, Receive-As, ms-exch-store-admin

This seems so trivial. but for some reason, I'm having a problem with the second cmdlet. Suggestions?

[mitchelrl]

I have an account BESadmin, it has view only rights, the first CMDlet was a breeze, but when I try to perform the second, that's as far as I get.

Suggestions, help or a smack in the head for overlooking something simple would be greatly appreciated.