Windows Server 2003 Service Pack 1?

[Jim Ray]

If you are going to use a manufacturer's product, use it the 
manufacturer's way and do the update.  Just have a fall back plan in 
case you bring down a production network like I did:

http://www.neuse.net/news-2005-05-win2k3sp1error.htm

Oh, and don't count on Microsoft to save your tail.  Here's a more 
technical description of the problem:

http://www.neuse.net/news-2005-05-win2k3sp1response.htm

Other than checking for plenty of free space on the operating system 
partition, it works just fine at my accounts.

Regards,

Jim

Jim Ray, President
Neuse River Network, Inc.

tel: 919-838-1672 x111
toll free: 800-617-7652
cell: 919-606-1772
http://www.Neuse.Net

Ask about our Clean Technologies.  Established in the Carolinas 1997.



Brian Henning wrote:

> Hi Folks,
>   Windows Server 2003 has been bugging me for a month at least about 
> installing Service Pack 1.  I've been deferring, knowing Microsoft's 
> penchant for pushing out Service Packs fully capable of helpfully 
> hosing a working system and turning it into a quivering mess.
>
> So...
>
> Can some folks out there comment on the smoothness of upgrading Server 
> 2k3 to Service Pack 1?  Some key elements of my situation:
>
> - This is not a directly public-facing machine; it has internet access 
> behind NAT but does not provide any public-facing services.
> - It is NOT an AD master browser.
> - It DOES share certain volumes.
> - Properly-functioning Java is a big deal; currently using Sun's JVM 
> with a few extra libs.
> - It runs Terminal Services with two CALs..  wouldn't want those to 
> get messed up somehow.
>
> I think that's the main set of issues that strike me as things that a 
> Service Pack might affect.  Does anyone care to comment and perhaps 
> lend insight into particular bugaboos for which I ought to be on the 
> lookout?
>
> Thanks a bunch!
> ~Brian
>