Guest OS Credential problem - Workgroup

[zaiga]

Hi,
I am trying to set up a new job for a Windows 10 VM running on a Hyper V Core.
I am using the following: Hostname\User (In my case: testcomputer\user1)
But it simply doesn't want to connect during the "Test now" sequence.

I can access from another server to shared folders on the Windows 10 VM.

Although I have a feeling that something needs to be changed on Windows 10 to allow the access ?

Greetings!

[HannesK]

Hello,

testcomputer\user1

is that user an administrator? As an alternative, did you try to enable and use testcomputer\administrator?

Best regards,
Hannes

[zaiga]

Hi,
thank you for the answer!

I am not that experienced with windows, what do you mean exactly by "enabling" administrator in windows?


Thank you!

[HannesK]

Hello,
the administrator account is disabled per default since some versions of windows. you can enable it in the computer management (right click on windows button)

I ask the other way round: what's the purpose of testing the credentials?


Best regards,
Hannes

[zaiga]

Thank you for the answer! It worked (partly) after the activation.
1.Whats wrong with the main account for Veeam? (Both Accounts are part of the Administrator Group)
2.But I still get the following errors:



The purpose is that I would like to backup a SQL Server running in a VM later. And I am testing Veeam right now.

[HannesK]

Hello,
RPC is good, it should be used always in "normal" environments. Yes, for SQL logshipping & restore it is important.

As you mentioned you are not too deep into Windows, I suggest to leave the PowerShell direct part as it is. It's just a fallback that should never be used anyway in "normal" environments.

Best regards,
Hannes

[zaiga]

Thank you for the answer, I meant that I mostly work with Linux systems.

1. Whats wrong with the main account in contrast to the Administrator Account?
2. I was reading that RPC is "enough" but Veeam doesn't produce a Backup then, it stops with an Error and says that powershell doesn't work.

[HannesK]

Thank you for the answer, I meant that I mostly work with Linux systems.

I guessed something like that - I had several customers with similar background

@1: to be honest, I don't know. It was just a guess - normally I don't see people running Windows10 as servers and I just guessed it because that was the main difference between server and client OS I saw

@2: that's strange. RPC is the first way per default and only if it fails, then it tries powershell. To answer the question why the job fails, I can only suggest to open a case. Please post the case number here.