[TheMeister]

Hi,
I'm building a BES for Exchange test server and want to know if there is a problem if I point it to my prod Exchange server.
Prod already has the Prod BES server with it's own DB.

Test would also point to the Prod Excahnge and have it's own DB with only test users assigned to it.

Any problems with that type of setup?
I do not have a test Exchange setup.

[hdawg]

no problems ... I'd recommend also using a different besadmin user for this "test environment" too.

If you wanted to be real nice to yourself you could put all the test users in a specific store or storage group.

[juwaack68]

Hi hdwag.

This is interesting. We have a QA BES that is pointed to a QA Exchange server. However, the Exch server doesn't communicate with the outside world (I don't know why, I'm not the Exch admin, and I didn't stay at a Holiday Inn last night).

I'm looking to rebuild the QA BES (to get it from Win2000 to Win2003), and having it point at Production seems like it would be much easier to do Enterprise Activation.

[hdawg]

Originally Posted by juwaack68

Hi hdwag.

This is interesting. We have a QA BES that is pointed to a QA Exchange server. However, the Exch server doesn't communicate with the outside world (I don't know why, I'm not the Exch admin, and I didn't stay at a Holiday Inn last night).

I'm looking to rebuild the QA BES (to get it from Win2000 to Win2003), and having it point at Production seems like it would be much easier to do Enterprise Activation.

I would try to convince someone to let that QA Exchange Server have access to the Internet. If you already have the environment, and policy / "security" is preventing you from doing your job (assuming that making sure BES is happily working is part of your job) then justify the need for it. Having a test / qa environment is critical, and you can't truly test unless you have something similar (if not identical) to your production environment. If the QA environment is significantly different than your production environment you very well may be better off having the QA BES using your production Exchange ... especially if Exchange isn't similiar in QA.

I understand keeping things separate; I try to do it all the time ... sometimes you just can't due to resources, and you do what you can.

and now I'm starting to ramble ... that said, I think you know where I stand on this one

[TheMeister]

Originally Posted by hdawg

no problems ... I'd recommend also using a different besadmin user for this "test environment" too.

If you wanted to be real nice to yourself you could put all the test users in a specific store or storage group.

Thank you very much.

[juwaack68]

Originally Posted by hdawg

I would try to convince someone to let that QA Exchange Server have access to the Internet. If you already have the environment, and policy / "security" is preventing you from doing your job (assuming that making sure BES is happily working is part of your job) then justify the need for it. Having a test / qa environment is critical, and you can't truly test unless you have something similar (if not identical) to your production environment. If the QA environment is significantly different than your production environment you very well may be better off having the QA BES using your production Exchange ... especially if Exchange isn't similiar in QA.

I understand keeping things separate; I try to do it all the time ... sometimes you just can't due to resources, and you do what you can.

and now I'm starting to ramble ... that said, I think you know where I stand on this one

I'm right there with ya, hdawg. I'll see if I can get them to change the QA Exchange to access the internet. That would be ideal.....

btw, I'm still pursuing the other thing.....