Open Discussion

Expand all | Collapse all

Supporting backups of Windows roaming profiles - or not?

  • 1.  Supporting backups of Windows roaming profiles - or not?

    Posted 17 days ago


    ------------------------------
    Robert Talda
    System Engineer IV
    Ithaca NY
    rpt4@cornell.edu
    ------------------------------


  • 2.  RE: Supporting backups of Windows roaming profiles - or not?

    Posted 17 days ago
    If you are asking if code42 crashplan backs up roaming profiles in Windows, you can configure the crashplan client (or on an authority server if you have access to one) to backup the local "Users" folder.

    That should allow a user's roaming profile to be captured in the backup if they have logged onto the domain-connected computer using their domain account credentials at least once.

    Since we have users all over the US in our organization, not all users are able to sync with our domain unless they have VPN access (not all are authorized to have access too). This is how we use code42 to backup roaming profiles remotely.

    ------------------------------
    Mitchell Aubitz
    Desktop Support Specialist
    Eden Prairie MN
    ------------------------------



  • 3.  RE: Supporting backups of Windows roaming profiles - or not?

    Posted 17 days ago
    I would say no to this.  As a roaming profile is usually stored on a windows login server, it wouldn't make sense.

    ------------------------------
    Michael Zopes
    Senior System Technician
    Westminster CO
    ------------------------------



  • 4.  RE: Supporting backups of Windows roaming profiles - or not?

    Posted 17 days ago
    Just realized that something (probably my browser) ate the original post...must have been as confusing as managing these profiles.

    Rather than recreate the whole post, I'll try to summarize.  We have a unit with shared devices that relies on roaming profiles to deliver a consistent user experience.  And now that unit wants to use Code42 to protect the data on those devices. (Not the profiles, for as one respondent pointed out, the profiles are kept on the server).
    However, the backup defaults for the organization specify ":user".   Now, the question we have: does the ":user" specification follow through the various home directories, i.e., is the Code42 app dynamically determing the value of ":user" each time - or is it hard coded?  In theory, if the Code42 app is installed 'per user', it could because the app is running as a process that could determine the home directory on startup - but we aren't sure.

     From the Org Admin in the unit who was testing deployment using a package with his organization's deployment token embedded:
    "[After deploying Code42 to the device, Windows] decided to login me with a temp profile... and the deploy script correctly determined that that was my current profile dir[ectory].   now that I logout'ed, that dir[ectory no longer exists.  now I do want [Code42 app] to backup files if a temporary profile dir gets created"
    <aside>...which we verified it does...
    "[now]  the idea of temporary profiles on the computer [is] login, temp profile dir, then profile is deleted at logout
    so if a user never has a real permenant profile dir (or gets a temp one b.c. of a windows network glitch)...
    eg, first time I login, I get c:\users\dweeb.cnfad
    next login, I get c:\users\dweeb.cnfad.001
    next login, I get c:\users\dweeb.cnfad.002
    then it fixes itself and I'm back at c:\users\dweeb.cnfad
    if for some reason the computer cannot get to the roaming profile on the server, at login time, it is likely to create something like c:\users\temp.cnfad.003"

    For the moment, the Org Admin is installed in "Everybody" mode (aka for all users of a device) and overrode the backup defaults for the device, using ":allusers" instead of ":users".  This isn't desirable long term because it does introduce the ability of one user - the one logged on at the time of deployment - to look in their archive and  see data  from all the other users on that device.

    THanks for sharing any experiences,
    Bob

    ------------------------------
    Robert Talda
    System Engineer IV
    Ithaca NY
    rpt4@cornell.edu
    ------------------------------



  • 5.  RE: Supporting backups of Windows roaming profiles - or not?

    Posted 16 days ago
    :user is the general expression variable that will capture the local "Users" folder on a windows installation (' C:\Users '  for example)

    Since that is the default location a profile's folders are created in Windows, any profile's folders that are created there will be backed up if specified in the backup client or authority server's backup defaults list.

    If a temp directory is created and deleted at a later point, you would need to backup its parent directory (and wait for the backup to finish) to make sure whatever is temporarily created is backed up.

    For example, you log in and a temp directory is created under C:\Users. If you have the "C:\Users" folder marked to be backed up in the backup client or authority server, then it should back up any temp directory inside the "C:\Users" directory as well. In your situation, you would have to make sure the backup is done before logging out (if that is when the temp directory is deleted) to be sure the crashplan client grabbed the data.

    Also, if you have access the authority server you would need to remember what is set for preference of whether to backup open files or not.

    ------------------------------
    Mitchell Aubitz
    Desktop Support Specialist
    Eden Prairie MN
    ------------------------------