Re: Local Security Settings

From: llie (anonymous_at_discussions.microsoft.com)
Date: 06/01/04

  • Next message: llie: "Re: Local Security Settings" 
    Date: Tue, 1 Jun 2004 03:00:50 -0700

    >-----Original Message-----
    >
    >>
    >>That is a Security ID (SID) that belongs to an account
    >on your system,
    >>or a previous installation of XP.
    >>
    >>Those IDs usually are shown with Group or User names. If
    >all you see is
    >>that number, you may have already mucked around too much
    >with XP Home
    >>Edition or you may be looking at leftovers from your
    >previous XP
    >>installation that you overwrote or you may be looking at
    >leftovers from
    >>deleted accounts.
    >>
    >>--
    >>Kent W. England, Microsoft MVP for Windows Security
    >>.
    >>
    >
    >1. I have XP Pro on this machine. XP Home or any other
    >OS has never been on this machine.(read original post)
    >2. XP has never been reinstalled on this machine,
    >repaired, or overwrote, nor have I ever had to "restore"
    >a restore point.
    >3. That number is in addition to the other entries, i.e.
    >Administrator etc...
    >4. There are three accounts on my system. Administrator
    >and two users, of which one of the users never gets
    >used. There has only been one other account which was
    >deleted.
    >
    >I had much the same problem with Xp in the beginning, and
    it took 4 reinstalls and lots of grief with Microsoft
    folks (and my DSL people)to get them to acknowledge that I
    actually did have unwanted users on my system. Long
    story, but it had to do with insecure DSL LAN as I was
    trying to update the very insecure XP Home (an hour
    maybe?) and the static IP I have.... Anyway, I suggest you
    read up on the users who are built in to XP and those who
    aren't, and watch your logs! ANd check task manager
    regularly! I was locked out of my own network folders and
    log files (so these buggers couldn't get traced), which is
    how I KNEW something very wrong was up... but it wasn't
    until I screamed bloody murder with lots of googled
    research under my belt that anyone paid attention to me.
    Go to Black Viper .com for a great set of directions on
    how to configure your services (what to turn off,
    especially), and then to Tweakxp.com for configuring
    permissions and the like.
    >.
    >

  • Next message: llie: "Re: Local Security Settings"

    Relevant Pages

    • Re: Problems installing SQL Server 2005 in two node cluster
      ... I'm assuming that SQL Server 2005 doesn't need to be an administrator ... that make sure you are not using domain admin-level accounts for the service ... Server2005Setup Log Files" and "StartingSQLServerManually." ... This is the fifth attempt at installation, ...
      (microsoft.public.sqlserver.clustering)
    • Re: Local Security Settings
      ... >>installation that you overwrote or you may be looking at ... There are three accounts on my system. ... but it had to do with insecure DSL LAN as I was ... log files, ...
      (microsoft.public.windowsxp.security_admin)
    • Re: Local Security Settings
      ... >>installation that you overwrote or you may be looking at ... There are three accounts on my system. ... but it had to do with insecure DSL LAN as I was ... log files, ...
      (microsoft.public.windowsxp.security_admin)
    • Re: Local Security Settings
      ... >>installation that you overwrote or you may be looking at ... There are three accounts on my system. ... but it had to do with insecure DSL LAN as I was ... log files, ...
      (microsoft.public.windowsxp.security_admin)
    • Re: Local Security Settings
      ... There are three accounts on my system. ... but it had to do with insecure DSL LAN as I was ... >log files, ... I used the Black Viper site a long time ago as ...
      (microsoft.public.windowsxp.security_admin)
    • Quantcast