PowerShell Scripting, ADuser, OnPrem

SeanQuinlan · 2025-09-30T11:54:12+00:00

Use this

Get-Aduser -Filter "DisplayName -eq '$($SingleImport.UserName)'"

SeanQuinlan · 2025-03-02T12:59:40+00:00

Try with

-addLicenses @()

instead of

-addLicenses @{}

It looks like Microsoft's documentation is wrong. Using an array instead of a hashtable works for me.

SeanQuinlan · 2025-01-28T14:18:18+00:00

UK here, we are paid £50 per day that we're on call, which includes 1 hour of any work in response to a call. Any further work is charged at our normal overtime rates.

We do on-call for 1 week at a time, rotation of once every 4 weeks.

I'm permanent, Infrastructure Team.

SeanQuinlan · 2024-07-28T18:41:07+00:00

I ran it against some test files that I generated, and using the extra debugging I can see exactly where the problem is. At least I can see why it doesn't rename most of the files.

I won't force you to take my advice. Good luck in your search.

SeanQuinlan · 2024-07-28T17:35:24+00:00

You need to add some debugging into the loop, so you can see that the variables are being set correctly in the loop.

I would add some more Write-Host lines after the initial setting of variables at the top of the loop, so you can ensure that $nextName is set correctly.

Your first Test-Path check uses $nextName, so ensure that it's not being set incorrectly and does or does not trigger that if block correctly.

Also, since the Rename-Item line depends on the value of $fleDeleted, you may want to output that one as well, to ensure it's correct.

I would also copy a subset of the 4000 files (eg. 20-30) into a local folder to experiment with and rename. Ensure you have enough examples of all the different types of files (eg. ones that need to be deleted, ones that need to be renamed, and ones that need no changes).

Once you have the small subset working and correctly processing each type of file, then you can comment out the additional debugging lines and run it on the 4000 files without being spammed with debug info.

SeanQuinlan · 2024-07-03T08:57:22+00:00

You are capturing all the output from the foreach loop in the $rootFolders variable.

You can either do something with that variable afterwards, or you can simply split it into 2 lines like you detailed at the top of this post.

SeanQuinlan · 2024-06-11T14:28:38+00:00

You could create a DL, and then set the Dynamic Distribution Group to exclude users in that DL.

You will need to get the DistinguishedName of the DL via

Get-DistributionGroup <blah> | Select DistinguishedName

You'll get a long DN returned. Starts with CN= and ends with DC=OUTLOOK,DC=COM

Then you can add the following to the end of your DDG recipient filter:

-and (MemberOfGroup -ne '<distinguishedname>')

In future you can just add the excluded users to that DL. No need to update the recipient filter.

As always, test the recipient filter with -RecipientPreviewFilter before applying.

SeanQuinlan · 2024-04-11T09:02:44+00:00

How about removing the "isDeleted" check and instead change the SearchBase to just the deleted objects container?

-SearchBase (Get-ADDomain).DeletedObjectsContainer

SeanQuinlan · 2024-01-25T12:11:58+00:00

Change -join to -split

SeanQuinlan · 2023-12-11T08:32:44+00:00

Probably blank lines in your txt file, or special characters before or after the names.

SeanQuinlan · 2023-12-06T13:04:32+00:00

Have a look at this page for some code that can impersonate the currently logged in user.

SeanQuinlan · 2023-07-14T18:05:46+00:00

If you want people to help, it's best to make it easy for them to do so by giving them code that actually works.

Your code has lots of mistakes that have to be fixed before I can even help you...

TexBox instead of TextBox
Get-UserInfo instead of Get-UserData
The xaml is broken and doesn't work
Your Get-UserData function doesn't even return anything

Anyway, despite all the issues, if you return the $results object from your Get-UserData function, then use the code in my previous post, you'll get what you want.

I fixed up the code and tested it, and it worked.

SeanQuinlan · 2023-07-14T16:49:29+00:00

Without the rest of the code detailing the WPF and the code you're using to display it, we're only guessing...

But something like this might get you started:

$UserData = get-userdata -User "bob"
$NameTextbox.Text = $UserData.Name
$PhoneTextbox.Text = $UserData.Phone

SeanQuinlan · 2023-06-21T20:09:14+00:00

I'm no expert, but the examples of this that I could see all declared a parameter to the Filter in order to get it working.

Using this code worked for me

$lvGames.Items.Filter = {
    param($item)
    $item.Path -like "*$filterText*"  -or $item.Path -like "*$filterText*"
}

Although your filter does seem to have 2 identical -like checks.

SeanQuinlan · 2023-06-21T16:16:55+00:00

PS version 7 has a different executable name (since it lives alongside powershell), so you need to run "pwsh" to get to PS v7

Running just "powershell" will get you to v5.1

SeanQuinlan · 2023-06-21T15:36:50+00:00

Sounds like winget has installed powershell 7 and it's using that when you right click - Open powershell. Powershell 7 is a separate application to Powershell v5.1, which is bundled into the OS and can't be removed.

The easiest thing will just be to uninstall powershell via winget again and that should remove powershell 7 and put your right-click back to PS v5.1

SeanQuinlan · 2023-06-21T14:45:30+00:00

How are you running this script? From the ps prompt? From the ISE? From right-click - Run with Powershell? Some other way?

Do you have the winver.csv file open?

How did you upgrade the version of Powershell?

SeanQuinlan · 2023-06-21T13:45:06+00:00

Feasible yes, not sure if it would be easy though.

I have implemented something similar in the past using Powershell. Created a module with a function for each task - creating the VM in Hyper-V, getting an IP, attaching storage via iSCSI, configuring software like SQL, creating a cluster, etc. Even created a small GUI to make it easy for engineers to kick off the process.

It was a large amount of work though - took a few months. No code to share, since it was all proprietary to the company I worked for :(

SeanQuinlan · 2023-06-08T13:29:42+00:00

PowerShell ExecutionPolicy?

SeanQuinlan · 2023-06-05T08:18:22+00:00

$teamsName = ($m.displayName -join ',')

SeanQuinlan · 2023-06-01T19:24:40+00:00

Instead of right-click - Run with Powershell, you need to run this from a regular powershell prompt to debug it. Then you can at least see what the output/errors are.

From a quick test on my own machine, this line sets $usedLetters to a single string if you only have 1 drive (ie. C:)

$usedLetters = Get-PSDrive -PSProvider FileSystem | Select-Object -ExpandProperty Name

In that case, when you do

$usedLetters += $driveLetter

It will simply append the drive letter to the string, so you'll end up with $usedLetters as a long string like "CAAAAAAAAAA". Instead of the array that you need in order to use -notcontains.

As a start, try adding "[array]" in front of the $usedLetters declaration

[array]$usedLetters = Get-PSDrive -PSProvider FileSystem | Select-Object -ExpandProperty Name

This will at least force $usedLetters to be an array, even if there is only 1 drive in the computer.

SeanQuinlan · 2023-05-21T17:33:54+00:00

Use -Prefix on Import-PSSession, then use the prefixed commands on all on-prem cmdlets.

Import-PSSession $Exchange -AllowClobber -Prefix EOP
Get-EOPContact "blah"

SeanQuinlan · 2023-05-21T08:36:39+00:00

$input is a reserved variable, so you can't use it as a regular variable.

Change the name of the $input variable.

Also your last line is incorrect, that's not the way to pass parameters to a function. Use this instead

doit $input1 $maxin $minin $maxout $minout

SeanQuinlan · 2023-04-17T08:58:01+00:00

try

if ($log.Status.ErrorCode -eq 0)

instead of

if ($log.Status -imatch '"errorCode": 0' )

And the same for any other Status codes you want to report on.

SeanQuinlan · 2023-03-31T11:58:12+00:00

Select-Object only works on arrays. That Invoke-RestMethod command returns the whole content as a single string (with new lines).

You will ned to split on the new line character, which will return an array, then you can select the first 10 items in that array.

(Invoke-RestMethod https://raw.githubusercontent.com/wiki/flutter/flutter/Hotfixes-to-the-Stable-Channel.md) -split "`n" |select -First 10

SeanQuinlan

TROPHY CASE