Professional Documents
Culture Documents
In an SBS 2003 to SBS 2008 migration scenario, both of these GPOs will be present after the installation of SBS 2008 if folder
redirection was previously enabled. As part of the post-migration steps, you will add the desired users to the Windows SBS
Folder Redirection Accounts, force group policy update on all clients, and then remove the GPO created by SBS 2003 that is
linked at the domain level. Users who are members of the new group will have their data automatically moved from the SBS 2003
machine to the SBS 2008 machine upon their next login. Those users who are not participating in folder redirection will have their
data moved back to their local client machine upon their next login. If you attempt to move the data manually or if both SBS
servers are not online during this entire process, then you will run into failures (see troubleshooting section below).
There are two locations where you can accomplish this. The first place is under Shared Folders and Websites > Shared
Folders > Redirect folder for user accounts to the server
The second is under Users and Groups > Users > Redirect folders for user accounts to the server
Both locations launch the same window where you can choose which folders to redirect (Desktop, Documents, and Start Menu)
and for which user accounts. When you do this, the user account is made a member of the Windows SBS Folder Redirection
Accounts:
You may receive an informational message reminding you that it may take a few logins to complete the entire redirection process,
especially if you are migrating folder redirection settings from SBS 2003:
GPO settings detail
The top causes of folder redirection failure are incorrect permissions on the network share, Group Policy deployment failure, and
problems with Offline Files.
Permission Issues
Permission issues usually originate from manually moving the user’s folder from one location to another, or if the administrator
takes ownership of the user’s folder to gain access to the contents. To prevent the first scenario from occurring, use the Move
Users’ Redirected Documents Data wizard . A typical error you will receive on the client machine will be something like this:
If you suspect that you are in this situation, verify the following:
l The redirected user account must have at least Read, Traverse folder, List folder, Read attributes, and Read
extended attributes on the actual share \\SERVERNAME\RedirectedFolders. If you cannot open this share from the
client machine because you get an “Access Denied†, folder redirection will not work.
l The redirected user account must have Full control and be the Owner of their personal folder
\\SERVERNAME\RedirectedFolders\%USERNAME%\. If not, the GPO will fail to apply to that user upon login.
There are numerous potential causes to Group Policy deployment failures, use the checklist below to identify the most common:
l Users must be able to login to the domain from their client machines.
l The server must be able to successfully apply group policy to itself and user/computer accounts.
l Shares must be fully accessible from the server itself and the client.
Note: These first three bullet points are usually caused by network configuration error of the client, server, or both. For the
server, run the SBS BPA to identify these issues. On the client, make sure the interface it’s using to communicate with the
server has a valid IP address with the correct subnet mask and that it’s using the SBS server as it’s only DNS server.
l Ensure that the correct GPO is applying the Folder Redirection settings. We often see situations where Folder Redirection
settings have been incorrectly applied on another GPO at some point in time, usually on the Default Domain or Default
Domain Controllers Policy and usually with the wrong settings. Use the Group Policy Results wizard to determine which
GPO is applying the settings for the user account in question.
l Ensure the settings in the Small Business Server Folder Redirection GPO are correct according to the “GPO
settings detail†section above.
l When migrating from SBS 2003 to SBS 2008, follow the previously mentioned post-migration steps carefully to avoid any
confusion in the settings deployed to the client. If the client cannot reach the original network location on the source server
before the process is complete, this will fail.
Offline Files
There are certain circumstances that will result in Offline Files preventing the client from reaching network shares on the server.
One such issue that we run into frequently is documented in the following KB article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;274789
Usually the resolution to these cases is to reset the Offline File cache on the client and logging off and back onto the domain.