Link to home
Start Free TrialLog in
Avatar of Jeff Perkins
Jeff PerkinsFlag for United States of America

asked on

Problem with folder redirection on Server 2016

Ok, I migrated from SBS 2011 to Server Essentials 2016, I had some issues with folder redirection on the migration, see this previous question, but believed everything was solved until I demoted the old server and took it off line.   

Right now, if I log into a workstation with my domain admin profile or one of the user profiles, everything works without a hitch, documents, desktop, and favs are redirected to new server.  

The problem is when I log into the server, I only have one profile, my domain admin, which is allowed to log onto new server, and it doesn't matter if I log in remotely or locally, I get a network error because the desktop is looking for the redirect path to the old server which is now offline.  This only happens on the server.  

I'm sure this is Group policy problem, but if you read the previous question, you know I'm not at all remotely proficient in GP, and could use some help locating the problem. 

I also have some sort of issue on the server, the network icon in the systray, see this SS 

User generated imagethe icon shows there is no internet access, but this is not true, I can browse the internet fine from the server.

I ran the GP report wizard and the folder redirection error points me to the even log where there are 3 event's related to Folder Redirection.  The first one is a 510 error: The folder redirection policy hasn't been applied. It's been delayed until the next sign-in because the group policy sign-in optimization is in effect.

The other 3 are 513 errors relating to video, music, and pictures: Failed to remove policy and redirect folder "Videos" to "C:\Users\jp\Videos".
 Removal options=0x20009231.
 The following error occurred: "Failed to build the list of regular subdirectories under "\\oldServer\RedirectedFolders\me\My Documents\My Videos".".
 Error details: "The network path was not found.

Occurring right before the 510 error there are 3 errors about CertificateServicesCleint 6, 13, and 82.  If those are relevant, I will get more info upon request. 

Not sure what other information might be useful, so just ask. 

Thank you in advance.




Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

start with fixing the network problem. Where is dhcp server? (Servers should have static addresses)
Avatar of Jeff Perkins

ASKER

David,
DHCP is handled by the firewall/router.  
I ran an ipconfig /all on the server and everything looks to be good there.  Of note, I logged back in today just to run the ipconfig again, and now the icon for network does say internet access.... not sure what changed, because I just left it in hopes that someone would give me some guidance before I started messing things up.  
So evidently the networking issue is resolved.  I logged out and back in again on the server, in hopes that my folder redirect problem would go away, but it did not. Still getting the same network error as it tries to access the folder redirect on the old server.
ASKER CERTIFIED SOLUTION
Avatar of Steve Knight
Steve Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Oh and one more, if your router is handling DHCP, it should be giving out your domain controller / DNS server ONLY as DNS server too.  If you can't configure what DNS it gives out fom the router then turn it off being DHCP server and configure the server to do DHCP instead.

In a domain environment the only DNS in use MUST just be that provided by the domain controllers unless we are talking big IT systems that know when not to!

Steve
Steve,
Thank you for chiming in to help.  Ok I will address what you have said....
First, yes, the server has it's own reserved IP Address and is the DNS for my local network, the firewall router points to the internal server for local addresses and the proper forwards go from there.  DNS IS functioning fine, as is the network and internet on all systems.  That original problem of the icon saying there was 'no internet access' was incorrectly reported by windows, as the dns and internet were working fine, but I suspect there was some sort of cache that caused this, but it is now a mute point as everything on the internet/dns/dhcp side of my network is working AOK.
   
     Next, you said: As to the redirection it sounds like it is trying to "undo" the existing redirection.  I would suggest easiest way is either to adjust them in the registry directly and/or by moving the folder locations in Explorer - i.e. right click on the desktop folder and use the "Location" tab and move it to the location you DO want.  Say "no" to moving the existing contents.
     The folder redirection is working on every client on the network for multiple users including my domain admin user, the only place that I'm getting this error is on the server when I log on there.  Funny thing because the redirected folders are on the server and stored there without any issues..... Not sure if this was understood from my question and want to insure that if I make the changes within the server registry that this will not affect all of my other machines that are already working as they should?
   
     As for the DNS, yes the router/firewall is only pointing to my server for DNS.

I have to ask if the redirect didn't take place correctly, is that just because I probably didn't update the GP on the server before taking the old server off-line?  If so, this makes sense, and I just want to confirm again that this won't cause other problems with the client systems?      

   As for the security issues of using domain admin to login to local system, as DA I have two desktops that I use regularly, and need the redirect to work with these desktops, and don't use this particular DA login to access the other desktops in the organization, I do have a DA that is not part of the redirected group for work on other workstations.

That is all good to know,  sorry for questioning what you had setup but when I heard router was doing your dhcp 9/10 times it flags up incorrect dns.

Anyway the redirection is related to the user profile only.  The policy applies and does its stuff.  I imagine the admin user on the server is pointing at the old server still and so as policy applies its having problems.

The actual desktop redirected files for admin are on the new server location no doubt but just the redirection is wrong.

So changing the registry on the server suggested only affects that user that is logged in at the time and only on that device.

So there is zero chance of van affect any other user or computer and should solve your problem imo.

Steve


Awesome!  Yes, I know most people setting up small domain don't know the importance of DNS on DC, as well as the need to route back from router, but I've been doing this for a little while.  Just couldn't figure out what to do about the redirect that wasn't working.... or at least sort of....LOL  
I'll make the change you suggested and report back.  Thanks again for your help!
Thanks for the testimonial and hope that helped sort out the issue.  Some seemingly complex issues in Windows as you know boil down to just knowing which one thing to search for, and other trivial sounding things take us weeks to fix.