R
Roger Vicker, CCP
Hello,
I've just gotten into an upgrade that is giving me a small problem.
Current configuration is a WinNT 4 server (as the PDC) with three W2k
workstations. All end users were setup as roaming users (profile path
pointed to a server folder). It serves just as a file/printer server and
proxy server using the modem to get to the internet. The server's tape
backup was beginning to not always work when the video (or drivers)
failed. Therefore I can not log onto the server (well actually can but
can not see what I am doing) to make any changes or run programs to
assist in the below migration. There was no ERD created so we can't even
install a new video card to replace the integrated video because we
can't install the drivers. We have a new Windows 2003 server to replace it.
I have successfully transfered all the data files to the new server
(including the profile folders) using existing shares and setup new
users in Active Directory that match the old server. I have set the
"Profile Path" in each new user to point to the profile folder on the
new server where I have copied the files from the old server. All
permissions for the shares and data folders have been re-created. ICS
has been activated on the modem instead of the old proxy software.
The problem is that when the W2K workstation logs into the new server it
generates an error message that Explorer has failed and an Event Log
entry is being generated. Over and over and over and over... until
CTRL+ALT+DEL is used to log off the user or the whole PC crashes. If I
create a new user without loading anything into the profile directory it
can be used to log onto the W2K workstation but of course there are no
personal settings.
What would be the effective way to get the users on the new server
without them having to re-do everything in their profile? I could even
live with getting the workstation to copy the profile to it (as a local
user??) and then after the new server is in place moving it back to the
server.
I can get by with addresses of on-line documentation of how to do this
in a similar situation.
Thanks.
Roger Vicker, CCP
I've just gotten into an upgrade that is giving me a small problem.
Current configuration is a WinNT 4 server (as the PDC) with three W2k
workstations. All end users were setup as roaming users (profile path
pointed to a server folder). It serves just as a file/printer server and
proxy server using the modem to get to the internet. The server's tape
backup was beginning to not always work when the video (or drivers)
failed. Therefore I can not log onto the server (well actually can but
can not see what I am doing) to make any changes or run programs to
assist in the below migration. There was no ERD created so we can't even
install a new video card to replace the integrated video because we
can't install the drivers. We have a new Windows 2003 server to replace it.
I have successfully transfered all the data files to the new server
(including the profile folders) using existing shares and setup new
users in Active Directory that match the old server. I have set the
"Profile Path" in each new user to point to the profile folder on the
new server where I have copied the files from the old server. All
permissions for the shares and data folders have been re-created. ICS
has been activated on the modem instead of the old proxy software.
The problem is that when the W2K workstation logs into the new server it
generates an error message that Explorer has failed and an Event Log
entry is being generated. Over and over and over and over... until
CTRL+ALT+DEL is used to log off the user or the whole PC crashes. If I
create a new user without loading anything into the profile directory it
can be used to log onto the W2K workstation but of course there are no
personal settings.
What would be the effective way to get the users on the new server
without them having to re-do everything in their profile? I could even
live with getting the workstation to copy the profile to it (as a local
user??) and then after the new server is in place moving it back to the
server.
I can get by with addresses of on-line documentation of how to do this
in a similar situation.
Thanks.
Roger Vicker, CCP