Re: what is the correct procedure to join a worsktation to a domain

I did that and roaming profile does not update nor the script. I checked the
event view in the workstation with those errors

"AllenM" wrote:

You should have done this before you installed the fresh OS. Is the computer
account still visible in AD? Probably so which is why you cannot use the
same computer name. Delete the computer from AD first before rejoining the
domain.


"Martin_C" <MartinC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA441F9A-ECCB-41F9-AB05-A4118F2AD5E1@xxxxxxxxxxxxxxxx
Well the fresh install OS is already in WORKGROUP. I did all those work
because my sbserver gives an error when i join to the domain with a
duplicated computer name error. Well, every single user in our domain has
a
roaming profile except admin account.

"AllenM" wrote:

Seems like you did a lot of work just to remove a computer from the SBS
Domain. Pretty much just join a WORKGROUP and remove the computer account
from AD. The user roaming profile has nothing to do with the computer
account. Nor does the login script. Checkout the properties for the user
account in AD and make sure he does have a romaing profile and that the
SBS
Login script is part of his profile.

"Martin_C" <MartinC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:005AB194-ADF8-434B-9B49-47CB211D4E9A@xxxxxxxxxxxxxxxx
What I did:
1. replace old workstation ws21 HD to bigger one.
2. install fresh OS.
3. did not unplug the network connection.
4. rename user21 romaing profile on the sbserver to tempuser21
5. join to the domain. Prior joining the domain, i erased the
workstation
ws21
from the sbserver and from the active directory. Change
workstation
computer
name to ws21 and reboot. Join workstation ws21 to domain.
6. Change user21 password on sbs server
7. logon to ws21 with domain administrator account and copy user21
profile from
old HD to C:\Documents and Settings
8. reboot and logon to ws21 with user21 account

Symptons:
- logon script does not run on user account (administrator account
works)
- user roaming profile can not be updated in the server.
- On Event Viewer on client workstation:
usernev Event ID: 1030, 1006
LSASRV Event ID 40961

I did some research on these event ids and it seems my workstation with
windows sp2 is not communicating correctly with the server.

Is there anyway to avoid this roaming profile problem or I did
something
wrong?







.

Relevant Pages

  • Re: what is the correct procedure to join a worsktation to a domai
    ... roaming profile except admin account. ... The user roaming profile has nothing to do with the computer ... replace old workstation ws21 HD to bigger one. ...
    (microsoft.public.windows.server.sbs)
  • Re: Command line error on W2K, but NOT on XP.
    ... The script runs great on the ... but when I tried it on a W2Ksp4 workstation I get an error ... I verified the account does exist on this workstation. ...
    (microsoft.public.scripting.vbscript)
  • Re: Trust relationship between this workstation and Primary Domain
    ... it, with a new computer ID, a new workgroup ID, but again to no avail. ... password policy, renamed admin account, automatic updates are controlled by ... * PLEASE post all messages and replies in the newsgroups ... "Workstation ...
    (microsoft.public.win2000.networking)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... account is NEW to the workstation. ... needs admin group priv at workstation level. ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... The DNS Zone for your AD Domain must be DYNAMIC, ... Client computer must use STRICTLY the INTERNAL DNS server which can ...
    (microsoft.public.windows.server.active_directory)