Re: Roaming Problems

Thanks Cliff

I shall give that a go and keep you updated!

I know I've said it before but I'd just like to say again, thank you so much
for your continued help and input it is greatly appreciated!
Keith


"Cliff Galiher" wrote:

Eek. Okay. Generally speaking, just for future reference, that is *very*
bad. you should create two folders. One for profiles, shared, with caching
DISABLED. Roaming profiles get corrupted very easily and your event logs
will complain if caching is enabled. Redirected folders, however, can have
caching enabled and SBS will make the files automatically available offline
for domain users. Having the two in the same place can *really* confuse XP
(Vista is *slightly* better) depending on whether it detected the GPO for
folder redirectoin or the roaming profile path first.

Alas, it sounds like things are in the muck already, so we need to try and
fix this:

You can try changing the folder redirection and use the %USERPROFILE%
variable to see if you can get it to go to the original location.

For example, you would set the Desktop folder to redirect to location
%USERPROFILE%\Desktop

I would create a new GPO to do this and apply it selectively to a security
group comprised of a test user with problems. Then you can slowly add
users, verifying each one gets the GPO as added. That way, if an error
occurs or the GPO behaves in an unexpected fashion along the way, the damage
doesn't hit your entire userbase.

-Cliff

"Keith Whittle" <KeithWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:93B3FF2C-0A51-4197-88C9-07648BF9D169@xxxxxxxxxxxxxxxx
Sorry for the confusion, yes on the original setup profiles and folder
redirection where both in the same folder

Keith

"Cliff Galiher" wrote:

Unfortunately that didn't really answer my question...

Did you put your roaming profile directory in the same folder as your
redirected user folders??

-Cliff

"Keith Whittle" <KeithWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C40F7FC8-7870-4DCF-9006-D7227D7BDEAA@xxxxxxxxxxxxxxxx
Hi Cliff

Again it can be different from client computer to computer. But if I
look
at
properties for example on My Docs it's path is
\\servername\folder\user....
Also if I run rsop.msc the everything looks the same from before making
the
changes in steps 1-4

Keith

"Cliff Galiher" wrote:

Nope, that is not what I'd expect. How have you verified that files
are
still pointed at the server? And which files? Profile files? Or are
some
still going into the redirected folder location?

-Cliff

"Keith Whittle" <KeithWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:016A5C1B-FA61-4358-8AF6-01A15BCC27ED@xxxxxxxxxxxxxxxx
Hi Cliff

Sorry for the delay didn't get a chance to try anything till last
night.

Of your 8 steps I have so far go up to step 4 but i have stop there
for
the
time being. As whilst I have changed the GPO, done gpupdate /force,
removed
roaming from the AD and reset each user back to a local profile they
still
appear to be pointing file locations back to the server.

So I have not wanted to move on the Step 5 Delete all files from the
roaming
profile share till I had checked in!

Is this what you would expect or is something else going on?

Keith

"Cliff Galiher" wrote:

Eegads. Okay, you definitely have some problems, most of them
appear
to
be
a corruption in profiles, and are being complicated by folder
redirection.
You usually see this when you try to enable both at the same time.
They
are
codependent, so if one is broken, it causes odd symptoms that don't
truly
tell you what the problem is. The solution is to disable them and
then
re-enable singularly, resolving any problems before moving on to
the
other.

One question of note:

1) I was asking of all computers were in the same OU, not at the
same
OS.
OU == Organizational Unit. Basically trying to confirm that your
AD
structure was intact. But, with the errors you posted, I'll assume
they
are,
or at least the GPO is high enough in the structure that it is
applying
to
all machines, but failing do to those specific errors.

So here is what I'd do:

1) Change your Folder Redirection policy to "move files to original
location." Right now, as long as your profile issues persist,
folder
redirection cannot kick in...and we don't need it complicating
things.

2) gpupdate /force and reboot to make sure that gets applied.

3) Clear the roaming profile path on each user in AD.

4) On each user's workstation (if they have an assigned
workstation)
go
into
the system advanced control panel and change their profile back to
local
from roaming.

5) Delete all files from your roaming profile share. Delete all
files
from
your folder redirection share. (these should be different shares.)
Make
sure you have a BACKUP in case settings above didn't take...they
should,
and
you should know before you got here...but you can never be too
careful.

6) Ensure offline files caching is DISABLED on your profiles share.

7) Per user, add the roaming path back to AD. Have them log in.
Verify
that the roaming profile is created on the share. If there is a
problem
with the profile, the client will usually throw some form of
message
talking
about "using temporary profile." These *need* to be resolved
before
enabling folder redirection. This includes the machine hanging at
"logon."
That happens when the system is failing to merge the roaming
ntuser.dat
into
the local hive. Damned registry anyways. You may just have to
delete
the
local profile (and yes, the user will have to recreate their
settings)
but
that can be confirmed by logging into that workstation as another
user
with
a working roaming profile.

8) Once all profiles are roaming properly and CONFIRMED, then you
can
go
back to your GPO and set your folder redirection. Since the client
(XP/Vista) creates the roaming profile directory with the
appropriate
permissions, and will also create the user redirected folders with
the
appropriate permissions, the errors you saw above should no longer
occur.

Hope that helps,

-Cliff



"Keith Whittle" <KeithWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:EBE76295-965C-487C-8388-9DC04E2C345F@xxxxxxxxxxxxxxxx
Hi Cliff

Whilst gpupdate /force seems to have sorted some of the problems
I
am
continuing to have a few others.

When I run rsop.msc to check some of the users are fine and are
set
correctly but others are not redirecting some of the folders (my
docs,
desktop etc).
From the rsop report I get a four variants on messages;
1) Folder Redirection failed due to the error listed below.
Cannot complete this function.

Additional Information:
Failed to apply policy and redirect folder "Desktop" to
"\\servername\roam\username\Desktop".
Redirection options=9211.
The following error occurred: "Failed to copy files from
"C:\Users\username.domainname.000\Desktop" to
"\\servername\roam\username\Desktop"".
Error details: "The system call level is not correct.

2) Failed to apply policy and redirect folder "Documents" to
"\\servername\roam\username\My Documents".
Redirection options=9211.
The following error occurred: "Unexpected error from
PerformRedirection".
Error details: "The filename or extension is too long.

3) Group Policy Infrastructure failed due to the error listed
below.
Logon failure: unknown user name or bad password.

Note: Due to the GP Core failure, none of the other Group Policy
components
processed their policy. Consequently, status information for the
other
components is not available.

4) Failed to apply policy and redirect folder "Documents" to
"\\servername\roam\username\My Documents".
Redirection options=9211.
The following error occurred: "Failed to copy files from
"\\servername\Users\username\My Documents" to
"\\servername\roam\username\My
Documents"".
Error details: "The specified network name is no longer
available.

They all seem a bit inconsistent the problems to say the least.

Thanks in advance for your continued help!
Keith

"Keith Whittle" wrote:

Hi Cliff

Thanks for getting back to me so quickly, much appreciated!

In answer to your questions
Problem One
1) All machines are on the same OS
2) There are no additional security filters or WMI filters
applied
to
the
GPO that control profiles and folder redirection (unless there
is a
sneaky
one lurking somewhere that I have missed?)
3) Logons, I have logged on and off multiple times and the GPOs
still
are
not picking up

On a more positive note, I have run a test on one terminal and
gpupdate
/force appears to have done the trick! I will try and roll this
out
across
the floor tonight and keep you updated on if there are any other
problems.

Problem Two
1) Yes this was a fail on both fronts, either with folder
redirection
or
roaming profile or bother.
2) (Sorry for not giving more details in my original message)
The
terminal
just sits on the logon screen (I even left it over an entire
.

Relevant Pages

  • Re: Roaming Problems
    ... yes on the original setup profiles and folder ... redirection where both in the same folder ... Did you put your roaming profile directory in the same folder as your ...
    (microsoft.public.windows.server.sbs)
  • Re: Roaming Profiles and Redirected Folders Inconsistent
    ... However, in SBS, we usually enable offline folder for the redirected My ... I suggest we do not enable roaming profile and folder redirection for same ...
    (microsoft.public.windows.server.sbs)
  • Re: Roaming Profiles and Redirected Folders Inconsistent
    ... the roaming profile no longer ... However, in SBS, we usually enable offline folder for the redirected ... profile and folder redirection for users and the roaming profile do ...
    (microsoft.public.windows.server.sbs)
  • RE: mydocuments missing after logff logon sbs2003 win xp
    ... I understand that you enable folder ... empty after every time logoff and logon SBS. ... The roaming profile on SBS will sync with client computer when it logoff ... It is not a good idea to redirect the My Document redirection ...
    (microsoft.public.windows.server.sbs)
  • Re: Roaming Problems
    ... roaming from the AD and reset each user back to a local profile they still ... and are being complicated by folder ... Change your Folder Redirection policy to "move files to original ... Clear the roaming profile path on each user in AD. ...
    (microsoft.public.windows.server.sbs)