Ian,
I have two suggestions for you, but I have not actually implemented either
of them so I can't guarantee they will be ideal.
1. use %logonserver% in the path for the profile:
Explanation:
If you go to the command prompt, and type 'set', then press enter, the
entire list of paths/variables that are in use for that session are listed.
One of them is Logonserver. Create an identical profiles folder on each
server active directory server, and make sure it has the same share name on
each server. Which ever server the user logs onto, the name of that server
becomes the Logonserver variable....and hence %logonserver% can be used. In
the properties of the user account, set the profile path to be
%logonserver%\sharename\%username% (note here that sharename and %username%
are to be changed to whatever you use). There shouldn't be a need to put
'\\' at the start of it.
You will need to ensure that the profiles are on all Domain Controllers,
otherwise, the user will logon, the server name of the AD server they are
attached to becomes the value of %logonserver%, then they wont be able to get
the profile if it's not there.
2. Use distributed file system (DFS):
Explanation:
I beleive (not 100%) that when you set up DFS, you can specify multiple
sources for the DFS shares. You could setup a DFS share that has two sources
(the sources being shared folders on different servers, containing the
profiles). If one server is not available, the profiles will be available
from the other. In the user account in AD, set the profile path to be
whatever the path is for the DFS share that you create.
I really hope that the above helps you. I will willingly help further.
I've only ever considered these, but we are yet to try implementing it. If
you do give it a go, I'll be very interested to hear the outcome.
Cheers
Dan
(e-mail address removed)
