A friend sent me a screenshot of this post, and consequently YamlWav is now live on GitHub marketplace and PyPI. I hope it stops there.
ristophet
u/ristophet
Feed options
Hot
New
Top
View
Card
Compact
There are a few types of business that are exempt, but unless they are on that list they are likely breaking the law. Here's an interesting page on who is covered by the NLRB: https://www.nlrb.gov/about-nlrb/rights-we-protect/the-law/jurisdictional-standards
Yeahhh there hasn't been strong incentive for businesses / managers to know or share the information with employees. It seems like most people aren't aware. It will absolutely bite a business if they blatantly suppress protected communication and someone files a complaint.
Department of Labor link on making a complaint https://www.dol.gov/agencies/whd/contact/complaints
Also, in the United States, workers discussing wages is protected communication under The National Labor Relations Act.
Edit to add this link to the NLRB.gov page on the topic: https://www.nlrb.gov/about-nlrb/rights-we-protect/your-rights/your-rights-to-discuss-wages
Ok great. I'm stumped then as long as dev and test SCCM environments are completely, 100% separate. (Edit to add clarity: I mean dev test and prod have their own primary sites, there is no CAS, and they certainly don't trust each other in any way.) Now, if it turns out that dev, test, and prod are all inside a single shared SCCM environment with a single primary site and things are only broken out by SCCM permissions and network segmentation... Then I have seen this behavior before.
Example: Prod environment has all prod servers and workstations. "Air-gapped" network also exists and is managed (shudder) by the prod SCCM system. Separation is maintained by network segmentation, and SCCM permissions. There are two management points, one on each network. prod SCCM clients would routinely attempt to connect to the "air-gapped" network's MP, fail, and just give up. They would not try and connect to another MP. It is as if SCCM expects all healthy management points inside of a primary site to be accessible to all clients at all times.
This was years ago, and hopefully there are better controls to enable one to function in this multiple logical environments through network segmentation but really only one primary site kind of set up.
If this sounds like your stack, then you (they?) will have to find a way to ensure SCCM only offers the proper MP to the client or that the client only lets itself use the MP group policy has declared it can use. The other comment about AllowedMP gives me hope that you can solve this without getting caught in between the SCCM admins and the networking team.
