Run vbs script from maxl shell

Hi -
I created one vbs script (test.vbs) which copy file from one location to another one. I'm calling this vbs script from one maxl script (copy.msh).
Here is the code in copy.msh:
login "$user" "$pw" on "$server";
shell "$(path)test.vbs xx.rul";
When I run copy.msh script from windows command line, I get the window popup message:
"Windows can not open this file test.vbs" ...
Do I have to configure something on my machine to run vbs script? Any help on this would be highly appreciated.
Thank You!

Ensure the $path variable is being assigned the correct value. Based on the error you quoted, its not being assigned a value at all.
It would help if you posted your actual code. Pls put the code inside {code} {code} tags for easier viewing.
Robb Salzmann

Similar Messages

Running VBS script from CAD Agent

Edit:
I found it, it is thru Agent Desktop Administrator.
We have a scrip set up to populate members account numbers from the call in menu, when the memeber talkes to the call center agent, the account number is populated in the agent screen.
This is a vbs scrip located on a network share. The share was off line and the agent were getting the following pop-up message:
Error Launching Application
Acction Name:           Runscript
Application:              \\share\desktop_cfg\script.vbs
Error Masseage:     The network path was not found
I need to be able to point the agents to a new share for this scrip. Where do I find this parameter to change it?

Hi Wilson,
Yes. Every time you launch the CAD\CAD-BE , it checks for the updates from UCCX (for version upgrades) and also from the CDA side, if any it syncs.
Work Flow Configuration enables you to configure and maintain the appearance and behavior of Agent Desktop, Agent Desktop—Browser Edition, and IP Phone Agent.
The CAD client applications must be restarted for any configuration changes you make
to go into effect.
Hope it helps,
Anand
Please rate helpful posts..

Running SQLPLUS script from command prompt on SUN

We are making a migration from VMS to SUN ( SunOS 5.10) and from 9i to 10g. We have encountered an unanticipated problem with running scripts from the command line in SUN(SQLPLUS execution from the command line). All of our packages have a naming convention such as "DM$LOAD.PKB". I know it is a strange naming convention.
The problem is that when the package creation script is run in SQLPLUS at the command prompt SQLPLUS can not open the file.
SQL> @dm$load.pb
SP2-0310: unable to open file "dm$load.pb"
SQL> host ls
dm$load.pkb
SQL>
Setting the escape character does not seem to help.
SQL> set escape '\'
SQL>
SQL> @dm\$load.pb
SP2-0310: unable to open file "dm$load.pb"
SQL>
Unfortunately, we can not rename the scripts. This can be done from a shell script, but our Tech Services refuse to run the SQL scripts from a shell script
Any ideas on how to get SQLPLUS to run the scripts from the SUN command line?

I did not notice that the cut and paste was poor. It should have read
SQL> @dm$load.pkb
SP2-0310: unable to open file "dm$load.pkb"
SQL> host ls
dm$load.pkb
Any ideas will be greatly appreciated.

Initiating batch scripts from Maxl Script Editor in Admin Console??

Guys,
Is it possible to initiate batch scripts from Maxl script editor in Admin Console.
I dont want to automate the scripts as my data loading process can happen at any time.
Thanks in advance
A

Hi A,
I'm not sure what you're asking? Do you want to run a batch of Maxl scripts, or a batch file, or a single Maxl Script? Why do you choose to use the Admin console to do this? Could you run what you're trying to run in batch from the command line?
Executing MaxL and MDX Scripts
To execute a MaxL script or an MDX script:
Open or create the script.
From the server drop-down list on the toolbar, select the Analytic Server to execute the script against.
The drop-down list contains only Analytic Servers that are displayed in your Enterprise View. For more information about connections, see Connecting to Analytic Servers in MaxL and MDX Script Editors.
Specify how errors should be handled during execution. See Setting MaxL and MDX Execution Options.
Specify how you want results to be displayed in the Results tab. See Viewing MaxL and MDX Results.
If the script contains variables, specify how undefined variables are resolved during execution. See Resolving Undefined Variables.
To execute the entire script, right-click and select Execute from the pop-up menu.
To execute only part of the script, highlight the statement or statements that you want to execute, right-click, and select Execute from the pop-up menu.
The script executes against the specified Analytic Server, and the results are displayed in the Results panel.Regards,
Robb Salzmann

When I run my script from a shortcut ExtendScript is invoked, but it is not when I run it the menu

I am using Photshop CS2 on Win XP
I have configured a keyboard shortcut (Crtl+Alt+P) to run a .jsx file from the ...\Presets\Scripts\ folder.
When I activate the script via the Keyboard Shortcut ExtendScript is invoked, and breaks execution on the main() statement (see below).
When I activate the script via the File/Scripts menu ExtendScript is not invoked and the script runs to completion.
The .jsx file is a wrapper for a .vbs script which does the 'real' work.
The .jsx is:-
function main()
var VBSscript=File("C:/Program Files/Adobe/Adobe Photoshop CS2/Presets/Scripts/GGN_PS_Code_v1_2.vbs");
if(VBSscript.exists) VBSscript.execute();
main();
Does anyone have any ideas as to how to disable the invokation of ExtendScript when I run the script from the skortcut?

Thanks Paul.
I am out of the office at the moment, but your answer rings true. Certainly the .jsx extension is associated with ExtendScript. I'll delete the association and try again when I am back in the office.
Many thanks

How can i run unix script from my apex page

how can i run unix script from my apex page and take the output of unix script as a hidden variable and display it on the report region of that page

I had a requirement to run a Fortran program against some data that woudl be extracted from the database after the user set up their filtering criteria and made some additional input. SInce the program was to complex to conver to PL/SQL, we decided to try and invoke it from Apex. This is how I did it.
1. I followed the steps in Tim Archer's excellent article "Oracle External Procedure to Run Host Commands" (http://www.timarcher.com/?q=node/9). If the link does nto work, google the article's title.
Using this steps I created a function which accepts any OS command, including calling my own shell scripts, and runs them. I called my PL/SQL function "shell" instead of "USF_RUN_HOST_CMD " as Tim did in his example (step 9).
2. In Apex,
a. I created a button to run my shell command. (I named it P2_RUN_SHELL)
b. I created a PL/SQL process whose source looks as follows:
shell('/home/ackness/scripts/cr_xcf_file.sh > /tmp/cr_scfp_file.log');
and which was conditioned on the the button P2_RUN_SHELL.
It works like a charm.
Note: since you can run your own scripts using this method, you can encapsulate a series of commands in a UNIX shell script and invoke that script from Apex. This allows you to be able to test or run you commands from the command line as well as Apex and makes it easier to develop/debug/enhance the scripts in the future.
Ackness

IDCS5-win. Error while running a script from indesign(not via estk)

Hi all,
After running the script from indesign, I get following error
ASSERT '(engine->getDebugFlags() & ScScript::kExtendedErrors) == ScScript::kExtendedErrors' in ..\..\..\source\components\script\javascript\JavaScriptRunner.cpp at line 412 failed.
..\..\..\source\components\script\javascript\JavaScriptRunner.cpp (412)
any idea about this?
The script runs fine when run from ES tool kit.
Thanks

Hi,
My colleague found the problem. We were using extendables library and we still haven't figured out what was actually happening, but removing it solved the problem.

How to run a script from Oracle Form (Beside using HOST command)

I would like to run a script from Forms 6.0. I know that we can actually issue this command :
host('plus80.exe' username/password@connect_string @c:\scriptname);
BUT, is there any other alternative ?

Sqlplus is a different program, so one way or the other you have to leave Forms to run sqlplus. What is you objection against HOST?
You can also run sqlplus from the database, but again you need a stored java procedure to call sqlplus (sort of HOST command that runs in the database).
Francois' solution works if your script just has a query to run, but if you have specific sqlplus commands (spool etc.) forms_ddl is probably not a solution.

Running sql scripts from different directory

Hi
I have sql scripts in different directories as follows:
D:\myapp\sql
- load.sql
- init.sql
D:\myapp\sql\schema
-users.sql
-structure.sql
D:\myapp\sql\populate\
- data1.sql
- data2/sql
load.sql call all the other scripts as below:
@init.sql
@schema\users.sql
@schema\structure.sql
@populate\data1.sql
@populate\data2.sql
All my scripts run correctly when I run load.sql from D:\myapp\sql on comand prompt.
I need a way to run this script from a different directory say D:\ or C:\
I am writing a installer which will execute from a different directory.
Right now I get a file not found error for scripts within schema an populate folder.
Please let me know how can I make this work from a different directory.
Thanks
kelvin

Hi peter. i think you cannot run files spread across different locations.
--the method which u specified always looks to the defined path

Valid sesion for run jython script from a plan

If I run a cr_clij script i have to do
app.execStr('udb.login -u user -p password') once and do not produce the login information anymore.
It is possible to do the same with the sessionID, if I run the script from a plan on the BUI? Or do I have to add the '-s sessionID' option to all clui commands?
Thanks

Hi TemPart:
string cmdArg = “C:\\Scripts\\test.ps1″;
Runspace runspace = RunspaceFactory.CreateRunspace();
runspace.Open();
Pipeline pipeline = runspace.CreatePipeline();
pipeline.Commands.AddScript(cmdArg);
Collection [PSObject] results = pipeline.Invoke(); // please Update [] bracket with less then and greater then bracket
runspace.Close();
Had to modify this slightly:
string cmdArg = “Powershell.exe -file C:\\Scripts\\test.ps1″;
Runspace runspace = RunspaceFactory.CreateRunspace();
runspace.Open();
Pipeline pipeline = runspace.CreatePipeline();
pipeline.Commands.AddScript(cmdArg);
Collection [PSObject] results = pipeline.Invoke(); // please Update [] bracket with less then and greater then bracket
runspace.Close();
If this is helpful please mark it so. Also if this solved your problem mark as answer.

Run a script from a script

Can anyone help me run a script from a script to kill an event listener?
There is an event listener on save. The same script may be run multiple times before changing workflows (which require different sets of scripts).
The eventual goal is to have a time stamp in a specific text frame that will already have content. The new stamp will overwrite the old, and only happen before close. Right now it's set for "on save" because I can't figure out an if else statement for "before close". I don't want to have to end the session to be able to work different job types. I need to be able to kill the event listener when exiting documents that create one.
I'm throwing crap at the wall, hoping it will stick. I'm sure there's a better way to handle it. Anyone have ideas.
CS3 & CS4 javascript
Thanks

Here's the kind of thing I use:
function runShortRanges() {
    var shortRangesScript = File(getScriptPath().parent.parent + "/IndexExtras/ShortRanges.jsx");
    if (shortRangesScript.exists) {
      app.doScript(shortRangesScript);
In this case, I want to run a particular script in a known location, only if it exists. It's a way of adding optional functionality to a script.
Dave

Running ISA Scripts from SSL enabled IOP server?

When attempting to run a script from an SSL enabled IOP server, scripts no longer run.
Is there a setting to enable the script to utilize the appropriate SSL port?
Thank you.

Can you please elaborate some more information on the above post.

Running Oracle Scripts from Command Line

Hi,
How can i run Oracle scripts from command line.
Actually i need to run these scripts from MSBuild before running Unit test projects

C:\>sqlplus @myscript
That would be the easiest variation
C:\>sqlplus user/passwd@tns_alias @myscript
would be an often used variation
And then there is of course the version with parameter passing:
C:\>sqlplus user/passwd@tns_alias @myscript param1 ... paramx
Dunno about MSBuild

Running sqlplus scripts from Java code?

hi
I need to programmatically run sqlplus scripts from Java code on a machine that doesn't have sqlplus installed.
Is there any Java class library available for doing this?

The Ant approach could probably work for me, thanks for the tip.
The setup seems rather complex however, given the simplicity of the task. I would prefer just running a Java based SQL*Plus from in a separate process or doing this via an API that would allow me to run SQL*Plus scripts (parse script, substitute variables, run statements).
Oracle SQL Developer v1.1 appears to include an API that does exactly this.
The ScriptParser, Substitution and SQLPLUS classes in the oracle.dbtools.raptor.scriptrunner package (oracle.sqldeveloper.jar) seem to do just what I need based on my tests.
Can I use these classes for this purpose in my application? Is repackaging allowed?
Does Oracle have any plans for releasing this sort of functionality separately e.g. as part of the Instant Client?

Powershell: how to run vbs script with switches.

Background: To remove a specific service, I usually log into a server, go to path c$\Program files\HP... find a specific vbs, and run it using CMD.exe.
Now, I'm new to powershell, so I'm looking into automating this job. When I use CMD, I run cscript path\serviceinstall.vbs
-r.
How do I add cscript switches to powershell?
IF
((test-path -path "servername\C$\Program Files\...") -eq "true")
invoke-command -scriptblock ""servername\C$\Program Files\...\serviceinstall.vbs -r?

1. You cannot run VBS as a scriptblock.
2. If youactually were to have read the full help ypu would have seen how to use the command.
3. Given you initial questin and the vague answers you gave there is nothing any could do to help you.
If you do not give accurate information you will not likely get answers that are helpful.
I recommend starting at the beginning and learning PowerShell basics. If you had done that you would know that a script block is not a quoted string with vbscript in it or the path to a file.
When working with any technology it is important to read the instructions carefully. It is also useful to knowhow to do basic research on the technology you are trying to learn.
There are 15 examples in PowerShell V2 for Invoke-Command. Here they are as captured directly from PowerShell V2. (The is no update-help on V2. All help is built in.)
-------------------------- EXAMPLE 1 --------------------------
C:\PS>invoke-command -filepath c:\scripts\test.ps1 -computerName Server01
Disks: C:, D:, E:
Status: Warning, Normal, Normal
Description
This command runs the Test.ps1 script on the Server01 computer.
The command uses the FilePath parameter to specify a script that is located on the local computer. The script runs
on the remote computer and the results are returned to the local computer.
-------------------------- EXAMPLE 2 --------------------------
C:\PS>invoke-command -computername server01 -credential domain01\user01 -scriptblock {get-culture}
Description
This command runs a Get-Culture command on the Server01 remote computer.
It uses the ComputerName parameter to specify the computer name and the Credential parameter to run the command in
the security context of "Domain01\User01," a user with permission to run commands. It uses the ScriptBlock paramete
r to specify the command to be run on the remote computer.
In response, Windows PowerShell displays a dialog box that requests the password and an authentication method for t
he User01 account. It then runs the command on the Server01 computer and returns the result.
-------------------------- EXAMPLE 3 --------------------------
C:\PS>$s = new-pssession -computername server02 -credential domain01\user01
C:\PS> invoke-command -session $s -scriptblock {get-culture}
Description
This example runs the same "Get-Culture" command in a session (a persistent connection) on the Server02 remote comp
uter. Typically, you create a session only when you are running a series of commands on the remote computer.
The first command uses the New-PSSession cmdlet to create a session on the Server02 remote computer. Then, it saves
the session in the $s variable.
The second command uses the Invoke-Command cmdlet to run the Get-Culture command on Server02. It uses the Session p
arameter to specify the session saved in the $s variable.
In response, Windows PowerShell runs the command in the session on the Server02 computer.
-------------------------- EXAMPLE 4 --------------------------
C:\PS>invoke-command -computername Server02 -scriptblock {$p = get-process powershell}
C:\PS> invoke-command -computername Server02 -scriptblock {$p.virtualmemorysize}
C:\PS>
C:\PS> $s = new-pssession -computername Server02
C:\PS> invoke-command -session $s -scriptblock {$p = get-process powershell}
C:\PS> invoke-command -session $s -scriptblock {$p.virtualmemorysize}
17930240
Description
This example compares the effects of using ComputerName and Session parameters of Invoke-Command. It shows how to u
se a session to run a series of commands that share the same data.
The first two commands use the ComputerName parameter of Invoke-Command to run commands on the Server02 remote comp
uter. The first command uses the Get-Process command to get the PowerShell process on the remote computer and to sa
ve it in the $p variable. The second command gets the value of the VirtualMemorySize property of the PowerShell pro
cess.
The first command succeeds. But, the second command fails because when you use the ComputerName parameter, Windows
PowerShell creates a connection just to run the command. Then, it closes the connection when the command is complet
e. The $p variable was created in one connection, but it does not exist in the connection created for the second co
mmand.
The problem is solved by creating a session (a persistent connection) on the remote computer and by running both of
the related commands in the same session.
The third command uses the New-PSSession cmdlet to create a session on the Server02 computer. Then it saves the ses
sion in the $s variable. The fourth and fifth commands repeat the series of commands used in the first set, but in
this case, the Invoke-Command command uses the Session parameter to run both of the commands in the same session.
In this case, because both commands run in the same session, the commands succeed, and the $p value remains active
in the $s session for later use.
-------------------------- EXAMPLE 5 --------------------------
C:\PS>$command = { get-eventlog -log "windows powershell" | where {$_.message -like "*certificate*"} }
C:\PS> invoke-command -computername S1, S2 -scriptblock $command
Description
This example shows how to enter a command that is saved in a local variable.
When the entire command is saved in a local variable, you can specify the variable as the value of the ScriptBlock
parameter. You do not have to use the "param" keyword or the ArgumentList variable to submit the value of the local
variable.
The first command saves a Get-Eventlog command in the $command variable. The command is formatted as a script block
The second command uses the Invoke-Command cmdlet to run the command in $command on the S1 and S2 remote computers.
-------------------------- EXAMPLE 6 --------------------------
C:\PS>invoke-command -computername server01, server02, TST-0143, localhost -configurationname MySession.PowerShell
-scriptblock {get-eventlog "windows powershell"}
Description
This example demonstrates how to use the Invoke-Command cmdlet to run a single command on multiple computers.
The command uses the ComputerName parameter to specify the computers. The computer names are presented in a comma-s
eparated list. The list of computers includes the "localhost" value, which represents the local computer.
The command uses the ConfigurationName parameter to specify an alternate session configuration for Windows PowerShe
ll and the ScriptBlock parameter to specify the command.
In this example, the command in the script block gets the events in the Windows PowerShell event log on each remote
computer.
-------------------------- EXAMPLE 7 --------------------------
C:\PS>$version = invoke-command -computername (get-content machines.txt) -scriptblock {(get-host).version}
Description
This command gets the version of the Windows PowerShell host running on 200 remote computers.
Because only one command is run, it is not necessary to create persistent connections (sessions) to each of the com
puters. Instead, the command uses the ComputerName parameter to indicate the computers.
The command uses the Invoke-Command cmdlet to run a Get-Host command. It uses dot notation to get the Version prope
rty of the Windows PowerShell host.
To specify the computers, it uses the Get-Content cmdlet to get the contents of the Machine.txt file, a file of com
puter names.
These commands run synchronously (one at a time). When the commands complete, the output of the commands from all o
f the computers is saved in the $version variable. The output includes the name of the computer from which the data
originated.
-------------------------- EXAMPLE 8 --------------------------
C:\PS>$s = new-pssession -computername Server01, Server02
C:\PS> invoke-command -session $s -scriptblock {get-eventlog system} -AsJob
Id Name State HasMoreData Location Command
1 Job1 Running True Server01,Server02 get-eventlog system
C:\PS> $j = Get-Job
C:\PS> $j | format-list -property *
HasMoreData : True
StatusMessage :
Location : Server01,Server02
Command : get-eventlog system
JobStateInfo : Running
Finished : System.Threading.ManualResetEvent
InstanceId : e124bb59-8cb2-498b-a0d2-2e07d4e030ca
Id : 1
Name : Job1
ChildJobs : {Job2, Job3}
Output : {}
Error : {}
Progress : {}
Verbose : {}
Debug : {}
Warning : {}
StateChanged :
C:\PS> $results = $j | Receive-Job
Description
These commands run a background job on two remote computers. Because the Invoke-Command command uses the AsJob para
meter, the commands run on the remote computers, but the job actually resides on the local computer and the results
are transmitted to the local computer.
The first command uses the New-PSSession cmdlet to create sessions on the Server01 and Server02 remote computers.
The second command uses the Invoke-Command cmdlet to run a background job in each of the sessions. The command uses
the AsJob parameter to run the command as a background job. This command returns a job object that contains two ch
ild job objects, one for each of the jobs run on the two remote computers.
The third command uses a Get-Job command to save the job object in the $j variable.
The fourth command uses a pipeline operator (|) to send the value of the $j variable to the Format-List cmdlet, whi
ch displays all properties of the job object in a list.
The fifth command gets the results of the jobs. It pipes the job object in $j to the Receive-Job cmdlet and stores
the results in the $results variable.
-------------------------- EXAMPLE 9 --------------------------
C:\PS>$MWFO-LOg = Microsoft-Windows-Forwarding/Operational
C:\PS> invoke-command -computername server01 -scriptblock {param($log, $num) get-eventlog -logname $log -newest $nu
m} -ArgumentList $MWFO-log, 10
Description
This example shows how to include the values of local variables in a command run on a remote computer.
The first command saves the name of the Microsoft-Windows-Forwarding/Operational event log in the $MWFO-Log variabl
e.
The second command uses the Invoke-Command cmdlet to run a Get-EventLog command on the Server01 remote computer tha
t gets the 10 newest events from the Microsoft-Windows-Forwarding/Operational event log on Server01.
This command uses the "param" keyword to create two variables, $log and $num, that are used as placeholders in the
Get-EventLog command. These placeholders have arbitrary names that do not need to match the names of the local vari
ables that supply their values.
The values of the ArgumentList parameter demonstrate the two different ways to specify values in the argument list.
The value of the $log placeholder is the $MFWO-Log variable, which is defined in the first command. The value of t
he $num variable is 10.
Before the command is sent to the remote computer, the variables are replaced with the specified values.
-------------------------- EXAMPLE 10 --------------------------
C:\PS>invoke-command -computername S1, S2 -scriptblock {get-process powershell}
PSComputerName Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
S1 575 15 45100 40988 200 4.68 1392 powershell
S2 777 14 35100 30988 150 3.68 67 powershell
C:\PS> invoke-command -computername S1, S2 -scriptblock {get-process powershell} -HideComputerName
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
575 15 45100 40988 200 4.68 1392 powershell
777 14 35100 30988 150 3.68 67 powershell
Description
This example shows the effect of using the HideComputerName parameter of Invoke-Command.
The first two commands use the Invoke-Command cmdlet to run a Get-Process command for the PowerShell process. The o
utput of the first command includes the PsComputerName property, which contains the name of the computer on which t
he command ran. The output of the second command, which uses the HideComputerName parameter, does not include the P
sComputerName column.
Using the HideComputerName parameter does not change the object. You can still use the Format cmdlets to display th
e PsComputerName property of any of the affected objects.
-------------------------- EXAMPLE 11 --------------------------
C:\PS>invoke-command -comp (get-content servers.txt) -filepath c:\scripts\sample.ps1 -argumentlist Process, Service
Description
This example uses the Invoke-Command cmdlet to run the Sample.ps1 script on all of the computers listed in the Serv
ers.txt file. The command uses the FilePath parameter to specify the script file. This command allows you to run th
e script on the remote computers, even if the script file is not accessible to the remote computers.
When you submit the command, the content of the Sample.ps1 file is copied into a script block and the script block
is run on each of the remote computers. This procedure is equivalent to using the ScriptBlock parameter to submit t
he contents of the script.
-------------------------- EXAMPLE 12 --------------------------
C:\PS>$LiveCred = Get-Credential
C:\PS> Invoke-Command -ConfigurationName Microsoft.Exchange `
-ConnectionUri https://ps.exchangelabs.com/powershell `
-Credential $LiveCred -Authentication Basic `
-scriptblock {Invoke-Command {Set-Mailbox dan -DisplayName "Dan Park"}
Description
This example shows how to run a command on a remote computer that is identified by a URI (Internet address). This p
articular example runs a Set-Mailbox command on a remote Exchange server. The backtick (`) in the command is the Wi
ndows PowerShell continuation character.
The first command uses the Get-Credential cmdlet to store Windows Live ID credentials in the $LiveCred variab the c
redentials dialog box appears, enter Windows Live ID credentials.
The second command uses the Invoke-Command cmdlet to run a Set-Mailbox command. The command uses the ConfigurationN
ame parameter to specify that the command should run in a session that uses the Microsoft.Exchange session configur
ation. The ConnectionURI parameter specifies the URL of the Exchange server endpoint.
The credential parameter specifies tle. Whenhe Windows Live credentials stored in the $LiveCred variable. The Authe
nticationMechanism parameter specifies the use of basic authentication. The ScriptBlock parameter specifies a scrip
t block that contains the command.
-------------------------- EXAMPLE 13 --------------------------
C:\PS>$max = New-PSSessionOption -MaximumRedirection 1
C:\PS> Invoke-Command -ConnectionUri https://ps.exchangelabs.com/powershell `
-scriptblock {Invoke-Command {Get-Mailbox dan} `
-AllowRedirection -SessionOption $max
Description
This command shows how to use the AllowRedirection and SessionOption parameters to manage URI redirection in a remo
te command.
The first command uses the New-PSSessionOption cmdlet to create a PSSessionOpption object that it saves in the $max
variable. The command uses the MaximumRedirection parameter to set the MaximumConnectionRedirectionCount property
of the PSSessionOption object to 1.
The second command uses the Invoke-Command cmdlet to run a Get-Mailbox command on a remote server running Microsoft
Exchange Server. The command uses the AllowRedirection parameter to provide explicit permission to redirect the co
nnection to an alternate endpoint. It also uses the SessionOption parameter to specify the session object in the $m
ax variable.
As a result, if the remote computer specified by the ConnectionURI parameter returns a redirection message, Windows
PowerShell will redirect the connection, but if the new destination returns another redirection message, the redir
ection count value of 1 is exceeded, and Invoke-Command returns a non-terminating error.
-------------------------- EXAMPLE 14 --------------------------
C:\PS>$so = New-PSSessionOption -SkipCACheck
PS C:\> invoke-command $s { get-hotfix } -SessionOption $so -credential server01\user01
Description
This example shows how to create and use a SessionOption parameter.
The first command uses the New-PSSessionOption cmdlet to create a session option. It saves the resulting SessionOpt
ion object in the $so parameter.
The second command uses the Invoke-Command cmdlet to run a Get-Hotfix command remotely. The value of the SessionOpt
ion parameter is the SessionOption object in the $so variable.
-------------------------- EXAMPLE 15 --------------------------
C:\PS>enable-wsmanCredSSP -delegate server02
C:\PS> connect-wsman Server02
C:\PS> set-item wsman:\server02*\service\auth\credSSP -value $true
C:\PS> $s = new-pssession server02
C:\PS> invoke-command -session $s -script {get-item \\Net03\Scripts\LogFiles.ps1} -authentication credssp -credenti
al domain01\admin01
Description
This example shows how to access a network share from within a remote session.
The command requires that CredSSP delegation be enabled in the client settings on the local computer and in the ser
vice settings on the remote computer. To run the commands in this example, you must be a member of the Administrato
rs group on the local computer and the remote computer.
The first command uses the Enable-WSManCredSSP cmdlet to enable CredSSP delegation from the Server01 local computer
to the Server02 remote computer. This configures the CredSSP client setting on the local computer.
The second command uses the Connect-WSman cmdlet to connect to the Server02 computer. This action adds a node for t
he Server02 computer to the WSMan: drive on the local computer, allowing you to view and change the WS-Management s
ettings on the Server02 computer.
The third command uses the Set-Item cmdlet to change the value of the CredSSP item in the Service node of the Serve
r02 computer to True. This action enables CredSSP in the service settings on the remote computer.
The fourth command uses the New-PSSession cmdlet to create a PSSession on the Server02 computer. It saves the PSSes
sion in the $s variable.
The fifth command uses the Invoke-Command cmdlet to run a Get-Item command in the session in $s that gets a script
from the Net03\Scripts network share. The command uses the Credential parameter and it uses the Authentication para
meter with a value of CredSSP.
I suggest spending som etime learning the basics. It will save you a lot of frustration in the future.
¯\_(ツ)_/¯

Run vbs script from maxl shell

Similar Messages

Maybe you are looking for