keyongtech


  keyongtech > windows.server.* > windows.server.update_services > 11/2007

 #1  
11-05-07, 07:21 PM
Rick
I got new server hardware to replace my existing WSUS server. Old server was
a domain controller plus our intranet box. I got the new hardware to split
things up. It will also be a domain controller along with a WSUS server

I set it up and followed a recommended method of being a replica to move the
updates and computers over to my new server. After everything appeared to be
moved it went back to sync from the internet

Anyway now my new WSUS server cannot be contacted when I try and connect via
the console.

I get the "server may be using another port" message. All I can get in my
console is my old server.

I have tried to uninstall the WSUS on the new server & try again from
scratch but it won't let me

Probably something simple but I am not seeing it

thanks
 #2  
11-06-07, 01:03 PM
Augusto Alvarez
Have you checked the event viewer on both the new and old server?

Do you have the DB on each server or on a separate server?

Cheers!
 #3  
11-07-07, 02:13 PM
Rick
It was a goof on my part, forgot to install something

I got the WSUS working partially. I have all my approvals & updates over but
I cannot seem to copy my computers over.

I was hoping that they would attach when scheduled for updates but they
haven't. My new server is using the same name & IP as my old server so I
figured this would work. The old server has been renamed and re-IP'ed

Even when I try the wuauclt.exe /detectnow from a workstation, they do not
connect.

Any ideas



"Augusto Alvarez" wrote:
[..]
 #4  
11-07-07, 02:51 PM
Winfried Sonntag [MVP]
Rick schrieb:

> Even when I try the wuauclt.exe /detectnow from a workstation, they do not
> connect.


Have a look in %windir%\WindowsUpdate.log at the client.

Winfried
 #5  
11-07-07, 04:46 PM
Rick
I see this error when I look at the log

SelfUpdate Failure Software Synchronization Windows Update Client failed to
detect with error 0x80244017.


"Winfried Sonntag [MVP]" wrote:
[..]
 #6  
11-07-07, 09:02 PM
Winfried Sonntag [MVP]
Rick schrieb:

> SelfUpdate Failure Software Synchronization Windows Update Client failed to
> detect with error 0x80244017.


http://support.microsoft.com/kb/896226/

Try this from a Client. Is a download coming?
http://YourWSUSServer/selfupdate/wuident.cab

Winfried
 #7  
11-08-07, 12:41 PM
Rick
I have over 500 computers & servers (2000,XP, server 2000 & 2003) that
connected to my old WSUS server with no problems, these will not connect into
my new server at all

We have the firewall turned off on each computer so that is not an issue. We
do not use a proxy server either. As far as I can tell everything is setup
the same

The computers do not show up at all in WSUS on the new server. I was able to
download the updates from the old server but my approvals & computers did not
come over when I initially sync the new with the old

Do I have to somehow have to import these somehow

Also that link to the cab file would not work



"Winfried Sonntag [MVP]" wrote:
[..]
 #8  
11-08-07, 01:52 PM
Winfried Sonntag [MVP]
Rick schrieb:

> Also that link to the cab file would not work


Which link to what cab file? Pls try:
http://YourWSUS:8530/selfupdate/wuident.cab and
http://YourWSUS/selfupdate/wuident.cab
Where is coming a download up? Is this the wsus entry in your policy?

Winfried
 #9  
11-08-07, 02:08 PM
Rick
sorry I was a little brain dead with the link, forgot to change the server
part of the link

this is what comes up


[SusClientUpdate]
ServerUrlEx="http://download.windowsupdate.com/v7/windowsupdate/a"
StructureKeyEx=/AU|ARCH|OS|LANG
StructureKeyEx2=/AU|ARCH|OS2|LANG
StructureKeyEx3=/WSUS3|ARCH|OS3

[ARCH]
x86=/x86
ia64=/ia64
x64=/x64

[OS]
5.0.2195.0-5.0.2195.2.9999=/W2KSP2
5.0.2195.3-5.0.9999.9999.9999=/W2K
5.1-5.1.9999.9999.9999=/XP
5.2-5.2.9999.9999.9999=/NetServer
*.*:6.0-6.0.999999.999999.999999=/UNSUPPORTED

[OS2]
*.*:5.0.2195.0-5.0.2195.2.9999=/W2KSP2
*.*:5.0.2195.3-5.0.9999.9999.9999=/W2K
*.*:5.1-5.1.9999.9999.9999=/XP
*.*:5.2-5.2.9999.9999.9999=/NetServer
*.*:6.0-6.0.5999.999999.999999=/UNSUPPORTED
*.*:6.0.6000.0.0-6.0.999999.999999.999999=/Vista

[OS3]
*.*:5.0.2195.0-5.0.2195.2.9999=/Other
*.*:5.0.2195.3-5.0.9999.9999.9999=/Other
*.*:5.1-5.1.9999.9999.9999=/Other
*.*:5.2-5.2.9999.9999.9999=/Other
*.*:6.0-6.0.5999.999999.999999=/UNSUPPORTED
*.*:6.0.6000.0.0-6.0.999999.999999.999999=/Vista

[LANG]
ar=/ar
cs=/cs
da=/da
de=/de
el=/el
en=/en
es=/es
fi=/fi
fr=/fr
he=/he
hu=/hu
it=/it
iw=/he
ja=/ja
ko=/ko
nec=/ja
nl=/nl
nb=/no
no=/no
nn=/no
pl=/pl
pt=/pt
pt-BR=/ptBR
ru=/ru
sv=/sv
tr=/tr
zh-TW=/zhTW
zh-CN=/zhCN
zh=/zhCN






"Winfried Sonntag [MVP]" wrote:
[..]
 #10  
11-08-07, 02:13 PM
Rick
the last one was from the server side

I ran this one from a workstation



[SusClientUpdate]
ServerUrlEx="http://download.windowsupdate.com/v7/windowsupdate/a"
StructureKeyEx=/AU|ARCH|OS|LANG
StructureKeyEx2=/AU|ARCH|OS2|LANG
StructureKeyEx3=/WSUS3|ARCH|OS3

[ARCH]
x86=/x86
ia64=/ia64
x64=/x64

[OS]
5.0.2195.0-5.0.2195.2.9999=/W2KSP2
5.0.2195.3-5.0.9999.9999.9999=/W2K
5.1-5.1.9999.9999.9999=/XP
5.2-5.2.9999.9999.9999=/NetServer
*.*:6.0-6.0.999999.999999.999999=/UNSUPPORTED

[OS2]
*.*:5.0.2195.0-5.0.2195.2.9999=/W2KSP2
*.*:5.0.2195.3-5.0.9999.9999.9999=/W2K
*.*:5.1-5.1.9999.9999.9999=/XP
*.*:5.2-5.2.9999.9999.9999=/NetServer
*.*:6.0-6.0.5999.999999.999999=/UNSUPPORTED
*.*:6.0.6000.0.0-6.0.999999.999999.999999=/Vista

[OS3]
*.*:5.0.2195.0-5.0.2195.2.9999=/Other
*.*:5.0.2195.3-5.0.9999.9999.9999=/Other
*.*:5.1-5.1.9999.9999.9999=/Other
*.*:5.2-5.2.9999.9999.9999=/Other
*.*:6.0-6.0.5999.999999.999999=/UNSUPPORTED
*.*:6.0.6000.0.0-6.0.999999.999999.999999=/Vista

[LANG]
ar=/ar
cs=/cs
da=/da
de=/de
el=/el
en=/en
es=/es
fi=/fi
fr=/fr
he=/he
hu=/hu
it=/it
iw=/he
ja=/ja
ko=/ko
nec=/ja
nl=/nl
nb=/no
no=/no
nn=/no
pl=/pl
pt=/pt
pt-BR=/ptBR
ru=/ru
sv=/sv
tr=/tr
zh-TW=/zhTW
zh-CN=/zhCN
zh=/zhCN





"Winfried Sonntag [MVP]" wrote:
[..]
 #11  
11-08-07, 02:17 PM
Winfried Sonntag [MVP]
Rick schrieb:

> sorry I was a little brain dead with the link, forgot to change the server
> part of the link


OK, you are sure, the correct WSUS-Server entry is in the registry on
the clients? Which one is working? with Port 8530 or Standard Port 80?
Do you have a ISA Server in your network?

Winfried
 #12  
11-08-07, 06:28 PM
Rick
I uninstalled IIS & WSUS and then re-installed and the problem went away.
Everything appears to be talking

thanks for your help

"Winfried Sonntag [MVP]" wrote:
[..]
 #13  
11-09-07, 08:00 AM
Winfried Sonntag [MVP]
Rick schrieb:

> I uninstalled IIS & WSUS and then re-installed and the problem went away.
> Everything appears to be talking
>
> thanks for your help


Thanks for response. ;)

Winfried
Similar Threads
UPGRADE - WSUS 3.0 to WSUS 3.0 SP1, remote SQL database

Hi I’m trying to upgrade WSUS 3.0 to WSUS 3.0 SP1 but I’m getting an error that prevents me doing that. I have Windows Server 2003 SP2 on x86 platforms. At the...

Does upgrade to WSUS 3 completely remove WSUS 2?

Hi, Pardon my ignorance as a relative newbie. I have upgraded to WSUS 3.0 but if I look at update services from the Server management console, I get a message : "Windows...

Upgrade WSUS Build 2.0.0.2620 to WSUS 3.0

I hope this has not been addressed but I would like to upgrade to 3.0 from my current build. (Background) I have WSUS 2 installed on a server running Win2003 RC2 with SQL...

Upgrade WSUS 2.0 to 3.0 on New Hardware

I'm in the process of getting ready to install a new WSUS server to replace our existing server. Having just discovered that WSUS 3.0 is available I'd like to install this...

Upgrade WSUS SP1 with SQL2000 SP4 to WSUS 3 beta2

Reading the documentataion the claim is that WSUS 3 will completely upgrade overtop of a WSUS sp1 installation perserving everything you have in place. However I don't see...


All times are GMT. The time now is 06:26 AM. | Privacy Policy