Hello If you note the location of these folders they are on you M: drive. This drive does not exist until the Exchange IFS (installable file system) is running. IIS starts before this is available hence the red stop signs. However IIS can still read these directories once they are available. IIS just "forgets" to update the status of the folders. Stopping and Starting IIS will fix the interface so they show available. However if you check you should find them available even with unavailable icon present. Bill -----Original Message----- From: Chris Cerer [mailto:ccerer@xxxxxxxxxxxx] Sent: Tuesday, December 17, 2002 12:45 PM To: [ExchangeList] Subject: [exchangelist] Services do not start automatically http://www.MSExchange.org/ I have a problem with IIS services not starting when the server starts. Specs: W2K server SP2, E2K SP3. When the server is restarted, I get a stop sign on the following folders under my default web site in IIS: Public, Exchange, and Exadmin. If I go to the properties of each of these, and browse to the location where the folder is, then it goes to running. (If I tell it where to find the folder, it starts or comes online, whatever you want to call it.) Is there a reason that my server can't remember where to find these locations, and I have to "remind" it every reboot? Thanks, Chris ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: wtholmes@xxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')