Hello,
I just upgraded the version 13 and now my reporting script will not work with the following error; 'Get-VBRComputerBackupJobSession' is not recognized as the name of a cmdlet. Why do you always change stuff, I have another word for it, and not tell anyone? How do I fix this?
-
cowboy898
- Novice
- Posts: 7
- Liked: never
- Joined: Oct 23, 2017 1:42 pm
- Full Name: john steele
- Contact:
-
david.domask
- Veeam Software
- Posts: 3152
- Liked: 725 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Script broken after updage
Hi cowboy898,
The cmdlet still exists, so at first blush not sure what the challenge is. Do you import the Veeam Powershell module first?
All changes are recorded in the corresponding change log in the User Guide, and breaking changes / minor changes are documented.
The cmdlet still exists, so at first blush not sure what the challenge is. Do you import the Veeam Powershell module first?
Code: Select all
Import-Module Veeam.Backup.PowershellDavid Domask | Product Management: Principal Analyst
-
cowboy898
- Novice
- Posts: 7
- Liked: never
- Joined: Oct 23, 2017 1:42 pm
- Full Name: john steele
- Contact:
Re: Script broken after updage
I had done that once but guess I have to do it again. But now I'm getting this. but because its name does not include an approved verb, it might be difficult to find. For a list of approved verbs, type Get-Verb. What ever that means Thanks David.
-
cowboy898
- Novice
- Posts: 7
- Liked: never
- Joined: Oct 23, 2017 1:42 pm
- Full Name: john steele
- Contact:
Re: Script broken after updage
Who creates that module?
-
cowboy898
- Novice
- Posts: 7
- Liked: never
- Joined: Oct 23, 2017 1:42 pm
- Full Name: john steele
- Contact:
Re: Script broken after updage
OK. All fixed. Thanks for the help.
Who is online
Users browsing this forum: cowboy898 and 3 guests