Posts tagged "windows"
Create Windows user using SALTstack
The first thing i did using salt stack was creating a local windows user. Creating users on different OS builds are fully supported by using the built-in salt functions.
First create a mapping in your top.sls config which point to your Windows state directory.
Sample config in top.sls Defining 2 hostnames, one with a wildcard for matching a server group.
|
1 2 3 4 5 6 7 8 9 |
base: '*': - generic 'TST02 or TST0*2': - tst.win_generic #This match the following hostnames: TST02 and TST012,TST022,TST032 etc. #The SLS file in folder tst. |
Content of the win_generic.sls
|
1 2 3 4 5 6 7 8 9 10 11 |
tst_user: user.present: - name: TSTUser - groups: - Administrators - Users - fullname: TST Comod - password: {{ pillar['passwords']['TSTUser'] }} - enforce_password: False #More parameters: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.user.html |
In this example I use pillar for securing passwords. If you don’t use pillar, just use a plain text password in the password field.
Ill write a blog article how to use Pillar in SALT.
Install git with PowerShell on Windows
With the following PowerShell function you can download and install git using PowerShell.
It downloads the latest “stable” git release to the given temp directory and installs it with default parameters.
Another and more easy way is using the package manager Chocolatey.
The Script:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 |
function CheckAndInstallGit { Param( [string]$Repo, [string]$TempDir ) try { git } Catch { Write-host "Git not available on your device. " -ForegroundColor Yellow Write-host ": Downloading and installing git..." -ForegroundColor Yellow $InstallGit = $True } If($InstallGit){ $releases = "https://api.github.com/repos/$repo/git/releases" [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $Response = (Invoke-WebRequest -Uri $releases -UseBasicParsing | ConvertFrom-Json) $DownloadUrl = $Response.assets | where{$_.name -match "-64-bit.exe" -and $_.name -notmatch "rc"} | sort created_at -Descending | select -First 1 If(!(test-path $TempDir)) { New-Item -ItemType Directory -Force -Path $TempDir | out-null } # --- Download the file to the current location Write-host "Trying to download $($repo) on your Device.." -ForegroundColor Yellow Try{ $OutputPath = "$TempDir\$($DownloadUrl.name)" Invoke-RestMethod -Method Get -Uri $DownloadUrl.browser_download_url -OutFile $OutputPath -ErrorAction Stop } Catch { Write-host $_.exception.message Write-host "Failed to install Git on your laptop, download and install GIT Manually." -ForegroundColor Red Write-host "Download Location: https://gitforwindows.org/" -ForegroundColor Yellow } Write-host "Trying to install GIT on your Device.." -ForegroundColor Yellow Try{ $arguments = "/SILENT" Start-Process $OutputPath $arguments -Wait -ErrorAction Stop } Catch { Write-host $_.exception.message Write-host "Failed to install Git on your laptop, download and install GIT Manually." -ForegroundColor Red Write-host "Download Location: https://gitforwindows.org/" -ForegroundColor Yellow } } Else { Write-host "Git is already installed, no action needed." -ForegroundColor Green } } CheckAndInstallGit -Repo "git-for-windows" -TempDir "c:\temp" |
How to check the SFP state on a Physical Windows Host
In the past we have had an issue with a bad batch of SFP’s in our Windows servers. The issue occurs randomly after a couple months in production.
The answer from HP about the bad SFP’s:
“The problem is due to the Manufacturing anomaly which has been corrected now .This issue causes early life degradation of Transmit (Tx) Power, causing the affected device to fail between 6-months and 1-year from first operation, depending on operational use. Affected SFP+ Short Wave Transceivers that begin to fail, first exhibit symptoms typical to Tx power degradation followed within weeks by symptoms typical to Tx power failure.”
They could not provide us more information about the affected serial / product numbers. Only way to check those SFPs is reading the operational status with a small tool.
Tool name: qaucli.exe
Which can downloaded from: Click here
Run the .exe to get the tool installed.
|
1 2 3 4 5 6 7 |
cd "C:\Program Files\QLogic Corporation\QConvergeConsoleCLI" #To get the hba_instance_number, run: qaucli -pr fc -g #Then run this command for the status report qaucli -pr fc -dm <hba_instance_number> gen |
Check the Status. If the status not match “normal”, replace the SFP.
I automated the checks with a little not so fancy (I know) script.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 |
$cred = get-credential $vmhosts = get-scvmhost $finalreport = @() foreach($ahost in $vmhosts){ $session = New-PSSession -ComputerName $ahost.name -Credential $cred -Verbose $data = invoke-command -Session $session -ScriptBlock { Start-Process -NoNewWindow -FilePath "C:\Program Files\QLogic Corporation\QConvergeConsoleCLI\qaucli.exe" -ArgumentList "-pr fc -g" -RedirectStandardOutput "c:\output.txt" Start-sleep 10 $a = get-content "c:\output.txt" $b = $a | where{$_ -match "Online"} $Data = @() $Data += $env:computername Foreach($c in $b){ $HBA = $c.split(" ")[11].trimend(")") Start-Process -NoNewWindow -FilePath "C:\Program Files\QLogic Corporation\QConvergeConsoleCLI\qaucli.exe" -ArgumentList "-pr fc -dm $HBA gen" -RedirectStandardOutput "c:\status.txt" start-sleep 5 $z = get-content c:\status.txt $e = $z | where{$_ -match "status"} $data += $e $data } } Remove-PSSession $session $Finalreport += $data } $finalreport |
NOTE: Only tested with QLOGIC adapters. Don’t know if this also work for the Emulex ones.
For Emulex refer this: For Emulex adapters use the Emulex® OneCommand® Manager Application to view the transceivers, their status and TX power level on the PortAttribute screen.
How to install terraform on Windows
- Download Terraform
- Unzip Terraform to c:\Terraform
- Add terraform to your environment variables:
|
1 |
set PATH=%PATH%;C:\terraform |
Test your installation typing terraform in CMD.
Your output should look like this:
Generate CPU Load with PowerShell
In some situations you need to stress your system a little (for example: to check if your monitoring is functioning properly.)
Installing some random .exe files from some anonymous websites is not always a good idea. So hereby a little script for blowing your CPU to 100%.
The script creates a nice calculation for all of your “Windows Logical Processors”
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
$NumberOfLogicalProcessors = Get-WmiObject win32_processor | Select-Object -ExpandProperty NumberOfLogicalProcessors ForEach ($core in 1..$NumberOfLogicalProcessors){ start-job -ScriptBlock{ $result = 1; foreach ($loopnumber in 1..2147483647){ $result=1; foreach ($loopnumber1 in 1..2147483647){ $result=1; foreach($number in 1..2147483647){ $result = $result * $number } } $result } } } Read-Host "Press any key to exit..." Stop-Job * |
Enable safe mode Windows 8 or 10
Last week I was working on a young defect SSD powered computer running on Windows 10. Hitting the F8 key for enable the save mode while booting was almost impossible. Don’t know if the key is disabled or Microsoft reduced the time periods for pressing F8 near 0 seconds.
Enable safe mode Windows 8 or 10 with MSCONFIG
Go to your command prompt (CMD) or search for the executable called “run” and type MSCONFIG and hit enter. Switch to the boot tab and select the button “safe boot”, then reboot.
Enable F8 key Windows 8 or 10
To enable the F8 key. Run the command prompt (CMD) as administrator. Search for RUN or directly CMD -> right click -> Run as administrator. And copy the following lines into the prompt and hit enter. Reboot needed:
|
1 |
bcdedit /set {default} bootmenupolicy legacy |
Change back to the default settings:
|
1 |
bcdedit /set {default} bootmenupolicy standard |
Recent Comments