I like godaddy very much , we have 1 hosting account and almost 50 domains there.I will like to buy Certificate also from them.This tips really helps us.

Thanks

FYI on our certificate purchase through Go Daddy. Although we have an account with Verisign we chose to move forward with Go Daddy due to the drastic difference in cost. Unfortunately we found out why it was so much cheaper, difficult support.

We began the SSL certificate purchase process on 9/29. Go Daddy required that we submit documentation showing proof of right through one of these forms:

1)Articles of Incorporation

2)Business License

3)Tax Certificate

4)"Doing Business As"

We are a non-profit organization so we do not have numbers 1,2, or 4. However, we do have a tax exempt document that we keep on-hand to submit for these type of requests. This form was submitted to Go Daddy on 9/29 with the required payment and CSR. We continued to watch the process through their website as it was approved at each level. After it had remained at the reviewing documentation step for multiple days, we called Go Daddy on 10/6 directly and waited for approximately 45 minutes before we spoke with anyone. They informed us that the document provided was not sufficient as it did not have the State Seal along with the proper company information (this was never reflected on the website and we never received contact from them regarding this, we would have never known if we had not called). We returned to our Financials Department to look for additional documentation but the tax exempt document was the only one that fit their criteria.

We went back to Go Daddy support (after waiting on hold for 30 minutes) and reiterated the fact that we were a non-profit organization that does not pay taxes. We also covered the fact that the document we supplied had the State Seal with our organization's information and license number. Go Daddy support went back to their auditors to request this once again, and it was denied a second time.

At this point we've stopped this process with Go Daddy and are working with our management team on budget allocation to purchase the much more expensive certificate through Verisign. Although the price was great with Go Daddy, their support was extremely difficult. We highly recommend that if you run across other non-profit organizations, do not waste their time with Go Daddy.

Hope this helps in the future, thanks!

Hi William,

I'm having some problems:

1. do i need to follow Microsoft instruction to create the certificate from GoDaddy ?

http://technet.microsoft.com/en-us/library/cc161804.aspx#BKMK_AMTprovisioning1

2. i cant understand where to put the "Intel(R) Client Setup Certificate for the OU" in the CSR.

to create the CSR i'm usuing IIS Console to request a certificate and then submit it to GoDaddy.

after i'm getting the certificate from them, i cant import it to SCCM OOB.

can you clear it out for me please,

thanks,

kobile

I also encountered many bumps in the road when configuring the Enterprise CA and obtaining the cert from GoDaddy AND getting it in the right format.

I offer the following:

1. Read ALL of the directions from the TechNet site.
2. If you are to modify the certificate templates, you MUST have Windows 2003 Enterprise - not Standard
3. When configuring the Enterpise CA to issue the modified certificate, if the certificate template that you created (e.g. ConfigMgr AMT Provisioning) is not being displayed in the 'Certificate Template' Drop-down list (http://enterpriseCA/certsrv), ensure that the Active Directory 'ConfigMgr Out of Band Service Points' group (or the actual OOB Service Point server) is listed in the LOCAL COMPUTER's (Local Users and Groups\Groups) group named 'CERTSVC_DCOM_ACCESS'.  Otherwise, the server won't have the permissions to see the item in the list.
4. For creating the Cert Request, ensure that:
   The Key Size is set to 2048 or higher;
   The 'Mark keys as exportable' is checked;
   The 'Export keys to file' is checked;
   Select the 'PKCS10' as your Request Format (with SHA-1);
   Check the 'Save Request to a File' - you will open it in Notepad and copy the contents to paste in the GoDaddy Cert Request
5. GoDaddy Request:
   Ensure you shoose the 'Deluxe High Assurance SSL' certificate;
   There is now a checkbox for the 'Intel Client Setup Certificate' when you submit your request - this will add the proper text to the OU (in lieu of or addition to the OID that was setup in the Cert Template);
   Have all your information ready - they check with your Secretary of State for business verification as well as ensuring your EXACT business name is listed in various public phone books for phone number validation (ours was not EXACT in many registries - they finally found an accepted registry that matched)
   BE PERSISTENT with them to get your SSL Cert - they don't tell you exactly what the hold up is and what you are wating for - CALL THEM if you really need to process your Cert and keep it moving along.
6. Once you have your Cert, load it into the Server's local computer certificate store.  INSTALL the intermidiary certificate as well.
7. Certs are delivered in the '.crt' format.
8. At one point in SCCM, you will need to import the certificate from a '.pfx' format.  GoDaddy will not provide it.
   To convert the certificate, you will need:
       a.  The .crt file issued from GoDaddy
       b.  The .pfk (Private Key') file that was created when you made your certificate request
       c.  Download from Microsoft the PVKIMPRT.EXE utility. 
   
       EASY to run [e.g.  pvkimprt.exe -PFX certfromgodaddy.crt yourprivatekeyfile.pvk <ENTER> you will then be prompted with a PrivateKey password window - this is the password of your 'yourprivatekeyvile.pvk' when it was created - enter the password and click OK - this will start the Certificate Export Wizard. 
   
   You can Export the private key again and then ensure the 'Personal Information Exchange - PKCS #12(.PFX)' is selected (probably the only option) and then select 'Include all certificates in the certification path if possible' AND 'Enable strong protection...' - add your new private key password (or re-use the original), select the location, click finish and then you are done. 
   
   You may now upload your .pfx certificate (Whew!)

I hope this helps others that may encounter the same issues that I did.