Q

Clients writing to log files on our SUS server to get their updates

We are implementing SUS here and have even joined susserver.com. One of the neat tricks there is to combine SUS with WOL as at http://www.xs4all.nl/~equator/suswol/. We installed SUS cabs and created a (hidden folder) for the WOL files and logs on a D: partition of the server. Would you be concerned that the clients need to write to the log files on our SUS server in order to get their updates this way? The files are R W. Couldn't someone do other damage if they wrote other things to the log files?
I'll agree with you that there's always that risk. Writing something to the logs isn't a big worry. You can always grab the proper information from the client logs. My big concern, though, is if something overwrote the log file with an .exe, except renaming it with a .txt or .log extension. Accessing the log file may cause the client to run it instead. Assuming it's a virus disguised as a log file, could spell trouble. SUS 2.0 (or WUS) will work with SQL and MSDE connections, so the log file issue should go away then.
This was first published in March 2004

Dig deeper on Microsoft Windows Data Backup and Protection

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchServerVirtualization

SearchCloudComputing

SearchExchange

SearchSQLServer

SearchWinIT

SearchEnterpriseDesktop

SearchVirtualDesktop

Close