McGruber
asked on
TS Powershell stopped working
Running this powershell script via Task Scheduler:
mport-module psterminalservices
$body = ""
$servers = get-tsservers
foreach ($server in $servers)
{
$sessionCount = 0
$sessions = get-tssession -computername $server.ServerName
foreach($session in $sessions)
{
if($session.UserName -ne "")
{
$sessionCount++
}
}
$a = @{Expression = {$_.SessionId}; Label = "Session "; Align="Left"}, `
@{Expression = {$_.ConnectionState}; Label = "State "; Align="Left"}, `
@{Expression = {$_.UserName}; Label = "User "}, `
@{Expression = {$_.DomainName}; Label = "Domain "}, `
@{Expression = {$_.ClientIPAddress}; Label = "IP "}, `
@{Expression = {$_.ClientName}; Label = "Machine "}, `
@{Expression = {($_.CurrentTime - $_.ConnectTime).Hours.ToSt
@{Expression = {$_.IdleTime.Hours.ToStrin
$body += "=========================
$body += ("Windows Terminal Server: " + $server.ServerName.tostrin
$body += "=========================
$body += $sessions | format-table $a -auto | out-string -width 1000
$body += "`n`n`n"
}
$emailFrom = "administrator@domain.com"
$emailTo = "it@domain.com"
$subject = "Terminal Server Users"
$smtpServer = "mail.domain.local"
$smtp = new-object Net.Mail.SmtpClient($smtpS
$smtp.Send($emailFrom, $emailTo, $subject, $body)
How can I debug to see where it is failing? Renamed a server over the weekend - suspect it must be that. What needs to run on the ts servers for the script to pick it up?
mport-module psterminalservices
$body = ""
$servers = get-tsservers
foreach ($server in $servers)
{
$sessionCount = 0
$sessions = get-tssession -computername $server.ServerName
foreach($session in $sessions)
{
if($session.UserName -ne "")
{
$sessionCount++
}
}
$a = @{Expression = {$_.SessionId}; Label = "Session "; Align="Left"}, `
@{Expression = {$_.ConnectionState}; Label = "State "; Align="Left"}, `
@{Expression = {$_.UserName}; Label = "User "}, `
@{Expression = {$_.DomainName}; Label = "Domain "}, `
@{Expression = {$_.ClientIPAddress}; Label = "IP "}, `
@{Expression = {$_.ClientName}; Label = "Machine "}, `
@{Expression = {($_.CurrentTime - $_.ConnectTime).Hours.ToSt
@{Expression = {$_.IdleTime.Hours.ToStrin
$body += "=========================
$body += ("Windows Terminal Server: " + $server.ServerName.tostrin
$body += "=========================
$body += $sessions | format-table $a -auto | out-string -width 1000
$body += "`n`n`n"
}
$emailFrom = "administrator@domain.com"
$emailTo = "it@domain.com"
$subject = "Terminal Server Users"
$smtpServer = "mail.domain.local"
$smtp = new-object Net.Mail.SmtpClient($smtpS
$smtp.Send($emailFrom, $emailTo, $subject, $body)
How can I debug to see where it is failing? Renamed a server over the weekend - suspect it must be that. What needs to run on the ts servers for the script to pick it up?
ASKER
I get a 0 x1 error in task manager. The powershell script runs every two hours and is supposed to email my group with the tsusers on each terminal server. I do not see an error - that is why I inquired about a debugging tool or mechanism to find the error.
I suppose your scheduled task runs the powershell command with a parameter of the file containing the script. The problem with this is that there actually is no way to capture the output (e.g. error messages) you would get from an interactive session in the scenario. The problem is well documented here.
If you read that article, at the end the author recommends you set up your scheduled task to call a good old command (.CMD) file, and in that command file use redirection (>filename.log) to send the powershell output.
To summarize.
- your scheduled task should execute CMD with parameters "-C c:\scripts\call-ps-script.
- call-ps-script.cmd should containt a command something like
"powershell -c c:\scripts\ps-script.ps1 >ps-script.log"
Or, just open an interactive powershell session and run the script interactively to see any error messages.
If you read that article, at the end the author recommends you set up your scheduled task to call a good old command (.CMD) file, and in that command file use redirection (>filename.log) to send the powershell output.
To summarize.
- your scheduled task should execute CMD with parameters "-C c:\scripts\call-ps-script.
- call-ps-script.cmd should containt a command something like
"powershell -c c:\scripts\ps-script.ps1 >ps-script.log"
Or, just open an interactive powershell session and run the script interactively to see any error messages.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I resolved it myself.
Besides that, what error are you getting with it at the moment? normally the error you get in PowerShell will help you identify where it's falling over.