Today an odd thing happened… After adding a new server to the farm (same hardware, drive letters, etc.) the new server lacked the logs directory, it was configured in an alternate drive, but is was present in all servers in the farm but this.

In case you don’t know it, I think is a good practice to have both IIS and MOSS logs in a different partition from the system drive, just in case something goes wrong and the logs fill the system drive and make your server unstable, so it’s better to isolate the logs in another partition.

Well the thing is that, after adding the server to the farm, the logs folder is not created in the new server even if the drive is available, so the solution is this:

- In case all the servers in your far do not have a common drive, set the diagnostics log folder to a folder that is present in all servers (in our case d:\moss_logs").

- In the servers that do not have this folder created, create and give the appropriate read/writer permissions to it(authenticated users was what I used) .

- Restart the WSS Tracing service in the servers you created the folder, and make a web petition to those servers, so you can see how the log files are created.

So in this point you hopefully have all the servers in your farm tracing the events.