Non auto start of IIS at W2000 start

Hi...I have finally managed to get IIS 5.0 running on my W2000 Pro
system. I had to first set up and start a Microsoft Network.
My initial purpose for installing it is so I can pretest a web site
coding before uploading; i.e. no interest right now in operating a server
for anyone but myself and that only for the testing of trial site
designs. So the automatic startup of IIS when I begin a W2000 session
isn't really needed. To get IIS to run at all I did a lot of web
searching and haven't found anyone wanting a strictly manual launch
server. To make the automatic launch work I placed a short cut to that
network in the start menu and when W2000 finally loads (it seems to take
several minutes longer now than pre IIS) IIS will respond to
http://localhost and I can open the management consol. Is there a cleaner
way to do this, have my Microsoft Network working at startup?
Most web articles state a manual start is not good because it may affect
other services. From what I can see the only other services affected are
those under IIS. There's lots of good info on manually stopping and
restartng IIS but nothing about that auto launch with W2000. Has anyone
tried just placing all the IIS services on manual without any bad side
affects? I guess I'd have to decipher just what they are called in the
Services list. Any suggestions would be appreciated.
Regards, Nick

IIS can be configured to start manually without problems -- so that you can
demand-start IIS whenever you want.

You just need to place the "World Wide Web Publishing" service on Manual.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"enaitee" <u617ix49o002.RemoveThis@sneakemail.com> wrote in message
news:Xns9474C5E7423B7enaiteetoastnet@130.133.1.4...
Hi...I have finally managed to get IIS 5.0 running on my W2000 Pro
system. I had to first set up and start a Microsoft Network.
My initial purpose for installing it is so I can pretest a web site
coding before uploading; i.e. no interest right now in operating a server
for anyone but myself and that only for the testing of trial site
designs. So the automatic startup of IIS when I begin a W2000 session
isn't really needed. To get IIS to run at all I did a lot of web
searching and haven't found anyone wanting a strictly manual launch
server. To make the automatic launch work I placed a short cut to that
network in the start menu and when W2000 finally loads (it seems to take
several minutes longer now than pre IIS) IIS will respond to
http://localhost and I can open the management consol. Is there a cleaner
way to do this, have my Microsoft Network working at startup?
Most web articles state a manual start is not good because it may affect
other services. From what I can see the only other services affected are
those under IIS. There's lots of good info on manually stopping and
restartng IIS but nothing about that auto launch with W2000. Has anyone
tried just placing all the IIS services on manual without any bad side
affects? I guess I'd have to decipher just what they are called in the
Services list. Any suggestions would be appreciated.
Regards, Nick