User profile does not replicate to Server
-
Of course... I expect he'll be in the office on Sunday and this to be fixed.....
-
anything in the event log?
-
Ping?
-
The user didn't somehow get moved in to the domain guest group did they? That will wipe a profile at logout.
-
Well this is an odd one. I believe there is something a tad off with AD.
So, worked on it a while longer last night and 'got through it'. In a weird and not so 'standard' way.
The user is in their own container as they are the business owner. They have different security than everyone else. I didn't set this up, it's what we have to work with.
Copied the user to a new user to save the security credentials. That worked perfectly. The new user created the user folder in the \server\redirect\ folder. Great possible way to resolve this once and for all. Users folder 'moved' on the server, and traces of the users profile removed from the two primary computers - ones I'm worried about the most.
Deleted his old user (thuser) and copied the new user back to ADUC\thuser.... sign in and nope didn't work. It didn't create the users folder on the server... odd,... why is that?
Went back and again copied the copy to a new user ADUC\th1user - signed into the th1user account and it created the folder as it was suppose to. Very odd.
So, as of now, the User is using TH1User and has all his folders and files.
My guess is that the Domain and AD is a bit screwy.. We are trying to convenience them that :
- AD is messed up and needs a new build
- Server has experienced some issues in the past, subject to possible issues and needs to be replaced.
- Some things need to be changed to conform to MS Best Practices for smoother operation and reliability.
-
I wonder if you have a drive problem. The old thuser folder used to exist, there might be problem at the drive level that is preventing the old one from truly being deleted, etc.
just a thought. -
@Dashrender said:
I wonder if you have a drive problem. The old thuser folder used to exist, there might be problem at the drive level that is preventing the old one from truly being deleted, etc.
just a thought.It's long been suspect that the AD has corruption in it. It's been proposed to the client to flush the server and restart. regretably this has been rejected - as the proposal for a replacement server as the current one is a tad limited and close to exceeding it's limits.
Short term fix is to flush the user and create a new one. all seems to working but since the OTS (One Time Setup) is more than he can stand,.. well.. The issue isn't an issue any longer.
Thanks -
-
Isn't this a client who was fired? Problem fixed!
-
-
@scottalanmiller said:
Isn't this a client who was fired? Problem fixed!
Yup... unfortuneatley the client refused to put in the hardware and required all updates to all machines be shut off, and requested all machines be rolled back from 10 that he hated....
