Search results for '(app:forums OR groupid:24)' matching tag 'PS Remoting'

Run cmd with arguments not work

Jirka — Fri, 22 Mar 2013 05:00:00 GMT

"c:\jenkins\nightbuild\Setup-Application Name-8.12-#28.exe" /c=installCmd.xml
- this is working script started automatic instalacion.
Im not able start this command line using PowerShell.

I tryed many ways but nothing is working like from cmd.

& "c:\jenkins\nightbuild\Setup-Application Name-8.12-#28.exe" /c=installCmd.xml

Its not working even on local server.

http://social.technet.microsoft.com/wiki/contents/articles/7703.powershell-running-executables.aspx
- I tryed many ways from this article too.

I have bitten off more than I can chew and can't see the forest for the trees...HELP!!!

Oseis — Tue, 21 Aug 2012 05:00:00 GMT

I have written the following script but each fix I do breaks 2 other things. For instance I am loading variable data to an .xlsx and it errored that the object was not a string. So I added .ToString method and it now says my passed variable ($computer) loaded using the Get-Content cmdlet is null!

Prior to using .ToString it went had no issues with the variable.

I am frustrated, stuck and out of time. Please help!

Oh yeah and the excel formulation broke as well.

$computers = Get-Content -Path H:\Computer.txt
$Ping = Test-Connection -ComputerName $computer -Count 1 -ErrorAction SilentlyContinue
Foreach ($computer in $computers)
    {
        #Check if machine is online
        if ($Ping)
            {
                #begin Row count for Excel
                $Row=3
                #Start WinRM Services
                $service = Get-WmiObject -ComputerName $computer -Class Win32_Service -Filter "Name='WinRM'"
                $service
                $service.StartService()

                #If Online eq true Get Environment Variables
                $Build = Invoke-Command -ComputerName $computer -ScriptBlock {$env:bldver}
                $Domain = Invoke-Command -ComputerName $computer -ScriptBlock {$env:userdomain}
                $DNSDomain = Invoke-Command -ComputerName $computer -ScriptBlock {$env:userdnsdomain}
                $LogonServer = Invoke-Command -ComputerName $computer -ScriptBlock {$env:logonserver}
                $NLTest = Invoke-Command -ComputerName $computer -ScriptBlock {([System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()).FindDomainController()}
                $OnlineStatus = "Online"
                $OS = (Get-WmiObject Win32_OperatingSystem).Version
                $SID = Invoke-Command -ComputerName $computer -ScriptBlock {$env:username}
                $UAT = Invoke-Command -ComputerName $computer -ScriptBlock {$env:uatdata}


                #Determin if PC is logged onto Domain
                if ($Logonserver -eq $computer)
                    {
                        $Loggedin = "Locally"
                    }
                else
                    {
                        $Loggedin = "Domain"
                    }

                #Get IP and NIC Info
                $NICItems = gwmi -class "Win32_NetworkAdapterConfiguration" -name "root\CimV2" -comp $computer | Where-Object {$_.defaultIPGateway -ne $null}
                    ForEach ($NICItem in $NICItems)
                    {
                        $MAC = $NICItem.MacAddress | select-object -first 1
                        $IP = $NICItem.IpAddress | select-object -first 1
                        $Subnetmask = $NICItem.ipsubnet | select-object -first 1
                    }

                #Create Excel Spreadsheet
                $Excel = new-object -comobject Excel.Application
                $Workbooks = $Excel.Workbooks.Add()
                $Worksheets = $Workbooks.worksheets
                $Worksheet = $Worksheets.Item(1)
                $Worksheet.Name = “Clientside Commonality ”
                $Excel.Visible = $True
                $Cells = $Worksheet.Cells

                #Create Title and Column Headers
                $Cells.Item(1,1) = "Commonality Tracker"
                $Cells.Item(1,7) = Get-Date
                $Cells.Item(2,1) = "Computer Name"
                $Cells.Item(2,2) = "Online Status"
                $Cells.Item(2,3) = "Domain"
                $Cells.Item(2,4) = "DNSDomain"
                $Cells.Item(2,5) = "UAT"
                $Cells.Item(2,6) = "MAC Address"
                $Cells.Item(2,7) = "IP Address"
                $Cells.Item(2,8) = "Subnet Mask"
                $Cells.Item(2,9) = "Logged In User"
                $Cells.Item(2,10) = "Operating System"
                $Cells.Item(2,11) = "Build Version"
                $Cells.Item(2,12) = "Netsh results location"
                $Cells.Item(2,13) = "Authenticated"
                $Cells.Item(2,14) = "NLTest DC"

                #Format Cell Headers
                $Cells.Item(1,1).Font.Bold = $True
                $Cells.Item(1,1).Font.Size = 22
                $Cells.Item(1,7).Font.Bold = $True
                $Cells.Item(1,7).Font.Size = 20
                $range.ColumnWidth = 50
                $range.Font.Bold = $True
                $range.Font.Size = 14
                $range.HorizontalAlignment = 3
                $range = $excel.Range("A2",”L2")
                $range.ColumnWidth = 50
                $range.Font.Bold = $True
                $range.Font.Size = 14
                $range.HorizontalAlignment = 3

                #Begin populating Excel
                $Cells.Item($Row,1) = $computer.ToString()
                $Cells.Item($Row,2) = $OnlineStatus.ToString()
                $Cells.Item($Row,3) = $Domain.ToString()
                $Cells.Item($Row,4) = $DNSDomain.ToString()
                $Cells.Item($Row,5) = $UAT.ToString()
                $Cells.Item($Row,6) = $MAC.ToString()
                $Cells.Item($Row,7) = $IP.ToString()
                $Cells.Item($Row,8) = $Subnet.ToString()
                $Cells.Item($Row,9) = $User.ToString()
                $Cells.Item($Row,10) = $OS.ToString()
                $Cells.Item($Row,11) = $Build.ToString()
                $Cells.Item($Row,13) = $Loggedin.ToString()
                $Cells.Item($Row,14) = $NLTest.Name



                #Check OS version and Run boot trace if Windows 7
                $Acct = "System"
                $Netsh = Invoke-Command -ComputerName $computer -scriptblock {$Trace}
                $Reboot = Invoke-Command -ComputerName $computer -scriptblock {"Shutdown /r /c "+"This computerwill restart in 10 Minutes to capture essential data to troubleshoot your issues. Please save your work and pardon the interruption."+" /t:600"}
                $Schedule = Invoke-Command -ComputerName $computer -scriptblock {$Task}
                $Task = "schtasks.exe /create /s $computer /ru $Acct /tn $TaskName /tr $TaskRun /sc $Schedule /F"
                $TaskName = "Stop netsh"
                $TaskRun = "netsh trace stop"
                $Trace = "netsh trace start capture=yes persistent=yes report=yes tracefile=C:\bootcap.etl"



                If ($OS -eq "6.1.7601")
                    {
                        $OSType = "Windows 7"
                 #       $Netsh
                 #       $Schedule
                 #       $Cells.Item($Row,12) = "C:\bootcap.etl"
                 #       $reboot
                    }
                else
                    {
                        $OSType = "Windows XP"
                    }
                #Increment Row
                $Row += 1
            }
        else
            {
                $OnlineStatus = "Offline"
            }

        #Populate Excel for offline machines

        $Cells.Item($Row,1) = $computer
        $Cells.Item($Row,2) = $OnlineStatus

        #Increment Row
        $Row += 1



     }

#Stop WinRM Services
$service.StopService()

#Autosize Columns
$Worksheets.UsedRange.EntireColumn.AutoFit() |out-null

#Save your work
$Workbooks.SaveAs("H:\Troubleshooting.xlsx")
$Excel.quit()

#EOF

Re: Call Exchange shell/cmdlets from Quest Shell - Proper method?

virtuallynothere — Tue, 03 Jul 2012 05:00:00 GMT

Thanks, so the tools are installed on the system I need to run this script from, and I got this to work, so is this not recommended either?

c:\program files\Microsoft\Exchange\V14\bin\RemoteExchange.ps1 ; connect-ExchangeServer - Auto

Is that OK or do I need to do the Remote session noted in your reply above?

Re: Call Exchange shell/cmdlets from Quest Shell - Proper method?

virtuallynothere — Fri, 29 Jun 2012 05:00:00 GMT

I tried to do that, but when I run the get-pssnapin - registered the exchange tools don't come back as registered.

Then I've read it's not "supported" to add the snapin for the exchange tools in another shell aside from the exchange shell, so you should use a remote connection, and then I found another thread about using a command like the one below, but that fails as well as connect-exchangeserver is "unknown".

'C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1'; Connect-ExchangeServer <target server>"

Call Exchange shell/cmdlets from Quest Shell - Proper method?

virtuallynothere — Thu, 28 Jun 2012 05:00:00 GMT

Hello,
I now know the best methods of remoting thanks to Don & the folks here.

But I have to use the Quest shell as we utilize their Active Role solution and I need to write a script that runs when something is done to users accounts through that system.

I know how to set it up and what commands I need to run, I am not sure of how to call the Exchange shell which installed locally or connect to Exchange in order to run the commands I need.

Can anyone help me out?

Thanks!

Re: Remote Powershell - options to run commands?

virtuallynothere — Thu, 21 Jun 2012 05:00:00 GMT

Don,

So I've read a fair amount since this post and I bought your last book, but I'm looking at the new "lunches series", and I think I'm still a beginner, but do I need to know powershell 1 or 2 before ordering the powershell 3 book series?

I've read about 20 contradicting threads or articles on the right & wrong way to do remote powershell in terms of executing commands for Exchange Admin, AD Admin, or Microsoft OCS tasks, and using powershell remotely for anything.

Here's the latest article I read, so is it actually "wrong" to think that I could setup a system that has all the modules/snapins that I need, such as Exchange, AD, OCS, Quest, etc, then remote into that machine from my laptop, and perform whatever admin tasks or run scripts that I want to?

It seems like the "right" way is to do it as this article states, but I've read quite a bit about how people use "remote powershell" profiles, and at the very least it seems like there's no reason I couldn't run the powershell commands from my laptop if I have the AD tools, Exchange, and OCS tools installed locally. So essentially I'm confused, if you can help I would really appreciate it.

I couldn't get the training videos right now do to budget and work not covering them.

http://blogs.technet.com/b/heyscriptingguy/archive/2012/01/23/learn-how-to-use-powershell-to-run-exchange-server-commands-remotely.aspx

serilisation of objects in powershell

ash.cash — Sat, 02 Jun 2012 05:00:00 GMT

is there any preferred order of serialization of a custom .NET objects in powershell.does it follows any order in which the fields and properties of a class is serialized into xml format ?

Remote Powershell - options to run commands?

virtuallynothere — Thu, 24 May 2012 05:00:00 GMT

Hi - I realize thanks to Don that remote "profiles" aren't exactly possible right now in Powershell.

But if I want to remote into 1 system that has the tools I need, Exchange mgmt shell, AD shell, quest cmdlets, etc, how can I remote into that system, have a custom shell open so that I can see which modules/cmdlets are available, and then invoke commands from that remote system to other systems that may only have some of the items installed?

IE: I want to setup a central system so I remote into that, then I can do work with powershell for ad commands, exchange commands, etc and have the commands run against other servers where I have remote powershell enabled or even just do things like create mailboxes, get user info, etc without having all of the tools installed on my system?

remoting in powershell

ash.cash — Wed, 23 May 2012 05:00:00 GMT

is there any way of exposing the private data members of a .net object in power shell while transferring the object across the wire.if yes please provide some references for it.

Script/command - query sql server & configure firewall rules?

virtuallynothere — Wed, 25 Apr 2012 05:00:00 GMT

I am trying to find a way to use powershell to query a sql server and provide back the instance names with the port numbers used, then ideally get the port numbers and add them to specific rules I create for the Windows firewall.

Currently I use the netsh commands for the firewall config and go to the gui to locate the ports.