K
KearneyB
Guest
I'm having a problem with a network logon searching for a roaming profile
even though the roaming profile path has been deleted from the user's
properties on the server.
Problem began when my PDC hard drive crashed and I wound up having to
reformat and rebuilt a new PDC server from scratch, though the roaming
profiles were stored on another drive that was not lost.
However, in the new AD, I did not recreate the roaming profile path, but
when the user logs on to the network, he's told his roaming profile cannot be
fround.
I went into the work station and checked the USER and deleted the RP path,
but the problem persists. It also happens when I try to log on as that user
from any other computer in the network.
So how can I get rid of this "ghost" of a roaming profile?
even though the roaming profile path has been deleted from the user's
properties on the server.
Problem began when my PDC hard drive crashed and I wound up having to
reformat and rebuilt a new PDC server from scratch, though the roaming
profiles were stored on another drive that was not lost.
However, in the new AD, I did not recreate the roaming profile path, but
when the user logs on to the network, he's told his roaming profile cannot be
fround.
I went into the work station and checked the USER and deleted the RP path,
but the problem persists. It also happens when I try to log on as that user
from any other computer in the network.
So how can I get rid of this "ghost" of a roaming profile?