共用方式為


BizTalk Server 2006 User Task Permissions Dependency Matrix

So how about something like this? This is not in the game plan, but I think it should be and would like to get some voting in before I churn too many cycles on it. Feel free to leave comments or ping me directly. Thanks!

Take a look at the image below (click to enlarge).

  1. Does this help address your questions on what security rights you need to perform tasks?
  2. Are there other things you expect to see on this chart? Can you provide a list of things you want to see?
  3. Is the chart too confusing? If so, how would you like it to be presented?
  4. Any other feedback in this area?

Note: This chart is pre-release content and is subject to change.

Comments

  • Anonymous
    November 19, 2005
    I like it...Matrix-style puts your option into context. Having a consistan look and feel, i.e. the software req matrix makes it even better. I'd say it is worth the effort considering BTS 2004 setup/config issues when released...
  • Anonymous
    November 21, 2005
    Luke, I think this kind of chart will be very useful to the server administrators. I think it's a good addition to the docs.
  • Anonymous
    November 24, 2005
    I think this would be very useful - especially if it works over a distributed installation. We've hit problems with permissions where our development (SDK), BizTalk Server runtime and SQL are all on different machines, using domain accounts.
  • Anonymous
    November 25, 2005
    I think this is a very useful diagram to have as part of the documentation. Can you include it as an HTML file in the documentation rather?
  • Anonymous
    November 29, 2005
    How about if we shipped it as a poster?
  • Anonymous
    November 30, 2005
    Hi Luke,

    I would opt for both the hardcopy(ies) (3?) and the digital one in the documentation, looks pretty handy!
  • Anonymous
    May 10, 2006
    BizTalk Server 2006の管理者が何かをやるときにどういう権限が必要か示した表を作っているらしいです。まだ未完成らしいですが、いいですね。

    http://blogs.msdn.com/luke/archive/2005/11/18/494706.aspx...