Understanding Roles Vs Features
To my understanding and as per microsoft's training material's Features add additional functionality (augments) to Roles. However, when you configure a Role - it "seems" to be just be a collection of Features. So my question is, when creating a design document or an As-Built document for a client. If I were to just add all Features that were installed, would that encompass all the Roles. Ie. if they were to click all those featues on a new vanilla installation, would they get the same functionality as what I selected in my Role. Hope this makes sense
January 17th, 2008 2:17am

No, you would not. The roles are to be seen as infrastructural building blocks, whereas features are individual bricks. You'll need to include the roles in your document.
Free Windows Admin Tool Kit Click here and download it now
January 17th, 2008 3:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics