Everyone, I have this script; see below, that will add/change a primary SMTP address. Id like everyones comment on it because it just seems too simple. We are thinking of adding a different primary smtp address such as first initial, last name , other than the standard of 8 char to left of the @ sign. Ive tested it ok on our lab exchange server and it worked.but like I said it just seems to simple. Tiny.. Start-Transcript c:\temp\mailboxcreatelog.txt Import-CSV c:\temp\input.csv | %{ Set-mailbox -Identity $_.DisplayName -EmailAddressPolicyEnabled $false Set-Mailbox -Identity $_.DisplayName -PrimarySmtpAddress $_.primarysmtpaddress }

if you have it working in your lab and production is simliar I don't see any reason for it not to work. script seems clean and I think it shuold do the job. Lasse Pettersson http://anewmessagehasarrived.blogspot.com

if you have it working in your lab and production is simliar I don't see any reason for it not to work. script seems clean and I think it shuold do the job. Lasse Pettersson http://anewmessagehasarrived.blogspot.com

Lasse, thanks for the encouragement...just seems to simple... tiny..

Lasse, thanks for the encouragement...just seems to simple... tiny..

I would highly suggesting changing your EAP to use the new format instead of disabling EAP enforcement on the objects. If you only want the new e-mail address to go to certain objects use filters, the Custom Attributes fields are great for this. In general e-mail addresses should be change via EAPs not directly. Without EAPs there is no way to enforce standard formatting of addresses. Admins will need to remember to set the e-mail address as needed when creating new users too if the default\matching EAP isn't configured to have the desired format.If this post helps to resolve your issue, please click the "Propose as Answer" If you find it helpful , mark it as helpful by clicking on "Vote as Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster. If you need an expert migration consultant to assist your organization feel free to contact me directly. Jason Sherry | Blog | Hire Me | Twitter: @JasonSherry Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP

I would highly suggesting changing your EAP to use the new format instead of disabling EAP enforcement on the objects. If you only want the new e-mail address to go to certain objects use filters, the Custom Attributes fields are great for this. In general e-mail addresses should be change via EAPs not directly. Without EAPs there is no way to enforce standard formatting of addresses. Admins will need to remember to set the e-mail address as needed when creating new users too if the default\matching EAP isn't configured to have the desired format.If this post helps to resolve your issue, please click the "Propose as Answer" If you find it helpful , mark it as helpful by clicking on "Vote as Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster. If you need an expert migration consultant to assist your organization feel free to contact me directly. Jason Sherry | Blog | Hire Me | Twitter: @JasonSherry Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP

Disable address policy can be a good thing in some cases and can be bad in some cases. One thing I hate is when there is conflict with email addresses, then policy simply add a sequence number afterwards with out telling. Lasse Pettersson http://anewmessagehasarrived.blogspot.com

Disable address policy can be a good thing in some cases and can be bad in some cases. One thing I hate is when there is conflict with email addresses, then policy simply add a sequence number afterwards with out telling. Lasse Pettersson http://anewmessagehasarrived.blogspot.com