Howdy, I am trying a new script that is hopefully easier than the last I tried. I have a server that performs actions to create, modify, and disable user accounts. I have a command that retrieves the list of users I need to report on and now I am not sure how to get to the next steps of creating this...
Does anyone know what the difference between these 2 commands are in terms of what they do considering both add windows features? The "AS" is what I can't find online details on. Add-WindowsFeature as-net-framework The standard seems to be: Add-WindowsFeature Net-Framework
Thanks, I looked at the results of Get-WindowsFeature as-net-framework and compared that to the Get-WindowsFeature NET-Framework-Core and the only output is the "name" and that just shows the 1st as being As-Net-Framework and the other is the Net-Framework-Core, but I don't see any difference...
Hi Don/Jeff, I'm pretty confident I've come across such a script in the not so distant past but I can't for the life of me find it now - when I need it! From memory this was a simple function to wrap/bind parameters to the SFTSequencer command line interface, the real difference/advantage...
I'm using the following code format below: $tobj = New-Object PSObject $tobj | Add-Member -Name "Server" -Value $Server -MemberType NoteProperty $tobj | Add-Member -Name "Scenario" -Value $Arraypwshell.scenario -MemberType NoteProperty $tobj | Add-Member -Name "Result"...
Good Morning, I've come across a strange error with the import-pssession cmdlet, and wanted to run it by the experts. I'm using it in a larger account creation script the import the exchange cmdlets from an exchange server to create a mailbox. In testing it all in the shell the below commands...
Filed under: Parameter, #errorlevel, Powershell, power shell, powershell Script, parametervalidation, import-pssession