Software Update Services
6 отговора
313 прегледа
Re: Software Update Services
Тук!
Работи добре - доколкото мога да преценя след двуседмична работа! В началото генерира подозрително голям трафик, ( издърпа огромно количество ъпдейти и всяка една станция чинно си ги дръпна ) но като цяло е добре! Евентуално проблеми може да създаде бекъпа на всеки ъпдейт, но ако поразчистваш станциите редовно...
"Няма да я целувам засега" си казал принца и слязал от Спящата Красавица
Работи добре - доколкото мога да преценя след двуседмична работа! В началото генерира подозрително голям трафик, ( издърпа огромно количество ъпдейти и всяка една станция чинно си ги дръпна ) но като цяло е добре! Евентуално проблеми може да създаде бекъпа на всеки ъпдейт, но ако поразчистваш станциите редовно...
"Няма да я целувам засега" си казал принца и слязал от Спящата Красавица
Re: Software Update Services
Има готина статия по въпроса в newsletter-а на Mark Minasi ([линк]) от януари тази година. Разпространява се безплатно, но иска регистрация.
За да ти спестя едно регистриране, ето началото на статията:
SUS Basics: What it Can and Can't Do
In July of 2002, Microsoft offered an alternative called Software Update Service. Basically it lets you set up your own private Windows Update on a server inside your organization, and then lets you configure all of the systems inside your organization to look at that private SUS server for patches instead of Microsoft's Windows Update server. With SUS, you can
Control which patches your users see
Cause their systems to download and apply patches without the need for user intervention, and
Greatly reduce the patching burden on your Internet bandwidth, as users grab patches over your LAN -- in my previous example you'd just download that IE service pack once over the Internet, install it on your internal SUS server, and then your 1000 users would get their patch over your internal network, with no extra load on your Internet connection.
But SUS won't do everything. The price is right, but it's limited in what it'll let you do.
First of all, SUS only handles the critical updates. Look at Windows Update and you'll see three sorts of downloadable items: "critical updates," which are OS patches that fix some security problem, "updates," which are patches that either fix a non-security-related problem or that add some value to your system, like a recent XP patch that adds support for IPv6, and "drivers," which are obviously updated hardware drivers. SUS only distributes critical updates, and there's no way to use it to locally host updates and drivers.
Second, SUS only delivers patches for the Windows 2000, XP and 2003 operating systems. Windows 9x and Windows NT 4 patches can't be delivered with SUS. Nor does SUS deliver patches for Office, SQL Server, Exchange, ISA Server, etc -- only the stuff "in the box" with 2000, XP and 2003. (Good news, though -- Microsoft will fix this with SUS 2.0, which will appear sometime in the middle of this year.) There is also no way to use SUS to deliver your own non-Microsoft patches.
Third, while SUS takes the place of Windows Update, it doesn't present the same user interface as Windows Update. As you'll see, the SUS client wants to work in the background, unobtrusively downloading patches and then, if those patches require a reboot, to do that reboot at some scheduled time. Windows Update can work like as well, but what if you've just installed a system and you want to go get all of your patches and install them immediately? Well, with Windows Update, you can do that -- you just go to the Windows Update Web site, select your patches, pull them down, install them, reboot and you're done. But there's no similar way to just fire up a Web browser, point to a given SUS server and just tell it to get you up to date with patches now -- there is no interactive, browsable interface for SUS clients and no way to speed up SUS's patch application.
Fourth, there is similarly no way for an administrator to sit at some central location and instruct the SUS server to force some new patch on every client, now. You can sort of help the process along, but you can't say "do it now" as you can with Windows Update. With SUS, "patience is a virtue."
Останалото е съвети за инсталиране, за наблюдение и за отстраняване на проблеми.
Иначе този newsletter определено си заслужава да се чете. Може да си направиш труда и да се регистрираш, няма да сбъркаш.
А аз самият нямам опит с това нещо, мисля да го сложа, когато излезе версия 2.0.
Боян
За да ти спестя едно регистриране, ето началото на статията:
SUS Basics: What it Can and Can't Do
In July of 2002, Microsoft offered an alternative called Software Update Service. Basically it lets you set up your own private Windows Update on a server inside your organization, and then lets you configure all of the systems inside your organization to look at that private SUS server for patches instead of Microsoft's Windows Update server. With SUS, you can
Control which patches your users see
Cause their systems to download and apply patches without the need for user intervention, and
Greatly reduce the patching burden on your Internet bandwidth, as users grab patches over your LAN -- in my previous example you'd just download that IE service pack once over the Internet, install it on your internal SUS server, and then your 1000 users would get their patch over your internal network, with no extra load on your Internet connection.
But SUS won't do everything. The price is right, but it's limited in what it'll let you do.
First of all, SUS only handles the critical updates. Look at Windows Update and you'll see three sorts of downloadable items: "critical updates," which are OS patches that fix some security problem, "updates," which are patches that either fix a non-security-related problem or that add some value to your system, like a recent XP patch that adds support for IPv6, and "drivers," which are obviously updated hardware drivers. SUS only distributes critical updates, and there's no way to use it to locally host updates and drivers.
Second, SUS only delivers patches for the Windows 2000, XP and 2003 operating systems. Windows 9x and Windows NT 4 patches can't be delivered with SUS. Nor does SUS deliver patches for Office, SQL Server, Exchange, ISA Server, etc -- only the stuff "in the box" with 2000, XP and 2003. (Good news, though -- Microsoft will fix this with SUS 2.0, which will appear sometime in the middle of this year.) There is also no way to use SUS to deliver your own non-Microsoft patches.
Third, while SUS takes the place of Windows Update, it doesn't present the same user interface as Windows Update. As you'll see, the SUS client wants to work in the background, unobtrusively downloading patches and then, if those patches require a reboot, to do that reboot at some scheduled time. Windows Update can work like as well, but what if you've just installed a system and you want to go get all of your patches and install them immediately? Well, with Windows Update, you can do that -- you just go to the Windows Update Web site, select your patches, pull them down, install them, reboot and you're done. But there's no similar way to just fire up a Web browser, point to a given SUS server and just tell it to get you up to date with patches now -- there is no interactive, browsable interface for SUS clients and no way to speed up SUS's patch application.
Fourth, there is similarly no way for an administrator to sit at some central location and instruct the SUS server to force some new patch on every client, now. You can sort of help the process along, but you can't say "do it now" as you can with Windows Update. With SUS, "patience is a virtue."
Останалото е съвети за инсталиране, за наблюдение и за отстраняване на проблеми.
Иначе този newsletter определено си заслужава да се чете. Може да си направиш труда и да се регистрираш, няма да сбъркаш.
А аз самият нямам опит с това нещо, мисля да го сложа, когато излезе версия 2.0.
Боян
