I expect that that would be true of many of the new attributes for Exchange 2007 and Exchange 2010.
Microsoft no longer wants you to touch objects directly. Use the cmdlets. This allows them to change details of the implementation without changing the administrative interface. I think the best you are going to be able to do is the data types that the cmdlet accepts. Which is close enough, in my opinion. http://technet.microsoft.com/en-us/library/bb123981.aspx ForwardingAddress Optional Microsoft.Exchange.Configuration.Tasks.RecipientIdParameter The ForwardingAddress parameter specifies a forwarding address. ForwardingSmtpAddress Optional Microsoft.Exchange.Data.ProxyAddress The ForwardingSmtpAddress parameter specifies a forwarding SMTP address. Each of those data types is documented. http://msdn.microsoft.com/en-us/library/microsoft.exchange.data.proxyaddress(v=exchg.140).aspx http://msdn.microsoft.com/en-us/library/microsoft.exchange.configuration.tasks.recipientidparameter(v=exchg.140).aspx Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Young, Darren [mailto:[email protected]] Sent: Thursday, July 14, 2011 5:02 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding Google on that attribute gets 2 results Translate http://www.msxfaq.de/migration/targetaddress.htm to English and there's a little info, not much. MSDN Bings nothing. Search on our Premier site returns 0 results. TAM didn't find anything either so it must be secret even to Microsoft. So I pulled the schema reference from here http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5401 and all it has is that it is for the Mail-Receipient Class and the Change is add:mayContain. Any idea where documentation is on the values for that attribute? From: Michael B. Smith [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 3:43 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding msExchGenericForwardingAddress Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Young, Darren [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 4:41 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding Thanks. Any idea what attribute is used to store that? From: Michael B. Smith [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 3:35 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding You are correct, the example is wrong. I'll report it. You still don't have to have a mail contact if you don't want one. You do this instead: Set-mailbox -ForwardingSMTPAddress [email protected]<mailto:[email protected]> Note the addition of "smtp" in the parameter. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Young, Darren [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 4:04 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding So, I create a new Mail Contact with the external address then use that object for the option -ForwardingAddress it works. In AD altRecipent is in fact set to the DN of the previously created Mail Contact object. And there are several new attributes on that object vs. what we used in 2003. MS's docs here: http://technet.microsoft.com/en-us/library/dd351134.aspx appear to be incorrect, when I try using their example it says there's no such object. I didn't think it was as simple as passing the target address. From: Michael B. Smith [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 2:23 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding Set-Mailbox requires a mailbox, which means that it requires a user object. That's far different than a contact. TTBOMK, the actual implementation of forwarding hasn't changed (in terms of the attributes used), but Exchange 2010 does stamp objects with more attributes than Exchange 2003 or Exchange 2007 did, and if the attribute's versions aren't correct then Exchange 2010 complains. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Young, Darren [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 3:06 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding What does Exchange do when you set the forwarding via Set-Mailbox? How is that forward actually implemented by 2010? From: Michael B. Smith [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 12:45 PM To: MS-Exchange Admin Issues Subject: RE: 2010 Mail Forwarding If it's truly a CONTACT then you should be using New-MailContact. You can also migrate an AD contact to an Exchange contact by using Enable-MailContact. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Young, Darren [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Thursday, July 14, 2011 12:34 PM To: MS-Exchange Admin Issues Subject: 2010 Mail Forwarding For mail forwarding, in Exchange 2003 we built a web app that creates a contact object with a targetAddress of the external email then "attached" that to the altRecipient attribute for the user. This still works after we "upgrade" the contact object to work with 2010, however I would like to move this to a more native 2010 method. Is it really as simple as Set-Mailbox -Identity <> -ForwardingAddress <address>? If so, where does Exchange store this forwarded address? Darren Young Systems & Security Architect Computing Services University of Chicago Booth School of Business 5807 South Woodlawn Avenue Chicago, IL 60637 Voice 773.702.0331 | Fax 773.702.0233 --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
