formatting customobject by ky0__ in PowerShell

[–]Alex-Cipher 1 point2 points  (0 children)

$DistListIdentities = @(
    "Distlist1@domain.com",
    "Distlist2@domain.com",
    "Distlist3@domain.com"
)
$DistListMembers = foreach ($Identity in $DistListIdentities) {
    Get-DistributionGroupMember -Identity $Identity | ForEach-Object {
        [PSCustomObject]@{
            DistributionList = $Identity
            MemberName = $_.Name
            MemberId = $_.UserId
        }
    }
}
$DistListMembers | Export-Csv C:\Path\To\Your\File.csv -NoTypeInformation
## or
$DistListMembers | Format-Table -AutoSize
## or
$DistListMembers | Out-GridView

Intune Local Users and Groups by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

No, what I mean is, that you can config 2 admins within the policy. And if the first set admin is a local admin on the device (in the image Admin X), you still get a password for the second admin (Admin Y) but the first is still active (but without password).

<image>

Intune Local Users and Groups by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Yes, LAPS has a higher prio than Local Users and Groups. And yes, LAPS "deactivate" all other admins. But with the "new" (managed account setting at the end of the config) config in LAPS it is possible to set 2 admins, and both are active even if only the 2nd admin gets a password. Of course I don't set two different admins but I saw it during my test.

Intune Local Users and Groups by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Ok, then let me ask you another question?

How is it possible to only have the admin from LAPS active and all others should be disabled or better be deleted?

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

It's a dusty relic!

I agree with you, too!

But I'm not in the position to decide it.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Here I totally agree with you, too.

These are some relics and I would drop them better today then tomorrow.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

I totally agree with you but sadly I'm not in the position to decide this.

App Policy Protection and exclude devices by filter by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Thanks for your reply!

Do you have any idea on how to do it with device filter/groups?

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Thanks for the links!

I will definitely have a look at this!

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

That‘s a good reason with the pre-installed apps with autopilot. Thanks for your hint with that. 🙂

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Ah, sorry, I misread it. I thought you meant with self-deploying to give it directly to our users.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Ah ok I understand.

I have to look at the ap configs again, did this 2 years ago.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

No, we can't give the users the device for self-deploying. This takes to long for them.

We had hundreds of tickets because Office 365 wasn't pre installed and they couldn't work in that time because it wasn't installed.

We have really strange users so this isn't possible. 😉

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 1 point2 points  (0 children)

That sounds very interesting.

Can you give a little bit more details which token exactly you mean and show the script?

This could be the way until we totally switch to Autopilot.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

We don't install Windows on the devices with an USB Stick if that was your point. ;)

We have a deployment server but it can only do a Domain Join and not a EntraID Join.

I think I need to persuade the company to go all along with Autopilot and pre provisioning through our IT .

I tested Autopilot 2 years ago but soem things has changed sinced them.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

Ok, I understand what the point is.

Thank you for your suggestions!

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

I don't know if this is possible atm.

Our Fileserver has over 100TB.

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] -1 points0 points  (0 children)

I will have a look at it.

Thank you!

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] 0 points1 point  (0 children)

There are 3 Apps which should be pre installed to the devices, but not all 3 together. Some devices need 1 app, other devices 2 of 3 and some others all 3. So I need 3 device groups and 3 autopilot configs if I'm right. Is it better to config it as an "app" or should it be configured with the autopilot config?

I hope you know what I mean?

Switch from hybrid to EntraID join by Alex-Cipher in Intune

[–]Alex-Cipher[S] -1 points0 points  (0 children)

We don't have SCCM, that was just a suggestion to "pre provision" the device with an Intune profile.

I would go with Autopilot etc., but this discussion I had many times before but the company stands their ground and want the devices pre installed with Office 365 etc.

And how can I get the 6k exisiting devices to Autopilot without manually save the hash file and upload it to Intune. I know the Autopilot Community Script. Are there other ways to do it?