• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 678
  • Last Modified:

Adding a recipient policy to only an OU

Hi All,

We need to add a new email address to our exchange setup.

The exchange server is currently setup for addresses of someone@company.co.uk
We now need to accept emails addressed to anotherone@companypoland.pl for a new set of users

The email domain (companypoland.pl) is registered and the MX is pointing to us so the only thing left to do is assign emails to the new domain address users. I would like to create all these new users in a new OU and automatically apply recipient policy to give them their new address @companypoland.pl but dont want this to apply to all users in the organisation, I have tried to apply a recipient policy with a filter on it to filter by OU, when creating this, the LDAP query appears as (&(ou>=""))

Is it me or should this be something like
(&(ou>="Staff Users/Company Poland"))

Either way I have tried creating this by firstly selecting the ou which gives,  (&(ou>=""))
and also creating a direct ldap query with syntax (&(ou>="Staff Users/Company Poland"))
After applying both these and forcing them the addresses are still not given to the users in that OU, it is as if it is ignored.

The policy has priority2 and is set to be responsible for all mails sent to this domain (new poland one)

Anyone any ideas?

Am I doing something wrong?

Will up points if it is a long job,

Thanks,
0
A4eIT
Asked:
A4eIT
  • 4
  • 3
1 Solution
 
SembeeCommented:
Recipient Policy cannot use an OU as a filter.
You will need to use something else to automatically create the email addresses - such as a group.

Depending on how many users there are, another trick would be to simply create them by hand. Set the recipient policy to have no filter and then add the email addresses to each that needs them.

Simon.
0
 
SembeeCommented:
oops, forgot to post my source.

http://support.microsoft.com/default.aspx?kbid=296112

Simon.
0
 
A4eITAuthor Commented:
Solution is good except we do not have a new domain for the polish users, they just need to come under our own,

The fix essentially describes applying the filter to logon names ending in the new mail domain, then creating the accounts choosing the polish domain in the logon name, problem is we only have one domain so the logon name box when creating an account only allows you to select @ourinternaldomainname, there is no seperate one selectable,  presumably because we only have one domain. Seems a bit long winded to setup a new domain just to correctly apply recipient updates,

Another quick question, you say create a policy with a blank filter, how is this done, do you just have nothing in the filter box, just verifying this as I dont want to be messing around with vbscript if it automatically updates all the addresses.

Thanks for replies so far, also upping points
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
A4eITAuthor Commented:
Points upped
0
 
SembeeCommented:
A blank policy is exactly that - no filter.
With no filter set, no users will get the addresses automatically. However the presence of the domain in recipient policy means that Exchange will accept email for the domain.
When the number of users getting a new domain is small, this is the method I use.

Don't get SMTP domain and Windows domain confused. You are talking about an SMTP domain, not a Windows domain.

I was quoting the article as a source for the cannot do OU, not the fix.
The fix reads as if it is suggesting an alternative UPN on the user accounts. The UPN is then used to create the email addresses. (http://support.microsoft.com/default.aspx?kbid=243629).

Simon.
0
 
A4eITAuthor Commented:
>A blank policy is exactly that - no filter.
>With no filter set, no users will get the addresses automatically. However the presence of the domain in recipient policy means that Exchange will accept email >for the domain.
>When the number of users getting a new domain is small, this is the method I use.

Couldnt get any other method working so settled for this, not ideal but sufficient,

>Don't get SMTP domain and Windows domain confused. You are talking about an SMTP domain, not a Windows domain.

Wasnt doing, was under the impression the MS document was describing how to apply a filter to look at UPN then apply recipient details based on domain part of upn

I was quoting the article as a source for the cannot do OU, not the fix.
>Thanks makes sense, the workaround seemed to be describing the above (filter by domain)

The fix reads as if it is suggesting an alternative UPN on the user accounts. The UPN is then used to create the email addresses. (http://support.microsoft.com/default.aspx?kbid=243629).
>as said we dont have any other domains to use as the ending of the UPN but no matter, im satisfied with the current one.

So.... Well done Simon, again you get the points....




Simon.
0
 
A4eITAuthor Commented:
Thanks very much BTW - How rude of me :)
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now