We all started at the beginning, no worries
For a fresh install you can use the Install-Module -Name VMware.PowerCLI command.
1 person found this helpful
Thank you for your help. I still haven't been able to get PowerCLI added, but your information helped me to learn where the error is in my system. I believe that PowerShell Studio, combined with my incompetence, has proliferated a total of five (5) different paths for where modules may be located. I was trying to keep everything in just one location so that I could easily verify when a module was properly installed or not. I believe that I have some cleanup to try and do; although I'm not certain yet where to start. I suppose that I could just wipe everything out and start from scratch. Unfortunately, that would also wipe out all the scripting work that I did last week in preparing queries for SCCM. I need to decide if i want to either lose it all or take some additional time and back that stuff up. I'll most likely go with the latter, but that still doesn't help me to decide how to get 5 paths down to one and simplified my PowerShell file structure and profile so that this doesn't happen again.
Well, as the quote goes, 'back to the drawing board', in this case the whiteboard *LOL*.
Thanks again LucD, you ROCK as always!!
PS gets modules from multiple places.
You can check which folders those are by doing
I'm not sure if Studio adds anything to that.
But those are locations for modules, not necessarily where you store your own scripts.
Unless of course, you have packaged your functions into one or more modules.
These locations also reflects in which 'Scope' a module was installed.