I'm running a PowerShell script to build hash tables for quick lookups of users' email addresses, including their proxyAddresses. I've noticed that accessing the proxyAddresses attribute slows down the script significantly. Here's how my function works: I retrieve users using Get-ADUser, specifically looking for email addresses, and then I plan to filter, remove duplicates, and hash those proxyAddresses for easy access. However, it seems every time I access proxyAddresses, it's like it's running a query to fetch data, which I confirmed when disconnecting my device from the network. After some tests, I still see delays when accessing these fields, regardless of how I reference them. Is there a more efficient way to handle this object?
3 Answers
Have you tried using Get-Recipient? If you use it with the -Identity parameter, it retrieves the SMTP address without caring if it's primary or secondary. It could really speed things up if you're doing reverse lookups!
Instead of running Get-ADUser and then repeating it, try something like just selecting the first 100 users directly. You could do this: `$userList | Select -First 100 -Property SamAccountName, ProxyAddresses`. This might cut down the redundant calls and speed things up!
Good point! I’ll try minimizing my calls to Get-ADUser. I was just using a simplified example in my code snippet, but I see how that would help.
You might want to consider using a directory searcher instead of Get-ADUser. It pulls data directly from AD using .NET classes, and I’ve seen scripts go from 30 seconds down to under 5 seconds with this method. A bit tricky at first, but it’s worth it!
That sounds like an awesome solution! I hadn’t looked into it yet, but I’ll definitely give it a shot.
I see your point! But for reverse lookups, I need to build a user email hash. It helps with cases where aliases don’t match up. Plus, with AD modules, it’s easier for sharing since Exchange modules can be cumbersome. Thanks for the suggestion though!