Re: Moving Roaming Profile



There is a GPO setting to add domain admins to the roaming folder. It
is under computer config, admin templates, system ,user profiles and
is call "Add the Administrators security group to roaming user
profiles.

The only problem is this only affects new profiles. you'll have to
take control of the directory where the profiles are stored and then
redo permissions.

Jeff Pitsch
Microsoft MVP - Terminal Services

On May 13, 11:00 am, lozza <lo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hey Jeff,

I've just run into another issue while looking into this a little more. The
user profile share although it has Domain Admins full control on this
folder/subfolder/files... I still cannot for some reason access the user
profile folder and when I copy and paste it over to the new location... it
goes over as a blank empty folder... any ideas why this is happening?

Lozz



"Jeff Pitsch" wrote:
I would do what you said.  If you don't, and you let users on and
everything is screwed up, you've seriously inconvienced the users if
not upset them outright.  How much downtime will it then take for you
to put everything back?  Not long but you need to tell the users more
downtime is needed and they can't work.  Lost work, lost money.  You
are much better off creating those users ahead of time and testing
with them after you move everything.  Then if things are messed up,
you switch everything back and the users never know the difference.
You then figure out what went wrong, correct the mistake and try
again.

Jeff Pitsch
Microsoft MVP - Terminal Services

On May 13, 9:58 am, lozza <lo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Jeff,

Thanks your response... very much appreciated. I would like to test but I
struggle in understanding how I would test and revert back if it doesnt work,
because all my redirection settings and roaming profiles locations are done
for all users via GPO. So in this sense, it is a move all users folders at
one go or not.

I guess before allowing users to log on I could create some test users
beforehand hand, create some folders on their desktops, my docs folder etc
etc and then do the move and see if they still exist, once logged in....
before letting any end users back on.

I guess then, if this doesnt work... I just set the redirection locations
and profile locations back to their original location and and everything will
kick in... what I dont want in the xxxxxx.001 profile that gets created
sometimes for some reason.

Thanks
Lozza  

"Jeff Pitsch" wrote:
That looks good but you're missing a very important step which is
doing due diligence and testing, testing, testing.  Before I would
allow any users on the system i would test everything out with a test
user or two to make sure it still all works.  Other than that, i think
it looks good.

Jeff Pitsch
Microsoft MVP - Terminal Services

On May 13, 8:57 am, lozza <lo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Guys,

Looking for some tips here if possible. I have roaming profiles enabled and
redirected folders enabled on my Terminal Servers via GPO to a dedicated
resilient file server. I have created the shares these folders are stored
under using the permissions structure explained in Article ID: 274443.. I also
keep the cached copies of roaming profiles on the servers just in case. I
have about 500 users balanced across 8 nodes in a cluster

Now my issue is the file server is being decommisioned and I'm a little
concerned about the sequence of steps I need to take to move these roaming
profiles and redirected folders safely without losing user data.

Would the following be a good plan of action:

1) Request downtime for whole TS Environment
2) Shutdown all TS Servers (to release any locks on profile/redirected
folders preventing copying)
3) Create the top level shares again using Article ID: 274443
4) Copy and paste the roaming profiles and redirected folders (desktop, My
Documents, App Data) to their respective top level shares
5) Ammend the GPO targeted to the TS Servers for roaming profile and
redirected folder locations to new locations
6) Restart TS Servers
7) Allow users to start logging on and their profiles and redirected folders
will be in tact and now available from the new location.

Or have I got the procedure horribly wrong? Any assistance to ease my
confidence would be greatly appreciated.
Lozz- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

.



Relevant Pages

  • Ive had it! Cannot get the users to roam correctly
    ... I need to create id's that where all the information is roaming AND the ... DO I need to redirect the folders if under user properties I set up roaming ... Documents and settings folder instead of my custom Profiles folder? ...
    (microsoft.public.windows.server.sbs)
  • RE: Group Policy attribute that controls roaming profile
    ... This article describes the way to prevent folders from roaming. ... roaming profiles with their profiles directory stored on a central server. ... If I check "Block Policy ...
    (microsoft.public.win2000.general)
  • Re: Backup - Not Getting Any Response - Please Help
    ... >> With a re-install the SIDs will change so the users will have to ... >> Reconnect to the "New" Domain and so will get new Profiles. ... >> be an issue if the store isn't too big. ... >> During the re-install select new locations for the User Folders and ...
    (microsoft.public.windows.server.sbs)
  • Re: Convert 97-2002 PST files to 2003 Format and Transfer to New C
    ... Should I convert my files on the old machine before I copy the pst files to ... Profiles are in the registry and don't copy well. ... be transferred and will Outlook give me the selection of profiles when I ... Note that all data files are Personal Folders File ...
    (microsoft.public.outlook.installation)
  • Re: Convert 97-2002 PST files to 2003 Format and Transfer to New C
    ... The profiles are saved in the registry. ... Do not use the export/import feature provided in Outlook. ... Change the file name of the ANSI pst file to something other than ... Unicode folders generated when Outlook was opened the first time. ...
    (microsoft.public.outlook.installation)