Mandatory Profiles/Mixed OS environment

[lafleur1977]

Hello,

 

We are currently using Windows XP/server 2003 terminal server for the vast majority of our network. We are looking to upgrade to Windows 7/windows server 2008 terminal server which we will phase in. At the moment all students load a windows XP mandatory profile via AD user properties when they log on. I am unsure how I might go about pointing students to mandatory profiles for different OS's (Windows XP, 7 and server 2008). I know a profile V2 (vista onwards) needs to have .v2 appended to the end of its name but this would only allow for distinguishing between 2 mandatory profiles.

 

How do other people go about mandatory profiles in a mixed environment? My understanding of a mandatory profile is that they set settings, defaults and restrictions that cannot be changed. Group policy and preferences can be used to achieve the same thing so maybe there isn't a need for them?

 

Thanks

[sted]

i gave up on mandatory on win7 but if you create one for xp and one for 7 xp called pupil.man win7 called pupil.man.v2 it will work fine just creating them on 7 is a pita involving sysprep and many many fails lol

[Michael]

i gave up on mandatory on win7 but if you create one for xp and one for 7 xp called pupil.man win7 called pupil.man.v2 it will work fine just creating them on 7 is a pita involving sysprep and many many fails lol

 

I've had no problems creating .MAN profiles and I certainly didn't use Sysprep! As Sted mentioned though, you do need to keep two copies of profiles - essentially v1 and v2 and Windows will intelligently pick the right version it needs.

[lafleur1977]

i gave up on mandatory on win7 but if you create one for xp and one for 7 xp called pupil.man win7 called pupil.man.v2 it will work fine just creating them on 7 is a pita involving sysprep and many many fails lol

 

Thanks for your reply. I have already created XP and 7 profiles with the .v2 for 7 successfully. I was just wondering about the third OS (being server 2008 in this case) and how to point to all 3.

[Michael]

Thanks for your reply. I have already created XP and 7 profiles with the .v2 for 7 successfully. I was just wondering about the third OS (being server 2008 in this case) and how to point to all 3.

 

2000/XP/2003 use v1 profiles

 

Vista/2008/7/2008 R2 use v2 profiles

 

When creating the profile you'd name it:

 

Profile and Profile.v2 accordingly.

 

When specifying a user's profile, you'll typically specify:

 

\\SERVERNAME\Profiles$\Profile

 

As I wrote above, Windows XP or 7 will intelligently pick the right profile it needs

[sted]

you can do ts profiles separately if it helps there is a user tab for it

[lafleur1977]

you can do ts profiles separately if it helps there is a user tab for it

 

I have looked at that before but never managed to get it working. By specifying the profile location in the AD user properties ts profile tab, should it load that then on a terminal server or is there additional configuration elsewhere?

[sted]

just add it and it works shame u cant do lots at once directly lol bulkad users does allow it thogh