{"id":255,"date":"2015-07-23T09:56:27","date_gmt":"2015-07-23T08:56:27","guid":{"rendered":"http:\/\/blogs.kent.ac.uk\/unseenit\/?p=255"},"modified":"2015-11-11T15:58:21","modified_gmt":"2015-11-11T15:58:21","slug":"ad-attributes-required-for-automatic-exchange-provisioning","status":"publish","type":"post","link":"https:\/\/blogs.kent.ac.uk\/unseenit\/ad-attributes-required-for-automatic-exchange-provisioning\/","title":{"rendered":"AD Attributes required for automatic Exchange provisioning"},"content":{"rendered":"<p>I&#8217;ve been doing a lot of work recently getting our FIM ready to provision and manage mailboxes and other objects in\u00a0Exchange 2013 and, in doing so, I have made much reference to a table of attributes required for different object types which only seems to exist in the form of an image.<\/p>\n<p>The authoritative source for this information is from\u00a0<a href=\"https:\/\/technet.microsoft.com\/en-us\/magazine\/ff472471.aspx\">Technet<\/a>\u00a0but doesn&#8217;t seem to have been updated for Exchange 2013. The closest I&#8217;ve come to something from Microsoft has been the <a href=\"https:\/\/technet.microsoft.com\/en-us\/library\/bb738148(v=exchg.150).aspx\">Update-Recipient<\/a> documentation but that only refers to MailboxUser attributes.<\/p>\n<p>Here is\u00a0list\u00a0of required attributes for Exchange 2013 to make automatic provisioning work:<\/p>\n<ul>\n<li>Mailbox user\n<ul>\n<li><strong>mailNickname<\/strong> (eg &#8220;foo&#8221; &#8211; the local part of the email address)<\/li>\n<li><strong>homeMDB<\/strong> (user&#8217;s mailbox database)<\/li>\n<li><strong>msExchHomeServerName<\/strong> (user&#8217;s mailbox database server)<\/li>\n<\/ul>\n<\/li>\n<li>Mail enabled user &amp; Mail enabled contact\n<ul>\n<li><strong>mailNickname<\/strong><\/li>\n<li><strong>targetAddress<\/strong> (eg. &#8220;SMTP:foo@example.com&#8221;)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Some time after these attributes are set or unset (or when Update-Recipient is called on that user object), Exchange will &#8220;do the right thing&#8221; \ud83d\ude42<\/p>\n<h4>Other useful attributes<\/h4>\n<ul>\n<li>Mailbox user\n<ul>\n<li><strong>msExchMailboxGuid<\/strong> (Exchange will invent one if it&#8217;s not there)<\/li>\n<li><strong>msExchArchiveDatabaseLink<\/strong> (same as msExchHomeServerName but for Archive mailbox)<\/li>\n<li><strong>msExchArchiveName<\/strong> (text used in OWA to describe the Archive mailbox)<\/li>\n<li><strong>msExchArchiveGUID<\/strong> (mailbox guid for Archive which you seem to have to invent!)<\/li>\n<li><strong>msExchELCMailboxFlags<\/strong> (magic flags used for various things including enabling Archive mailbox &#8211; see <a href=\"http:\/\/blogs.kent.ac.uk\/unseenit\/managing-ad-boolean-in-integer-flagsets-with-fim\/\">this post<\/a> for more information)<\/li>\n<li><strong>mDBUseDefaults<\/strong> needs setting to TRUE to persuade Exchange to apply the default quota policy<\/li>\n<li><strong>msExchPoliciesExcluded &amp;\u00a0msExchPoliciesIncluded<\/strong> seem to control which of a subset of the plethora of policies get applied to an account. We&#8217;re using this to stop\u00a0the Default Email Address Policy from applying to managed mailboxes. With a little trial-and-error you can move\u00a0the {GUID} from\u00a0<em>included<\/em> to\u00a0<em>excluded<\/em> and presto! \ud83d\ude42 Without this Exchange will fight with FIM if it disagrees with proxyAddress changes \ud83d\ude41<\/li>\n<\/ul>\n<\/li>\n<li><strong>proxyAddresses<\/strong> (multivalued list of valid addresses for this user) Eg.\n<ul>\n<li>SMTP:foo@example.com<\/li>\n<li>smtp:john.smith@example.com<\/li>\n<\/ul>\n<\/li>\n<li><strong>msExchSenderHintTranslations<\/strong> &#8211; Mailtip text, can&#8217;t find any documentation on how this is supposed to work but I&#8217;ve been using a value of &#8220;default:&lt;html&gt;&lt;body&gt;$text to be displayed&lt;\/body&gt;&lt;\/html&gt;&#8221; which seems to do the right thing \ud83d\ude42<\/li>\n<\/ul>\n<p>If there are more that would be useful to go on this list then please let me know!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been doing a lot of work recently getting our FIM ready to provision and manage mailboxes and other objects in\u00a0Exchange 2013 and, in doing &hellip; <a href=\"https:\/\/blogs.kent.ac.uk\/unseenit\/ad-attributes-required-for-automatic-exchange-provisioning\/\">Read&nbsp;more<\/a><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[28943],"tags":[28975,28969,28970,28944],"_links":{"self":[{"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/posts\/255"}],"collection":[{"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/comments?post=255"}],"version-history":[{"count":3,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/posts\/255\/revisions"}],"predecessor-version":[{"id":293,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/posts\/255\/revisions\/293"}],"wp:attachment":[{"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/media?parent=255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/categories?post=255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/unseenit\/wp-json\/wp\/v2\/tags?post=255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}