locked
ADFS and workfolders RRS feed

  • Question


  • Hi, I am trying to setup a server following the guide as below.

    http://blogs.technet.com/b/filecab/archive/2014/03/03/deploying-work-folders-with-ad-fs-and-web-application-proxy-wap.aspx.

    I am stuck with Binding with netsh;

    $subject = "workfolders.mydomain.com"
         Try
        {
         #In case there are multiple certs with the same subject, get the lastest version
         $cert = Get-ChildItem CERT:\LocalMachine\My |where {$_.Subject -match $subject|sort $_.NotAfter -Descending | select -first 1 
         $thumbprint = $cert.Thumbprint
         $Command = "http add sslcert ipport=0.0.0.0:443 certhash=$thumbprint appid={CE66697B-3AA0-49D1-BDBD-A25C8359FD5D} certstorename=MY"
         $Command | netsh
        }
        Catch

        {

          "        Error: unable to locate certificate for $($subject)"
            Exit

        }

    I am getting the error netsh> one or more parameters are not found. 

    Beside having to change the subject; what should i change?

    Wednesday, January 13, 2016 2:50 AM

Answers

  • I'd also try running the NETSH command under a CMD (command) prompt.. I've actually seen PowerShell reject http add sslcert parameters, yet the command prompt accept. Todays, weird but true fun fact :-)

    http://blog.auth360.net

    Wednesday, January 13, 2016 5:45 PM
  • Just to be on the safe side, can you try this command instead?

    $Command = "http add sslcert ipport=0.0.0.0:443 certhash=$thumbprint appid=""{CE66697B-3AA0-49D1-BDBD-A25C8359FD5D}"" certstorename=MY"


    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Wednesday, January 13, 2016 3:27 PM

All replies

  • Just to be on the safe side, can you try this command instead?

    $Command = "http add sslcert ipport=0.0.0.0:443 certhash=$thumbprint appid=""{CE66697B-3AA0-49D1-BDBD-A25C8359FD5D}"" certstorename=MY"


    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Wednesday, January 13, 2016 3:27 PM
  • I'd also try running the NETSH command under a CMD (command) prompt.. I've actually seen PowerShell reject http add sslcert parameters, yet the command prompt accept. Todays, weird but true fun fact :-)

    http://blog.auth360.net

    Wednesday, January 13, 2016 5:45 PM
  • Same here... I always run netsh commands in a classic command prompt...

    Here I believe the curly brackets are the issue. This is why they are between quotes in my suggestion. Let's see if that works, let us know! 


    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Wednesday, January 13, 2016 6:06 PM
  • yep CMD seems to work
    Thursday, January 14, 2016 1:39 AM