Re create a roaming profile

Nutbusta · 27 May 2006 at 08:49

I'm currently having rather hit and miss results when trying to re create roaming profiles. I was hopeing somone could just check my process for any floors:

1. have the user reset their machine or using Dameware log in myself.

2. Browse to the profile on both the local machine and the server and rename then.

3. Get the user to log on resulting in a new share being create on the server and profile folder on the client machine.

4. I then set the permissions on the share by removing inheritence and giving the user full control. This is set to propagate down to child objects.

5. I then copy everything (from the renamed server profile) but app data and the ntuser to the users profile folder.

My thinking being that when the user logs off the new profile will be uploaded to the new empty server share and eveything should be peachy. This doesn't always up/down load properly. Any floors in my plan?

masterk · 27 May 2006 at 10:53

When i do it i sometimes have to reset the permissions 2 or 3 times to get it to work for some reason.

Also i wouldnt copy anything over but desktop shortcuts, gets too messy otherwise.

Nutbusta · 27 May 2006 at 11:01

masterk said:
When i do it i sometimes have to reset the permissions 2 or 3 times to get it to work for some reason.

Do you set the permissions from your machine or MSTSC into the actual server that hosts the share?

masterk said:
Also i wouldnt copy anything over but desktop shortcuts, gets too messy otherwise.

Any particular reason? is it quite easy to copy the file which is causing problems?

masterk · 27 May 2006 at 21:46

I normally set the permissions from the machine i am on over the network.

Profiles tend to get corrupted a lot for me, and its always a file or two you wouldnt suspect, i just do a brand new fresh profile, all the user would have to do is configure their outlook and pst files anyway.

Nutbusta · 28 May 2006 at 10:32

You may find that if youset the permissions from the machine your working on it can take a while for the changes to propagate through the network. About 20 minutes with the network I work on.