@wirestyle22 said in Quick List of Useful Powershell Commands: @IRJ said in Quick List of Useful Powershell Commands: @wirestyle22 said in Quick List of Useful Powershell Commands: @IRJ Every day is like 12 hours of work in an 8 hour day and that's when I don't have random things thrown at me. I am working on the weekend but it's mostly in Linux. May need to make time You could probably feel comfortable with it in a week if you used it for everything. It is quite amazing how much you can feel lost with something one day and the next day you 100% get it. This happens alot and learning isn't always linear. There is generally a break through period. Yeah I just don't have the time. Everything has to be fixed immediately here. There is no room for it unfortunately. I'm going to go through the book @Dashrender and I both purchased called Learn Powershell in a Month of Lunches You learn stuff one bite at a time. My PowerShell chops are much better after a year at my current gig. And they improved doing one task at a time. Like that cmdlet I posted for finding user names. I did that enough to where I started to understand exactly what I'm telling the cmdlet to do, which leads to learning other cmdlets and such quicker.

NVM. Decided to work randomly.

@manxam so much longer, though. I had checked that out, but find the other to be better. However if you are writing a script to fill out a form, I can see this being handier.

A simple scheduled task to run a simple PoSh script would be easiest IMO.

@Romo said in Deploy Active Directory via PowerShell: Great Job @EddieJennings !!, Really liked the flow and tempo of the video Thanks

Topic has been forked, please keep discussions of OS comparisons to a different thread.

@Obsolesce said in PowerShell: Running the Get-Command command in a remote session reported the following error: @scottalanmiller said in PowerShell: Running the Get-Command command in a remote session reported the following error: @JasGot said in PowerShell: Running the Get-Command command in a remote session reported the following error: and lastly, is WinRM running? or need to be restarted? Was running. But restarted just in case, but no change. Is it just one PC it's not working on? Does it work on others? Only one to run it on. I'll have to find another machine to test against. It exists only for that machine.

^^^ It's always hilarious when a scumbag scammer thinks their input is valuable.

@Obsolesce Haven't tried it by running it directly as SYSTEM, it has been run as a user and checked to be run with the highest privileges. As it was when it was working before.

@wrx7m said in PowerShell - Off-boarding Script: @dafyre said in PowerShell - Off-boarding Script: @wrx7m said in PowerShell - Off-boarding Script: @dafyre I think I found where you got it - https://www.powershelladmin.com/wiki/Powershell_prompt_for_password_convert_securestring_to_plain_text Anyway, I am not sure where, in my script, I should place that function. You'd put the actual function at the top of your script, and then just $myPassword=convertFrom-SecureToPlain -securepassword $MySecurePassword Wherever you need the password in plain text form. Thanks. It mostly works. The only problem is that it isn't actually using the password I specify at the top. It is somehow generating its own and then writing it at the end. I put in write-host "Plain Text Says: $plainText" and it shows the password that I typed in for the secure variable at the beginning, followed by the one that it generated. Plain Text Says: $#@%4#@177 Jof91348 Works fine for me here.... Check and make sure you don't have an extra write-host or anything somewhere.

@Kelly said in Use Powershell to audit Windows service accounts: Unless you're wanting to use Powershell for a learning experience you might look at something like this: http://www.cjwdev.com/Software/ServiceCredMan/Info.html. If you still want to use the Powershell route this might be a good way to check the success of your script. That looks like it will do exactly what we want... thanks for the link.

Not yet.

@IRJ said in Free equivalent of Hyena: https://gallery.technet.microsoft.com/office/Active-Directory-Audit-7754a877 That looks pretty cool!

Long file names can be a serious pain... for copy and backup reasons. I recall a NTG client that used a long name for the directories,.. and it made updating nearly impossible Should follow the KISS method... Directory names don't need to be 120 characters long,.. and four deep.

@Pete-S It was on linux - ProFTPD

@JaredBusch : Awesome! Glad to hear it worked for you...

Troy Hunt uses it for the "I Have been PWned" https://www.troyhunt.com/serverless-to-the-max-doing-big-things-for-small-dollars-with-cloudflare-workers-and-azure-functions/

@NerdyDad said in Changing NICs in virtual servers: Here is the actual code in a more searchable context, sterilized for general use. Very useful! Thanks!

@wrx7m said in PowerShell - Create New AD User Using Prompts and Variables: If I get rid of the attempt to combine the 2 existing variables into a 3rd, I get this error. New-ADUser : A positional parameter cannot be found that accepts argument '+'. At \\FP02\it\Scripts\AD\AD-InitialUserCreationVariables.ps1:5 char:1 + New-ADUser -Name "$GivenName $Surname" ` + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-ADUser], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ActiveDirectory.Management.Commands.NewADUser Like this I think: New-ADUser -Name "$($GivenName) $($Surname)"` From: https://blogs.technet.microsoft.com/stefan_stranger/2013/09/25/powershell-sub-expressions/

They aren't in the ML community but special shoutout to Ariel Sanchez and Joe Houghes for this help. Somebody needs to get them into ML. https://twitter.com/TheRealNerdyDad/status/1049365117140447238

Turns out that it needed the -Credential flag, which Microsoft doesn't document as a requirement. This worked find... Add-Computer -DomainName "mydomain" -Credential mydomain\myusername

The specific package adobereader is a horrible example though. Because until this month, you installed adobereader-update which also installed adobereader first as part of the package. But now, suddenly, adobereader is all that is needed. adobereader history. adobereader-update history.

The batch file I have for one client is this: powershell Rename-Computer -NewName "COMPUTER_NAME" -DomainCredential DOMAIN\ADMINUser -Restart Where COMPUTER_NAME to not exceed the 15 character limit ETA: I should add that this batch script start with installing Chocolatey package management tools, then the default applications,

Since I was working with only ONE user this is what I needed to change it to, else was getting Parameter set cannot be resolved Import-module ActiveDirectory Get-ADUser -Filter {Name -eq "SomeUser"} -SearchBase "OU=Users,OU=OUGroup,DC=DOMAINname,DC=com" | Set-ADUser –scriptPath “\\SERVERNAME\netlogon\2018ADUC-script.txt” But it worked!

This would work on prem exchange. Probably works with a tweak for o365. Get-mailbox | get-inboxrule | remove-inboxrule

@penguinwrangler Good work! I admit I would have been to lazy to go through all that. I would just have written a program to deal with it straight up instead instead of trying to use nix commands and scripting. Anything to avoid "escape hell" as I like to call it.