As part of the troubleshooting, I had the user login to a different workstation with their same credentials and we experienced the same slow login. when I looked at the event log, I saw the following error:

Log Name:      Application
Source:        Microsoft-Windows-Folder Redirection
Date:          4/21/2012 10:57:42 PM
Event ID:      502
Task Category: None
Level:         Error
Keywords:     
User:          DOMAIN\firstlast
Computer:      DOMAIN-PC.DOMAIN.local
Description:
Failed to apply policy and redirect folder "Documents" to "\\SERVER\RedirectedFolders\firstlast\My Documents".
Redirection options=0×9021.
The following error occurred: "Failed to copy files from "\\SERVER\RedirectedFolders\firstlast\Documents" to "\\SERVER\RedirectedFolders\firstlast\My Documents"".
Error details: "The system call level is not correct.
".

I did some research on this error, and came up with one valid result, which claimed that it was being caused by server quotas. As part of the trouble shooting, I turned off quota’s on the server, however I had previously checked the users properties in the SBS 2008 console and verified Folder Redirection was enabled, but the quota’s box was unchecked.

I do question why the policy was attempting to take the same server and users folder and move files from the “Documents” folder to the “My Documents” folder. As I checked the GPO, it is set to move the files from the old location which is a default setting.

So to take the troubleshooting a step further, I ran GPRESULT /V >C:\gpresult.txt  and viewed this text file. I do not see anything out of the ordinary being applied to the computer. Now, when I check the GPO’s on server, I see a old GPO that was created and is no longer being applied. In that GPO, I see the following:

As you can see from this screenshot, the disabled “Folder Redirection” GPO had the policy pointed to the \\SERVER\RedirectedFolders\%USERNAME%\Documents but if we look at the Small Business Server Folder Redirection Policy which is created by the Small Business Server, it is pointed to \\SERVER\RedirectedFolders\%USERNAME%\My Documents  as shown below

On the Windows 7 machine, when I look at the properties of the “My Documents” folder, I see it is still pointed to the old policy’s setting, of \\SERVER\RedirectedFolders\%USERNAME%\Documents as shown below:

So how do we go about fixing this? Well, the best way to fix this is to edit the current GPO, Small Business Server Folder Redirection Policy. On this GPO, I changed the setting “Move the contents of Documents to the new location” to disabled by unchecking the box as shown below:

Then, on the Windows 7 machine, at the command prompt type in GPUPDATE /FORCE and then logoff

Now I login as that user, and look at the event log. We now see success, as the policy does not need to move the existing “Documents” to “My Documents” and the policy is able to successfully apply as shown below.

Now there is one more step to fix this issue. I will need to copy the data from the “Documents” folder to the “My Documents” folder. When I attempted to look at the old Documents folder, it was now empty. The reason for this, Offline Files are enabled on the Windows 7 machine, and as it couldn’t connect to the previous path, all the time the user was saving documents it was offline as you can see in the previous picture of the properties of My Documents it was missing the green sync icon. So when I logged in to the computer with the fixed policy, the Windows Sync Center determined it was now online and able to write to \\SERVER\RedirectedFolders\firstlast\My Documents , and it has the data in the CSC cache, so it just copied the data back to the server for me. If you don’t have Offline Files enabled, simply copy the data from Documents to My Documents folder. Here is a screenshot showing it now online

If you are wondering why there are two My Documents folders, the second one that is not Sync’d is actually Documents. I just deleted this folder as it is not valid.

I suggest re-enabling this policy setting once the issue is resolved so that if you have a user who didn’t have this policy applying or in the SBS Console you checked the box  and you now want it, that the files are moved from their default location to the server location.

I also saw that Microsoft released a hotfix titled You encounter a long logon time after you enable the "Do not automatically make redirected folders available offline" Group Policy setting in Windows 7 or in Windows Server 2008 R2 at  http://support.microsoft.com/kb/2525332  however, in this case it does not apply.

As you can see, the error The system call level is not correct is a very generic error which by just looking at it, tells you almost nothing.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

Upon doing some more research, I came across this hotfix from Microsoft http://support.microsoft.com/kb/981259 which does not specifically address Exception e0010004 but does address e0010005. I installed this hotfix and then proceeded to manually transfer all FSMO roles using NTDSUTIL on the SBS 2011 server from it’s self to it’s self . This might sound strange, but I wanted to do this per another article I read on Microsoft’s site. Once I confirmed that all the roles transferred over from the new SBS 2011 to it’s self. I then moved the roles back to the old SBS server. Then verifying event logs, everything looked clean and happy.

I also noticed this event on the old SBS 2003 server. This seemed odd to me because look at the user….it is a a SID with no matching name. This is not normal.

I then unpromoed the failed SBS 2011 server and removed it from the domain. I then decided to inspect the SBS 2003 DNS server. I noticed under GC’s that there were two entries. One was the current server, in this case 10.55.100.10 and another of 10.55.100.60. Well there was no other GC with an IP of this, so that stood out like a sore thumb. I then deleted this invalid entry and looked at all other entries, Name Servers, etc. to verify it was clean.

On the old SBS 2003 server, I followed Microsoft troubleshooting to increase my logging. To increase NTDS diagnostic logging, change the following REG_DWORD values in the registry of the destination domain controller under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
Set the value of the following subkeys to 5:
5 Replication Events
9 Internal Processing
Note Level 5 logging is extremely verbose and the values of both subkeys should be set back to the default of 0 after the problem is resolved. Filtering the Directory Services event log should be performed to isolate and identify these events.

I did this on the source controller even though it mentions to do this on the destination server. Next I restarted netlogon service via command prompt. NET STOP NETLOGON & NET START NETLOGON

I performed the migration again. It failed, but I was able to capture a lot more events in the event log. This time I saw

Event ID 1925: Attempt to establish a replication link failed due to DNS lookup problem. Following  http://technet.microsoft.com/en-us/library/cc778061(WS.10).aspx  I started looking at DNS as the issue. this lead me to http://technet.microsoft.com/en-us/library/cc785014(WS.10).aspx It turns out, that someone previous had turned of Zone transfers. The DNS server looked like this:

and this:

To fix it, it should look like this:

and

Make sure to also check the AD domain, in this case csg.local, as those settings were also modified.

I also noticed that they had DNS forwarders on, pointing to external address’s, but when I ran the original Internet Connection Wizard on the SBS 2003 server, it made no mention of this. Weird.

Ah, once I did this, I was able to migrate correctly.

Note, make sure to cleanup the old failed SBS 2011 servers from AD, Name servers and DNS so you get a clean migration.

As this was a new customer for me, I had no knowledge of the previous IT person’s skills or abilities, or how things were setup or should I say not setup correctly. Lesson learned is when you enter a situation where you don’t know what was done before, look at everything, even though it is time consuming, the troubleshooting takes even more time.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

• Small Business Server 2011 Standard Edition
• Small Business Server 2011 Essentials
• Windows Storage Server 2008 R2 Essentials
• Windows MultiPoint Server 2011

More information about this update is available on the Official SBS Blog page at http://blogs.technet.com/b/sbs/archive/2011/09/29/windows-server-solutions-bpa-updated-september-2011.aspx

So how do you get the update? First, make sure you have the Microsoft Baseline Configuration Analyzer 2.0 installed. To get it, go here. Next, make sure to download and install the Windows Server Solutions Best Practices Analyzer 1.0 here

During the install, you will be prompted with this screen:

Make sure to check this box during your install, or you will not be prompted to automatically update!

Once you have it installed, launch the BPA either via the SBS Console under security (if you selected to integrate it in the console) or when you launch it under the start menu. You will see in the system tray an icon/pop up stating to update, like this:

Select that, and a window will open

Close the BPA you have open and then wait about 5-10 seconds. The next box will change and allow you to click on it. That’s it, you are now updated!

Hey Lyle, I don’t see it prompting me. Why?

Ok, so you got it installed, but now you launch it and don’t see it prompting you for the update. No problem, here is how to fix this:

Open up the registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsServerSolutions\BPA

Look for the DWORD item “Update”.  It is probably set to a 0. We want to change it to a value of 1. It should now look like this:

Close out the BPA if you have it open. Now re-launch it and you will see it appear in the SysTray.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

For the time being, hold off on installing RU3 until Microsoft get’s this fixed. In fact, they state that they have pulled the Rollup for now. I suggest looking at the EHLO link above to confirm when it is fixed.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

Enjoy.

Lyle Epstein

Kortek Solutions

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

For a list of versions and when they were shipped, see http://socialcompare.com/en/comparison/android-versions-comparison

The bug I identified was if you setup the phone to Sync with the Exchange server, in this case Exchange 2010 SP1 RU2 and then proceed to select a contact, change the picture of the contact to one that is on the device, and re-sync, you will now see the new picture in your Outlook. That is how it is suppose to work. The bug part comes in when you now edit that contact, say change the phone number or email address. Now sync the device, and you will notice the data doesn’t change in the device. The only way to fix it from my testing was to delete the contact via the phone. Once you do that, re-sync, and it will be gone from the Contacts in Outlook. Now go into your deleted items and you will see the contact. Move it back to your contacts, and re-sync the phone, and the contact is now correct on the phone. But if you make a change to the contact again, you will run into the same issue.

This was VERY annoying! I had found an update to the Android OS but it required rooting the phone, something I didn’t want to do. After the update came down today from Sprint, I retried my issue, and the bug has now been fixed. Other things I noticed in the new update is the support for OOF, or Out of Office. That is a nice touch as Active Sync get’s more aligned to the features in Exchange 2010 and EAS. I also noticed that the new update now enforces Active Sync’s security policies, including requiring a device password.

Now we wait for Microsoft’s own Windows Phone 7 to start supporting more Exchange EAS policies. If you are interested in knowing more about EAS, here is a chart by Marco Nielsen

Versions

The important versions of EAS usually follow the Exchange Server releases and they are are currently:

More details can be found here.

Compatibility Comparisons

Due to the incremental versions, protocol licensing and various implementations on different mobile devices, OS platforms and software clients it is very hard to get a complete view of what features are supported on a given device. Even if the mobile device is running a specific OS platform, the OEM, and mobile operator (especially here in North America) can decide to make specific changes.

I have found several references that may help, but all will obviously become out of date as new platform versions, software and devices come out.

I take no responsibility for their accuracy or the content. All information should always be tested on the devices you have on hand. I also apologize if the links become dead after a given amount of time, please ping me and I can update.

This excellent chart was posted by Marco Nielsen at http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=22540&zoneid=100

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

The White House is currently reviewing a new set of much tougher laws for software piracy, including jail time of up to 20 years. There are several other items in this list of recommendations that do not pertain to software, like drug offenses, but all fall in the intellectual property category. If you want to see what these new limits are about take a look at http://www.whitehouse.gov/sites/default/files/ip_white_paper.pdf 

I am pretty sure this one will get signed into law. This is a good thing, as software piracy hurts everyone.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog

In order to identify what originally happened in the migration, I went to C:\Program Files\Windows Small Business Server\Logs and viewed errors.log file. In this file, it showed ConfigureGP: Windows Small Business Server group policies cannot be configured. This was a good clue that this part of the migration got messed up. It is quite similar to the issue talked about on the official SBS Blog site

How to Manually Create the SBS 2008 and WSUS Group Policies Objects at http://blogs.technet.com/b/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx 

To fix the issue, follow the instructions on that site except the difference here is that this is a SBS 2011 server and that blog entry was written for SBS 2008. Instead of using the file gpofix.txt that is listed on that site, use the updated SBS 2011 file you can download here

I suggest before doing this, to backup your GPO’s, WMI filters and delete these GPO’s and WMI filters as they will be recreated with this script. if you don’t know how to backup your GPO’s, check out this site http://www.petri.co.il/backing-up-group-policy-objects.htm 

When you run this updated script, it will create the following Group Policies objects

• Windows SBS Client – Windows 7 and Windows Vista Policy
• Windows SBS Client – Windows XP Policy
• Windows SBS Client Policy
• Windows SBS CSE Policy
• Windows SBS Users Policy

In addition, 3 WMI filters will be created

• Windows SBS Client
• Windows SBS Client – Windows 7 and Windows Vista
• Windows SBS Client – Windows XP

Everything else on the Official SBS Blog site is the same. To confirm that it was applied correctly, take a look at your Group Policy Manager and you will see the newly created ones with the current date and time.

Of course if you want to see even more details, open the file GPOTask.log at C:\Program Files\Windows Small Business Server\Logs and you can see each action that was taken. If you are not aware of this folder and logs, it is one of the standard places I look on a SBS 2008 or SBS 2011 server when troubleshooting SBS related issues.

Lyle Epstein Kortek Solutions Lyle Epstein's Systems Engineer Blog