You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to launck vCheck script, but I have a lot of errors:
Get-ChildItem : Impossible de trouver le chemin d'accès
Get-ChildItem : Impossible de trouver le chemin d'accès « C:\Users\user\Downloads\Plugins\
Get-ReportHTML : Le terme «Get-ReportHTML» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou
programme exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct et
réessayez.
and a lot more..
Don't need to understand french to see that's something missing like a module maybe?
However, I have checked the prerequisites: PowerCLI version, vCenter version, etc... It's totally ok.
Of course I've launched Powershell/PowercLI with an admin account from different workstations..;
Any idea?
The text was updated successfully, but these errors were encountered:
If you launch with admins permissions, you may lost access to the folder.
If you launch with user "Admin", user "admin" may not have the right to access c:\users\user folder.
I suggest launching the script with the user "user" or to COPY the vcheck folder to another place where both users (user and admin) may have access (read/write) like c:\temp\ .
Error when launching vCheck
Hello
I've been trying to launck vCheck script, but I have a lot of errors:
Get-ChildItem : Impossible de trouver le chemin d'accès
Get-ChildItem : Impossible de trouver le chemin d'accès « C:\Users\user\Downloads\Plugins\
Get-ReportHTML : Le terme «Get-ReportHTML» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou
programme exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct et
réessayez.
and a lot more..
Don't need to understand french to see that's something missing like a module maybe?
However, I have checked the prerequisites: PowerCLI version, vCenter version, etc... It's totally ok.
Of course I've launched Powershell/PowercLI with an admin account from different workstations..;
Any idea?
The text was updated successfully, but these errors were encountered: