patch with misc changes to freeze before trying portability to win7

CertificateCreationProcedure.txt

@@ -4,29 +4,29 @@
 
 (1) In the Visual Studio developer prompt, type:
 
-makecert -pe -n "CN=Certification Authority for Development" -cy authority -ss root -sr LocalMachine -a sha256 -r CertAuth4Dev.cer
+makecert -pe -n "CN=Certification Authority for Development" -cy authority -ss root -sr LocalMachine -r
 
 This creates a certification authority and install it under "Trusted Root Certification Authorities\Certificates" (in management console).
 
 (2) Then, use the new CA to create a new certificate for your local machine. Notice you must use your computer name in the command below:
 
 [In server machine]
 
-makecert -pe -n "CN=MyComputerName" -ss My -sr LocalMachine -a sha256 -in "Certification Authority for Development" -is root -ir LocalMachine -eku 1.3.6.1.5.5.7.3.1 SignedByCA4Dev.cer
+makecert -pe -n "CN=MyComputerName" -ss My -sr LocalMachine -in "Certification Authority for Development" -is root -ir LocalMachine -eku 1.3.6.1.5.5.7.3.1
 
 [In client machine]
 
-makecert -pe -n "CN=MyComputerName" -ss My -sr LocalMachine -a sha256 -in "Certification Authority for Development" -is root -ir LocalMachine -eku 1.3.6.1.5.5.7.3.2 SignedByCA4Dev.cer
+makecert -pe -n "CN=MyComputerName" -ss My -sr LocalMachine -in "Certification Authority for Development" -is root -ir LocalMachine -eku 1.3.6.1.5.5.7.3.2
 
 (In a development environment confined within a single box, you can choose to have only one certificate for both client and server authentication, hence eliminating the "-eku" option.)
 
 Because both client and server must rely in the same certificate CA, when you create the CA in one box, you must export the certificate to a file (including the private key) and import it into the other box. This way, the certificates in both boxes will have been issued by a common trusted CA.
 
 (3) SERVER ONLY - In the management console (mmc.exe), use the snap-in for certificate management to look for the certificate you have just created. The thumbprint is the hash you will use in the command below. These commands will assign the new certificate to the endpoints localhost:8888 and localhost:8989:
 
-netsh http add sslcert ipport=0.0.0.0:8888 certhash=8f43288ad272f3103b6fb1428485ea3014c0bcfe appid={04EBD759-F3FF-4992-8D02-C1BFDB027A58} clientcertnegotiation=enable
+netsh http add sslcert ipport=0.0.0.0:8888 certhash=da834158826f2207f9a1bbcce8fed201ad391376 appid={04EBD759-F3FF-4992-8D02-C1BFDB027A58} clientcertnegotiation=enable
 
-netsh http add sslcert ipport=0.0.0.0:8989 certhash=8f43288ad272f3103b6fb1428485ea3014c0bcfe appid={0670F436-50EA-4B8A-B62A-02EF8B39F9C9} clientcertnegotiation=enable
+netsh http add sslcert ipport=0.0.0.0:8989 certhash=da834158826f2207f9a1bbcce8fed201ad391376 appid={0670F436-50EA-4B8A-B62A-02EF8B39F9C9} clientcertnegotiation=enable
 
 (The application ID can be any GUID.)
 

TestWwsClient/tests_wws.cpp

@@ -382,7 +382,7 @@ namespace integration_tests
 	};
 
 	// Thumbprint of client side certificate for transport security
-    const char *clientCertificateThumbprint("88f2c3e46ccb972d28b12829e03cd8cbc3dcd72a");
+    const char *clientCertificateThumbprint("da834158826f2207f9a1bbcce8fed201ad391376");
 
 	/// <summary>
 	/// Tests synchronous web service access

VideoTranscoder/MFSinkWriter.cpp

@@ -314,7 +314,7 @@ namespace application
                     "IMFSinkWriter::GetServiceForStream");
             }
 
-            if (FAILED(hr = codec->SetValue(&CODECAPI_AVEncCommonQualityVsSpeed, &CComVariant((UINT32)67))) ||
+            if (FAILED(hr = codec->SetValue(&CODECAPI_AVEncCommonQualityVsSpeed, &CComVariant((UINT32)75))) ||
                 FAILED(hr = codec->SetValue(&CODECAPI_AVEncAdaptiveMode, &CComVariant((ULONG)eAVEncAdaptiveMode_FrameRate))))
             {
                 WWAPI::RaiseHResultException(hr, "Failed to set property for H.264 encoder", "ICodecAPI::SetValue");