Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 811701

Summary: RFE: Add extended example showing all the functionality choices
Product: Red Hat Enterprise Linux 6 Reporter: Deon Ballard <dlackey>
Component: doc-Identity_Management_GuideAssignee: Deon Ballard <dlackey>
Status: CLOSED WONTFIX QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: mweetman, pkennedy
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: 6.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-26 21:22:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Deon Ballard 2012-04-11 18:50:38 UTC
It would be nice if there were a long, detailed Example Corp summary that went through the different functionality options for setting up and deploying IPA in an SMB environment and explains why certain options are available or why certain choices were made.

Something like....
---------------------------------------------------
"Widget Co. has around 100 servers running Windows, RHEL and Solaris, they have asked you to design and build a solution using IPA so that they can use their Active Directory accounts to log on to all servers."

"Design:
You decide to implement a master IPA server with one replica, create a dns sub-domain of the AD domain for all *nix hosts ...  "

"Build:
You build a RHEL 6.2 host to be your master IPA server ....

# install IPA - (see section x.y.z)
yum .... "

Comment 3 Deon Ballard 2012-11-09 19:46:36 UTC
Clearing flags to change the release.