SUS management - Any Ideas?

I have tried numorous failed attempts of setting up our SUS server on our local domain. It seriously does not like me. I have installed the latest version of SUS and MBSA on the server and my client machine runs the latest version of MBSA and also the "SUSadmin" utility to set up options for the SUS server
In the options in SUSadmin, I have set the following options

Specify the name your clients use to locate this update server:
Server name: SERVER1 (our servername

and this server is syncronising directly from the microsoft updates site.

Our server is running small business server 2000 which supports Group policy management and all that. I have tried to set these options for automatic updates so that our clients connect to the server in opposed to microsoft updates site (no offence all you microsoft guys out there ;P) as our server stores all updates from syncronisation locally. Under the group policy setting I have tried setting the "local intranet server used to aquire updates" to both server1 and http:\\server1 and neither has really done anything

running MBSA from dos, there is an option to call a program "mbsacli.exe" and specify a SUS serve
I have tried the following:
mbsacli.exe /sus "server1
mbsacli.exe /sus "SERVER1
mbsacli.exe /sus "http://server1/susadmin
mbsacli.exe /sus "http://SERVER1/SUSadmin
mbsacli.exe /sus "http://server1

and so on. None of these really work, I either get an "invalid sus server" "could not get list of approved updates" or it connects to microsof again. This is really frustrating. Any ideas on how to fix this?? If I can get it scanning correctly here, then I could fix the group policy

SUS services is installed on the D:\ on our serve
MBSA is installed on the C:\ of our serve
Just in case that bears any importance...

Ron
Wed Feb 11 22:42:17 CST 2004

Robbo,
You might have better luck with your question in the softwareupdatesvcs NG.

Ron Chamberlin
MS-MVP

"robbo" <rstewart@laneford.com.au> wrote in message
news:F19EC35B-9604-488A-8E20-A8EADD1C2480@microsoft.com...
>I have tried numorous failed attempts of setting up our SUS server on our
>local domain. It seriously does not like me. I have installed the latest
>version of SUS and MBSA on the server and my client machine runs the latest
>version of MBSA and also the "SUSadmin" utility to set up options for the
>SUS server.
> In the options in SUSadmin, I have set the following options:
>
> Specify the name your clients use to locate this update server:
> Server name: SERVER1 (our servername)
>
> and this server is syncronising directly from the microsoft updates site.
>
> Our server is running small business server 2000 which supports Group
> policy management and all that. I have tried to set these options for
> automatic updates so that our clients connect to the server in opposed to
> microsoft updates site (no offence all you microsoft guys out there ;P) as
> our server stores all updates from syncronisation locally. Under the group
> policy setting I have tried setting the "local intranet server used to
> aquire updates" to both server1 and http:\\server1 and neither has really
> done anything.
>
> running MBSA from dos, there is an option to call a program "mbsacli.exe"
> and specify a SUS server
> I have tried the following:
> mbsacli.exe /sus "server1"
> mbsacli.exe /sus "SERVER1"
> mbsacli.exe /sus "http://server1/susadmin"
> mbsacli.exe /sus "http://SERVER1/SUSadmin"
> mbsacli.exe /sus "http://server1"
>
> and so on. None of these really work, I either get an "invalid sus server"
> "could not get list of approved updates" or it connects to microsof again.
> This is really frustrating. Any ideas on how to fix this?? If I can get it
> scanning correctly here, then I could fix the group policy.
>
> SUS services is installed on the D:\ on our server
> MBSA is installed on the C:\ of our server
> Just in case that bears any importance....
>
>
>

Torgeir
Wed Feb 11 23:39:11 CST 2004

Hi

Fyi, there is a separate newsgroup for SUS:

microsoft.public.softwareupdatesvcs

news://msnews.microsoft.com/microsoft.public.softwareupdatesvcs

URL to the group softwareupdatesvcs for those who uses the Web
interface to access the newsgroups:
http://www.microsoft.com/windowsserver2003/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.softwareupdatesvcs

A Web site about SUS with a FAQ and a SUS forum:
http://www.susserver.com/

More SUS Web sites:
http://www.cites.uiuc.edu/sus/faq.html
http://www.faqshop.com/sus/default.htm



--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page Scripting Guide: http://www.microsoft.com/technet/scriptcenter

Karl
Thu Feb 12 05:44:59 CST 2004

It seems to me your question might be better answered in a group for MBSA
questions [or post in both SUS and MBSA groups at the same time]. I believe
there is such a group.


"robbo" <rstewart@laneford.com.au> wrote in message
news:F19EC35B-9604-488A-8E20-A8EADD1C2480@microsoft.com...
> I have tried numorous failed attempts of setting up our SUS server on our
local domain. It seriously does not like me. I have installed the latest
version of SUS and MBSA on the server and my client machine runs the latest
version of MBSA and also the "SUSadmin" utility to set up options for the
SUS server.
> In the options in SUSadmin, I have set the following options:
>
> Specify the name your clients use to locate this update server:
> Server name: SERVER1 (our servername)
>
> and this server is syncronising directly from the microsoft updates site.
>
> Our server is running small business server 2000 which supports Group
policy management and all that. I have tried to set these options for
automatic updates so that our clients connect to the server in opposed to
microsoft updates site (no offence all you microsoft guys out there ;P) as
our server stores all updates from syncronisation locally. Under the group
policy setting I have tried setting the "local intranet server used to
aquire updates" to both server1 and http:\\server1 and neither has really
done anything.
>
> running MBSA from dos, there is an option to call a program "mbsacli.exe"
and specify a SUS server
> I have tried the following:
> mbsacli.exe /sus "server1"
> mbsacli.exe /sus "SERVER1"
> mbsacli.exe /sus "http://server1/susadmin"
> mbsacli.exe /sus "http://SERVER1/SUSadmin"
> mbsacli.exe /sus "http://server1"
>
> and so on. None of these really work, I either get an "invalid sus server"
"could not get list of approved updates" or it connects to microsof again.
This is really frustrating. Any ideas on how to fix this?? If I can get it
scanning correctly here, then I could fix the group policy.
>
> SUS services is installed on the D:\ on our server
> MBSA is installed on the C:\ of our server
> Just in case that bears any importance....
>
>
>

Torgeir
Thu Feb 12 08:26:20 CST 2004

"Karl Levinson [x y] mvp" wrote:

> It seems to me your question might be better answered in a group for MBSA
> questions [or post in both SUS and MBSA groups at the same time]. I believe
> there is such a group.

Hi

The MBSA group:

microsoft.public.security.baseline_analyzer


--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter