Wsus 3.0 sp1 uninstall
Tuesday, September 29, PM. Hi, I want to see if the information that Lawrence provided was helpful. Please keep us posted on your progress and let us know if you have any additional questions or concerns.
We are looking forward to your response. Wednesday, October 7, AM. Sadly my description wasn't clear enough. I tried Example 1 but i could not reinstall the role. However further restores are no longer an option as the server is also running WDS and its live. When i followed the other suggestions on removing the role none of them worked.
I now have the WSUS role still installed but i am unable to remove it. I have been experiencing the same problem uninstalling and reinstalling wsus. To give a short description, i am trying to uninstall wsus on sbs r2, but I get a message that it is not there.
I try to install and get a message saying that it is already installed. I tried your suggestions with the windows cleanup utility and it found no instances of wsus. There were also no entries in the registry. There is a wsus administrator account in AD, but the properties show that it was either incompletely installed or has had part of it deleted.
Is there any other way to completely remove only the wsus installation so that I can get it installed correctly? Any help would be greatly appreciated, as this is driving me up the wall. I have copies of log files and the wsus administrator account properties if you would like to see it.
Thanks in advance. I restarted the server, everything came up except SBS monitoring, just had to rerun the configuration and that's working. And, WSUS of course not working. I have not tried to do anything else. Below is what appear when I go to server management, Update Services.
My inclination was to try reinstalling 3. I have not tried to reinstall R2 components. No, I didn't backup the 3. A dministrat ion, or one of its dependencies, was not found. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System. Source Error: An unhandled exception was generated during the execution of the current web request.
Information regarding the origin and location of the exception can be identified using the exception stack trace below. Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft. Administra tion' could not be loaded. Recreated them, install failed. Apparently the fix is to flatten and rebuild the server, which I don't really want to do, because it's got other stuff installed on it, and configuration was a pain. It's a standalone server, not part of a domain.
There's no DC, read-only or otherwise, and no disk compression. I full agree about the nuisance, had to manually fix such configurations already dozens of times in our environment. The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums.
Windows Server Application Compatibility and Certification. Sign in to vote.
0コメント