using Colin.Bowern;

Life ends with a semi-colon.

  Home  |   Contact  |   Syndication    |   Login
  22 Posts | 0 Stories | 2 Comments | 33 Trackbacks

News

Archives

Post Categories

Thursday, January 26, 2006 #

Join the team that is building the next generation of Internet-based communities for music legends and new recording artists. If you are passionate about music and love regularly dealing with challenges then this is THE place to work. A strong development team with great team spirit and work culture is waiting for you here at Official Community – a place that provides an opportunity to make an industry wide impact.

We are looking for a highly motivated people who love to rock to fill the following positions in Toronto, Canada:

  • Software Developer
  • Systems Administrator
  • Web Developer
  • Junior Web Developer
  • Community Coordinator

Get hands on with the latest Microsoft technologies and help promote web standards! For more information check out http://www.officialcommunity.com/opportunities


Most server administrators separate their content from their system data (at least I think they do :) ).  Content that grows will from time-to-time get by the monitoring process and bring a server to a halt because there is insufficient space on the sytem drive to continue. 

As I built up another test server image I had a desire to delete the c:\wmpub\wmiislog folder which Windows Media Services leaves behind.  From explorer you can't delete this folder because it is in use.  But what is using it?  After a quick search with Sysinternals Process Explorer I found that winlogon.exe is the culprit. 

Screenshot of Process Explorer handles window showing winlogon.exe's handle on the wmiislog folder

But why?  A search of the internet has revealed no published rational behind this.  Being a fan of keeping things in order there doesn't appear to be any purpose behind the folder so I'm nuking it.  To make this happen I first had to close the handle using Process Explorer (right click on the handle, “Close Handle”) and then remove the folder.

The bad news is that upon reboot the folder reappeared.  Hopefully we'll see this change in the next release of Windows Server.