Powershell License, Configuration and Error

Post by **support-log** » Thu Jun 28, 2012 2:31 am

Hi,

I have some troubles with Power Shell Studio.

I would like to know what kind of license you give, because I want to install it on several computers by SCCM deployment.

Recently, I bought a Power Shell Studio 2012 to have the latest version of some functions of Primal Forms and I have a license.

1 - I don't understand why, when I start Power Shell Studio 2012, it shows me a "warning: Power Shell V2" on the Console.

2 - How to import a System Automation assembly in?

3

Post by **davidc** » Thu Jun 28, 2012 4:18 am

Our
licenses are on a per user bases. You can purchase multi-user licenses, but for
that you will have to contact sales.

Before
I can answer questions 1 & 2 I need to know what OS and version of
PowerShell you are running.

Post by **support-log** » Thu Jun 28, 2012 4:51 am

Support-Log@revenuquebec.ca2012-06-29 11:28:37

Post by **support-log** » Fri Jun 29, 2012 4:21 am

Thank you for your quick response.

OS : Windows XP SP3 32 Bits FRENCH CANADIAN
Version : PowerShell Studio 2012 V3.0.4

I need a Corporative License approximatively for 100 users.
Ok, but my trouble is : To make my installation, I use an administrator profile.

Post by **Alexander Riedel** » Fri Jun 29, 2012 6:07 am

Can you please confirm that you attempt to roll out a single user license to 100 users?We have a way of rolling out unattended installs with pre-configured licenses, but this requires a multi-user license key.If you are not sure, please email your license key to support@sapien.com and I can check how many licenses it contains.Please do not post any license keys here.

Post by **davidc** » Fri Jun 29, 2012 6:45 am

The
PowerShell V2 message is most likely do to having PowerShell V1 installed. This
will also affect the assembly since PowerShell Studio looks for the PowerShell
V2 Assembly.

You
can add default Assemblies in the Options->Editor

You
can add an assembly to a specific form by using the Assemblies button the
Ribbon (under the Editor category in the Home tab). Note: You must be in the
script editor to see the Assemblies button.

David

Post by **support-log** » Tue Jul 03, 2012 6:13 am

Can you please confirm that you attempt to roll out a single user license to 100 users?
We have a way of rolling out unattended installs with pre-configured licenses, but this requires a multi-user license key.
If you are not sure, please email your license key to support@sapien.com and I can check how many licenses it contains.
Please do not post any license keys here.

Hi Alexander ,
An analyst of my team will contact you ASAP.
Thank you

Post by **support-log** » Tue Jul 03, 2012 6:27 am

The PowerShell V2 message is most likely do to having PowerShell V1 installed. This will also affect the assembly since PowerShell Studio looks for the PowerShell V2 Assembly.

You can add default Assemblies in the Options->Editor
You can add an assembly to a specific form by using the Assemblies button the Ribbon (under the Editor category in the Home tab). Note: You must be in the script editor to see the Assemblies button.

David

Hi David,
I try to install PowerShell 2012 on XP "Vanilla" (clean) without previous versions.

Post by **davidc** » Tue Jul 03, 2012 7:22 am

PowerShell is not installed on XP by default. You will have to install it separately. David

Post by **support-log** » Thu Jul 05, 2012 2:08 am

PowerShell is not installed on XP by default. You will have to install it separately.

David
Ok

SAPIEN Technologies