Forcing version 2 on remote session for SharePoint management using Powershell -


it seems sharepoint 2010 still incompatible powershell version 3.0.

i aware possible force compatibility executing powershell -v 2 switch, there way force compatibility mode when using remote session via pssession using remote desktop quite impractical launch shell?

if start client powershell -v 2. outgoing remote sessions should use v2 on remote end automatically.

update: appears mistaken - think in fact had discussed powershell team, apparently it's not fixed. anyway, can create session configuration on server forced version 2.0:

ps> $psversiontable  name                           value ----                           ----- psversion                      3.0 wsmanstackversion              3.0 serializationversion           1.1.0.1 clrversion                     4.0.30319.18010 buildversion                   6.2.9200.16434 pscompatibleversions           {1.0, 2.0, 3.0} psremotingprotocolversion      2.2  ps> register-pssessionconfiguration -psversion '2.0' -name "powershell2" 

accept of prompts. now, must pass name of new remote session configuration when invoking client side (in example, client , server same machine: desktop)

ps> icm localhost -configurationname powershell2 { $psversiontable }  name                           value ----                           ----- psremotingprotocolversion      2.1 buildversion                   6.1.7600.16385 pscompatibleversions           {1.0, 2.0} psversion                      2.0 clrversion                     2.0.50727.6400 wsmanstackversion              2.0 serializationversion           1.1.0.1 

as can see, remote endpoint running 2.0.

i hope helps.


Comments

Popular posts from this blog

c# - Operator '==' incompatible with operand types 'Guid' and 'Guid' using DynamicExpression.ParseLambda<T, bool> -