[Deas]

hello,

i have my bes test setup running this way - exchange 2007 sp2 ru2 on w2k8 sp2 and bes 5.0.1 mr1 on w2k8 r2. just install what bes tells you and there is no problem with the mapi profile.

brgds Deas

[kjarrodc]

fyi - as of april 8th, bes 5.0.1 on 2008 r2 64bit is supported on the compatibility list.

[dcolpitts]

I can confirm I have BES Express 5.0.1 running on 2008 R2 with NO issues. The client has a single HP DL380G6 with ESXi 4.0 Update 01 installed on it. We are running two 2008 R2 VMs. The first VM has Active Directory, File & Print services, BackupExec 2010, and Exchange 2010 Standard Edition. The second VM has BESx 5.0.1 install in it, and ABSOLUTELY nothing else. The BESMGMT database resides in the first VM and is the same instance that BackupExec 2010 uses.

dcc

[lion777]

well.. have anyone tried BES 5.x.x with Win2k R2 Domain controllers?

Cheers..

[SmoothRunnings]

Originally Posted by lion777

well.. have anyone tried BES 5.x.x with Win2k R2 Domain controllers?

Cheers..

In short you should never install anything on your domain controllers especially BES; this is following microsoft's best practices (if you are MS certified you'd know that already).

But if you must there shouldn't be a problem. :o)

A.

[lion777]

Meaning of my question is : Have anyone installed BES 5.x.x in Win2k8 R2 Domain environment.

Cheers!!

[dcolpitts]

Originally Posted by lion777

well.. have anyone tried BES 5.x.x with Win2k R2 Domain controllers?

Cheers..

Uhh - did you read the post IMMEDIATELY above your question? That would have very clearly answered your question. YES.

[Alexander]

Be aware of this nice hidden feature of W2K8:

Microsoft's Knowledgebase artice KB949469:

Quote from the article:
'NSPI connections to a Windows 2008-based domain controller may cause MAPI client applications to fail with an error code: "MAPI_E_LOGON_FAILED

This behavior occurs because Windows Server 2008 only allows for a default maximum of 50 concurrent NSPI connections per user to any domain controller. Additional NSPI connections are rejected with a MAPI_E_LOGON_FAILED error code.'

Took me 2 days to figure out.... because the error is logged in the eventviewer on the DC