Recent content by ee61re

By default, yes it would, because the default domain name is *. However, you can add entries for specific destination domains. For example, you could place an entry there for abc.com, and allow OOF for them - maybe your company works closely with abc.com, so having them know when your people...

oops, sorry, I didn't mean recipient policies. Have a look here: http://www.support.microsoft.com/kb/262352/ Rob

You can allow/disallow OOO messages being sent out to specific destination domains, by creating an appropriate recipient policy. I dont think there is a way of basing the restriction on sender though.

From the client, can you ping the exchange server by name?

I stand corrected. That said, it seems to rely on the recipient having Outlook, the message being sent using at least Rich Text, and for some features, assumes an Exchange server is in the loop. Otherwise, its just another header entry, I suppose.

The private/confidential/personal/normal flag that a user can set on an email is just a flag, nothing more. Its value doesn't change any security at all.

import the PST into the persons mailbox, then configure Outlook to connect to that mailbox. Why not use MAPI (Exchange protocol) for desktops and laptops - IMAP is a protocol intended for remote users, in the same way that POP3 is.

the server may well already have the RSA board installed in it. Depends what you ordered, etc. We have 150+ 336s with RSA. We have them connected to a switch, and the RSA cards default to getting an IP address from a DHCP server. Assuming you know the IP address of them, you can then connect...

how are you moving the mailbox? If you are using exmerge, then you need to remove the user from BES, move the mailbox, then add the user again, because the hidden items in the mailbox don't work properly after having been exmerged into a new mailbox. If you are doing a 'traditional' move...

They start with a 1. Rob

The DHCP server needs to be on the same subnet as the RDM server, but doesn't have to be on the same server as RDM. In fact, from testing we have been doing today, it performs a lot better if the 2 functions are kept apart. Assuming your client systems are all in the same subnet as the DHCP...

or under discovery preferences, setup a unicast range that covers the IP addresses in each subnet - therefore no broadcast or relay required. alternatively, if your network config allows subnet directed broadcasts, you could just enter the subnets into the discovery preferences. I suspect that...

no. Our dev setup was like this. Our live setup runs 2003 server, and the director/rdm and dhcp installs are on the same box. are you actually having a problem? Or are you just playing 'what if'? Rob

probably worth upgrading director to 4.20.2 and RDM to 4.2, to see if the problem goes away? Rob

Possible. Why not break the team and just run as single NICs for a while, see if the problem goes away? I would probably look into upgrading the NIC drivers first though, and possibly the NIC firmware.