Ah security, the balance between not allowing access at all and allowing too much access. In Windows 10 Microsoft changed RDP’s defaults. They modified the default for “SecurityLayer…
After implementing SSL for our WordPress site, I noticed that the padlock in chrome was not green. I knew because we were using a self-signed internal CA it wouldn’t be perfect, but I was still curious. So checking it through www.whynopadlock.com it indicated that the SSL certificate was using SHA-1 algorithm. Well, current searches revealed that this will soon be deprecated and that we were in need of updating our CAs to SHA-2 in order to avoid padlock warning in chrome (and all other necessary security requirements). Here’s a quick synopsis of the steps taken on the Windows Server 2008 R2 CA role server.
open administrative command prompt
‘certutil -setreg ca\csp\CNGHashAlgorithm SHA256’
‘net stop certsvc && net start certsvc’
observe the CA properties now showing SHA256 for ‘Hash Algorithm’
The next steps involved updating the CA certificate itself:
in Certificate Authority MMC console, select the CA and open All Tasks, select Renew CA Certifcate.
Accept the request to stop the Active Directory Certificate Service
Select Yes to generate a new signing key.
To confirm the configuration:
Select the CA and open Properties
On the General tab, observe the actual Hash Algorithm of SHA256
View the certificate properties and browse the Details. Under the Signature hash Algorithm it should display SHA256. Notice that the previous certificate details show SHA1.
All certificates generated by the CA should now be using SHA256 Hash Alogirthm.
Trying to import the client’s workstations and servers into the current vsphere environment. After taking a system image within Windows, I mounted the USB device (with WindowsImageBackup directory in the disk’s root) and restored into the VM. Subsequent boot yielded BSOD. Stumbled upon this VMware KB article which solved the problem first shot.
Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
In the Registry Editor, select HKEY_LOCAL_MACHINE.
Select File > Load Hive.
Navigate to the drive on which Windows is installed (usually C:\).
Open the file named SYSTEM located at Windows/system32/config.
Name the file as P2V, when prompted.
Navigate to HKEY_LOCAL_MACHINE\P2V\ControlSet001\services\LSI_SAS.
Ever try to log onto a cisco switch console with a blue rollover cable on Windows 8.1? I had the problem of my USB-to-serial not working until I found this driver. Putty works great now!
1. Download the driver Profilic_Win8_x64_x86 and extract it 2. Open Device Manager3. Expand Ports (COM & LPT) 4. Right click device name Prolifc USB-to-Serial Comm Port and select Property 5. Select Driver tab 6. Click Update Driver 7. Choose Browse my computer for driver software 8. Choose Let me pick from a list of device drivers on my computer 9. Click Have Disk 10. Choose the folder that you extracted from the downloaded zip file. 11. Choose file “ser2pl.inf” and click Open 12. Click OK 13. After successfully installed restart your PC.