Windows 2003 redirect desktop

What we are configuring here is client side caching. My view is that normally, clients can adequately cache their own programs locally. Perhaps caching is one of those Group Policies that you only need for laptops. Let us move on to more important policies: Desktop and My Documents. There is a knack to configuring all these 4 redirection settings.

At first, it seems at first as though there are no policies in the container. If you are organized, then you would have shared out the redirect folder on the server. When you configure Folder Redirection policies, you need to pay careful attention to creating the subfolders that each user needs, in particular check the network share and NTFS ACL permissions, otherwise users will be disappointed with an error message.

Best practice states that you should create only the root share on the server, and then let the system create the folders for each user. This is an area where you need testing and impersonating the users. When troubleshooting, I confess that my strategy is to get a test user working with everyone having full control, then I gradually throttle back the permissions until Folder Direction still works, but each user can only access their own folder.

When you launch this tool it analyzes a users effective NTFS permissions for a specific file or folder, takes into account network share access, then displays the results in a nifty desktop dashboard! Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account please place appropriately.

Choose computer and select the proper user in the wizard. Collect Gpsvc. Entry: GpSvcDebugLevel. Vaule data: 0x Collect gpresult output. Arthur Li. TechNet Community Support. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. You try to redirect the users or computer OU in a domain that hasn't transitioned to the Windows Server domain functional level.

In this situation, you receive the following error messages:. Error, unable to modify the wellKnownObjects attribute. Verify that the domain functional level of the domain is at least Windows Server Unwilling To Perform. If you try to redirect the users or computer OU by using incorrect credentials in the target domain, you may receive the following error messages:.

You try to redirect the users or computer OU to an OU that doesn't exist. In this situation, you may receive the following error messages:. Setup failed while installing sub-component Domain-level permissions with error code 0x please consult the installation logs for a detailed description. You may cancel the installation or try the failed step again. The following data appears in the Exchange Server Setup log that is parsed with log parser.

Exchange Server should be similar. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.