Jump to content

DiGGiTY

Member
  • Posts

    157
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by DiGGiTY

  1. What you're looking for is this:

    User Key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\

    Explorer]

    System Key: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\

    Explorer]

    Value Name: NoRecentDocsNetHood

    Data Type: REG_DWORD (DWORD Value)

    Value Data: (0 = track shares, 1 = disable tracking)

  2. I'd suggest getting the books that Mark Minasi publishes. He is the well-known author of the 'Mastering' series. You'll find that the majority of professionals use his books because they are the most complete references for Windows Server products.

    If you are interested in more technical nuances and obscure details, be sure to check out Microsoft's 'Notes from the Field' series. There's lots of good stuff there.

  3. Microsoft released a tool named BootVis that optimizes your startup time... It is not available for download at Microsoft any longer, but if you do a Google for 'download bootvis' you should be able to find it.

    It works... I've used it a lot over the last few years.

  4. There are plenty of wireless keyboards out there with mouse functions on the touch pad. You have to understand that deploying a full blown Media Center in your living room is cutting edge (viz. expensive).

    Give it time. High end displays, video cards, and sound boards all exist today, but they will be less expensive in the future. This is how it always is with newer technology.

  5. Here's another interesting point: Initially the large antivirus companies were adament in respect to keeping antivirus and antispyware products separate--they weren't intersted in handling spyware.

    Presently, Symantec and McAfee (the big 2) have released their first versions of antivirus integrated with antispyware removal. Prior to that these companies only detected spyware.

    Gartner group recommends that businesses use a stop-gap solution presently to handle spyware. Gartner says that your long-term solution will be offered by antivirus vendors.

  6. If you run DCPromo on a server that is already a DC, isn't the only option you get to choose is to demote the DC to a Member Server?

    Yes, you are correct. You first have to demote the domain controller with dcpromo.

    Also, you mentioned that you wanted to view two domains in AD Users & Computers... In case you weren't aware, you can connect to different Domains from that console:

    post-50504-1113595559_thumb.png

  7. Using code to perform the function might be easier... Here's a decent snippet.

    'RegObj must be installed to run this script.

    'http://msdn.microsoft.com/vbasic/downloads/addins/default.asp

    'Author.Mike Ford.08.26.03

    Dim rserver

    const objKey = "\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\"

    const name = "DefaultUserName"

    strComputer = Inputbox("Remote Computer?")

    If strComputer = "" Then

    WScript.Quit

    End If

    Set fso = WScript.CreateObject("RegObj.Registry")

    Set connect = fso.RemoteRegistry(strComputer)

    Set username = connect.RegKeyFromString(objKey).Values(name)

    wscript.echo "The Last Logged on User was: " & username

  8. Sysinternals has a command line tool that can return the locally logged on user (and more info as well). You can use this to create a text dumpfile and parse it to pull out the relevent data:

    PsLoggedOn

    You can determine who is using resources on your local computer with the "net" command ("net session"), however, there is no built-in way to determine who is using the resources of a remote computer. In addition, NT comes with no tools to see who is logged onto a computer, either locally or remotely. PsLoggedOn is an applet that displays both the locally logged on users and users logged on via resources for either the local computer, or a remote one. If you specify a user name instead of a computer, PsLoggedOn searches the computers in the network neighborhood and tells you if the user is currently logged on.

    PsLoggedOn's definition of a locally logged on user is one that has their profile loaded into the Registry, so PsLoggedOn determines who is logged on by scanning the keys under the HKEY_USERS key. For each key that has a name that is a user SID (security Identifier), PsLoggedOn looks up the corresponding user name and displays it. To determine who is logged onto a computer via resource shares, PsLoggedOn uses the NetSessionEnum API. Note that PsLoggedOn will show you as logged on via resource share to remote computers that you query because a logon is required for PsLoggedOn to access the Registry of a remote system.

    Installation

    Copy PsLoggedOn onto your executable path and type "psloggedon".

    PsLoggedOn works on NT 4.0, Windows 2000 and Windows XP.

    Usage

    usage: psloggedon [-?] [-l] [-x] [\\computername | username]

    -l

    Shows only local logons instead of both local and network resource logons.

    -x

    Don't show logon times.

    \\computername

    Specifies the name of the computer for which to list logon information.

    username

    If you specify a user name PsLoggedOn searches the network for computers to which that user is loggedon. This is useful if you want to ensure that a particular user is not logged on when you are about to change their user profile configuration.



×
×
  • Create New...