Jump to content

Recommended Posts

Posted

Network has been working fine, but after some pcs were added to network & server windows updates done,the following occurs;(win2003 server, ranger, xp workstations)

when logging in at some (some only) workstations it goes straight to the user's my docs.(some other workstations are fine)

Then if they close my docs they are faced with a

blank blue screen.

On server event viewer says -event id 1085 The Group Policy client-side extension Folder Redirection failed to execute. Please look for any errors reported earlier by that extension.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

&

event id 107

Failed to perform redirection of folder My Documents. The folder is configured to be redirected from to <>. The following error occurred:

The specified path is invalid each time the server is restarted.

Are these linked to problem and what is the solution?

thanks

Posted

If your using Sophos and its an issue with a service in Sophos.

 

Unfortunately I can't recall what the service is called but I'll check tomorrow and post

Posted
If your using Sophos and its an issue with a service in Sophos.

 

Unfortunately I can't recall what the service is called but I'll check tomorrow and post

 

well we did update the sophos console on the server at the same time..

Posted

For Folder Redirection to work correctly, users need write access on the local machine. You can still hide/remove access to C:\ for users when browsing My Computer, so don't worry about this.

 

By using the MMC (Start, Run, MMC), choose Local Users and Groups, then specify the local or a remote workstation. Under Groups, add Domain Users.

 

Now restart the workstation and logon as a user who you wish to use the Redirected Desktop/Start Menu etc...

 

Let me know how you get on :)

Posted
If your using Sophos and its an issue with a service in Sophos.

 

Unfortunately I can't recall what the service is called but I'll check tomorrow and post

 

secmon.exe (Even if you allow it, it still has an issue with it)

 

The whole reason we dropped Sophos, its not compatible with ranger

Posted

Sorry forgot to look today (battling with some CCTV cams that have decided to have a rest) but Strawbeery has it right. You need to disable HIPS.

 

Only way to cure it if your going to carry on with Sophos and Ranger.

 

Unfortunately adding secmon to the allow list doesn't help

Posted
Sorry forgot to look today (battling with some CCTV cams that have decided to have a rest) but Strawbeery has it right. You need to disable HIPS.

 

Only way to cure it if your going to carry on with Sophos and Ranger.

 

Unfortunately adding secmon to the allow list doesn't help

 

 

although it seems too at first, the hash changes on the file and hips will nuke it again.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...