Mandatory Profiles annoyance windows 7 xp mixed environment

[MaXiM]

Hi, I have raised this topic before and followed advice but still it doesn't work. I have a mandatory profile called user.man

Users log into their XP comptuers on the domain with it. I have now added a few Windows 7 PC's into the mix. Users are unable to log in to those computers. I have copied the user.man folder and created a new folder called user.man.v2 and copied it into the profiles folder.. It doesn't work.

 

I thought I just had to make a copy of the original user.man and rename the copy to user.man.v2

 

Any ideas?

[Steve21]

Err perhaps I'm mistaken, but isn't it still a .man file, but in the "profile path" it's .v2?

 

*Edit - e.g.

 

(Old style)

\\server\profiles\test\NTUSER.dat

 

Goes to:

 

(New style)

\\server\profiles\test.v2\NTUSER.MAN

 

It shouldn't be a .v2 on the MAN file, unless I'm mistaken anyway

 

Steve

 

Steve

Edited March 28, 2011 by Steve21

[riffleman]

An XP profile does not work with Windows 7, so it's not as simple as copying the old profile and renaming it .v2.

 

You need to create a default Win7 profile on a PC and copy it to both the netlogon share and the new location for your v2 profile. Have a look on technet for creating a default profile.

[MaXiM]

I thought I posted this but guess not:

OK so I create a new Mandatory Profile on Windows 7 PC.

I then make sure the new windows 7 profile is the same name as the xp one? so my old one was called user.man... i make sure the new one is called user.V2 ?

I then copy the new profile I made into the same location that the XP one is located in?

So now AD user FRED who has profile path: user.man can login to a Windows 7 PC?

[sted]

sigh

 

create a mandatory profile on win7 (a total pita)

export it to your profiles share as name.man.v2 (in your case by the looks user.man.v2)

leave ad alone win7 knows to use the .v2 version xp wont even see it

[witch]

I found out today that I had mandatory profiles which I didnt know you could have on roaming and it meant that the V2 profiles could not be created. So I took advice and ended up removing the user.man and now all is well and the win 7 machines are working fine.

Why do you need the mandatory bit anyway on a roaming profile?

[riffleman]

You don't. You either have mandatory profiles, which means any changes made to the profile are not saved back to the server, or you have roaming profiles, which do save changes. If you have user.dat in the same folder as user.man, it works the same as if it were a roaming profile. You should only have one or the other in the profile folder.