Re: Upgrade from W2K Server to Server 2003 "gotchas"...



In news:utwRW2XvFHA.1436@xxxxxxxxxxxxxxxxxxxx,
Gib Curry <admin@xxxxxxxxxxxxx> typed:
> It began with an inability to run Update for my Win2000 Advanced
> Server....
> After spending far too much time researching that and trying to fix
> userdata persistence, I decided that it was time to just upgrade to
> Server 2003.
> I put the CD in and installed "over" the existing Win2000 Advanced
> Server because you can't simply upgrade!??!

Yes you can.
>
> Thus, all my data is just fine, thank you, but, there were no Users or
> Computers. Makes sense.

No, not to me, unless you did a clean install. You should've been able to
upgrade in place. Were you upgrading to W2003 Standard or Advanced? You can
go from advanced --> advanced in place. If you were trying to go from
Advanced-->standard, that might explain it - but I have honestly never tried
this.
>
> So, everything gets set up. I go to the first workstation and try to
> logon. I did it, but not until I had hopped through a lot of weird
> hoops.
> Of course, the Administrators password on the workstation is
> "different" than the new server password

As it should be anyway - your domain admin credentials shouldn't be the same
as your local workstation credentials, for security reasons.

> - the new server following
> the strong password protocol of upper/lower alpha and numeric
> characters.
> I finally got the Administrator logged on from the workstation to the
> new server. Then, I joined the new domain and tried to add the first
> user.

Add the user where? ADUC? You do that on the server.

You shouldn't have had to create a new domain.
>
> It appears that a whole new profile was created.

Yes, because you have a new domain.

> So, I did the whole
> copy the folders from user's directories to the new one. That
> worked, but all the applications wanted to be reinstalled.

What applications?
>
> So, I did the registry edit and pointed the logon to the old user
> directory. That worked. Now, the first workstation logs on just fine
> and looks and acts just the way it did before, but with perhaps a
> noticeable decrease in wait times.
>
> On to the second workstation; mine. I've spent all day and tried all
> the above and then some.
>
> I can ping the gateway, the server, the first workstation. I can
> logon to my local machine accounts (Administrator and mine) but not
> the network accounts.

If you haven't joined the domain yet, that makes sense.

> I can see the accounts listed in the console
> and can even (sort of) change the passwords.

Local accounts? What does "sort of" mean?
>
> But that doesn't really get me anywhere because, I can't get the
> machine to join the domain. No matter what account I logon with I
> get the same error. "Your computer could not be joined to the domain
> because the following error has occurred: The specified server
> cannot perform the requested operation. OK"

Can you change to a workgroup, and then reboot, and then login as local
admin and join the domain?
>
> Well, no, not OK.
>
> I'll need at some point to also deal with changing my logon from the
> old, lowercase, seven letter password to a new upper/lower case +
> number format.
> Thank you, in advance, for any light shed on this dark little
> issue.....
> For Now,
>
> Gib Curry

Sounds as though you're painted into a corner here, to a degree. I'm a bit
confused as to where you've ended up - if you're really in a tight spot, you
might want to call PSS.

Check your DNS, too.


.

Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: DCOM Errors in Event log
    ... A time difference between the workstation and the server do you? ... An error occurred during logon ... Les Connor [SBS Community Member - SBS MVP] ... on the server in the security log we are getting error 537 in the event log. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 537
    ... Nothing on workstation has changed, although I have recently applied SP1 for the SBS2003 server. ... I have around 2000-3000 errors in my event log. ... An error occurred during logon ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... I know this may just be you, but note that a) workstation hardware isn't a ... of my POP3 e-mail accounts as an Exchange Server account. ... Are you using Outlook 2003, and using the Folder List view in the navigation ...
    (microsoft.public.windows.server.sbs)
Loading