Maybe I'm a dreamer, but I would have thought that RU10 would have updated the link.
But thank you - this will prove helpful indeed. Kurt On Tue, Sep 8, 2015 at 7:16 PM, Michael B. Smith <[email protected]> wrote: > Really. :-) > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Tuesday, September 8, 2015 9:46 PM > To: [email protected] > Subject: Re: [Exchange] Exchange 2010 and powershell on my workstation > > Really? That simple? > > Oy. > > Kurt > > On Tue, Sep 8, 2015 at 5:19 PM, Michael B. Smith <[email protected]> > wrote: >> Remove the "-version 2.0". >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Kurt Buff >> Sent: Tuesday, September 8, 2015 8:14 PM >> To: [email protected] >> Subject: [Exchange] Exchange 2010 and powershell on my workstation >> >> for my own simple-minded purposes, I keep a list of command line invocations >> for the apps that I have installed on my workstation. >> >> The one for the Exchange shell is: >> >> runas /netonly /user:[email protected] \ >> "%windir%\system32\WindowsPowerShell\v1.0\powershell.exe \ >> -version 2.0 -noexit -command \".\ >> 'C:\Program Files\Microsoft\Exchange >> Server\V14\bin\RemoteExchange.ps1'; \ >> Connect-ExchangeServer -auto\"" >> >> (whew - that's a long command line) >> >> The problem is that it wants PS 2.0 compliance. This makes integration for >> my user provisioning much more manual that is ideal. >> >> The server is at SP3 RU10, and I've installed RU10 on my workstation also. >> >> Is there a way to use the PS v4 that I have running on my Win8.1 workstation >> with Exchange? >> >> Kurt >> >> > >
