kcnychief

So I had a test environment with one server and four clients, that had WSUS installed, configured and working perfectly. Because of lack of hard drive space on the server, which admittedly was an oversight when I began the test scenario, I decided to go away from WSUS. (Before I go any further, please no suggestions about adding hard drive space, modifying settings, etc. This is the path I want to go.)

Problem is, now I can't seem to get to the Windows Update website - http://windowsupdate.microsoft.com

I know that when WSUS is configured, you can block all that through GPO, configure the Intranet update, etc. I have turned off the intranet configuration, re-configured all WU settings in both Computer and User configurations, forced an update and let the time interval pass for the GPO updates, and still can't get there. I know that best practice is to install a seperate Group Policy with a seperate administrative template for WSUS, but by the looks of my setup I didn't go that route.

I'm kinda stumped, can't figure out what else I have to reset or adjust, anyone have a suggestion for what I can try?

Thanks in advance

---

Mastershakes

Have you looked at their cleanup script?

Worked great on our servers....

http://www.microsoft.com/windowsserv...s/default.mspx

(near the bottom of page)

I know you don't want to go this way, and you've likely already used it... just wanted to be sure.

shakes.

kcnychief

That script is to be run on machines that are upgrading from the RC to the release version. I have un-installed WSUS completely, and need to troubleshoot why clients aren't able to access http://windowsupdate.microsoft.com

I only skimmed it, but I might look over that page a bit more later, thanks.

---

madmatt

Did you run gpresults to make sure they are running the latest GPO?

---

kcnychief

Yup, and gpupdate /force, and rebooted, and let the time interval pass for an automatic refresh.

There actually is only one Group Policy defined for this area. That is why I know that I didn't create a seperate one with it's own Administrative Template. Perhaps I should have followed the "best practice" and done it that way. Maybe I will try creating a new policy altogether, and implementing that....

Kinda stumping me atm, but I'll figure it out. Thank god it's only a test environment for my own personal pleasure

---

madmatt

Did you set all the WU policies back to "Not Configured"?

---

kcnychief

I set a few of them to not configured, and then did a refresh. After that didn't seem to help I put them back to enabled/disabled where appropriate. I have always wondered how exactly a not configured works. Does that just not change the setting, or does it revert to some type of default?

---

madmatt

When set to "Not Configured" it uses the default.

---

kcnychief

I'll check that out, thx.

---

kcnychief

Doesn't seem to be working after a refresh and verification of the latest policy running. I'll be patient and let things apply for a bit. Here is the error I get when trying:

I need to spend more time on google about this too...

---

madmatt

Oh. That policy is in a different place.

User Config
Admin Templates
Windows Components
Windows Update
...

---

kcnychief

Yeah, I set both user and computer back to not configured, still not working yet.

---

madmatt

Set that last one to disabled then and make sure the clients are still set to update.

---

kcnychief

I got this to work.

I ran a gpresult, and notice an old policy which I thought I had disabled/deleted was still being applied. After modifying the settings on that GPO, all set.

Now onto the next issue with NAV, which shouldn't be as hard

---