Help Needed: Major Screw-Up with Windows Update on My Servers

0
2
Asked By TechWhiz147 On

Hey everyone, I'm in a bit of a jam and could use some advice. I tried to disable Windows Update on all my Windows servers because the UI was just showing a blank screen that closed right away. In my attempt to fix it, I ran a second, overly aggressive PowerShell script. Now, after rebooting, I've got some serious issues. The local Group Policies seem to be broken, and users can't log in to Terminal Services like before. I know the changes I made were drastic, and I don't have any recent backups to restore from. Is there any way to fix these local Group Policy issues and get TS users' logins working again without a complete system restore? Any help would be greatly appreciated!

4 Answers

Answered By CautiousCoder99 On

Wow, that's a tough situation. First off, you really shouldn't run scripts in production without testing them on a few low-impact servers first. It's painful, but without recent backups, rolling back these changes is going to be tricky. You might be able to manually restore the registry keys if you can compare them to a working system, but it's going to be a lengthy process. Good luck!

ServerSavvy22 -

Definitely a painful lesson learned! Just make sure this doesn’t happen again in the future.

Answered By MentalHealthSupport On

Just a thought - you might have catastrophic changes, but take a deep breath. Nobody's going to die from this, though you might face consequences. Remember, everyone has messed up at some point. Focus on what steps you can take now, like looking for snapshots or restore points. You’ll get through this; it's part of learning.

CautiousCoder99 -

Thanks for the reminder, I really needed that!

Answered By RealisticAdmin On

Honestly, it sounds like you've wiped out a lot of your local policy settings. You should escalate this to someone who can possibly restore from backups. If there are any VM snapshots or restore points available, those might be your best shot.

TechWhiz147 -

Huge mistake, I know! I'm really kicking myself for it.

Answered By DebuggingGuru On

That second script really messed things up. Instead of resetting those properties to default, it looks like it removed them. If you can access a working machine, exporting the necessary keys there and importing them might help. But prep yourself, it's going to be a tough fix.

ServerSavvy22 -

Honestly, I'm thinking of rebuilding everything from scratch with the correct policies in place.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.