mignonnedavis
asked on
sbs 2008 want to redirect folders on computer already connected to network
I accidently connected acomputer to the sbs 2008 without the redirected folders clicked off. so, I thouight I'd just click that off, and re run the connect program. but it doesn't work. any idea how to get a computer already attached to a server to start redirecting folders to the server?
You can access the redirect options in SBS via the SBS Console by selecting the user's account properties > Folders (on the left pane) > Check box - Enable folder redirection to the server.
Should be noted as well that there is no need to disconnect/reconnect the client system for this to work. Update the options as needed for your user accounts in the SBS console and log off and on a few times.
[NOTE] Data redirect needs to start on the client side not the server side for it to function. In other words, if you place a file in the User Redirects user directory it will not show on the client side when the user logs in. You must sign the user in and put the files in the Documents or desktop area for the SBS redirection to function.
[NOTE] Data redirect needs to start on the client side not the server side for it to function. In other words, if you place a file in the User Redirects user directory it will not show on the client side when the user logs in. You must sign the user in and put the files in the Documents or desktop area for the SBS redirection to function.
ASKER
I had already done what you suggest with the check box (that's what I meant by clicked it off, sorry). It had absolutely no affect on users who had already been set up without the redirect. so, are you saying that if I instead log the user in, and move their files the redirect folder on the server, this will start the redirecting?
No, the files need to be on the client computer. Once you make this change it will typically take up to 4 - 5 log ins for it to be in effect.
ASKER
So, since it sounds like I already did everything I could, I should just try logging in and out over and over till I see the redirect symbols?
That would be correct assuming all has been done correctly.
If you are not sure then start from the beginning. Firstly, you would need to completely remove the system from the domain, make sure your redirect settings are turned on, then reconnect using http://connect/ which I'm assuming you used the first time to connect the client systems. When you do so, be sure to match the local user account to the domain account. If the local user account documents are set to private the account documents and settings will not transfer.
If you are not sure then start from the beginning. Firstly, you would need to completely remove the system from the domain, make sure your redirect settings are turned on, then reconnect using http://connect/ which I'm assuming you used the first time to connect the client systems. When you do so, be sure to match the local user account to the domain account. If the local user account documents are set to private the account documents and settings will not transfer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks again. I've checked all the permissions, etc. and all are good. I had 5 computers which were not redirecting and after the logging in and out several times, I'm only left with 2 which, no matter what, will not redirect. Would you suggest deleting the user and computer and re-adding the user and the computer again?
I have run into this several times with SBS, When you create a user account with redirects it creates the redirected folder to go with the account. Sometimes it does not create the correct permissions on the redirected folders for the user on the server. It is possible that recreating the user account could solve this issue but then you could adjust these permissions manually just the same. Either way.
When you go to connect the client computer and xfer their data. Be sure to have the client system set to use DHCP > open a browser and go to http://connect/ > run the connect software and select 'Setup other people' > Input Admin Account > Add User that will be using the client > Match the users Old (local) account with the New (domain) account. If the Old is not visible then this means their documents and settings directory is set to private and this must be undone prior to proceeding.
[NOTE] Though it has not been officially published in Microsoft's Best Practices documentation, many MCSEs, MCPs, and Direct MS Engineers advocate throwing one's keyboard and/or kicking the system in question during this troubleshooting process. Microsoft expressly covers these practices and warranties all hardware against failure or damage. REF Article: http://support.microsoft.warranty4stupidity.com/WeDont/really/coverThis
[Disclaimer] A portion of this post has been meant purely as entertainment and is not factual. If you can not spot which portion then, well, that is very very sad.
When you go to connect the client computer and xfer their data. Be sure to have the client system set to use DHCP > open a browser and go to http://connect/ > run the connect software and select 'Setup other people' > Input Admin Account > Add User that will be using the client > Match the users Old (local) account with the New (domain) account. If the Old is not visible then this means their documents and settings directory is set to private and this must be undone prior to proceeding.
[NOTE] Though it has not been officially published in Microsoft's Best Practices documentation, many MCSEs, MCPs, and Direct MS Engineers advocate throwing one's keyboard and/or kicking the system in question during this troubleshooting process. Microsoft expressly covers these practices and warranties all hardware against failure or damage. REF Article: http://support.microsoft.warranty4stupidity.com/WeDont/really/coverThis
[Disclaimer] A portion of this post has been meant purely as entertainment and is not factual. If you can not spot which portion then, well, that is very very sad.
ASKER
logging in and out a few times fixed the redirect on all but one computer. So, I just removed the computer from the server and then re-did it. Still not sure why it didn't work on this one though.