Roaming Profile Madness

[Guest]

I'm having trouble logging onto our domain without vista logging me on using
a tempory profile - I've moved my old xp profile data out of my network share
and am now left with a blank folder - I have a script that is run at logon to
connect 3 network drives.

The error in even viewer is...
-------------------------------------
Log Name: Application
Source: User Profiles Service
Date: 21/06/2006 08:24:47
Event ID: 1521
Task Category: None
Level: Error
Keywords: Classic
User: APR\DGR
Computer: BETA-PC
Description:
Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile will
not be copied to the server when you logoff. Possible causes of this error
include network problems or insufficient security rights. If this problem
persists, contact your network administrator.

DETAIL - The network path was not found.
-------------------------------------

My username is an domain administrator - and i have full admin rights over
that folder - I can browse that folder in explorer and can copy and paste
files to and from it...

Any help on this would be greatly appreciated, am a little lost...

 

[Eric G. van der Paardt]

I'm having trouble logging onto our domain without vista logging me on
using
a tempory profile - I've moved my old xp profile data out of my network
share
and am now left with a blank folder - I have a script that is run at logon
to
connect 3 network drives.

I'm using Vista on my (WS2K3) domain as well, everything is working great
(love the new login screen)... but I'm not using roaming profiles. I am
using a GPO to redirect 'My Documents' to a mapped drive and this seems to
be fine. I'm using a stardard .BAT file to 'net use' serveral drives on
startup. This triggers the UAC every login, but all of my drives map fine.

The error in even viewer is...
-------------------------------------
Log Name: Application
Source: User Profiles Service
Date: 21/06/2006 08:24:47
Event ID: 1521
Task Category: None
Level: Error
Keywords: Classic
User: APR\DGR
Computer: BETA-PC
Description:
Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will
not be copied to the server when you logoff. Possible causes of this error
include network problems or insufficient security rights. If this problem
persists, contact your network administrator.

DETAIL - The network path was not found.
-------------------------------------

My username is an domain administrator - and i have full admin rights over
that folder - I can browse that folder in explorer and can copy and paste
files to and from it...

Any help on this would be greatly appreciated, am a little lost...

Blind guess, you network is set to 'Public' instead of 'Private' or like
mine 'Domain Network' in the 'Network Center'. Or perhaps Discovery and
sharing is turned off?

Good Luck.
E

 

[Guest]

No, this seems to be a widespread issue. I am fairly certain that all
security settings are correct on my Vista system and my WS2K3 domain. I am
also logging in as a domain admin as well as regular user accounts. The users
have been given local logon permissions, domain permissions to log on to any
computer, and all work fine under XP SP2. Domain network is automatically
selected by Vista. It is not a user setting. If Vista can see the domain
controller (which it can,) it classifies the network as a domain network. As
far as I can tell, the issue arises with the changing state of the network
while the system is logging in. Vista has different network profiles for each
user. It seems that it is closing the bootstrap profile and trying to load
the account's roaming profile w/o being connected to the network. The event
logged either says that the host name cannot be resolved or the path cannot
be found, which further suggests the probability of this being a network
issue. In my specific case, it is a wireless network. I am not sure if this
problem exists on wired networks or not. I have seen several similar posts in
this group, but no answers that work so far. We might just have to wait for
RC1. Hopefully MS has already fixed it since 5384 or will have it fixed by
RC1 (or, better yet, will patch 5384 with a fix for it.)

If anyone does find a fix for this, please post it ASAP.

RossB

 

[Guest]

Ok I have found the problem and it dates back to Win XP. The OS has locked
the account. It can be fixed by editing a key in the registry.

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList.
Under here you will find some long numbers these are known as the Users SID,
if there are a lot of people logged onto the machine there will be a long
list in here.(Hopefully not). Click on 1 of them and check the details in the
right hand pane and it should give you a profilePath.

If you have blown away you profle, delete the key.

 

[Guest]

Well, good news and bad news.

bad Your fix didn't work. You can't change those keys while logged in
with the user and question and they just go away when you log out.

good While looking at the key you mentioned, I noticed it was
appending ".V2" to the end of the share name it was looking for for the
profile. I copied the profile into another folder, shared it as that, and now
it works! It still gives a message saying that the profile was not completely
synced when it logs off, but it appears to have kept all of the changes that
I made while logged it.

Thanks for pointing me to that key! I've been trying to figure that problem
out for a couple of months and never thought to look there. As it turns out,
I just need to add 3 characters to the share name.

MS: It would be nice if it would look for the share specified in the account
info on the LDAP server and not append characters to the end of it.

Thanks,
RossB

 

[Guest]

Hi,

I have been having this problem as have what appears to be numerous other
posters in this thread, I read in another post that you have to be careful to
setup your user account as admin on the first boot after install,

***Quote***

Hi Scott,

This is a known security test going on with Vista Pre-release builds.

The FIX for your problem is:

1. When you join the machine the machine to the domain, at that time when it
ask you to reboot, do not reboot
2. Instead go to the Control Panel and under User and Account Settings, add
your domain user name to the Administrator Group
3. Then you can safely log off and log back in

The BUG here is
1. When you join the machine to the domain, the default Administrator
account gets locked out
2. Before joining the machine to the domain, users have to create another
administrator Account on the local machine (which is way beyond expectation
for layman)
3. Then you logon to the new user account on the local machine which is a
part of the administrator group and then join the machine to the domain.

*****If you miss the step of creating a new Administrative user account
before joining the machine to the domain, mind you, you would have to rebuild
the Vista image and start all over from scratch******

*** End of Quote ***

surely the registry can be used to enable the local profile as admin, not
being up on reg settings I have no clue, but I am sure one of you techno
wizards can work out which value needs to be changed (crosses fingers and
prays)