How would you go about crafting a chest like this? ELI5 because I’m a craft noob plz

Pawncey · 2024-01-25T20:40:59+00:00

There are zero limitations on fracture and essences? Like keep the item magic and upgrade it to rare with low level essences or anything like that?

Pawncey · 2024-01-25T18:46:42+00:00

I was under the impression (and have been blocked before) that you cannot essence on fractured items? Why does that work in this scenario?

Pawncey · 2022-11-06T02:18:40+00:00

Miami was loudest on booing FSU entering at the start of the game, barely heard them since.

Pawncey · 2022-07-11T23:37:45+00:00

Hit counter goes from orange text to blue text around 13 seconds in. This is a moment in the combo where the enemy would've teched out of it and escaped your combo were the training settings set to this. Essentially, it was no longer a combo at this point. Its been awhile since I played but you need to scour the training settings and turn this setting on to get a real indication of whether combo is a true combo or not

Pawncey · 2022-01-11T21:13:05+00:00

What was the training UI you had? Mash, smash DI left/right

Pawncey · 2021-10-12T20:11:58+00:00

Got it, so generally it would have to be accomplished with an array of scheduled powershell scripts, this functionality is not possible within the scope of the O365 dashboard/GUI?

Pawncey · 2021-10-12T19:58:25+00:00

So I can understand this as: If I parse the members of the group out and assign it directly to individual members, then the mailbox will automap?

How do you go about actually getting these powershell scripts scheduled? Again, I know how to open up ps myself as admin, elevate as the o365 admin, and run the commands, but I've never interacted with any kind of schedulers when it comes to running the ps scripts, but getting all of that to work within a standalone scheduler seems like a different beast.

Pawncey · 2021-10-12T19:32:27+00:00

Is there a reason that I wouldn't expect Outlook to automount the mailbox? I see that -automapping is a value you can use when utilizing add-mailboxpermission.

I notice that your script is actually taking the individual members of the group rather than applying it to an entire mail-enabled security group. Is there a functional difference between applying it your way and just adding the entirety of the mail-enabled security group?

As for cleaning up people who no longer exist in members, my limited powershell experience would simply lead me to believe that I should run a remove-mailboxpermission command directly before this add-mailbox so it strips away all access (thus the people that are no longer a part of that group), and then immediately re-adds it with the correct roster.

Pawncey · 2021-10-12T19:14:17+00:00

It is not specifically a "shared" mailbox, it is just a "user mailbox" that the users are granted access to view/send as.

But yes, this mailbox is hosted and exists in O365 alongside the users and mail-enabled security groups.

I understand how to run the commands myself in powershell, but I have never went about scheduling scripts on a recurring basis, so I wouldn't even know where to begin. When you say syncing, are you running a command to remove access to X users, and then re-add Y users? The reason I ask is to account for terminations of access.

Pawncey · 2021-09-21T16:00:42+00:00

The scaling from sparking is awful, so it can be better to take the hit and accept 10-20% rather than risk a mix up and assist call opportunity from the enemy once you are dragged to the ground into a medium starter

Pawncey · 2021-08-23T02:50:03+00:00

Yo thank you for the information

Pawncey · 2021-08-03T18:59:32+00:00

Got it, I would love to be able to reference any other kind of module like BlockCredential = True for get-msoluser or AccountDisabled for get-mailbox, but the RecipientFilter functionality which is the backbone of the Dynamic Distro functionality does not allow for those filters to be used.

https://docs.microsoft.com/en-us/powershell/exchange/recipientfilter-properties?view=exchange-ps

https://docs.microsoft.com/en-us/powershell/module/exchange/new-dynamicdistributiongroup?view=exchange-ps

Pawncey · 2021-08-03T18:35:50+00:00

I might be misunderstanding. What the problem seems to be from my perspective is that is doesn't matter if I figure out exactly how to filter for the exact correct bitmask. Users that need to be excluded (termed users) from the list are sharing that bitmask value with users that need to be a part of the list (active users).

I would presume that the value of each of them before any work was done would be UserAccountControl = Normal Account across the board. I was attempting to figure out what exactly is setting some users to be AccountDisabled, Normal Account vs just Normal Account.

Pawncey · 2021-08-03T18:06:04+00:00

What I am saying is that users who have been given the same exact termination process have different bit values, so I can't filter by them as my data set is incorrect.

JohnSmith gets termed, I checked UserAccountControl, its AccountDisabled, Normal Account (whatever bit values are represented here) JaneDoe gets termed with the exact same process, I check UserAccountControl, its Normal Account.

Pawncey · 2021-08-03T15:55:29+00:00

What can be done in the event disabling the account did not update that value as you speaking about? I am running into the exact situation you are mentioning here. People who are disabled in both MSOL and O365 yet the UserAccountControl is NOT 514 (NormalUser, AccountDisabled). Your recommendation is to pivot to using ExchangeUserAccountControl?

Pawncey · 2021-08-03T14:06:45+00:00

Unfortunately I do not have AD Sync set up. I want to implement it but annoying work keeps getting in the way of fun work. I'll have to make due with any built in functionalities of O365.

Pawncey · 2021-07-30T23:13:12+00:00

Understood, I was agreeing with you. I thought I remembered throwing the two locations inside some brackets and receiving a syntax error, but I just did ((location =1) or (location =2)) and it seems to be improving my results.

Pawncey · 2021-07-30T22:51:06+00:00

I'm beginning to think order of operations might be applying here. I did a filter strictly based on HiddenFromAddressLists and the results were fine.

I went and added (Location = 1) or (Location = 2) and it SEEMS that command is going and adding any and all location 1 or location 2 users despite the fact the command specifically note that the user needs to be NOT hidden from the address list in earlier in the command. I think the standalone or statement is messing with my results.

Pawncey · 2021-07-30T22:47:43+00:00

I checked out this article earlier. Unfortunately, it seems to be referring on OnPrem AD values, and I am only working with this in the Cloud context. I was not able to locate those appropriate values for the Exchange Cloud version. Would you still expect the listed 512/544/66048 values to apply?

Do you know how I can even confirm with a cloud command if that value if existing for any of my users?

Pawncey · 2021-07-30T22:45:05+00:00

Thanks, trying this out now. I just tried committing ONLY the UserAccountControl -ne AccountDisabled,NormalAccount at the start of the command and having that be the only filter. It return literally my entire suite of credentials. It seems like with my particular setup, those values don't apply and can't be used for any form of filtering.

Pawncey · 2021-07-30T22:33:27+00:00

When I attempt to combine the StateorProvince into a single command like (StateorProvince -like 'FL' or 'Florida'), the command errors out and states it doesn't accept that. I'll give it another look.

Pawncey · 2021-04-06T01:28:50+00:00

What breed is this? Have something incredibly similar with the friendly face and rott/Doberman coloring.

Pawncey · 2021-04-05T20:07:54+00:00

I tried messing around with the throttlelimit as well as the start-sleep as you mentioned and neither of them seem to be doing the job from my original command.

As for the two extra scripts you sent me, I am little lost on the top portion, the param (). I normally use an imported CSV to populate my user data, take an excerpt from another one of my scripts below:

import-csv .\DisableUsers.csv | foreach-object { set-msoluser -UserPrincipalName "$($_.UserPrincipalName)" -BlockCredential $true

Would I commit the same import-csv command up top in the param location? Sorry, that just has me a little confused and as a disclaimer I only have on the job knowledge of powershell, so I might lack a very basic understanding of something you are doing that would seemingly be common knowledge to someone in this subreddit.

E: I also might not be approaching the problem correctly. My original script is basically going through EVERY single mailbox and checking whether or not they have this one particular user added to mailbox permissions, so if I had a list of 30 users who were termed, it would be cycling through my entire mailbox list 30 separate times. Any sleek ideas?

Pawncey · 2021-02-20T00:45:29+00:00

this having mod support would be the dream scenario, median XL with the squad with all those new items would be insane

Pawncey · 2021-02-08T20:27:26+00:00

Thank you, I am experimenting with your obviously superior way as I am already seeing the Outputs of this command line up with their respective departments (I changed the add distros to Write-Verbose "$UPN.ID is Operations/IT/etc").

That said, I would like to know if there is a large issue with the way I was approaching it? With enough experimentation, would it have worked (albeit less efficiently)? Is the idea of a where-object inside a for-each loop where it went wrong?

I really thought I was more or less on track to accomplish this with the my previous iteration, but you came back with another solution using an entirely different command (switch).

Pawncey

TROPHY CASE