Kitematic - Self Signed Certificate In Certificate Chain

Found this issue while behind a enterprise proxy. Proxy uses self signed certificate. Windows has the certificate as trusted, docker works fine, but Kitematic is having the following issue:

While looking in the web found this article:
https://github.com/docker/kitematic/issues/1633

This solution works:

Basically need to set a variable:

set NODE_TLS_REJECT_UNAUTHORIZED=0

Once that is done open Kitematic it should work

Adding network printer to local machine in Windows.

In Windows, if you choose to share a printer, you can from another machine just navigate and right-click and select "Connect"

NodeJS behind proxy

I was getting this message when trying to run node js:

D:\Temp>npm install vss-web-extension-sdk
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "vss-web-extension-sdk"
npm ERR! node v6.11.5
npm ERR! npm  v3.10.10
npm ERR! code ECONNRESET

npm ERR! network tunneling socket could not be established, statusCode=407
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! Please include the following file with any support request:
npm ERR! D:\Temp\npm-debug.log

Well I am behind a Corporate enterprise, so I can the following command:

npm config set proxy http://[username]:[password]@[proxyServerAddress]:[proxyPortNumber]
and also ran
npm config set https-proxy http://[username]:[password]@[proxyServerAddress]:[proxyPortNumber]

Notice the same address on the first and second entries, that is normal. Just telling the https traffic to go through the same proxy.

Now I get this:

D:\Temp>npm install vss-web-extension-sdk
D:\Temp
`-- vss-web-extension-sdk@4.125.2
  +-- @types/jquery@3.2.16
  +-- @types/jqueryui@1.11.37
  +-- @types/knockout@3.4.47
  +-- @types/mousetrap@1.5.34
  +-- @types/q@0.0.32
  +-- @types/react@16.0.25
  `-- @types/requirejs@2.1.31

npm WARN enoent ENOENT: no such file or directory, open 'D:\Temp\package.json'
npm WARN MyProject No description
npm WARN MyProject No repository field.
npm WARN MyProject No README data
npm WARN MyProject No license field.

TFS2015 Exception Message: The file "" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

 Many hours later I find out what was going on with my TFS restore.

 I was trying to restore a TFS2013 backup into a TFS2015 system. I kept getting this error:

Looking into the error log I saw this one line:
Exception Message: The file "<your_backup_database_name>" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

As it turned out the directory of the <your_backup_database_name> was compressed in the Windows os level so I went and set to not compress anymore:

Hope this helps.

Once the above was done the system restored fine.

How to log yourself off from a remote server from command line on your workstation.

All of this information I got from:
This cool blog

First you must have administrative rights on the machine you are trying to log yourself off of.

You will need to get the SessionId to do that run this command bellow
quser /server:[ServerName]

You will something close to this:
USERNAME  SESSIONNAME  ID  STATE   IDLE TIME  LOGON TIME
[YourId]                2  Disc            3  10/2/2014 12:28 PM

Make a note of the number under the ID column. In this case it is 2.

Next you run the following command using the ID that you got before:
logoff 2 /server:[ServerName]

All done you are logged off.

Better way to unlock a file for free.

http://www.emptyloop.com/unlocker/welcome.htm

TFS custom enumeration not showing

I have been working with this solution I have 4 projects:
- Project to hold the xaml files
- Project to hold the first level library (contain my custom activities)
- Project to hold Business Layer stuff
- Project to test the Business Layer stuff

Everything was working great.

I had an enumeration that was in the "first level library". It was a parameter in my builds. I noticed a better place for it would be in the Business Layer project instead, so I moved. After I did this I got the following error on my builds:
"Failed to load the following parameters:"

<InArgument x:Key="EnumerationName" x:TypeArguments="enumerationLibrary:EnumerationName" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns=http://schemas.microsoft.com/netfx/2009/xaml/activities">[EnumerationName.DefaultValue]</InArgument>

I would also get the following:

The parameter EnumerationName could not be loaded because the type InArgument<MyNamespace.BLProjectName.EnumerationName> was not found. You cannot edit this parameter, but you can save your build definition without it.

I have already added my TFS folder to the build server's "Version control path custom assemblies" therefore I knew the DLL was in the right place and TFS should see it.

Well then I found this forum entry.

Basically TFS will NOT jump from a xaml workflow file to a DLL that does not have a Activity in it. Since I moved my enumeration to the Business project that project does not have an activity. The solution for this? Add a dummy activity into the project.

Here is an example from Valéry Letroye in the forum above:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.TeamFoundation.Build.Client;
using System.Activities;
 
namespace AG.SCRM.TeamBuild.Helpers
{
 
    //If a custom assembly uses a dependent assembly (reference) which is needed to run activities, 
    //they will not get deployed properly. If this is the case you will get “unknown type” errors on 
    //build definition initialization:
    // TF215097: An error occurred while initializing a build for build definition xxxx: 
    // The type ‘xxxx’ of property ‘xxxx’ could not be resolved.
    //To work around this issue, we add a dummy CodeActivity into the dependent assembly with the
    //class scoped attribute: [BuildActivity(HostEnvironmentOption.All)] 
 
    [BuildActivity(HostEnvironmentOption.All)]
    public sealed class DummyCodeActivity : CodeActivity
    {
        protected override void Execute(CodeActivityContext context)
        {
            throw new NotImplementedException();
        }
    }
}

I did the above and everything started working fine.

God bless,

Bruno