Following on from an earlier few posts about IIS, I hit an issue yesterday, where a client was trying, and failing, to connect the IIS tool ( istool.sh ) to their IIS environment, with a strange exception.
I suspected that the issue was their nice n' strong n' proper password, which contained special characters such as pling ( ! ).
Therefore, istool was seeing the password as an extension of the command, and parsing it accordingly.
Thankfully, there's an answer ( kindly provided by a colleague ) - wrap the complex password e.g.
Qp4$$w0rd!!
in single quotes like this: -
'Qp4$$w0rd!!'
Once we did that, we were golden :-)
No comments:
Post a Comment