server 2003 btw
Everyone already knows the benefits of roaming profiles and document redirection, but I found a way to do both, and in addition, retain local user settigns such as Outlook .pst's and mozilla profiles (which are not roaming compatible:Q)
To begin, set the group Policy folder redirections to the coressponding folders on the server. Make sure to make that seperate than the document root directory for speed. Having to pull down some fools 3GB My Docs directory is not fun. Then create all of the user accounts on the server. In addition, in that user's profile settings, make sure their profile points to the \\server\profiles\%username% directory and that the home folder points to their documents root folder. You logon to the clients PC as a local admin and copy their profile to their profile directory on the server. THen move their docs to their Documents root user folder.
Finally, use the network connection wizard on the server to import the local settings to the domain. It is very simple. VERY. VERY. SIMPLE.
The cool part comes into play right now. Becuase you have imported the local settings, the users local settigns are copied to the cached roaming profile.
HOWEVER, all of the desktop, application data, and docs get copied over the server as well.
What does this mean?
1. They have an effective roaming profile
2. They have an effective document redirection scheme.
3. They retain all of their local settings on that pc.
4. Using offline files for mobile users means that you can still take advantage of this on the road
5. If they are still using .pst's they can be moved to the documents root and mail settings can be rerouted so that the .pst's are backed up on the server. Obviously using the exchange pop connector is better, but I had only so much to work with
Basically, on that PC, it's hard for users to tell that you did anything at all besides the logon screen change. Only you will notice that My docs is actully pointing to the server, and that their profile is jsut cached. :thumbsup: It makes backups A PIECE OF CAKE. Just backup that drive...assuming that you partitioned a seperate user drive
Finally, when they log on to other domain pcs, they will still have acess to their desktop and their docs, not to mention priveledges and such
It fricken' kicks ass...and I came up with it on the spot. I couldn't finding anythign remotely similar to this so I had to improvise
The techs at Microsoft I spoke with were like:
"WTF?!? that actually works?!"
:laugh:
I know it ain't much but I am proud of my modest accomplishment
Everyone already knows the benefits of roaming profiles and document redirection, but I found a way to do both, and in addition, retain local user settigns such as Outlook .pst's and mozilla profiles (which are not roaming compatible:Q)
To begin, set the group Policy folder redirections to the coressponding folders on the server. Make sure to make that seperate than the document root directory for speed. Having to pull down some fools 3GB My Docs directory is not fun. Then create all of the user accounts on the server. In addition, in that user's profile settings, make sure their profile points to the \\server\profiles\%username% directory and that the home folder points to their documents root folder. You logon to the clients PC as a local admin and copy their profile to their profile directory on the server. THen move their docs to their Documents root user folder.
Finally, use the network connection wizard on the server to import the local settings to the domain. It is very simple. VERY. VERY. SIMPLE.
The cool part comes into play right now. Becuase you have imported the local settings, the users local settigns are copied to the cached roaming profile.
HOWEVER, all of the desktop, application data, and docs get copied over the server as well.
What does this mean?
1. They have an effective roaming profile
2. They have an effective document redirection scheme.
3. They retain all of their local settings on that pc.
4. Using offline files for mobile users means that you can still take advantage of this on the road
5. If they are still using .pst's they can be moved to the documents root and mail settings can be rerouted so that the .pst's are backed up on the server. Obviously using the exchange pop connector is better, but I had only so much to work with
Basically, on that PC, it's hard for users to tell that you did anything at all besides the logon screen change. Only you will notice that My docs is actully pointing to the server, and that their profile is jsut cached. :thumbsup: It makes backups A PIECE OF CAKE. Just backup that drive...assuming that you partitioned a seperate user drive
Finally, when they log on to other domain pcs, they will still have acess to their desktop and their docs, not to mention priveledges and such
It fricken' kicks ass...and I came up with it on the spot. I couldn't finding anythign remotely similar to this so I had to improvise
The techs at Microsoft I spoke with were like:
"WTF?!? that actually works?!"
:laugh:
I know it ain't much but I am proud of my modest accomplishment
Facebook
Twitter