Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3757
  • Last Modified:

How to make a local profile roaming even though option is greyed out

I need to know how to make a roaming profile from a local profile on an existing terminal server.  Nearly all of the profiles are local and I can not change them to roaming, as the option is greyed out.  I can not put the roaming profile path in their AD account because the roaming profile is only for this terminal server (for DR purposes).  Putting the profile in this field would cause problems with their regular login at their desktop.  How can I get the local profiles on this server to become roaming?  I have the proper permissions on the folder and I have group policy set up to apply for this Terminal server.  

Any help would be appreciated.
0
HeitmanProgrammers
Asked:
HeitmanProgrammers
  • 5
  • 5
  • 2
1 Solution
 
Hypercat (Deb)Commented:
If your group policy is in place and you have set up a shared folder for the roaming profiles, then go into the User profile manager tab on the TS and simplyi delete all of the old profiles. As long as the GP is set correctly and the folder permissions are correct, the new roaming profiles should automatically be copied from the roaming profiles folder to the server's Documents and Settings folder the next time the user logs on.
0
 
Rant32Commented:
Terminal Services has a dedicated option for roaming profiles that are only used when logged in with Remote Desktop.

It's in Group Policy | Computer Settings | Administrative Templates | Windows Components | Terminal Services | Set Path for TS profiles

You can literally enter \\server\share\profiles\%username% et voilĂ .
0
 
Rant32Commented:
Correction: do not add the user alias to the profile path (look at the setting's help)

Oh, I recommend using a different path/folder for TS profiles than regular roaming profiles, in case the user does have an existing roaming profile in their AD account.

The TS roaming profile setting takes precedence of the other roaming profile.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
HeitmanProgrammersAuthor Commented:
I have the Set Path for TS Roaming Profiles Group policy set to enabled with the UNC path listed.  The user I'm testing with has access to the share.  The path is listed as \\Server\share$\%USERNAME%.

Deleting the profile from the User profile manager just causes a new one to be created as a local, with Roaming still greyed out unfortunately.
0
 
Hypercat (Deb)Commented:
Is there a profile for that user with his/her user name and the correct permissions created in the roaming profiles shared folder? IIRC, my experience is that it won't work unless there is actually a folder there already. A local profile will be created initially, then should be synched to the roaming profile location when the user logs off. You have to go through at least one logon/logoff process for the roaming profile to be created. Then the next time the user logs on his/her profile should show up as "roaming."
0
 
HeitmanProgrammersAuthor Commented:
That does not work.  Doing a "Copy To" to that location does not work.  The profile will not allow me to change it to roaming.  I've logged on 2 times each time I test as well.
0
 
Rant32Commented:
Please verify with the GPMC Result wizard that the policy and correct TS profile path get applied.

Copying the profile folder manually does not usually work, because the system will check the ownership of the profile folder. The folder must be created by the user. There is a policy to disable that check but I don't recommend it.

http://support.microsoft.com/kb/327259

If you have just created the share, check that the share permissions allow Full Control :)
0
 
HeitmanProgrammersAuthor Commented:
I don't see it when I run the Group Policy Results wizard.  I have Loop Back processing on with it set to Merge.
0
 
Rant32Commented:
It's a computer setting, so you should refresh the policy change with a 'gpupdate'.

Loopback processing only applies to user settings.
0
 
Rant32Commented:
Mmh, it should have applied naturally by now?

Probably should mention it, just in case you have modified the permissions on the Group Policy Object to apply the policy only to selected groups (as is sometimes the case with loopback processing): the Terminal Server must also have the permission to apply the policy.
0
 
HeitmanProgrammersAuthor Commented:
I'm applying the policy to an OU that only contains the Terminal Server.  In the security filtering I only applied the user name.  I'll apply the Terminal Server name and try again.  I have to wait for replication to take effect however.
0
 
HeitmanProgrammersAuthor Commented:
This solved the problem.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now