The start up list in BC recommends this file as a Y, however I am finding contrary information,
Using the Secondary Logon Service and RunAs
The examples throughout this chapter show local administrators going about their daily work while logged on
using their Administrative accounts. This is generally not a good practice. Quite a few bad things can happen
when logged on with full admin permissions. Viruses can get activated and make sweeping changes.
Innocent mistakes can cause serious damage. Leaving your workstation open gives access to nefarious users.
The list goes on and on.
Windows Server 2003 comes with a Secondary Logon Service (SLS) that makes it possible to log on as a standard
user and then launch applications with alternative credentials to perform administrative tasks. This
is philosophically similar to the su (superuser) command in UNIX, but is implemented somewhat differently.
The Secondary Logon Service is installed by default and starts at boot time. The service is hosted by Services.exe.
The code is contained in Seclogon.dll.
Disable the Secondary Logon Service to Prevent Starting Processes Under Alternate Credentials
If in fact a hacker can use this or other means to invade my PC, . .
and I am online but not at my computer
is it possible for them to download or coppy my files
even though I have a firewall etc. ??
I guess if they can get that far that they could and or just take a Screen shot etc.