P
Peter
We did a domain rename a while back, that we thought was succesful. All steps
were carried out succesfully, but apparently there is something not right.
Looking at file security at clients and servers, they still reflect the old
domain name (ie user@olddomain.se and not user@newdomain.se). If we try to
set domain rights and search the user, it searches within the newdomain, but
still register the file/directory security as the @olddomain.
Normal processing is not a big problem, but copying files f.ex. sometimes
gets wrong security identifiers. - So I have a feeling something is dead
wrong with the AD and file rights matching. We don't have any distributed
file shares within the AD, but I went into the NTFRS console and there is no
root - is this a problem - or where do I start my investigation?
We have not yet renamed the domain controllers, so they still reflect the
old dns names, and yes the old dns structure is intact - should I remove all
pointers except the DC A hosts?
--
Kind Regards / Peter
were carried out succesfully, but apparently there is something not right.
Looking at file security at clients and servers, they still reflect the old
domain name (ie user@olddomain.se and not user@newdomain.se). If we try to
set domain rights and search the user, it searches within the newdomain, but
still register the file/directory security as the @olddomain.
Normal processing is not a big problem, but copying files f.ex. sometimes
gets wrong security identifiers. - So I have a feeling something is dead
wrong with the AD and file rights matching. We don't have any distributed
file shares within the AD, but I went into the NTFRS console and there is no
root - is this a problem - or where do I start my investigation?
We have not yet renamed the domain controllers, so they still reflect the
old dns names, and yes the old dns structure is intact - should I remove all
pointers except the DC A hosts?
--
Kind Regards / Peter