Add Kasten Helm Repo

 To install the Kasten Helm chart, follow this step

[root@ocp-svc ~]# helm repo add kasten https://charts.kasten.io/

"kasten" has been added to your repositories

Lastly, run 

helm repo update

Error: WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/ocp-install/auth/kubeconfig Error: no repositories found. You must add one before updating

 Error message when execute command helm version

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/ocp-install/auth/kubeconfig

Error: no repositories found. You must add one before updating

Solution: Remove the permission

chmod o-r ~/ocp-install/auth/kubeconfig

chmod g-r ~/ocp-install/auth/kubeconfig

Once done, execute helm version again

[root@ocp-svc ~]# helm version

version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"clean", GoVersion:"go1.15.11"}

More detail, please refer to https://github.com/helm/helm/issues/9115 

Access Denied ADMIN$

 Your machine is on workgroup and you would like to access the machine via share/credential.

Example:

\\computername\share

\\computername\ADMIN$

and has key-in computername\username but failed to gain access. The password is correct yet unable to access via Share. 

If you've encountered the same scenario, you can try this on the machine and put these registry key

Open Registry Editor

1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
2. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
3. Type LocalAccountTokenFilterPolicy to name the new entry, and then press Enter.
4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
5. In the Value data box, type 1, and then click OK.
6. Exit Registry Editor.

This should do the trick and solve the problem

Create Vcenter SSH Public Key

 To use SSH public key on vcenter, you need to perform this steps:

1. Create Key using puttygen (download putty to use this tool)

a) click on generate

b) move your mouse cursor to generate

c) Save the public key

d) Save the private key

2. Use putty to SSH into vcenter

To enable and start the Bash shell, type

> shell.set --enabled True

> shell

3. Edit authorized_keys

> sudo vi ~/.ssh/authorized_keys

a) Insert the public key. Example that you have created

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCw7K7657C3KVD8uEtuBxvEjPui4lD+xZqw0+k95mCH19/xOEWhY6UJREPVRTIw8sgIa2PvlUjuCh+m7ZUqHdheChFE55qxjvZLhGJrAU2MvpAv6ltL5ePUYo1iQYRD/PdMMJKY9EcOE7MOBFkSKKI9IYnLyGr3+6QDfSbeuLc42qNcxUQVTPhRAn6gbxj3ISTxOrf1PdwixbM5GGlyIPmYxzcRX91QFVuhsPfXPdOeWczm+0cBkqIPraRjBwmu3B5dTZz12EFQtQbZxc6fpxhyj0eIMsu8bFjk49IZkat1hLdP00unYOfyTrkAnF5XdtglNcw40ot5MwW4mRCKfGCZ rsa-key-20230406

b) save it and exit

4. To activate key authentication, you have to make sure /etc/ssh/sshd_config: has the following line

PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys

Error "No suitable authentication method is supported. Supported method "publickey"

Error message when adding Linux credential on Veeam Console

Error "No suitable authentication method is supported. Supported method "publickey" 

Note: Below is for AWS EC2 VM access. We would like to use a password instead of using pem key.

#cd /etc/ssh

#vi sshd_config

Locate PasswordAuthentication no

Change to

PasswordAuthentication yes

Save it.

Restart the ssh service

#systemctl restart ssh

Create a new linux account and add into Veeam Console

Linux - Create another user with root right

Create another user & assign it as root right

# more /etc/passwd

ubuntu user is a root admin on the Linux VM

#-id -a ubuntu

Create another user "veeamadmin" & assign same right as ubuntu user.

#useradd -u 1001 -g 1000 -m -d /export/home/veeamadmin veeamadmin

Check veeamadmin

#id -a veeamadmin

#visudo

Go to #User privilege specification, after root entry, key in

veeamadmin ALL=(ALL:ALL) ALL

Save the file

Assign password to veeamadmin

# passwd veeamadmin

Key in your password

To verify, type

su - veeamadmin