Roaming and CSIDL_APPDATA
Karl E. Peterson
that question, got me thinking more about this. I have virtually no experience with
roaming users. Microsoft says:
"As part of the User profile, this [CSIDL_APPDATA] folder will roam. Use this
folder to store all user-specific application preferences. For example, if a user
can specify a custom dictionary to be used in your application, you should store it
here. That way if the user roams from computer to computer, their dictionary will
roam with them. This also allows other users to have their own individual custom
dictionaries."
- http://msdn.microsoft.com/en-us/library/ms995853.aspx#w2kcli_req42
But I've also heard that this isn't necessarily the case. For example, IE temp
files aren't persisted back to the server, even though they're stored here. I'd be
interested in hearing more about this from anyone who's had actual experience with
roaming.
Thanks!
--
.NET: It's About Trust!
http://vfred.mvps.org
Karl E. Peterson
Argh! Nothing like articulating a question in order to have the answer come to you
moments after hitting Send! <g>
IE persists it's non-roaming data in CSIDL_LOCAL_APPDATA, not CSIDL_APPDATA. D'oh!
Nevermind... :-)
Bill McCarthy
"Karl E. Peterson" <ka...@mvps.org> wrote in message
news:ujL42VgY...@TK2MSFTNGP03.phx.gbl...
Yeh, the difficulty is in separating your two sets of data, even something
seemingly as simple as a MRU list gets quite complex when dealing with
roaming.
Karl E. Peterson
> Yeh, the difficulty is in separating your two sets of data, even something
> seemingly as simple as a MRU list gets quite complex when dealing with
> roaming.
I don't know a lot of net.admins that offer it as an option. Probably way more
HelpDesk workload than any want to dare take on.
Bill McCarthy
> Bill McCarthy wrote:
>> Yeh, the difficulty is in separating your two sets of data, even
>> something
>> seemingly as simple as a MRU list gets quite complex when dealing with
>> roaming.
>
> I don't know a lot of net.admins that offer it as an option. Probably way
> more HelpDesk workload than any want to dare take on.
> --
Yeh I've had problems with "Options" that we wanted to roam, and then
realized one or two of them were local machine dependant. The idea though
of having the app available to you on your laptop or desktop and being able
to resume work where you left off is what roaming is about.
Karl E. Peterson
> "Karl E. Peterson" <ka...@mvps.org> wrote ...
>> Bill McCarthy wrote:
>>> Yeh, the difficulty is in separating your two sets of data, even
>>> something
>>> seemingly as simple as a MRU list gets quite complex when dealing with
>>> roaming.
>>
>> I don't know a lot of net.admins that offer it as an option. Probably way
>> more HelpDesk workload than any want to dare take on.
>
> realized one or two of them were local machine dependant. The idea though
> of having the app available to you on your laptop or desktop and being able
> to resume work where you left off is what roaming is about.
It's a *great* concept! No doubt about it. Wish it worked well enough it was worth
the effort.
Bill McCarthy
"Karl E. Peterson" <ka...@mvps.org> wrote in message
news:e0lVtYkY...@TK2MSFTNGP04.phx.gbl...
It works best for frequent users, especially those constantly connect. The
offline files part for infrequent users has the latency issue of
synchronizing before you can go offline. Like if you haven't use the laptop
for a week or two it can be a pain to get things synched again.. if it's
just one or two files you want to work on at home or at a clients etc, then
a USB pen can seem easier. The real killer I find is when you pull the
laptop out after weeks and combined with the above you get hit with a set of
patches and the policy is set to force updating. It pays to fire up the
laptop a good half hour before you go home ;)