Bug 149631 - quick start guide
Summary: quick start guide
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site   
(Show other bugs)
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-24 17:30 UTC by Sarah
Modified: 2008-10-16 15:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-16 15:08:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Sarah 2005-02-24 17:30:06 UTC
Description of problem:
Hey,  There is this great new link on the website that explains how to register
your product and run up2date:
http://www.redhat.com/software/rhel/register/howto/.  I think this would be
great to also put as the quick start guide since it is a step by step guide and
easy to understand.  It includes a lot of key questions as well.  Please put
this into consideration.  Thanks so much!

SarahSt.Clair

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Sarah 2005-02-24 17:41:53 UTC
Another idea.  At the link to lost password/login.  Could you please switch it
around and put the email address and then send login at the top.  At the bottom
put your account and email address then send password.  Customer's get confused
and they think they need to know there login when they go to this link.

Comment 2 Amanda Carter 2008-10-16 15:08:23 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.


Note You need to log in before you can comment on or make changes to this bug.