Powershell Invoke-Command -Computername without FQDN

Question

I’m using a tool which uses Invoke-Commands. Test-Connection and other commands works without the Fully Qualified Domain Name when I type in the computer name. But when I want to use the Invoke Commands I have the use the FQDN of the computer. Does someone also notice that? Is this so or is the any workaround? Thanks for your help!

So what happens if you use just hostname? Do you get an error message? Nothing happens? Command is executed against wrong computer? Something else? — vonPryz
– vonPryz, Commented Aug 25, 2015 at 6:17
I don’t get any error message or somethings like that. It executes the command and I don’t get any return value — guiwhatsthat
– guiwhatsthat, Commented Aug 25, 2015 at 6:46

wavestone · Accepted Answer · 2018-06-17 18:46:43Z

1

its because your WSMANconfiguration is set to credssp and not basic.

credssp requires to enter FQDN rather than netbios name

I hope it helps

answered Jun 17, 2018 at 18:46

wavestone

796 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 11:51:21Z

0

I think this might provide you with the answer to your question along with why it is like that. I pretty positive that the commands share enought similarities to experience the same problem.

Powershell remoting with ip-address as target

edited May 23, 2017 at 11:51

CommunityBot

11 silver badge

answered Aug 25, 2015 at 9:19

Jonas

3062 silver badges11 bronze badges

Collectives™ on Stack Overflow

Powershell Invoke-Command -Computername without FQDN

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related