Re: Single XP Account for local and domain user

From: Pete Wright (pete_at_codemonkey.demon.co.uk)
Date: 07/17/03

  • Next message: Kristofer Gafvert: "Re: Microsoft Security Bulletin MS03-026 - 823980"
    Date: Thu, 17 Jul 2003 11:11:44 +0100
    
    

    That's great guys. Thank for all the great suggestions and advice!

    -- 
    Peter Wright
    Author of ADO.NET Novice To Pro, from Apress Inc.
    _____________________________
    "Durand" <not@an.invalid.address> wrote in message
    news:OjOgl%23ORDHA.2432@TK2MSFTNGP10.phx.gbl...
    > Pete,
    >
    > Create an account on your WS2k3 with the same name and password on your
    current
    > XP machine. Then on your XP machine, change the network name to domain and
    make
    > it the same domain name as your server. Then login your XP machine to join
    the
    > domain and you should not be presented with an option to create another
    account
    > on the XP machine. It really is that simple, from my experience with ws2k
    and
    > NT4 networks. The settings on your client machine you have will not
    change, but
    > if you still have doubts, set the XP machine in a workgroup with the same
    name
    > as your domain, and you'll still have the server controlling access to the
    > network though not all aspects of it as if it were joined to the domain.
    You do
    > not need to worry about having to go thru the trouble of creating new
    profiles
    > for joining the WS2k3 machine.
    >
    > -- 
    > Regards,
    >
    > Durand
    >
    > ________________________________
    > "Pete Wright" <pete@codemonkey.demon.co.uk> wrote in message
    > news:be91df$672$1$8302bc10@news.demon.co.uk...
    > Hi all,
    >
    > I'm fairly new to the server scene (well, actually, I'm completely
    > clueless), so bear with me here.
    > On my home network I have an XP Pro machine that has always been part of
    my
    > home network's workgroup. I log on to the client machine with my user name
    > and password and I have all my settings right where I left them.
    >
    > I'm now installing a Windows Server 2003 server on the network which
    ideally
    > I'd like to control all aspects of security. Now, even in my state of
    > complete stupidity I know that to utlise the active directory based
    security
    > features of Win2K3, I have to log into the domain from my XP machine. I
    have
    > a feeling though (seen it at work) that when I do this, I'm going to get
    > another user account on my XP machine with completely different settings
    etc
    > from my old one.
    >
    > Is there any way to configure either the XP client or the server so that
    my
    > new Domain account picks up all my old local client account stuff?
    >
    > Sorry if this has been asked a thousand times (I have looked, and can't
    find
    > anything that precisely matches what I want to do), and thanks in advance
    > for the help.
    >
    > -- 
    > Peter Wright
    > Author of ADO.NET Novice To Pro, from Apress Inc.
    >
    >
    >
    

  • Next message: Kristofer Gafvert: "Re: Microsoft Security Bulletin MS03-026 - 823980"

    Relevant Pages

    • Re: Logon Server Unavailable
      ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
      (microsoft.public.windows.server.general)
    • Re: Logon Server Unavailable
      ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
      (microsoft.public.windows.server.dns)
    • Re: Logon Server Unavailable
      ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
      (microsoft.public.windows.server.networking)
    • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
      ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
      (microsoft.public.windows.server.sbs)
    • Re: User getting "Account is Locked Out" for 2 days
      ... Then pull the network cable from that system to disconnect ... making this local profile newer than the one on the server. ... out what is going on...i have gone into his account and unchecked ...
      (microsoft.public.windows.server.sbs)

  • Quantcast