Home Folder with Roaming Profile

The problem is unless you spend a lot of money on a multi-system access file system, your profile is limited to that one server.   It really defeats the purpose of a home directory which you want universally available to you on the network.


Coralon

Can you please explain this a little better to me.  I have had 2 other technicians look at your response and we just don't understand what you mean in your answer.  If you could explain it  I would greatly appreciate it.  I will try to clarify what we are doing also.  We are moving from a NDS environment to an AD environment.  Our users are used to having mapped drives for personal storage.  I know this can be accomplished with a home folder and with folder redirect.  My concern was that with mapping a network drive (shown in screen shot) is that if the map is disconnected for some reason then the setup does not good.  If it appears as a logical drive then there should not be an issue.  I know how it needs to be setup but our network admin does not and need some expert advice on how to convince them that it is easier with a GPO that to manually do it the way they want to.

Yes we are and I do understand that the Home Folder will be a mapped drive.  Our network admin has taken an un-used domain server that was going to be used for VDI and using the storage allocated to that server as the home directory location by sharing out the root then manually mapping out a drive to each user.  We do not have a file server that is the sole purpose of providing storage.  He is creating every users folder on that share and then mapping a drive to each users pc instead of allowing a GPO to do this.  We have approx. 500 users that we are migrating over the next few months and this will be very time consuming that way he is starting it.  I need some form of help in helping him understand that there is an easier way to do things.  Also the screen shot is of the DC and the mapped drive is from the VDI server.  My suggestion was to have to DC have a LUN on it and not a networked mapped drive to be configured on another server as to the permissions and such would not reside on the same server.