Remote script execution on behalf of a local account

hello everyone, I have created a script to remove the certificate on remote computers.
I want to run this script on a remote PC under a local account. But it does not work, if the same script is run from a domain account, then everything is ok.
and I need from local. The local entry is a member of the Administrators group.

$del_cert_veeam = {$Path = 'Cert:\LocalMachine\My\'

$CertList = Get-ChildItem -Path $Path | Where-Object {$_.Issuer -like "CN=Veeam*"}

    remove-item "$($Path)$($CertList.Thumbprint)" -Force
}
$password = ConvertTo-SecureString "Qwerty@12" -AsPlainText -Force
$Cred = New-Object System.Management.Automation.PSCredential ("testpc01\user1", $password)
Invoke-Command -ComputerName testpc01.com.lan -Credential $Cred -ScriptBlock $del_cert_veeam

Error

[testpc01.com.lan] Connecting to remote server testpc01.com.lan failed with the following error message : WinRM cannot process t
he request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon ser
vers available to service the logon request.  
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport
.
Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Re
mote_Troubleshooting Help topic.

Have you tried adding:

-Authentication 'Negotiate'

To Invoke-Command?