Hello, We have a MDB that contains users from a domain which can have 1 of 3 different primary smtp addresses. I want to find a way that when our Help Desk creates accounts using the EMC the users in this MDB will have the correct primary smtp address. Can anyone think of an attribute that could be assigned to different mailbox policies during account creation? If not, can anyone recommend account provisioning tools which will allow us to set the primary smtp or set a variable used by mailbox policies and not require our Help Desk to open up a shell and launch a script? Thanks, Robert

On Tue, 6 Mar 2012 00:55:43 +0000, RTEAL wrote: > > >Hello, > >We have a MDB that contains users from a domain which can have 1 of 3 different primary smtp addresses. I want to find a way that when our Help Desk creates accounts using the EMC the users in this MDB will have the correct primary smtp address. > >Can anyone think of an attribute that could be assigned to different mailbox policies during account creation? Here's the list of properties that can be used in the -recipientfilter on EAPs: http://technet.microsoft.com/library/bb738157(EXCHG.80).aspx >If not, can anyone recommend account provisioning tools which will allow us to set the primary smtp or set a variable used by mailbox policies and not require our Help Desk to open up a shell and launch a script? Without knowing how you create those mailboxes now it's not really possible to say what properties you could use as a discriminator. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Our HD uses the Exchange Management Console to create accounts and it only has options for OU, name fields, and Database so without a script it would be difficult for us to take advantage of city, customattribute, etc. Does anyone have experience with account provisioning tools that use a GUI to allow one to fill out all fields during account creation? Thanks

can i ask why you dont want to consider scripts, as all what you asking for can be accomplish using powershell script?

On Tue, 6 Mar 2012 20:50:37 +0000, RTEAL wrote: >Our HD uses the Exchange Management Console to create accounts and it only has options for OU, name fields, and Database so without a script it would be difficult for us to take advantage of city, customattribute, etc. Rather than create mailboxes in a one-off fashion, wouldn't it be easier to have, say, a spreadsheet of the information necessary to create a new user and mailbox? Export the spreadheet to a CSV file and use one of the many example scripts you'll find on the Internet to manage the creation. You could even have that script run as a scheduled task. >Does anyone have experience with account provisioning tools that use a GUI to allow one to fill out all fields during account creation? Doesn't HR already do that? FYI, you can create the AD user account with ADUC and populate it with whatever you like. Then use the EMC to create the mailbox. Now your EAPs can use the already populated properties to generate the e-mail addresses. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Well, partly because I don't want our HD to have to run scripts or edit text file input and a GUI makes account creation easier. Secondly, because I would have to write the script and I don't think I could write a GUI. I'd probably have to ask for input and then, unlike with a GUI, a help desk person couldn't go back and correct errors. Given how dispersed our sites are I think a GUI would be easier. Robert

Hi Rich, Normally I bulk-create with a csv but we sometimes have to create a one-off account and I think the ideal tool for varying levels of Help Desk would be a one-step gui. The ADUC first approach works but it involves a second step and sometimes items get missed so I would rather just have a single method for account creation. I do appreciate the suggestions. Robert

If you want to assign email addresses and set as primary for certain users, why not base it on the OU field which HD fill out?Sukh

That's a good thought but in my case the given OUs will contain users which have different smtp addresses.

I haven't come provisioning tools for this specifically, but normally HR PeopleSoft does this, but this would be way too expensive for just this requirement.Sukh