Thanks for the information Macro.
Is it corrected in v2? if you come across. Or any alternate way to
execute process.
On Apr 16, 4:40*pm, "Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com>
wrote:
Quote:
> I'm sorry, what are you identifying here:
>
>
>
>
> Quote:
> > ## 1 ##
> > $co = new-object management.connectionoptions
> > $co.Username = "ServerName\UserID"
> > $co.SecurePassword = (read-host -assecurestring)
> > $scope = new-object management.managementscope "\\ServerName\root
> > \cimv2",$co
> > $scope.Connect()
> > $mp = new-object management.managementpath "win32_process"
> > $ogo = new-object management.objectgetoptions
> > $proc = new-object management.managementclass $scope,$mp,$ogo
> > $proc.Create("notepad.exe")
> Quote:
> > ## 2 ##
> > $comp = "ServerName"
> > $cre = get-credential ServerName\UserID
> > $win32ProcessClass = Get-WmiObject -List -Namespace 'root\cimv2' -
> > credential $cre -computername $comp | Where-Object { $_.Name -eq
> > 'Win32_Process' }
> > $win32ProcessClass.Create("notepad.exe")
>
> Neither works in your last scenario?
>
> I understand there are some small cross-domain authentation issues with
> get-wmiobject in v1.
>
> Marco
>
> --
> Microsoft MVP - Windows PowerShellhttp://www.microsoft.com/mvp
>
> PowerGadgets MVPhttp://www.powergadgets.com/mvp
>
> Blog:http://marcoshaw.blogspot.com- Hide quoted text -
>
> - Show quoted text -