Discussion Locked

XP profiles mandatory and locally

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear all.

I have an Windows Server infrastucture domain.

I have a computer lab that I want to set up with Windows XP.

The PCs are joined to the domain and I have created a mandatory profile on one of my servers.

This solution works. But, it is a single point of failure because if the server goes down then nobody can login.

Could you tell me how to set up a common user profile locally that will be loaded from c: local drive.

The ideal solution is to configure it locally (C: drive) and then assign to all domain user accounts the same local profile path at the Windows Server profile tab. Thus, whenever someone logs in, the Windows Server instructs the domain account to use the profile from C:\. With this solution I avoid the single point of failure problem.

I tried to do it by creating a profile on the local driver c:. Then I configured the profile path at the domain server but whever I try to log in from a client PC using a specific domain account, it says that "the system can not find a roaming profile and will use a temporary one. There is problem with the permissions. The owner of the folder containing the folder on the local driver C: must be the DOMAIN administrator". Something like that.

The only way to do that is to logon locally to the client PC as a DOMAIN administrator and create the profile locally in order to fulfil the XP request for ADMINISTRATOR ownership.

For security reasons I want to avoid logging in to the client PC as a domain admin.

Any ideas?

3 replies

by kenv

This paragraph is not very logical as you describe it:
The ideal solution is to configure it locally (C: drive) and then assign to all domain user accounts the same local profile path at the Windows Server profile tab. Thus, whenever someone logs in, the Windows Server instructs the domain account to use the profile from C:\. With this solution I avoid the single point of failure problem.

Is there more than one server? If the server is down, it won't "instruct" anything.
If the clients log into the domain (with a standard, roaming or mandatory profile), a local profile will get created. If the server is not available (on subsequent logins), the client should still be able to log in with cached credentials.

This discussion is closed to new replies.