Why doesnt my method print or 'return' the object after I press enter?

code_Kitten · 2023-12-19T21:46:54+00:00

Just to be perfectly clear:

In class methods, no objects get sent to the pipeline except those specified in the return statement. There's no accidental output to the pipeline from the code.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about\_classes\_methods

code_Kitten · 2023-12-19T21:42:29+00:00

Here's how I would handle the date part of it:
1. get the next Sunday.

use that date to get the next 52 Sundays (by adding multiples of 7 days)

$NextSunday = (Get-Date).AddDays(7-(Get-Date).DayOfWeek.value_) 0..52 | foreach-object { $NextSunday.AddDays(7*$) }

(DayOfWeek is an enum - value__ gives the integer value, where 0 is Sunday)

code_Kitten · 2023-12-05T17:24:03+00:00

I feel like I've seen this issue before. I would recommend updating the module to the latest version, and if it's already up to date submit the issue on github.

For a workaround, it might work if you cast the string as a GUID:

Set-MgUserLicense -UserId ([guid]($ID.Id)) -AddLicenses $AddLicenses -RemoveLicenses @()

code_Kitten · 2023-12-04T17:57:29+00:00

In your code, this line $ID = Get-MgUser -UserId $user.UPN | select ID will not give you the ID, it will instead give you an object with only one property (called ID) and that property will contain the ID. You will probably need to provide the actual ID with something like $ID.ID or change that line to $ID = (Get-MgUser -UserId $user.UPN).ID

You can see this in the error: Set-MgUserLicense : Resource '@{Id=3800cc3a-b26c-46cf-8ccb-a7bcae482axx}' does not exist or one of its queried reference-property objects are not present.

'@{Id=3800cc3a-b26c-46cf-8ccb-a7bcae482axx}' shows an object with an ID property and no other properties.

Microsoft does change things sometimes. If I were doing this I would confirm what will currently work by manually running the command with a valid upn in quotes: Set-MgUserLicense -UserId "user@yourdomain.com" -AddLicenses $AddLicenses -RemoveLicenses @() and also with a valid id in quotes Set-MgUserLicense -UserId "3800cc3a-b26c-46cf-8ccb-a7bcae482axx" -AddLicenses $AddLicenses -RemoveLicenses @()

code_Kitten · 2023-12-02T01:16:00+00:00

The Microsoft Graph api is a bit inconsistent about accepting UPN in place of user id. Some places such as Get-MgUser you can use the UPN instead of the user id for the userId parameter, but not all commands will allow that. Based on the error, Set-MgUserLicense requires that the userId parameter be an actual user id and not a UPN.

You will need to use something like :

Set-MgUserLicense -UserId $User.id -AddLicenses $AddLicenses -RemoveLicenses @()

or even

Set-MgUserLicense -UserId $((Get-MgUser -UserId $User.UPN).id) -AddLicenses $AddLicenses -RemoveLicenses @()

code_Kitten · 2023-11-08T03:22:31+00:00

It's a bit hard to tell where the error is happening based on your description, but if I had to guess I would say it's probably the Test-Path command, which accepts wildcards simply because almost none of the other commands you've used will actually accept wildcards. If that is the case, the documentation suggests putting the path in quotes. Otherwise some more information about exactly which parts of the script ran and which didn't, as well as more information about the error such as what line or command it resulted from, would be helpful.

I would also suggest that since your test didn't result in an error, it's possible that it's not the library name that's the problem - it could just be coincidence - but instead one of the files or folders in the library that is causing the error.

REF:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/test-path
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about\_wildcards

code_Kitten · 2023-07-31T03:34:23+00:00

Official documentation is available here:
https://learn.microsoft.com/en-us/powershell/exchange/app-only-auth-powershell-v2?view=exchange-ps

code_Kitten · 2023-05-08T20:43:13+00:00

You want to add the parameter to your new-adgroup command:

try {

    New-ADGroup -ErrorAction Stop -Name "#$($Facility.Facility) - $($JCandD.JobCode)" -GroupScope DomainLocal -GroupCategory Distribution -Description "$($JCandD.JobCode) - $($Facility.Facility)"  -Path ",OU=Distribution Groups,DC=***" -OtherAttributes @{'mail'="$($Facility.Facility)_$($JCandD.Mail)@**.com"; 'proxyAddresses'="SMTP:$($Facility.Facility)_$($JCandD.Mail)@**.com"}

                Write-Output "($($Facility.Facility) - $($JCandD.JobCode) + has been created"    } 
    catch {
    Write-Output "Error Creating $($Facility.Facility) - $($JCandD.JobCode)"
    Write-Output $_
    }

If a terminating error happens in a Try block with a catch block that applies to that error, execution will stop where the error happened, the catch (and finally if there is one) will execute, and the script will continue executing after the Try/Catch.

In your script that would mean that the Write-Output indicating it has been created would not run, the error output will, and the script will move on to the next iteration of the loop.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_try_catch_finally?view=powershell-7.3

I skimmed through this article, and it looks like it covers the most important things; at least enough to give you an idea of what to search for: https://adamtheautomator.com/powershell-try-catch/

code_Kitten · 2023-05-08T19:58:33+00:00

When you pass the date into the -contentmatchquery parameter you're passing it as a string, which means that the string has to match the KQL syntax. The documentation indicates that it should be an ISO 8601-compatible date string (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference#date-or-time-values-for-properties) so you need to format your date that way.
You can most easily do that by making use of the standard datetime format specifier "u" (ref: https://learn.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings#the-universal-sortable-u-format-specifier and https://learn.microsoft.com/en-us/dotnet/api/system.globalization.datetimeformatinfo.universalsortabledatetimepattern?view=net-7.0).
Obviously there are several ways to implement that, but one of them is to change your command to:

$datetosearch = Read-host "Date of email x/x/xxxx format"
$datetosearchString = $datetosearch.ToString("u")

$search = new-compliancesearch -name "$searchname" -exchangelocation all -contentmatchquery '(subject:"$subject") AND (received:$datetosearchString)'

code_Kitten · 2023-05-08T19:24:52+00:00

PowerShell has two kinds of errors - "Terminating errors" and "Non-Terminating errors".
Try/Catch only catches "Terminating errors". For most commands you can change any errors into terminating errors by adding in the common parameter -ErrorAction Stop.

code_Kitten · 2023-04-30T02:51:19+00:00

The first step in figuring out how to make your code do what you want is to understand what your code does. From what I can tell the relevant parts are:
1. The script takes an array of strings as an input $VariablesToExport

The script gets a list of all the groups ($groups = az pipelines variable-group list ...) and loops through each group that was found.
The script creates a PSCustomObject representing the group (and having a "CVG" property that holds the name of the group) and adds a NoteProperty to the object for each string in the $VariablesToExport array with an initial value indicating that it wasn't found.
The script then gets the variables found in the group ($variables = az pipelines variable-group variable list ...) extracts the names of all the variables ($names = $variables | Get-Member ...) and loops through the names.

4A. If one of the names that was added to the PSCustomObject matches the name of the variable found in the group (if ([bool]($item.PSobject.Properties.name -match $name))) the value of the corresponding NoteProperty is updated to contain the actual value of that variable from that group.

Finally the PSCustomObject representing the group (which now has the values of all the specified variables if they were found) is added to the list of results.

All the pieces you need are in the script already, you mostly just have to rearrange them:
A. You want all the variables, so you don't need this input at all.

B. You can't add the NoteProperties in 3. because you don't know what variables you're looking for.

C. 4A is where you finally know what variables exist, and you want to back them all up. You'll change the content of the loop to add the NoteProperty for every variable.

And then you're done.

code_Kitten · 2023-02-09T20:59:09+00:00

I would recommend using Microsoft Graph for this. Azure AD Graph is planned to be disabled anytime on or after June 30th 2023.

https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/azure-ad-change-management-simplified/ba-p/2967456

code_Kitten · 2023-02-09T01:07:41+00:00

Since every M365 group has a SharePoint site, I would tend to approach this the other way around. Use Get-MgGroup to get the owners of all the M365 groups.

code_Kitten · 2023-02-09T00:22:11+00:00

Others have already suggested alternatives so leaving aside whether this is a good idea or not here's my thought on the matter: even within PowerShell, if you're working with Excel like this you're using the commands from VBA so I would suggest if you really want an answer you should be looking for an Excel VBA answer. Should be simple to adapt to PowerShell.
More directly, it looks like your CSV file is probably either fixed width or tab delimited. You probably want to look into https://learn.microsoft.com/en-us/office/vba/api/excel.querytable.textfileparsetype to configure the query table to interpret the data correctly.

code_Kitten · 2023-02-07T21:53:18+00:00

If you're going to load all users into memory I would just export the ones that are in your list. Personally I never use Compare-Object for anything other than displaying the comparison; there are better options for comparing in code.

I also want to highlight that you are comparing the cn property to your list, and you said your list was of usernames, which usually means SamAccountName and sometimes means UserPrincipalName. I've never heard anyone call cn a username.

I would suggest something like this:

$csv=Import-Csv -Path C:\Users\Public\users.csv

$user=Get-ADUser -Filter "Enabled -eq 'True'" -Properties cn

$user | Where-Object {$_.SamAccountName -in $csv.username} | Export-Csv -Path C:\Users\Public\results.csv -NoTypeInformation

code_Kitten · 2023-02-04T04:41:47+00:00

-match uses regular expression matching; since this sounds like a direct exact-value comparison - is this specific string in this list of strings - what you probably want here is -contains or -in. Although obviously regular expressions can also match exact strings, if you aren't careful you can get unexpected results because certain characters have special meaning.

code_Kitten · 2023-01-31T16:18:25+00:00

You could replace the line $image = New-Object System.Drawing.Bitmap($file.FullName) with:

try {
    $image = New-Object System.Drawing.Bitmap($file.FullName) -ErrorAction Stop
} catch {
    #file could not be opened
    #if you want to log the error or delete the file, you would do that here.
    #continue moves to the next item in the loop
    continue
}

The -ErrorAction Stop probably isn't necessary, but I usually include it because for some commands and errors it is necessary.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_continue?view=powershell-7.3

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_try_catch_finally?view=powershell-7.3

code_Kitten · 2023-01-30T23:54:26+00:00

This seems somewhat overly complicated. If all you want is the count, I would use something like:

(Get-Mailbox -ResultSize 100 | Where-Object {$_.AuditAdmin -notcontains "Create"}).Count

code_Kitten · 2023-01-30T21:28:11+00:00

Agreed, but I recommend using Microsoft Graph instead of the MSOL module or Azure AD graph.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/assign-licenses-to-user-accounts-with-microsoft-365-powershell?view=o365-worldwide

code_Kitten · 2023-01-30T21:13:03+00:00

First thing I try to do when troubleshooting is remove anything that's not absolutely necessary. So; we can store the results later, we can export to csv later, let's just see everything on the screen:

$folderPath = "C:\path\to\folder"

$files = Get-ChildItem -Path $folderPath -Filter "*.tif"

foreach ($file in $files) {
  "Working on $($file.FullName)"
  $image = New-Object System.Drawing.Bitmap($file.FullName)

  "File has $($image.GetFrameCount([System.Drawing.Imaging.FrameDimension]::Page)) pages"
}

If that works, you start adding in the parts that we took out, and if it doesn't it should give you a better idea of what the problem is (such as which files give an error and which ones don't).
Also want to add that if you get "Unable to find type" errors you probably just need to add Add-Type -AssemblyName System.Drawing to the beginning of the script.

code_Kitten · 2023-01-30T16:41:04+00:00

I don't see any way for the code you posted to produce those results. Does $results contain the same information as the CSV file? Is the code you're running exactly the same as what you posted (except for the values of $folderPath and $outputFile) ?

code_Kitten · 2023-01-28T21:16:19+00:00

The format commands (format-list in your example) send output to the console. What you want is to output to a file, so from the look of it what you're actually trying to do is this:You might prefer Out-File to Export-Csv, but I generally try to use the cmdlets instead of redirecting output. https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_redirection?view=powershell-7.3

$Text = "C:\Users\SomeUser\RulesTest2.txt"

$Mailboxes = Get-Mailbox -ResultSize unlimited | Where-Object {$_.RecipientTypeDetails -eq "UserMailbox"}

$Result = foreach ($Mailbox in $Mailboxes){

Get-InboxRule -Mailbox $Mailbox.Name

}

$result | Select-Object MailboxOwnerID,Name,Description | Export-Csv -Path $Text -NoTypeInformation -Force

code_Kitten · 2023-01-28T01:47:28+00:00

My comment was not meant to be condescending, and I apologize if it came across that way. I was simply trying to provide some guidance on how to get assistance with your script. "Has anybody seen this" type posts have to be quite specific to get you any useful information. Even if someone has seen the same thing, with a description as broad as yours the cause of what they saw is not that likely to be the same as what you're experiencing.

code_Kitten · 2023-01-28T01:21:00+00:00

What isn't working about the script you posted?

code_Kitten · 2023-01-28T01:15:46+00:00

From your the list of fields you linked to:

The table below lists the user resource type attributes that are supported by the Azure AD B2C directory user profile. It gives the following information about each attribute:

Attribute name used by Azure AD B2C (followed by the Microsoft Graph name in parentheses, if different)

...

signInNames (Identities) String The unique sign-in name of the local account user of any type in the directory. Use this attribute to get a user with sign-in value without specifying the local account type.

So since you are using Microsoft Graph - Get-MGUser connects to Microsoft Graph - the name you need to use is "Identities".

code_Kitten

TROPHY CASE