Firefox Posted May 8, 2014 Posted May 8, 2014 Hopefully others out there are doing this and we're not unique. In the users AD path we set \\servername\profiles\Username%osver% on an XP machine we set a variable as %osver% = XP and on Windows 7 we set %osver% = W7 This means when logging onto a W7 machine it will load the UsernameW7 profile and XP UsernameXP profile All of this has worked well for years..........until we implemented VMware. Our physical devices still work the same, however when logging onto a VDI Desktop it completely ignores the variable and loads\creates Username%osver% as a profile name. It reads the variable as literal. Anyone else had similar issues?
plexer Posted May 8, 2014 Posted May 8, 2014 Why would you do that? Win 7 uses a .v2 profile anyway so it's allready seperate to an xp profile. Ben
Firefox Posted May 8, 2014 Author Posted May 8, 2014 We have a separate profile for users logging on via Terminal services, which being a 2008 R2 server also uses .V2 on these server we set a variable of %osver% = RDS Windows 8 also users .V2, and although we're not going down that route at this moment in time, with variables we should be able to adapt to a Windows 8 environment with little trouble
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now