From: "Hrvoje Mesing" 


Exactly what I tought :)

Ofcourse you found the info when I told you 'bout StorageDevicePolicies.
Still, none! of your links could be, at least easily, found if not knowing
about the same reg. key.

Ok, maybe the first link "changes to func. in WinXP SP2" .. but someone is
'bout to read the manual, not pinpointing the info/documentation through,
lets say MSDN, etc.

The problem is, in everyday usage, that MS docco. is not complete,
sometimes not right/accurate and sometimes there realy is non leading mark
to the solution.

Etc., etc., etc.

Pitty.

-+-
M.



"Rich"  wrote in message news:45eb14f0{at}w3.nls.net...
    http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2otech.msp
x#ECJAC
    http://www.microsoft.com/technet/security/guidance/serversecurity/tcg/tcgch
10n.mspx#ED4AE
    http://support.microsoft.com/kb/555441
    http://blogs.msdn.com/nickmac/archive/2004/09/13/228549.aspx
    http://blogs.msdn.com/paranoidmike/archive/2005/01/24/359390.aspx
    http://blogs.technet.com/eileen_brown/archive/2004/12/03/274539.aspx

"Hrvoje Mesing"  wrote in
message news:45eb07a9{at}w3.nls.net...

C'mon, there is realy no documentation. There are bunch of
"white" papers which are not alwasy ebent true about the theme
they are describing.

Clue: StorageDevicePolicies

Now please find me logical path to this piece of data when you are into
securing USB :) You can even try with premier and any other you did not
noted.

I only can say that MS docco. stinks - it is readily available right, but
it is full of holes.


-+-
M.

"Rich"  wrote in message news:45e9d696{at}w3.nls.net...
   You probably never understood because it isn't true.  Documentation is
readily available both in the product and online.  You must live in some
other universe if you have not seen MSDN, Technet, the knowlegebase, or the
rest of microsoft.com.

Rich

"Hrvoje Mesing"  wrote in
message news:45e9a650{at}w3.nls.net...
LOL!

"understand what it is you are changing" .. well, taking into
account Microsoft documentation on any product, it is highly unlikely
something will not be broken.

I never understood why Microsoft documentation sucks. Why there is no
decent Registry docs., why there are not documents by applications, OS
ver., functions, etc.

Unbelivable ...


-+-
M.


"Rich"  wrote in message news:45e4eb2b$1{at}w3.nls.net...
   Now you are trying to read more into what symantec wrote.  If you want to
express your own opinions, go ahead.  I don't see the point as I remember
them.  Don't try to attribute this to others though.

   The best way to change your system config is to first understand what it
is you are changing.  I do not believe you are qualified to recognize when
you have broken something.

Rich

"Geo."  wrote in message
news:45e4e663$1{at}w3.nls.net... The first sentence is complete, the second
merely gives a few obvious examples. While windows may not have the obvious
examples it has plenty, PLENTY of services that are not critical. But lets
not get into that argument, ftp can be critical to a web server for example
so it's completely subjective as to what is or isn't critical.

(examples of non-critical the dns client, function discovery, infrared
monitor, ssdp, etc)

As for your "breaking the system" comment. The best way to find
out if a service is critical or not is to manually stop it and see if
anything breaks, if nothing you need breaks then I guess it's not critical
huh?

Geo.

"Rich"  wrote in message news:45e465c1$1{at}w3.nls.net...
   The three examples are not enabled by default on any Windows client OS.
For Windows Server OS releases I don't believe these three were ever
enabled by default but my memory is fuzzy for Windows 2000.  Windows Server
2003 did not and Windows NT 4.0 and earlier didn't include these features
in the base product.

   What you do is randomly disable services which you don't even understand.
You have broken your system with your flailing.

Rich

  "Geo."  wrote in message news:45e45c00{at}w3.nls.net...
  Oh and one for Rich:

  Recommendations
  Symantec Security Response encourages all users and administrators to
adhere
  to the following basic security "best practices":

  Turn off and remove unneeded services. By default, many operating systems
  install auxiliary services that are not critical, such as an FTP server,
  telnet, and a Web server. These services are avenues of attack. If they
are
  removed, blended threats have less avenues of attack and you have fewer
  services to maintain through patch updates.

  So remember this Rich when you start complaining about me shutting down
all
  those extra services in Vista...

  Geo.

--- BBBS/NT v4.01 Flag-5