From IT Skills
Jump to: navigation, search

Why Powershell is bad for installators[edit | edit source]

1. There are different wikipedia:Windows_PowerShell#Versions:

  • PowerShell 2.0 is integrated with Windows 7 and Windows Server 2008 R2
  • PowerShell 3.0 is integrated with Windows 8 and with Windows Server 2012
  • PowerShell 4.0 is integrated with Windows 8.1 and with Windows Server 2012 R2

Therefore installators should support old 2.0 version by limiting itself.

2. Powershell has modules like MSBuild that require configuration. Innovative programmer will be tempted to use third-party modules.

This means that installators will become too complicated.

3. There is security configuration for Powershell on a server.

This means that system administrator may put security restrictions that unexpectedly will stop installators.

commands[edit | edit source]

cd "C:\program files (x86)\cruisecontrol.net\server"

  • most cpu usage

Get-Counter '\Process(*)\% Processor Time' | Select-Object -ExpandProperty countersamples | Select-Object -Property instancename,cookedvalue| Sort-Object -Property cookedvalue -Descending| Select-Object -First 10| ft -AutoSize

  • most memory usage

get-wmiobject WIN32_PROCESS | Sort-Object -Property ws -Descending|select -first 5|Select processname, @{Name="Mem Usage(MB)";Expression={[math]::round($_.ws / 1mb)}},@{Name="ProcessID";Expression={[String]$_.ProcessID}},@{Name="UserID";Expression={$_.getowner().user}}