In Exchange 2007, the Recipient Configuration node and its child nodes (Mailbox, Distribution Group, Mail Contact, Disconnected Mailbox) of the Exchange Management Console (console) are used for...
Published Jan 19, 2007
Version 1.0
Blog Post
Hi Jared, thanks for the cmdline tip for mailbox size.
I guess I consider the message size limits as something that most admins will want to touch (unless their policy happens to line up exactly with the default 10 mb limit).
I understand that there will be no reconvergence with ADUC - but could you speak a bit to how powershell will be used in longhorn server and possible integration there?
Consider our situation - we used to copy a user in the exchange-aware ADUC, which took care of things such as extended attributes, msExchUseOAB, msExchQueryBaseDN, and others -- but now we have to do a user copy in the basic win2003 ADUC, then use the exchange tools to stamp exchange attributes, then go back with adsi edit to put in those mxExch custom settings -- it triples the work...
Another example is enabling or disabling attachments in OWA. By default they are disabled and there's nothing in the gui - I had to dig into set-owavirtualdirectory to get them set.
I am not trying to be negative, but I guess I just wish the cli documentation was a bit more fleshed out since SO much of the functionality resides within it. Not to mention I haven't slept much in the last few days =)
thanks again,
Wes
I guess I consider the message size limits as something that most admins will want to touch (unless their policy happens to line up exactly with the default 10 mb limit).
I understand that there will be no reconvergence with ADUC - but could you speak a bit to how powershell will be used in longhorn server and possible integration there?
Consider our situation - we used to copy a user in the exchange-aware ADUC, which took care of things such as extended attributes, msExchUseOAB, msExchQueryBaseDN, and others -- but now we have to do a user copy in the basic win2003 ADUC, then use the exchange tools to stamp exchange attributes, then go back with adsi edit to put in those mxExch custom settings -- it triples the work...
Another example is enabling or disabling attachments in OWA. By default they are disabled and there's nothing in the gui - I had to dig into set-owavirtualdirectory to get them set.
I am not trying to be negative, but I guess I just wish the cli documentation was a bit more fleshed out since SO much of the functionality resides within it. Not to mention I haven't slept much in the last few days =)
thanks again,
Wes