Tony D
asked on
How to create a roaming profile in windows server 2008 R2 workgroup?
{{I tried a domain and it is to restrictive and dropping maps and user access...
How many times am I supposed to give access to a user and shares..}}
So I went to a workgroup environment with a single windows 2008 r2 server with 13 users with 3 with administrative rights and others with differing rights. Is there a best way to setup roaming profiles in this workgroup environment.
How many times am I supposed to give access to a user and shares..}}
So I went to a workgroup environment with a single windows 2008 r2 server with 13 users with 3 with administrative rights and others with differing rights. Is there a best way to setup roaming profiles in this workgroup environment.
Unless I'm missing some sort of special need, set them up like you would on a domain. If you need instruction: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/dd805fa7-3d3e-4e77-9533-bc38b3fbc597/
What are you talking about a domain being too restrictive? It sounds like you don't understand domains. Workgroups are HORRIBLE with way too many complexities to get them working right and solidly.
What exactly do you want roaming? a Roaming profile is something I NEVER recommend. Folder redirection is the best option. To setup for 13 users, you can go to each user, on each machine, and configure their accounts to point to a network share for their folders. This should take at least 6 hours for 13 users and machines... potentially longer if your users "roam" between machines. If this were a domain, it would take about 13 minutes. If that as it's a simple group policy setting where you pick what folders you want redirected.
What exactly do you want roaming? a Roaming profile is something I NEVER recommend. Folder redirection is the best option. To setup for 13 users, you can go to each user, on each machine, and configure their accounts to point to a network share for their folders. This should take at least 6 hours for 13 users and machines... potentially longer if your users "roam" between machines. If this were a domain, it would take about 13 minutes. If that as it's a simple group policy setting where you pick what folders you want redirected.
Agree with leew, not sure what difficulties you ran into.
Though I have setup roaming with folder redirection.
When users can use any combination of systems/workstations roaming profiles make sense in preserving their setting/configuration.
Also simplifies things during the workstation renewal cycle.
Presumably the issue with the domain you had was not that the workstations you have can not join a domain (home versions).
Though I have setup roaming with folder redirection.
When users can use any combination of systems/workstations roaming profiles make sense in preserving their setting/configuration.
Also simplifies things during the workstation renewal cycle.
Presumably the issue with the domain you had was not that the workstations you have can not join a domain (home versions).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
There is a GPO setting that when sets deletes the cached profile after a successful logoff.
Per user hive profile tool is needed. For older xp systems, while the feature is included in windows 7.
Roaming profiles with folder redirection are often maxing out in the 10s of MB.
Using local profiles runs into the same issue of having profile data accumulate.
Seen profile corruption ntuser.dat which leads to slow logon/logoff times. Redirected folders with offline access contribute to this as well if set.
Per user hive profile tool is needed. For older xp systems, while the feature is included in windows 7.
Roaming profiles with folder redirection are often maxing out in the 10s of MB.
Using local profiles runs into the same issue of having profile data accumulate.
Seen profile corruption ntuser.dat which leads to slow logon/logoff times. Redirected folders with offline access contribute to this as well if set.
>There is a GPO setting that when sets deletes the cached profile after a successful logoff.
Can you site reference material? Although this doesn't help and can potentially hurt in the event a person is logged on to two or more systems. If caught (and if files are saved to the profile) the local profile becomes a kind of backup. VSS can mitigate this to some extent, but even if used, at the end of the day, in my opinion, folder redirection does a MUCH better job at allowing a user to roam between machines, keep logon times minimal, and avoid data corruption than trying to use some form of roaming profile.
> Using local profiles runs into the same issue of having profile data accumulate.
To an extent, but historically, profiles include huge amounts of data in My documents and the Desktop - if these are redirected, the amount of data that ends up created/stored on the local machine is FAR less than a roaming profile
Can you site reference material? Although this doesn't help and can potentially hurt in the event a person is logged on to two or more systems. If caught (and if files are saved to the profile) the local profile becomes a kind of backup. VSS can mitigate this to some extent, but even if used, at the end of the day, in my opinion, folder redirection does a MUCH better job at allowing a user to roam between machines, keep logon times minimal, and avoid data corruption than trying to use some form of roaming profile.
> Using local profiles runs into the same issue of having profile data accumulate.
To an extent, but historically, profiles include huge amounts of data in My documents and the Desktop - if these are redirected, the amount of data that ends up created/stored on the local machine is FAR less than a roaming profile
A local profile actually will be larger than a roaming profile both having folder redirection.
The difference will be the user profile temp location which is discarded with roaming profiles while retained in local profiles.
http://technet.microsoft.com/en-us/library/cc781862(v=ws.10).aspx
I am not disagreeing on the folder redirection part.
Roaming profiles helps maintain the same settings for the user as well as simplify transition from old system to new system to a point.
The difference will be the user profile temp location which is discarded with roaming profiles while retained in local profiles.
http://technet.microsoft.com/en-us/library/cc781862(v=ws.10).aspx
I am not disagreeing on the folder redirection part.
Roaming profiles helps maintain the same settings for the user as well as simplify transition from old system to new system to a point.
ASKER
The problem I had with the domain setup is it kept losing the map to the app folder and logon problems. So that is why I went with a workgroup setup. Seeing there is only one server, I thought this would solve the mapping issue. (And so far it has and no more logon issues either!) The’ Roaming issue’ is this several users log on to different computers, not all users. I need to restrict access to the users to certain folders wherever they logon to...
Virtually all computers are older in a win7 and xp o/s.
Virtually all computers are older in a win7 and xp o/s.
ASKER
;;;of course win7 and xp are all updated and professional version.
ASKER
You mean I am the only one that has had problems on a domain with loosing map settings and log on issues with multiple users using the same workstations?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.