IIS (4.0) under Windows NT server 4.0 seems to lock html files after each read. It seems to unlock them after some time. Is there a way to prevent this locking to occur?
What I have found/read up to now:
If I stop and restart IIS, all files are now unlocked.
It doesn't seem to lock ASP files. But it isn't a good solution to use ASP files instead of html because of speed (ASP files need to be parsed).
The lock seem to be a read lock because some program are able to write over the file but some aren't. (Maybe these programs look for a lock instead of a write lock).
Someone tell to try changing this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\GlobalExpire=??? to 0. It said this worked for IIS 3.0 but this don't work for 4.0.
Programs that seem affected by this lock:
VisualSourceSafe (shadow folder)
TextPad (told by a friend)
Programs unaffected by this:
VisualInterDev (told by a friend)
It's a bug in IIS4.
MS states the solution is to add DisableMemoryCache with value 1 to the registry.
(so not GlobalExpire)
In some cases that is still not enough. I "fixed" the problem then by forcing
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Attackers love to prey on accounts that have privileges.
Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …