This will output a log file that gives information regarding the status of each computers updates. ![]() # Opens Ninite Pro and runs silent installers to update machinesĬmd /c C:\%Some file location%\NiniteOne.exe /updateonly /remote file:"$NiniteFile" /disableshortcuts /disableautoupdate /silent "$NiniteLog" $NiniteLog = "C:\%Some file location%\log.csv" $NiniteFile = "C:\%Some file location%\Computers.txt" # Run script to query AD OU=WSUS_Workstations for machinesĬ:\%Some file location%\Get_AD_Computer_Name.ps1 I then created another script, that calls the previous script. Apparently Ninite Pro cannot use the Unicode format and has to use ASCII. By default PowerShell’s Out-File command will send it in Unicode. The one thing that caught me by surprise (and took a couple hours to figure out) is the -Encoding parameter. Out-File -FilePath C:\%Some file location%\Output.txt -InputObject $ADAccount -Encoding ascii Also, you should come on over to r/sysadmin. Check out the package database at (formerly AppDeploy). $ADAccount = Get-ADComputer -Filter * -SearchBase "OU=Computers,DC=domain,DC=local" | Format-Table Name -HideTableHeaders What programs are you trying to deploy with ninite Pretty much everything has silent installation options that you can script, whether the developers know about them or not. ![]() Using a pretty simple PowerShell script I managed to do this. Coming from a small environment, it’s pretty easy add them, but in a larger organization, you’d have to automate the process. I went in and looked at my list of computers and realized I hadn’t been keeping it up to date when we deploy new computers. Today I figured out that my Ninite Pro was not installing updates on all computers automatically.
0 Comments
Leave a Reply. |