Konacno.

Smilovao se billy i na nas obicne smrtnike :P

337230 KB -> vece nego SP2 za XP

A nema Free CD da salju kao kod XP SP2. :angry:


degojs, sta je to ubrzano konkretno?

Ej,
ne sećam se sad više šta sam čitao na MSDN-u, čini mi se. Neke stvari su prebacili u sam kernel, slično kao što su uradili i sa delovima IIS-a 6.0, pa otud i (značajno)ubrzanje. Zaista se ne sećam više šta je pisalo, ali potražiću ako budem uhvatio vremena. U svakom slučaju, ovih dana će sigurno biti dosta pisano o tome, pa će verovatno biti i prilike da nam se popnu na glavu svima sa tim :)

Negde sam procito da su menjali odredjene delove koda i da je to dovelo do ubrzanja iako nisu to planirali... Takodje sam procitao da nema nikakvih promena na kernelu tako da mislim da nije u pitanju ovo sto je degojs rekao.

Damn it!
Uh ko će sad to da skida preko dial up-a, a baš mi se eksperimentiše.

One of my own personal favorites is the hot patching feature that allows you to patch your system binaries even if they are currently in use. By actually patching the binaries in memory, this new feature will significantly reduce the number of reboots required for hotfixes. You will still need to reboot after updating kernel-level binaries, but as always, the fewer reboots the better.

http://www.theregister.co.uk/2...05/review_of_windows_2003_sp1/

One new (to Microsoft) technique is hot-patching, which updates running code in memory. Hot patching does not replace the actual executable on disk until after the service or application has shut down. This typically happens on the next reboot. Keep in mind here that this technique requires the user that installs the update to have the “Debug Programs” privilege. If you have removed that privilege from Administrators, for example, you need to grant it back at least to the accounts that will install updates. Unfortunately, hot patching comes at a cost – hot patches cannot be integrated into an installation point by slip streaming.

Another technique being built into the new installers is warm patching. In this case, the update installer attempts to shut down the application(s) that is using the files in the update prior to installing it. This is important because often the reason a system has to be rebooted after patching is because the update updates files that are in use. By shutting down the service prior to patching it, you can avoid having to reboot the system after the update is installed. This is obviously faster than a full system reboot. However, warm and hot-patching is not available for all security updates, and does not work for some types of security updates. You may be able to manually recreate the same effect though.

http://www.microsoft.com/techn...les/patch_management.mspx#EBAA

Zna li neko kako da uspem da instaliram SP1 na 2003,Datacenter edition.
Uvek mi se pojavljuje poruka sadrzaja:


This Service Pack 1 has not been qualified by your hardware vendor for
installacion on this copy of Windows Server 2003 Datacenter Server.

Please contact your hardware vendor for additional information on obtaining a
Service Pack 1 that has been qualified for your system configuracion.

Moja konfiguracuija je sledeca:

1.Barton 2500+
2.ASUS A7N8X Motherboard
3.512 MB RAM DDR400

Au, pa šta će ti Data Center verzija? Problem je što ta edicija, kako mi se čini, ide u paketu sa određenim serverom (hardver) i onda se to isporučuje preko onih koji pružaju takva rešenja, a kasnije verovatno i podršku, na šta te ova poruka i upućuje. Sad bi ti trebao da kontaktiraš npr. IBM, Dell, HP ili koga već, ko ti je kao isporučio softver-hardver sistem da vidiš ima li SP1 specifično za taj sistem koji su ti oni kao isporučili, kako da postupiš, itd. To ja baš ono **super** teška kategorija i često jako specijalizovano.

Stavi Standard ili Enterprise i vozi :)

Koristis piratsku verziju i cd-key ti je banovan u Service Pack-u

Po sajtovima dosta razglabaju o bitno povecanoj sigurnosi i zastiti. Ocekivao sam probleme kao sa SP2 za XP, ali to ovde niko ne spominje ...?

Problemi koji su se javljali sa SP2 za XP ovde nema jer su i problemi najčešće bili uzrokovani zbog: a) na kompjuteru ima spyware aplikacija b) neki 3rd party firewall sumnjivog kvaliteta. Teško da ćeš bilo šta od toga naći na serveru, a i broj instaliranih aplikacija je često daleko manji u poređenju sa desktop sistemom i dodatno to su uglavnom "proverene" aplikacije. Izuzetaka ima, ali se za te aplikacije uglavnom dobro zna.

Čisto informativno..

The MSN Messenger server farm handles over 70 million concurrent sessions every single day. Until recently, they were using 250 32-bit servers to manage that load. When they switched to Windows Server 2003 x64 Edition running on x64 hardware, they reduced the size of the farm to just 25 servers. Yikes.

Nadovezao bih se na degojsovu poruku da su vecina problema korisnika sa WinXP+SP2 posledica manjeg znanja korisnika.
Ljudi koji koriste Server verziju Windows-a ipak uglavnom imaju vece znanje o Windows-u i njegovom koriscenju.

Ako zelite da zaobidjete instalaciju SP1 pri auto-update-u, pogledajte uputstvo.