bschwarting
asked on
WSUS - Changed Port from 80 to 8080, now an error
I had WSUS running fine with the default configuration. I wanted to use the same server as a web server also, but couldn't on the default port of 80 since WSUS was using it. I changed WSUS to 8080 and it seems to be operating fine, all clients are reporting in. I also updated our group policy to point to 8080 as well.
Here is my only issue. When I go to the WSUS admin page, now on port 8080, I get the error below:
########################## #########
Check your server configuration
One or more Update Service components could not be contacted. Check your server status and ensure that the Windows Server Update Service is running. Non-running services: SelfUpdate
########################## #########
Any ideas?
Here is my only issue. When I go to the WSUS admin page, now on port 8080, I get the error below:
##########################
Check your server configuration
One or more Update Service components could not be contacted. Check your server status and ensure that the Windows Server Update Service is running. Non-running services: SelfUpdate
##########################
Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
that's pathetic if that's the case.
No, especially if it isn't through IIS.
I believe if it is IIS you can still have a SelfUpdate virtual directory on the default port 80 site though...but I'm not certain on that.
I've tried to do the same thing because I wanted to run ePolicy Orchestrator on the same box...didn't happen. In the end I went with virtualizing the 2 "servers" on the same hardware just because of this.
I believe if it is IIS you can still have a SelfUpdate virtual directory on the default port 80 site though...but I'm not certain on that.
I've tried to do the same thing because I wanted to run ePolicy Orchestrator on the same box...didn't happen. In the end I went with virtualizing the 2 "servers" on the same hardware just because of this.
ASKER
well, it's changed back to port 80. thanks for the info. off to install IIS on another server!
Roger that...thanks for the points.
ASKER