Re: New Hardware, same domain name

KMD <KMD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Ok, I had a server die on me, no data loss, I Have good backups.

So I built a new server and loaded up 2003 sbs using the same domain
name and server name. The old server had so many problems before it
died that I didn't want to inherrit much from it other then the data
for some programs and the emails. Most of the workstations (WS)
didn't have a problem going to the new domain, but a few of them are.

This is how I attempted to do it.

1. Logged in as the local admin account on the WS and joined a
workgroup named temp.

2. Restarted the WS

3. Logged in as the local admin account on the WS and joined the
domain (same name as the orginal domain)

Did you use /connectcomputer?

4. Restarted the workstation and logged in as the domain admin.

5. Edited the registry on the WS to point to the old profile.

I don't do that, myself. I think that's your problem - because the domain
name is the same. For future reference, here's what I do:

-----------------------
While the computer is still in domain A, create a local user account.
Log in as the local user account.
Log out.
Log back in as an account with admin rights (but *not* the real domain user)
Go to control panel, system, advanced....in User Profiles, click the
Settings button
Select the domain user's profile, click on Copy To, and browse to the new
local user's c:\documents and settings\username folder.
Click OK.
Click the Change button in Permitted to use and select Everyone
Close out.
Log in as the local user and make sure the settings look right.

If so, you should be good to go...disjoin the computer from the domain,
making sure you know the local admin credentials....and then run the
/connectcomputer script. When asked which local account settings you want to
assign to the 'new' domain user on domain B, select the local user you just
created.
---------------------------


6. Logged in with the username who usually used that WS and all
their old files

My $.02 ... use folder redirection so there's not much in the
profile.....for My Documents, Application Data, and Desktop, to
\\server\users\<foldername>. I use custom GPOs for this, and also disable
offline files.. You really need to keep your profiles miniscule, even if you
aren't using roaming profiles.

and such seemed to be there and everything looked
good.

For the most part, this worked fine, but a few WS are having issues.

My workstation for instance can't access the network shares. The
files are shared correct, I can access them from other workstations.
I get a access denied message even though my account is a domain
admin account.

I don't want to have to reload these workstations, any idea what the
problem or solution might be? Thanks.

I'd wipe out the problematic profiles entirely & let them be recreated at
the user's next logon to see if this helps....copy out the data first to the
server.



.

Loading