• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1672
  • Last Modified:

Public Folder / Shared Calendar issue after migrating SBS 2003 to SBS 2011

I have recently performed a migration of a SBS 2003 server to SBS 2011 server which mostly went as planned. The public folder did not end up working quite right and now I am faced with a variety of small issues related to the shared calendar, plus I have remnants of the old 2003 server still showing up, but that machine is now long gone. I would like to configure the system to forget the old server (replication) and fine tune the public folder to be accessible and allow edits from Outlook 2010 and OWA. I am not using any older clients, but do have clients connecting with IOS and Android. The shared calendar is currently only accessible from Outlook when locally logged into the domain (or via remote access to a locally logged in PC) and even then, I get complaints from users who can't make changes to items they created in the calendar. Where do I begin?
0
Norm Dickinson
Asked:
Norm Dickinson
  • 5
  • 4
1 Solution
 
jkocklerCommented:
First thing to do is run DCDIAG on the new server, to make sure it's clean.

Post the output if you need to.

once it's clean, we can move onto removing the old server's metadata.
0
 
Norm DickinsonGuruAuthor Commented:
I ran using /dnsall and it showed two errors. One was related to NCSECDESC and the other was SYSTEMLOG. The Systemlog one was an issue with the Sharepoint timer. Attached output.
0
 
jkocklerCommented:
Okay those 2 are fine.

Follow the below article, it should work fine for you to get rid of the old server remnants. Obviously you are applying this to the old 2003 server objects.

http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx#bkmk_graphical
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Norm DickinsonGuruAuthor Commented:
The old server doesn't show up in that location - only the new one is there.
I do see indictions of the old server in the event log under critical errors, including Event ID 2155 every six hours, process w3wp.exe as well as in an Event ID 502, folder redirection - which appears to happen when I attempt to log in as Administrator on a connected workstation and it looks for a folder which was located on the old server.
0
 
jkocklerCommented:
Is the 2155 and w3wp.exe part of the same event, or 2 different?

As for the folder redirection, what does it state exactly? There are quite a number of folder redirection errors that can result from changing servers.

Usually though, if you have a folder redirection problem pointing to an old box, it means that the new server did not fully copy the contents from the old location, to the new location, resulting in a scenario where it will not remove the policy and/or use the new folder redirection policy, until it satisfies the move from the old location.

Depending on what your current redirection scenario is, you might end up having to manually go through the registry, and delete all references to the old server. I have had to do this with workstations, but never a server, so I would be very cautious in your case.
0
 
Norm DickinsonGuruAuthor Commented:
Yes, the 2155 is the event ID for the W3WP.exe event. The redirection event is separate and is stated as follows:
Event 502, Folder Redirection.
Failed to apply policy and redirect folder "Documents" to "\\oldservername\users\administrator\my documents."
Redirection options=0x9021
The following error occurred: Cannot create folder "\\oldservername\users\administrator\my documents."
Error details: The network path was not found.
0
 
jkocklerCommented:
Yea that redirection error is going to require registry editing.  Are you still using folder redirection?  If not, you might be able to disable the policy, first choosing to leave the folders where they are. This may get rid of the error.

If you are still using folder redirection, because you already removed the old server, deleting references to the old server from the registry is your only option. Basically search the registry for the old redirection path, and delete those keys.
0
 
Norm DickinsonGuruAuthor Commented:
Yeah, okay, thanks. It sounds like a lot of fun...after a full backup, that is.
0
 
jkocklerCommented:
Yea definitely a backup, but its really not that big of a deal. I doubt you will brick anything, just as long as you search for the full path, old server name included.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now