To help you better we need some information from you.
*** Please fill in the fields below if you are currently using a Trial Version of the Product. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product, version and build: Sapien 2018
32 or 64 bit version of product: 64
Operating system: Windows 2008 R2
32 or 64 bit OS: 64
Sapien 2018 does not find any of the VMWARE Powercli modules/Plugins.
I searched the forums and did not find an article that expains how to get Sapient to work with Powercli 5.5.
Please advise.
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
How do I import VMWARE Powercli into Sapien
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Re: How do I import VMWARE Powercli into Sapien
PowerShell Studio supports VMWare modules, but they must be in a discoverable location (in a PSModulePath folder).
1. Try refreshing PowerShell Studio's cmdlet cache:
If the module does not appear in the Object Browser:
or the module isn't in a PSModulePath, then you can use the CacheEditor to import the module.
Open CacheEditor:
Import Module:
Then press "Build" and exit the editor. The module should now appear on the list.
Video on CacheEditor:
https://www.sapien.com/blog/2018/01/02/ ... he-editor/
1. Try refreshing PowerShell Studio's cmdlet cache:
If the module does not appear in the Object Browser:
or the module isn't in a PSModulePath, then you can use the CacheEditor to import the module.
Open CacheEditor:
Import Module:
Then press "Build" and exit the editor. The module should now appear on the list.
Video on CacheEditor:
https://www.sapien.com/blog/2018/01/02/ ... he-editor/
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.