The most excellent LizL., has delivered unto us:
I found out how to install the certificate into the trusted root store:
The certificate has to be saved first and you do that by going to the website and clicking on the Certificate Error and then view certificate. Once you have that opened click on the Details tab. Choose Copy to File which opens the Export Wizard. Click Next at the first screen, choose the correct format and click Next, choose the Browse button and save the file to the desktop with the company name.cer, click Save, Next and then Finish. You should see an widow pop up that says the export was successful.
Once the certificate has been saved open up a command prompt with elevated privelidges, type in certmgr and hit enter. Once open expand the Trusted Root Certification Authorities and then click on certificates. Check for the name of the cert that you want to install and if not there right click on certificates and choose All Tasks then Import. That opens up the Import Wizard. Click Next, click Browse and go to the location of the certificate and click Open. Click Next, choose to place it in the Trusted Root Certification Authorities store and click Next. You will see the settings and click Finish. There will be a popup that says the import was successful. Go to the website and you should no longer have the error.
So far this is confirmed in Windows XP. If you see a BSOD with label SESSION3_INITIALIZATION_FAILED, 0×00000006F, it appears to indicate a missing or corrupt driver file. We can fix this problem by copying the appropriate file from install media or LiveCD or other source. The fix has thus far been confirmed to involve any or all of the following files:
ftdisk.sys
smss.exe
Browse to https://servername/remote; if it doesn’t go, that’s step 1. Then study the info in the link ‘Configure your computer to use Outlook via the Internet’, and make sure it is all correct. Lastly, check certificates.
Brand new D-Link wireless access point, DIR-615. Two different laptops saw the SSID, tried to connect; but Windows reported that it was not able to find a certificate for the network. Connection was reported “successful”, but it didn’t work at all.
Hung on D-Link tech support for 90 minutes, their tech had heard of the problem before, did have to go hunting…but the answer was in the WAP itself. On the console, under Advanced, there’s an item named Wi-Fi Protected Setup. This is enabled by default; and it has to be disabled, in order for this WAP to work with any wireless NICs except those few which have an automatic setup arrangement built-in, apparently called WPS.
Had some input yesterday of interest vis a vis Photoshop. At least two web resources indicate that Photoshop CS (version 8) is not compatible with XPSP2. Photoshop 7 works fine, and I have reports that CS2 also works fine.
