787
Microsoft is blocking Windows Customization Tools
(www.neowin.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Apr 2024
787 points (96.3% liked)
Technology
55610 readers
3751 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Maybe they are pushing back, which is why Control Panel still exists?
Meanwhile the new settings panel is telling me my network is private while control panel and network share settings tell me it's domain authenticated.
...while you're sitting in an internet café
It would be funny if true.
Sadly the reality is me calling with a client because this one single PC refuses to apply the damn GPOs... :(
Every day I'm thankful for having found a job where in such a case I can just send out a pre-imaged replacement pc from the pile and have them send the old one back.
I would like to. Sadly there are programs on it that can be reinstalled and configured by the respeonsible 3rd party but are still annoying.
The best: No other pc has trouble applying the damn gpo.
Even the DNS resolutiom seems to work on this shit thing... :|
I'd do a
gpupdate /forceon the client and look at the event viewer afterwards. If that doesn't turn up anything helpful, reinstalling is the most economical option.I have tried to narrow down the cause of the issue. Since I wasn't successful I ultimately escalated the ticket to my colleague and communicated to the client that if they can't narrow it down either, we will ultimately have to do that.
Not a pretty way to resolve the issue but sometimes it is like it is :/
My ultimate goal with every ticket is to not just close the problem but to resolve the root cause for the long term. But that (sadly) clashes with the amount of resources a client is willing to spent.
Solve the issue within 5min that arises every 10 days or so or solve the issue with 2 hours spent on troubleshooting and eliminating the issue