Post WSUS 3.0 installation issues eanderso 6/27/2007 7:50:00 PM Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed IIS, .net 2.0, and viewer before installation. I installed WSUS in its own site not using the default. The server seems to be working correctly. I can open the mmc and configure the server. I created a GPO with correct information like https://fqdn:8531. I assigned this to 3 servers for a test and nothing. Servers are not appearing in the console. Any ideas? Can I test the website to see if its working like WSUS 2.0 via the wsusadmin console? Thanks in advanced.

Re: Post WSUS 3.0 installation issues "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> 6/27/2007 8:20:41 PM eanderso schrieb: [Quoted Text] > Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed > IIS, .net 2.0, and viewer before installation. I installed WSUS in its own > site not using the default. > > The server seems to be working correctly. I can open the mmc and configure > the server. I created a GPO with correct information like https://fqdn:8531. > I assigned this to 3 servers for a test and nothing. Servers are not > appearing in the console. Any ideas? Can I test the website to see if its > working like WSUS 2.0 via the wsusadmin console? Yes, try this: http://WSUS-SERVER:8531/selfupdate/wuident.cab You're sure thats not Port 8530? Winfried -- http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx http://www.wsuswiki.com/Home

Re: Post WSUS 3.0 installation issues eanderso 6/27/2007 8:42:00 PM This is working and offering up to save the file. The 8530 was the http port. "Winfried Sonntag [MVP]" wrote: [Quoted Text] > eanderso schrieb: > > > Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed > > IIS, .net 2.0, and viewer before installation. I installed WSUS in its own > > site not using the default. > > > > The server seems to be working correctly. I can open the mmc and configure > > the server. I created a GPO with correct information like https://fqdn:8531. > > I assigned this to 3 servers for a test and nothing. Servers are not > > appearing in the console. Any ideas? Can I test the website to see if its > > working like WSUS 2.0 via the wsusadmin console? > > Yes, try this: http://WSUS-SERVER:8531/selfupdate/wuident.cab > You're sure thats not Port 8530? > > Winfried > -- > http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx > http://www.wsuswiki.com/Home >

Re: Post WSUS 3.0 installation issues "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/28/2007 12:20:24 AM "eanderso" <eanderso[ at ]discussions.microsoft.com> wrote in message news:997AB4FE-2CFD-4BCD-B217-FEDE2D487EB8[ at ]microsoft.com... [Quoted Text] > Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed > IIS, .net 2.0, and viewer before installation. I installed WSUS in its own > site not using the default. > > The server seems to be working correctly. I can open the mmc and configure > the server. I created a GPO with correct information like > https://fqdn:8531. Did you disable SSL on those resources in the WSUS website that cannot support SSL connectivity? These resources that need to have SSL disabled are documented in the Configuring SSL section of the WSUS Deployment Guide. > I assigned this to 3 servers for a test and nothing. Servers are not > appearing in the console. Any ideas? Can I test the website to see if its > working like WSUS 2.0 via the wsusadmin console? No, you'd have to log onto the MMC-based admin tool. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Post WSUS 3.0 installation issues eanderso 6/28/2007 2:36:06 PM Thanks for the response. The 3 test servers are all 2003 R2 SP2 boxes so i think they all support the SSL part. I can try it with the http:servername:8530 and see if that works but I'm not crossing my fingers. "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "eanderso" <eanderso[ at ]discussions.microsoft.com> wrote in message > news:997AB4FE-2CFD-4BCD-B217-FEDE2D487EB8[ at ]microsoft.com... > > Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed > > IIS, .net 2.0, and viewer before installation. I installed WSUS in its own > > site not using the default. > > > > The server seems to be working correctly. I can open the mmc and configure > > the server. I created a GPO with correct information like > > https://fqdn:8531. > > Did you disable SSL on those resources in the WSUS website that cannot > support SSL connectivity? > > These resources that need to have SSL disabled are documented in the > Configuring SSL section of the WSUS Deployment Guide. > > > > I assigned this to 3 servers for a test and nothing. Servers are not > > appearing in the console. Any ideas? Can I test the website to see if its > > working like WSUS 2.0 via the wsusadmin console? > > No, you'd have to log onto the MMC-based admin tool. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: Post WSUS 3.0 installation issues eanderso 6/28/2007 5:36:01 PM I solved the problem. I uninstalled WSUS then reread the installation requirements. I didn't install the .net 2.0 redistributable installation but just .net 2.0. Once the correct one was installed WSUS installed and is working correctly with 2 servers reporting in. Thanks the the help. "eanderso" wrote: [Quoted Text] > Thanks for the response. The 3 test servers are all 2003 R2 SP2 boxes so i > think they all support the SSL part. I can try it with the > http:servername:8530 and see if that works but I'm not crossing my fingers. > > "Lawrence Garvin (MVP)" wrote: > > > "eanderso" <eanderso[ at ]discussions.microsoft.com> wrote in message > > news:997AB4FE-2CFD-4BCD-B217-FEDE2D487EB8[ at ]microsoft.com... > > > Server OS - 2003 SP2. Installed WSUS after the SP2 installation. Installed > > > IIS, .net 2.0, and viewer before installation. I installed WSUS in its own > > > site not using the default. > > > > > > The server seems to be working correctly. I can open the mmc and configure > > > the server. I created a GPO with correct information like > > > https://fqdn:8531. > > > > Did you disable SSL on those resources in the WSUS website that cannot > > support SSL connectivity? > > > > These resources that need to have SSL disabled are documented in the > > Configuring SSL section of the WSUS Deployment Guide. > > > > > > > I assigned this to 3 servers for a test and nothing. Servers are not > > > appearing in the console. Any ideas? Can I test the website to see if its > > > working like WSUS 2.0 via the wsusadmin console? > > > > No, you'd have to log onto the MMC-based admin tool. > > > > -- > > Lawrence Garvin, M.S., MCTS, MCP > > Independent WSUS Evangelist > > MVP-Software Distribution (2005-2007) > > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > > > Everything you need for WSUS is at > > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > > > And, almost everything else is at > > http://wsusinfo.onsitechsolutions.com > > ..... > > > > > >