Word of Caution: This article contains a procedure to edit/change Windows Registry. Please take necessary precaution before attempting this.
I received an error this morning while trying to connect to one my clients’ server. The message as follows:
With the help of one of my contacts at the client site, also upon searching and following the link provided in the message itself, couple of help pages stood out:
- CredSSP updates for CVE-2018-0886
- CredSSP encryption oracle remediation
For those who would like to see the solution immediately without having to go through the details from above links, I shall brief the solution itself here.
There are basically two solutions:
- Run “Windows Update” on the remote server (or the workstation) to which you are trying to connect. This will ensure that you have the latest patch on the remote box and you wouldn’t be facing this issue again. This would work provided your machine also has got the latest updates applied.
- For those who cannot update the remote box for some reason(s), you would have to create a new registry entry as shown below:
Once above registry key is created, you must restart your workstation / client / computer without fail.
All good now to successfully connect to the remote box again.
A note of thanks to Dave.
This is my first post from Perth, WA. It’s been an excellent journey and so far so good. More about my Perth life later.
This is something that I never experienced before. When you download any file from PartnerSource or CustomerSource, Microsoft would let you do that only through it’s File Transfer Manager program. If you have that installed already, any download initiation would first invoke this program and then let you set the path/folder to take in that download and etc.
However, when I tried to do that from my new Windows 10 machine, the FTM did not open. I tried to figure that out, but later remembered this same issue happening on my Windows 8.1 machine.
Basically, from Windows 8.1, for some reason, calling the FTM from Internet Explorer worked only on a 32 bit Internet Explorer.
Looks like Microsoft has not fixed that yet. If you are wondering why your FTM didn’t work, this is the reason. Open your IE 32 bit mode and then try to download the file that you wanted to.
UPDATE (05-Oct-2015): Above did not work for me today. So further researching led me to this post which resolved my issue: Work around for getting File Transfer Manager to download from TechNet/MSDN
I often copy my chunk file on to GP application folder as part of my development work, so I must keep two explorer windows open always. Copy from my development folder and paste it on to GP application folder. Difficult and frustrating (at times) to shuttle between two folders every time.
Not anymore; I just created new shortcuts to Send To menu as shown below:
Just select my chunk file from my development folder, invoke Send To menu and send it straight to GP application folder. Awesome, isn’t it? It is, indeed. It saves almost 15-30 minutes a day depending how many times you perform copy paste with same source and destination folders.
Follow the steps explained in this blog post: How to add SkyDrive shortcut into your ‘Send To’ Menu.
The post discusses on how to add a shortcut for Skydrive, but it’s the same steps that you have to follow for any shortcut (internally on your computer or an external location).
I assure you that this trick alone would save you tremendous amount of time and effort in a day.
That’s pretty interesting stuff out there in The Old New Thing blog.
I got to read about why the close button of Windows is on the right corner?. In addition to the article, you got to read the comments which are as interesting (and funny, if I may say) as the article itself.
The idea behind the right corner placement is Fitt’s Law.
Read it on the source blog. I bet, it’s worth.
Alright… Another off-topic one, but is worth sharing. This post again shows how much Customers are aware about technology and go that extra mile to get educated on systems/software that they use.
The Old New Thing has got a post which explains a flaw in Windows Vista (yeah I can hear you yelling at me as soon as you heard that word) and Windows Server 2008, but got fixed in Windows 7 (are you OK now?) and Windows Server 2008 R2.
The post is about why you can’t use File Sharing wizard if you exclude inheritable permissions from a folder’s parent.
Just in case, people are wondering why this thing never work on Windows Vista (ok ok, that’s the last time I would utter that word) and Windows Server 2008, you have one more reason to dump *you know what*.