In my last post "Changing Server Name in Folder Redirection the Wrong Way - Part 2" (http://www.adshotgyan.com/2012/06/changing-server-name-in-folder.html), we saw an incorrect yet very common way to change the server name in Folder Redirection. We also saw the ramification of changing the server name that ways...
In this post, we will discuss what will happen if we make the Folder Redirection Group Policy as "Not Configured"
The Lab....
Domain Controller (MyDC) (Windows 2008 R2)
Member Server (OldServer) (Windows 2008 R2)
Member Server (NewServer) (Windows 2008 R2)
Client Machine (MyClient) (Windows 7)
OU (MyClients) (UserA, UserB, UserC)
And the Folder Redirection Group Policy....
The same old Folder Redirection Group Policy Settings...
My Client Machine....
The data pointing to the network location (Remember the fact that this is in continuation to my first post where the data was redirected to OldServer and not to NewServer)
Here is the data stored on the OldServer
This time I will make a change in Folder Redirection Group Policy Setting... We will make a change in the "Policy Removal" behaviour...
There are two options available in "Policy Removal"
1. Leave the folder in the new location when policy is removed
2. Redirect the folder back to the user profile location when policy is removed
By default, "Leave the folder in the new location when policy is removed" is Enabled
We will change it to "Redirect the folder back to the user profile location when policy is removed" so that when we make the Group Policy as Not Configured, then ideally, all the data will move back to the local profile of the User
And lets make this as "Not Configured"
And on the client machine, We got the event stating that the policy has been removed...
But wait... what is this...? Why do we still have the OldServer name in the Registry? Why is it still pointing to the Network Location?
And so does the location on the data...
So what we concluded? We concluded that making the Folder Redirection Policy as "Not Configured" is not an ideal way of making the Change...
If this is not the correct way then how can we make this change?... How can we move the data back to the user`s local profile? How? PATIENCE... Nah I am not saying that have patience and the will move back from the network location to the user`s local profile automatically :)... What I am saying is have patience and read my next post which talks about the correct way of moving the data back... :)
In this post, we will discuss what will happen if we make the Folder Redirection Group Policy as "Not Configured"
The Lab....
Domain Controller (MyDC) (Windows 2008 R2)
Member Server (OldServer) (Windows 2008 R2)
Member Server (NewServer) (Windows 2008 R2)
Client Machine (MyClient) (Windows 7)
OU (MyClients) (UserA, UserB, UserC)
And the Folder Redirection Group Policy....
The same old Folder Redirection Group Policy Settings...
My Client Machine....
The data pointing to the network location (Remember the fact that this is in continuation to my first post where the data was redirected to OldServer and not to NewServer)
Here is the data stored on the OldServer
This time I will make a change in Folder Redirection Group Policy Setting... We will make a change in the "Policy Removal" behaviour...
There are two options available in "Policy Removal"
1. Leave the folder in the new location when policy is removed
2. Redirect the folder back to the user profile location when policy is removed
By default, "Leave the folder in the new location when policy is removed" is Enabled
We will change it to "Redirect the folder back to the user profile location when policy is removed" so that when we make the Group Policy as Not Configured, then ideally, all the data will move back to the local profile of the User
And lets make this as "Not Configured"
But wait... what is this...? Why do we still have the OldServer name in the Registry? Why is it still pointing to the Network Location?
And so does the location on the data...
CONCLUSION:- We made the Folder redirection Policy as "Not Configured"... and We checked the option to move the data back to the user`s local profile... But then did the data actually moved back to the user`s local profile... NO...
