Bugzilla – Bug 153694
Simias Database not stored as part of Roaming Profile.
Last modified: 2009-10-08 09:16:46 UTC
"When you install iFolder 3 client on Windows, it creates SIMIAS files in the C:\Documentsandsettings\####\Local Settings\Application Data\simias Directory. This is not copied around as part of the roaming profile, which means that the users of iFolder3 at my customer can not sync the iFolder when hey login to other workstations. Are we (Novell) saying that iFolder 3 is not suitable for Windows Clients that user Roaming profiles ... That is a big user population to exclude. Can we add a setting so this path is user definable ? My customers other option is to throw out eDir and user AD! Thanks
This is working as designed. iFolder is intended to provide backup of local data on a workstation where the user is a dedicated user on the desktop. If the customer is using roaming profiles and does not expect the end-user to be at any one dedicated computer, what value is iFolder in this scenario? At present, we do not intent on supporting roaming profiles. If you were to add the path as user definable, then are you expecting the data to be removed when the user logouts of the workstation?
Just a follow up to this ... I know its down as Wont fix - But is there any chance roaming profiles may be addressed in the future. Thanks
Bruce - I'm going to reopen this bug as an enhancement. We will let Jared and Trent decide if this is a feature they are interested in putting resources on in our next bug scrub meeting.
Hi - My customers needs are the following. They have users whom use roaming profiles ... but are fixed to one machine. In this case - All we need is the "Choice" of where to place the simias info. Perhaps a registry fix, an "ini" file setting anything .. other than the default C:\Documentsandsettings\####\Local Settings\Application Data\simias Directory. That way it wont be destroyed when the local profiles are cleared up. Would this enhancment be possible ? Thanks Steve
Reassigning to Ramesh.
This wont be fixed. In case you feel this need to be considered for coming release please provide more, and do you still fell this is a requirement if so we could move to fate for PM to evalute.