Generate CSR: IIS 6 Microsoft Windows Server 2003

Follow these instructions to generate a Private Key and CSR. You must have at least Service Pack 1 installed.

1. Open the Internet Information Services (IIS) Manager. From the Start button select Programs > Administrative Tools > Internet Information Services Manager.
2. In IIS Manager, double-click the local computer, and then double-click the Web Sites folder.
3. Right-click the Web site for which you want to request a certificate, and then click Properties. By default it will be Default Web Site, yours may be different.
   
   
4. Select the Directory Security tab and click Server Certificate in the Secure communications section.
5. Click Next in the Welcome to the Web Server Certificate Wizard window.
6. Select Create a new certificate, Click Next.
7. Select Prepare the request now, but send it later.
8. At the Name and Security Settings screen, fill in the friendly name field for the new certificate
   Tip: the friendly name can be any name that helps you remember what this certificate is for when you see it in a list later. We recommend using your domain as the friendly name, such as mysite.com.
9. Select bit length. We recommend using a 2048-bit length (2048 is required for EV SSL). Click Next.
10. Leave the 'Select cryptographic service provider (CSP) for this certificate' unchecked. Click Next.
11. You will be asked for several pieces of info which will be used by GeoTrust to create your new SSL certificate. These fields include the Common Name (aka domain, FQDN), organization, country, key bit length, etc. Use the CSR Legend in the right-hand column of this page to guide you when asked for this information. The following characters should not be used when typing in your CSR input: < > ~ ! @ # $ % ^ / \ ( ) ? , &
12. Enter your Organization (e.g., Gotham Books Inc) and Organizational Unit (e.g., Internet Sales). Click Next.
13. THIS IS THE MOST IMPORTANT STEP! Enter your site's Common Name. The Common Name is the fully-qualified-domain name for your web site or mail server. What ever your end-user will see in their browser's address bar is what you should put in here. Do not include http:// nor https://. Refer to the CSR legend in the right-hand column of this page for examples. If this is wrong, your certificate will not work properly. Click Next.
14. Enter your Geographical Information for Country, State, and City. Do not abbreviate States and Cities. Click Next.
15. In the Certificate Request File Name box enter the path and file name where you want to save your CSR. You can use the default of c:\certreq.txt. Remember where you save it, you'll need to be able to find this CSR file later. Click Next.
16. Review the data on the Request File Summary screen and click Next.
17. Click Finish to complete the Wizard.
18. Now, from a simple text editor such as Notepad (do not use Word), open the CSR file you just created at c:\certreq.txt (your path/filename may be different). You will need to copy-and-paste the contents of this file, including the top and bottom lines, into the relevant box during the online order process.
    
    

How To Renew or Create New Certificate Signing Request While Another Certificate Is Currently Installed

Reference MS KB: http://support.microsoft.com/kb/295281

To create a new CSR or generate a renewal request while another certificate exists on your Web site, follow these steps:

1. In the Microsoft Management Console (MMC), right-click the default Web site, click New, and then click Site.
2. Create a new site and give it a temporary name.
3. Right-click the new site, click Properties, click the Directory Security tab, and then click Server certificate.
4. Select Create new certificate and follow the wizard to create a new CSR. When prompted, select Prepare the request now but send it later.
5. Use the CSR that you just created to request a new certificate from the certificate authority (CA) that issued the original certificate.
   
   NOTE: If you are renewing a VeriSign certificate, see the following Web site:
   http://www.verisign.com/repository/digidren.html (http://www.verisign.com/repository/digidren.html)
   If you are unable to renew the certificate by using this Web site, you can reach VeriSign's renewal department at the following e-mail address or telephone numbers:
   
   E-mail: renewal@verisign.com
   Technical Support: (877) 438-8776
   Sales: (650) 429-3347
6. When you receive the certificate from VeriSign or another third-party CA, save it to your hard drive. Remember the serial number of this certificate and where you save it.
7. Right-click the temporary site that you created in step 2, click Properties, click the Directory Security tab, click Server certificate, and then click Next. Follow the wizard. When prompted, select Process the pending request.
8. After the certificate has been installed, click OK, and then stop and start the Web site.
9. Right-click the temporary site that you created in step 2, click Properties, click Directory Security, and then click Server certificate.
10. Select Remove the current certificate and follow the wizard. This removes the certificate from IIS, but the certificate remains in the certificate store.
11. Right-click the Web site that has the original server certificate installed (that is, the certificate that you are renewing or replacing), click Properties, click Directory Security, click Server certificate, and then select Replace the current certificate.
12. Select the certificate that you just installed. If you see duplicate certificate names, make sure that you select the certificate that matches the serial number that you noted in step 6.

NOTE: The list of available certificates is populated from the personal certificate store, which is located under Certificates (Local Computer) in the MMC. To view the personal certificate store, add the Certificates snap-in for the Computer Account to your MMC.

NOTE: If IIS does not display the new certificate, you may need to copy it from the personal certificate store that is located under Certificates - Current User in the MMC into the personal certificate store that is located under Certificates (Local Computer). To view the personal certificate store, add the Certificates snap-in for the User Account to your MMC.

How to Get Rid of OTA Forced Reboots on Rooted Phone

[RS Guide] How to Get Rid of OTA Forced Reboots on Rooted Phone

Ok, so you have rooted your phone, and decided you would install the latest OTA update from Verizon. Now the update fails to install and your phone constantly reboots. Here is how you fix the problem.

Thanks for all the RS Members and Forum Members that have helped discover these solutions. We are not responsible for any damage done to your device by using these methods. They should be harmless, but you will possibly loose your data in the process.

There are 4 different solutions outlined here. Starting with the least damaging to your data. Please try them in order until you get your phone back working. Most people will be able to recover using the first method. But the other methods are included in case the first one doesn't work for you.

First of all when the OTA fails you should be left in ClockworkMod Recovery. You will know that is where you are based on the following menu that should be shown on your screen.

ClockworkMod Recovery v3.0.2.5 (ok if your version doesn't match)

Use vol keys to highlight and home to select.

- reboot system now
- apply sdcard:update.zip
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- +++++Go Back+++++

Method 1: (thanks to sonicbuffalo for posting this method)

1) Once you are in ClockWorkMod Recovery, scroll down to "Wipe cache partition".

2) Select "Wipe cache partition" using the home key or power button.

3) Now, scroll down to "Yes - wipe cache".

4) Press the home key or power button to perform the wipe.

5) When done, restart your phone.

6) Your ThunderBolt will boot into the Android operating system and will say that the UPDATE FAILED.

7) Choose Cancel to stop the update.

8) Restart your phone one last time and you'll see that the "Powering Off" loop is gone.


Method 2: This will delete your data

1) Once you are in ClockworkMod Recovery, select "wipe data/factory reset" using volume keys.

2) Press home key or power button to select.

3) Answer Yes, by scrolling with vol keys and home or power key to select.

4) When phone reboots, the powering off loop should be gone.

Method 3: This only works if you have a Nandroid Backup from prior to accepting the update.

1) Once in clockwork select "backup and restore" using vol keys.

2) Select using the home key or power button

3) From next menu select "restore"

4) Choose your backup from list and select.

5) Answer yes to restore backup

6) When phone reboots the "powering off" loop is gone.

Method 4: This is a last ditch effort if all other methods fail.

1) Download the Leaked Rooted Update from HERE.

2) Following instructions in THIS post load the rooted leak.

3) When your phone reboots, the powering off loop should be gone and you should be running the latest software and still rooted.

How to index IIS 7.0 Web sites in Windows Server 2008 by Indexing Service

We can use the following steps:

Install IIS 6 Management Compatibility

=============================

1.            Click Start , point to All Programs , point to Administrative Tools , and then click Server Manager .

2.            In the console tree of Server Manager, Expand Roles , and then right click Web Server(IIS). Click Add Role Services

3.            In the Add Role Services Wizard, select IIS 6 Management Compatibility, and then click Next .

4.            Follow the instructions in the Add Role Services Wizard to complete the installation.

Select the web site you want to search

==============================

1.       In Indexing MMC right click your catalog and choose Properties.

2.       Click Tracking tab.

3.       Select the web site in “WWW Server” dropdown list.

4.       Then click OK.

5.       If you open the property page again, you will see that “WWW Server” field is still empty. But it is just a UI issue.

6.       To verify whether you select the web site, please check the following values under the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\[Catalog Name]

IsIndexingW3Svc

W3SvcInstance

                               

Make sure the value IsIndexingW3Svc is 1 and the value of W3SvcInstance is your selected web site instance.

Set ContentIndexed metabase property

================================

In Windows 2003 you can select the option “Index this resource” on the virtual directory if you want to index some web pages. But in Windows 2008 there is no administrative UI for you to enable this option. We have to use command line scripts:

1.       Open a command prompt and change the current directory to %systemdrive%\inetpub\adminscripts.

2.       Run the command: cscript adsutil.vbs set w3svc/[web site instance]/root/[virtual director]/ContentIndexed 1

For example, if you want to enable “Index this resource” on the virtual directory MyVIR of the default web site, you can run: cscript adsutil.vbs set w3svc/1/root/MyVIR/ContentIndexed 1

After you enable the above options, you can restart your indexing service. The indexing service will automatically check the IIS settings and generate the catalog.

Close child window and refresh parent window

Put this in your event...

Page.ClientScript.RegisterStartUpScript(this.GetType(),"close","<script language=javascript>window.opener.location.reload(true);self.close();</script>");

Did my first session with counselor

I finally went to see a counselor for my addiction. Actually, I've been to a counselor before, but due to my own stubbornness would not continue to go. And that was like 4 years ago and I just kept feeding the addiction off and on promising myself that this would be the last time. Anyway, I think things are going to work out better this time. We had a good conversation of about an hour. A lot of things have come back to mind just in the short time we talked. For a while I've always wanted to deny that this problem started at a young age with me, but I guess it has. Even as a young child exposed to pornography it can cause permanent damage. When I say young I would say I was about eight years old. I guess it's not too hard to understand given how early childhood abuse can often manifest into the abused becoming the abuser at a later age. I'm feeling good about things right now, so I want to just keep it going. I'll check back in later.

“Request timed out” or “HTTP 404″ error when try to upload big files to Sharepoint 2007 Server

Example Scenario:
Server OS: Windows 2008 SP2
Application: Sharepoint 2007 with SP2
When upload file bigger than 28M to Document Library. IE may have one of the following errors:
“Request timed out” or “HTTP 404″
The result is file failed to upload.
The solution:
Note: This solution is to complete Microsoft KB 925083 (until they can perfect it, also the article is for Sharepoint Services, the central admin part is different on MOSS 2007)
The default Maximum Upload Size in Sharepoint 2007 is 50M, and there’s a reason for it.
Microsoft internal setting is set to 100M.
Theoretically, the size can be 2G. Which is the maximum size SQL can handle.
Solution 1: Ask your user to shrink the files they wanted to upload (eg. powerpoint files that contains high resolution pictures), or split the file to files smaller than 50M, if possible.
Solution 2: (take a deep breath)
Find out what’s the absolute maximum file size you need. Eg: let’s say 150M
Find out what’s the maximum time it will take, from your slowest satellite office that need to upload this 150M file to Sharepoint server (via ftp). In my case, it’s 2 hours…
(Note: A solution has been found for the extrem slow upload, see my post: It takes a long time to upload big files to Sharepoint Document Library via WAN)

1. Launch Sharepoint 3.0 Central Administration, go to “Application Management” -> Under “Sharepoint Web Application Management” section -> click on “Web application general settings”
2. In “Maximum Upload Size”, change the default “50″MB to “150″MB, or your maximum file size.
3. Scroll down, in “Web Page Security Validation” section, change “Security validation expires After” from 30 minutes to 120 minutes, or to your maximum time to complete the upload. (Note: if this setting isn’t changed, you may get following error when try to upload: “The security validation for this page has timed out. Click Back in your Web browser, refresh the page, and try your operation again.”  You can already see by increasing this value increases your security risk of been session hijacked)
4. Launch ”Internet Information Service (IIS) Manager” on each front end servers, expand IIS server node -> expand Sites -> Find the site that’s hosting your Sharepoint site and right click on it -> choose “Manage Web Site” -> choose “Advanced Settings” -> under “Behavior” expand “Connection Limites” -> change “Connection Time-out (seconds)” from 120 seconds to 7200 seconds.
5. On each front end servers, go to “Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\LAYOUTS” folder, make a copy of “web.config” file, then open the file with NotePad, look for following section:
   • <location path=”upload.aspx”>
         <system.web>
           <httpRuntime maxRequestLength=”2097151″ />
         </system.web>
       </location>
   • replace it with:
   • <location path=”upload.aspx”>
         <system.web>
           <httpRuntime executionTimeout=”999999″ maxRequestLength=”2097151″ />
         </system.web>
       </location>
   • save the files.
6. On each front end servers, go to “Inetpub\wwwroot\wss\VirtualDirectories\VirtualDirectoryFolder”:
   • make a copy of “web.config” file, then open the file with NotePad, look for following line:
   • <httpRuntime maxRequestLength=”51200″ />
   • replace the line with:
   • <httpRuntime executionTimeout=”999999″ maxRequestLength=”51200″ />
   • Go to very end of the file, right in front of “</configuration>” add following:
   • <system.webServer>
         <security>
           <requestFiltering>
            <requestLimits maxAllowedContentLength=”157286400″/>
           </requestFiltering>
         </security>
       </system.webServer>
   • Note: 157286400=150MB * 1024 *1024. Also if you do not put above code right in front of “</configuration>”, but right below “<configuration>” as from the KB, you will get following error:
   • Server Error
     500 – Internal server error.
     There is a problem with the resource you are looking for, and it cannot be displayed.
7. On each front end server, run “Command Prompt” as administrator, then run “iisreset”

Analysis:
There are multiple places has file size and timeout restriction, some of the behaviors are Windows 2008 IIS7 specific (such as the 28M restriction discussed in 942074)
As you can see, changing these value may enable upload bigger files in Sharepoint. However, from the user prospective, when they upload a big file from IE, there’s no progress bar indicating the percentage of the upload, and it may take a very long time to upload the file. Users may generally lost patience and click on “OK” button, which only triggers re-upload the same file.
Consider only change these settings when all your users are connected to Sharepoint servers via high speed low latency connections.

First post!!

Well, this is my journal. My escape. My place to just put it all out there and just get stuff off my mind. A lot of stuff goes on during the day and throughout life and sometimes we don't have time to capture it all and remember it the way it actually happened. I'd like to use this blog as a repository for my passions...my God, my family, cooking, reading, exercise, tech gadgets, and various aspects of software development. I'd also like to sound off about my struggles, my challenges and my weaknesses. A lot of like to think we're so strong of mind, but you'd be amazed at how some of the small things can bring us to our knees. I've battled with sexual integrity for much of my life and you'll see me discuss it here.