Maybe put all of the above into a separate script (even though the script already runs the snapin). Can I run a script within a script? For instance, something like this:Ĭ:\temp\RedistributeActiveDatabases.ps1 -DagName DAG1 –BalanceDbsByActivationPreference –confirm:$false Unfortunately it doesn't run correctly like the other script did. The thing is that there are so many switches to run this, and this script is so incredibly long, that the safest way to run it is to add the switches in the task where you can add the optional switches.
#MULTIEXTRACTOR CHANGE TEMP DIRECTORY FULL#
In the interest of full disclosure, I am trying to run the RedistributeActiveDatabases.ps1 script every weekend as the automated task. OK, I had to step away from this for a while, then I came back and tested it. Sure the non-intrusive stuff works correctly first before replacing my test script with that one. What I am trying to do is to make sure this runs OK, and then plug in the script that I want to run that is already an existing exchange script to relocate the active databases to their preferred server, but since that is rather intrusive, I want to make
#MULTIEXTRACTOR CHANGE TEMP DIRECTORY WINDOWS#
When looking at the transcript log (testscriptlog.txt) all it shows after the user/machine names, etc., is transcript started, output file is blah blah blah, then windows powershell transcript end and the end time. The task logs indicate it completes in about 6 seconds, but the task status says it is running until I manually kill it. And turning on the option to quit running after 1 day is not really desirable. I have tried exit and end on the end of the above, as well as leaving it as is to see if it will quit running the task, but it doesn't. Get-MailboxDatabase | Export-Csv c:\temp\testreport.csv -Force Start-transcript -path c:\temp\testscriptlog.txt -appendĪdd-PSSnapin .E2010 I did a test script where I put in the following: Even when I put a sleep switch in front of the cmdlet, it launches that also, then theĬmdlet, THEN the cmd prompt. It launches the shell just fine, it just doesn't wait until the command prompt in the shell is generated prior to running the cmdlet. That is why I am puzzled that it exhibits theīehaviour that it does. I also checked to make sure the permissions to run powershell weren't an issue. This will run fromĪ server that has the exchange tools installed, so the scripts will be there, the exchange plugin for powershell, etc. Actually, my task above does launch the exchange session. I think UAC may be the problem, but I don't think they will let me disable it (for security reasons). I already have "run with highest privileges" set. Server, and so far it looks like the task scheduler is not my friend. So how do YOU manage this issue? Ultimately I want this script to run un-monitored once a week on a separate To set it for the account to be logged in, and then I also had to be logged in with that account as well in order for the task to work. One of the other issues I encountered was that it wouldn't work at all (not even a simple task to launch a cmd prompt) if I set the settings to run whether the account was logged in or not. Is there a way I can just call that script from something I can tack onto the end of what you have above? All the documentation I found stated that you would ordinarily do a script but for really simple stuff you can just run theĬmdlet. Are you saying that I can just tack on the cmdlet at the end? Actually, for my end result I want to run an existing script that resides in the directory on the server where the exchange scripts reside with I tried extending the sleep command, but it made no difference. I tried putting in a sleepĬommand, but I just end up with a line with the sleep command, then the command for the script, then the prompt. Is the ems window launches and after it finishes connecting to an exchange server, but before it launches the prompt, it runs the script, so it runs the script, then has the prompt on the following line, waiting for a command. When I added the -noexit switch to see why it wasn't working, I saw that what is happening 'C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1' Connect-ExchangeServerīefore the closing quote (right after -auto at the end), I put in a command to get information on the mailbox databases and then pipe them out to a csv file. I have been trying to get a basic task to work in task scheduler and I have submitted the -noexit switch for troubleshooting purposes.Ĭ:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -version 2.0 -noexit -command ".
0 kommentar(er)
