[gptalk] Re: Where's the Documents Folder on a Roaming Profile Downloading onto a Vista Device?
- From: "Nelson, Jamie" <Jamie.Nelson@xxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Wed, 22 Oct 2008 14:15:54 -0500
Yeah, that's what I'm saying. As far as the second device is concerned,
it should have no idea a profile was ever created on the first. So you
would think it would at least create the "Documents" folder no matter
what.
Jamie Nelson | Operations Consultant | BI&T Infrastructure-Intel | Devon
Energy Corporation | Work: 405.552.8054 | Mobile: 405.200.8088 |
http://www.dvn.com <http://www.dvn.com/>
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Cruz, Jerome L
Sent: Wednesday, October 22, 2008 1:50 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Where's the Documents Folder on a Roaming Profile
Downloading onto a Vista Device?
Jamie,
The first Vista device they log onto does indeed correctly create the
Documents folder, so that's not where the problem seems to lie. The
exclusion setting prevents that Documents folder from synching to the
Profile server. Then when they log onto a "different" Vista device,
that's apparently when there is no Documents folder created by the local
system. But it seems strange that MS would not have thought of this and
create one anyway on that second device.
Jerry
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Nelson, Jamie
Sent: Wednesday, October 22, 2008 11:42 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Where's the Documents Folder on a Roaming Profile
Downloading onto a Vista Device?
Strange. Just because you've excluded the folder from roaming doesn't
mean it should not be present when a new profile is created. That should
be completely independent of Group Policy. Have you checked the shell
folder registry settings in instances where this is happening? Is the
"Personal" reg value present and pointed at the correct location (i.e.
%USERPROFILE%\Documents)?
Jamie Nelson | Operations Consultant | BI&T Infrastructure-Intel | Devon
Energy Corporation | Work: 405.552.8054 | Mobile: 405.200.8088 |
http://www.dvn.com <http://www.dvn.com/>
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Cruz, Jerome L
Sent: Wednesday, October 22, 2008 1:12 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Where's the Documents Folder on a Roaming Profile
Downloading onto a Vista Device?
Has anyone run into the following Roaming Profile behavior? We are
'finally' testing a Vista image for possible deployment to our customers
and the testers are reporting that, when they roam (log onto) a
different Vista device, their profile comes down correctly, but there is
no "Documents" folder created by the local system.
When I asked them: "What's the behavior when you don't actually have the
folder and you then click on something that attempts to take you there
(like Start | Documents)? There response is: Folder not found error.
So, they create the folder manually and report no further issues.
However, that cannot be the solution for the masses.
We currently have an exclusion for the '...Documents...' folder
targeting user accounts. There is no further Group Policy based
"redirection" of the "Documents" folder...this is because most of the
users maintain the use of a single device and we mainly use roaming
profiles to backup their settings for 'flatten and reload' scenarios,
'not' to roam. This was put in place for our Windows 2000 to Windows XP
migration a few years ago.
Anyway, here is the current Group Policy exclusion.
Prevent the following directories from roaming with the profile:
Desktop;
My Documents;
Recent;
Application Data\Adobe;
Application Data\AutoDesk;
Application Data\Macromedia;
Application Data\Microsoft\MSDAIPP;
Application Data\Microsoft\Clip Organizer;
Application Data\Roxio;
Application Data\Hummingbird;
Documents
Thoughts? Ideas?
Jerry
________________________________
Confidentiality Warning: This message and any attachments are intended
only for the use of the intended recipient(s), are confidential, and may
be privileged. If you are not the intended recipient, you are hereby
notified that any review, retransmission, conversion to hard copy,
copying, circulation or other use of all or any portion of this message
and any attachments is strictly prohibited. If you are not the intended
recipient, please notify the sender immediately by return e-mail, and
delete this message and any attachments from your system.
Other related posts:
