Link to home
Create AccountLog in
Avatar of xzay1967
xzay1967

asked on

Turn off redirected folderf rom workstations

Hello all, my client's sbs2008 server crashed, now the workstations are stilling looking for it in terms of folder redirection. How can I prevent the workstations from trying to connect to the now absent server? Workstations are XP and W7.
ASKER CERTIFIED SOLUTION
Avatar of VirastaR
VirastaR
Flag of India image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of xzay1967
xzay1967

ASKER

Thanks for the response, when I ran the commands you suggested, I got the below results

C:\Users\wanda>set 1
Environment variable 1 not defined

C:\Users\wanda>gpupdate /force
Updating Policy...

User policy could not be updated successfully. The following errors were encount
ered:

The processing of Group Policy failed because of lack of network connectivity to
 a domain controller. This may be a transient condition. A success message would
 be generated once the machine gets connected to the domain controller and Group
 Policy has succesfully processed. If you do not see a success message for sever
al hours, then contact your administrator.
Computer policy could not be updated successfully. The following errors were enc
ountered:

The processing of Group Policy failed because of lack of network connectivity to
 a domain controller. This may be a transient condition. A success message would
 be generated once the machine gets connected to the domain controller and Group
 Policy has succesfully processed. If you do not see a success message for sever
al hours, then contact your administrator.

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results.

C:\Users\wanda>
Hi,

Glad to see you tried.

By the way at first its not set 1(One) it's set l (el)

Then followed by that try the gpupdate /force.

I see some network issues from this machine to DC based on the message you are getting.

ok,no problem will first check whether the machine is connecting to the right DC first and based on the results will take it from there.

Let me know :)
Well remember the server is no longer available, hence the network error when trying to connect to it. So, I re-ran the command and it is still trying to connect to the dead/absent DC. I would like to set it so it no longer try to do folder redirection. There is no DC at the moment, so I need everything set back to local.
OK, that's what I thought, so we might need to reset the secure channel between the machine and the DC.

So now if you have admin privileges

Proceed with the below KB Article:

http://support.microsoft.com/kb/216393

Hope that helps :)
Based on your response "reset the secure channel" I assume I need to perform this procedure. I just need a layman explanation what this will do in terms to the user's ability to log on to the computer etc. These are real estate agents with little patience (no offense). I just want to make sure that doing this won't complicate their life make it so I have create new logon credentials for them.
_____________________
Netdom.exe
For each member, there is a discrete communication channel (the security channel) with a domain controller. The security channel is used by the Netlogon service on the member and on the domain controller to communicate. Netdom makes it possible to reset the security channel of the member. You can reset the member security channel by using the following command:
netdom reset 'machinename' /domain:'domainname
where 'machinename' = the local computer name and 'domainname' = the domain where the computer/machine account is stored.

Suppose you have a domain member named DOMAINMEMBER in a domain called MYDOMAIN. You can reset the member security channel by using the following command:
netdom reset domainmember /domain:mydomain
You can run this command on the member DOMAINMEMBER or on any other member or domain controller of the domain, provided that you are logged on with an account that has administrator access to DOMAINMEMBER.
I was able to turn off the redirection by editing the registry keys for shell folders and user shell folders.
This pointed me in the right direction