"My fellow LANDesk-icans"... "I am not a crook....."
Server 2008 Standard R2, sp1
IIS Services 7
Running on VMware
Network attached storage
I have a strange issue that our LD support hasn't seen before and no solution from them yet.
Within IIS, our \\<coreserver>\patch directory accessed via HTTP:// has issues. I've followed the standard setup guides (articles slip me at the moment) and also verified by a LANDesk technician, that they are configured correctly. For no apparent reason, the Directory Browsing shuts off, after being enabled. It doesn't happen right away, in fact it's likely a full day randomly at any point it will shut off.
1) Not a GPO, as it is in an OU that has GPO's ignored
At first, I thought it was this (exerpt of my email to LD support):
Server 2008 has the service called Computer Browser, is disabled BY DEFAULT in Server setup. Either this was an initial setup error on my part (assuming this is documented for LANDesk to work) on Server 2008, or it is an assumption when running IIS that I didn’t catch. Either way, I’m sure this is the problem.
Interestingly, even with the service turned off, the Directory Browsing would work for a period of time (likely 24 hours or so), before flipping to off within IIS manager. So, you could http browse to the directory even with Computer Browser disabled. At some point, there must be a timeout, that switches Directory Browsing off, since the actual service is not running. The Dependencies of Computer Browser service are : Server and Workstation services. These, by default after a 2008 install, are enabled and start automatically. However, Computer Browser is turned off in 2008 by default.
After enabling this service, enabling the IIS browsing, waiting a day; come in the next day and it's flipped off again. I have another web accessed share as you can see from this pic
called Packages with the same setup and it doesn't flip off the Directory Browsing
Any ideas on this ? Any suggestions would be appreciated.
As you can imagine, not having that work, will "break" my global preferred server clients (Europe, UK, India, Germany), as they try to pull from the Core rather than the Preferred server, causing timeouts and all kinds of junk. My understanding is, having this UNC share and HTTP share enabled and working, then the clients would not attempt the Core, as it would help "force" the clients to pull from the Preferred. At least the way I understand it.