Petergal

Thanks!

Petergal

Special kudos go out to the SBS support team in Las Colinas.  I consider Chris Puckett, Damian Leibaschoff, David Copeland, Douglas Boyd, Ed Walters, James Frederickson, Jeff Taylor, Jim Martin, John Bay, Justin Crosby, Mark Stanfill, Mike Lieser, Roderick White and Shawn Sullivan friends.  Keep up the outstanding work!  There are countless Microsoft customers that count on you for everything that you do.

My first day in my new position was Jan 15th.  I traveled my first day on the job!  We are delivering Launch Content mostly around Office 2007 and Vista.  I shadowed Charles Van Heusen in New Orleans and Baton Rouge on the week of the 15th.  The week of Jan 29th was in Boise and Salt Lake City with Fred Pullen.  The week of Feb 5th was spent in Redmond for TechReady (that's where Microsoft pulls in it's field people and shows us the new stuff).  The week of Feb 19th was with Stephen Demming in Baltimore and DC.  Today I am in Chicago with Don Roessler.  I will be flying solo in the April timeframe.  Check your local listings for a show near you! 

I am not sure what direction my blog will go.  I will definitely keep up my relationships with these geeks so if there is something late breaking and technical - you will see it here!  My initial thought is to have this be like an answer board for questions from events.  So whenever I say "ummmm, I don't know what licenses are required if you have Exchange 2007 Enterprise in an "edge transport" role and Exchange 2003 as your mailbox server...", I plan to post the answer on my blog.  Whatever the case may be, I hope that your visits to my blog prove to be valuable (mostly).

Petergal

What files to download:

l      From https://www.microsoft.com/downloads/details.aspx?FamilyId=C62D54A5-183A-4A1E-A7E2-CC500ED1F19A&displaylang=en, download efp.msi and V1Emulator.zip.

l      From https://www.microsoft.com/downloads/details.aspx?familyid=DC8332D6-565F-4A57-BE8C-1D4718D3AF65&displaylang=en, download netsvwrap.msi - the Virtual Machine Network Driver for Microsoft Device Emulator.

What to install:

l      Launch netsvwrap.msi to install the Virtual Machine Network Services Driver.  Follow the on-screen instructions.

l      Extract the contents of V1Emulator.zip.  Launch standalone_emulator_V1.exe to install the Windows Mobile 5.0 Emulator Manager.  Follow the on-screen instructions.

l      Double click on efp.msi to install the Windows Mobile 5.0 w/MSFP images.  Follow the on-screen instructions.

After the install is complete, you can access the emulator(s) via:  Start -> All Programs -> Microsoft Windows Mobile 5.0 MSFP Emulator Images.

The options to boot the emulators:

l      Device / Coldboot – Starts the selected emulator from a cold state (similar to a hard reset)

l      Device / Savestate – Restores the image from the last time the emulator was running assuming “Save State” was selected when the emulator was previously shut down or closed.

Configuring the emulator to connect to the LAN/Internet:

l      Launch the emulator of your choice (I strongly recommend the PocketPC.  It is much easier to navigate and it uses a touch screen).

l      In the Emulator Manager, click File -> Configure…

l      Click on the Network tab and place a check next to “Enable NE2000 PCMCIA network adapter to bind to:”.  In the dropdown, your physical network card should be selected.

l      Click OK.

l      Soft reset the device via File -> Reset -> Soft

Getting the emulator on the LAN/Web from behind a proxy server (think ISA server):

l      Tap Start -> Settings -> Connections -> Connections -> Set up my proxy server and place a check next to “This network connects to the Internet” and “This network uses a proxy server to connect to the Internet” and type in the local IP address of the proxy server.

l      If the proxy server uses a non-standard port (something other than 80) like the default SBS install w/ISA2004 does, you will need to modify the port for the proxy server.  Tap Advanced and then tap HTTP and edit the port accordingly.

l      Click OK all the way out

l      Launch Internet Explorer on the device and to go to https://mobile.msn.com

Getting the emulator on the internet through a standard NAT device (think the standard Linksys, DLink, etc. device):

l      Launch the emulator

l      Tap Start -> Settings -> Connections -> Connections -> Advanced -> Select Networks and change the top dropdown selection to “My Work Network”

l      Click OK all the way out.

l      Launch Internet Explorer on the device and to go to https://mobile.msn.com.

Enjoy!

Petergal

Remember to follow these steps (specifically uncheck Require SSL for the ExAdmin virtual directory in IIS) if you intend to use the MobileAdmin utility on your Small Business Server 2003 computer.  If not, when you search for a user/mailbox you will get the following error:

Server Error in '/MobileAdmin' Application.
--------------------------------------------------------------------------------

The remote server returned an error: (403) Forbidden.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The remote server returned an error: (403) Forbidden.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:

[WebException: The remote server returned an error: (403) Forbidden.]
   System.Net.HttpWebRequest.CheckFinalStatus() +680
   System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) +74
   System.Net.HttpWebRequest.GetRequestStream() +234
   Microsoft.Exchange.AirSync.Admin.Mailbox.propFindRequest(String deviceUri) +240
   Microsoft.Exchange.AirSync.Admin.Mailbox.getDevices() +194
   Microsoft.Exchange.AirSync.Admin.Devices.refreshDevicesTable() +135
   Microsoft.Exchange.AirSync.Admin.Devices.Page_Load(Object sender, EventArgs e) +190
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +750

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

The IP address of your local network adapter does not exist in the Local Address Table (LAT) for ISA Server. You will need to either add the IP address to the LAT or change the IP address of the network adapter. For more information, see Small Business Server Help.

This issue is caused by an incorrect value for LANNIC in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\

LANNIC is set when SBS is first installed.  When SBS setup sees two network cards during the initial setup (first run of setup, prior to the Component Selection Screen where you choose Exchange, Fax, etc) it will ask "hey, which of these two NIC's is your internal NIC?".  When you select the NIC, two things happen:  First, the other NIC is disabled.  Second, LANNIC is written to the registry with the GUID of the internal network card.  If you then subsequently swap cables, you might run into problems running the CEICW. 

To resolve this issue, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\LANNIC will have to be changed to reflect the actual GUID of the internal network adapter.

Here's what you do:

• Open Regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
• Expand Interfaces, you should see several folders underneath - highlight each of them, looking for a value called IPAddress with the internal IP address of the server.  You will need to determine which GUID (folder on the left with the really long weird number) is the actual internal network card.  Again, the one with IPAddress of the internal network card is the one you want.
• Right click on the GUID of the internal NIC on the left and choose "copy key name".
• Open notepad and paste the key into notepad.
• Now highlight the GUID in notepad (not the brackets, just the characters) and copy it.

For example, copy A7237F71-448E-4ED3-AE5E-2EF8976399B5 from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A7237F71-448E-4ED3-AE5E-2EF8976399B5}

• Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer and double click on LANNIC
• Copy the value you copied from notepad into LANNIC and click OK
• Re-run the Small Business Server Configure Email and Internet Connection Wizard.

This article has the same steps but the error is different.  If you follow the instructions in the popup error when running the CEICW ("Alternatively, disable the DHCP service manually, and then configure your client computer IP address properties.") you get further in the wizard but are then presented with the "ISA LAT error".

Happy SBS'ing!

Petergal

Result:

ActiveSync encountered a problem on the server. 

Support code:  0x86000108

This certainly sounds like a corrupt calendar item in the users mailbox or something goofy with the customers cell carrier (Compression issues maybe?).  So I fired up my Mobile 5.0 emulator and tested with the problem account (let's call him Justin).  Well, it failed with the same error code on the emulator.  So it does not appear to be device/carrier specific.  So the next thing we did was to export the mailbox to a PST and import it back into Exchange (exporting to PST *should* remove <not export> corruption).  After doing that it still failed!  Hmmmmm....this sounds like a job for Nextags!  Well, looking at Nextags logs is about one step better than getting cut with a rusty knife so I thought I would look around a bit more.  In the system log I found several events similar to the following:

Event Type: Information
Event Source: Ntfs
Event Category: (2)
Event ID: 37
Date:  7/17/2006
Time:  6:38:25 PM
User:  Domain\Justin
Computer: SBS-Servername
Description:
A user hit their quota limit on volume C:.

Event Type: Information
Event Source: Ntfs
Event Category: (2)
Event ID: 36
Date:  7/17/2006
Time:  6:38:25 PM
User:  Domain\Justin
Computer: SBS-Servername
Description:
A user hit their quota threshold on volume C:.

I wondered if disk quota limits were causing this to fail.  Note we have a public article on this event, it should be a Warning and not an Informational event!  So as a test, I turned off quota limits for the user on the C drive (open My Computer, right click on the C drive and click Properties, then the Quota tab, then the Quota Entries button.  Right click on the user and choose Properties and put the bullet next to "Do not limit disk usage" and hit OK).  This worked! 

The moral to this story:  ALWAYS check event viewer!!

Petergal

• I know the default behavior of a "clean" install of SBS.
• I ran into the same issue here at my machine at Microsoft (not SBS, actually on the Microsoft corporate network...you'll understand later).

Visio would really help in this description!

Site A
SBS2003 with a single NIC
10.0.0.2 is the IP
Multiple clients on the 10.0.0.x network

Site B
Several clients on the 10.0.1.x network

Site C
Several clients on the 10.0.2.x network

Here are the facts:

• The server and clients on Site A cannot access shares on Site B or Site C.
• The clients on Site B cannot access shares on Site C.
• The clients on Site C cannot access shares on Site B.
• Clients on Site B and Site C cannot access shares on client computers on Site A.
• Clients on Site B and Site C can access shares on the server itself located in Site A.
• All clients and server can access shares on their own site.
• All clients and server can ping all other clients by both FQDN and IP.
• Site A, Site B and Site C are all connected via dedicated T1 links.
• All the clients were configured correctly regarding their default gateways and DNS settings.
• All clients are joined to the SBS domain.

The error when trying to access shares was:
---------------------------
\\ClientComputer

No network provider accepted the given network path.
---------------------------
OK  
---------------------------

Here's the solution:  SBS configures via Group Policy the Windows Firewall on Windows XP SP2 machines.  There are exceptions for File and Printer Sharing in the policy that lock down File and Printer Sharing access to the local subnet of the client.  I edited the Windows Firewall Group Policy (Opened Group Policy Management, navigated to Forest -> Company.local -> Small Business Server Windows Firewall.  Right clicked on Small Business Server Windows Firewall and clicked Edit.  This brought up the Group Policy Object Editor for the Small Business Server Windows Firewall policy.)  Navigated to Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile.  On the right, opened the properties for "Windows Firewall:  Allow file and printer sharing exceptions".  The default configuration for "Allow unsolicited incoming messages from:  LocalSubnet".  I changed this to the following:  10.0.0.0/24,10.0.1.0/24,10.0.2.0/24.  I then did a "gpupdate /force" on a test client and was then able to access shares.  A quick test on clients on the different subnets was successful as well.  This policy does not apply to the SBS server itself, thus clients could access shares on the SBS box.

I had the same issue here on my machine on the Microsoft corporate network.  I would share something out and would get complaints from some people saying "you NOOB, give me access" (or some other choice words).  My computer's Windows Firewall is not managed via Group Policy.  I had to edit the Windows Firewall configuration on my local machine to allow access from other subnets.  Here's the location for the manual configuration on the client:  Properties of the Local Area Connection -> Properties -> Advanced -> Settings -> Exceptions -> File and Printer Sharing -> Edit -> Change Scope -> Any computer.

Have a good weekend!

Petergal

The customer was getting the above error when clicking on Public Folders in Exchange System Manager.  He was also getting the following error when running the Add Distribution Group wizard and selecting to create an "archive public folder":

---------------------------
Add Distribution Group Wizard
---------------------------
The wizard could not successfully configure this group. The following could not be completed:

- The Exchange public folder could not be created.

Do you want to keep this group?
---------------------------
Yes   No  
---------------------------

This article was followed without success.  What we did to resolve it was to remove a value in Active Directory using ADSIEdit.  We had to install the Windows 2003 Support Tools to get access to ADSIEdit.  With the SBS 2003 media, the support tools are located in cd2\support\tools\suptools.msi.  The attribute is msExchSecureBindings.  The value is :443:. 

Specifically,

Configuration >

    Services >

        Microsoft Exchange >

            Domain Name >

                Administrative Groups >

                    First Administrative Group >

                        Servers >

                            Servername >

                                Protocols >

                                    HTTP >

                                          1 >

                                              Exadmin

We right clicked on Exadmin and clicked Properties.  We scrolled down until we found msExchSecureBindings and clicked Edit.  By default, the value was/is :443: - we clicked to highlight :443: and clicked Remove.  It then showed <Not Set> for msExchSecureBindings.  We then restarted the Microsoft Exchange System Attendant and then restarted the IISAdmin service. 

For all you (us) geeks, here is the full "distinguishedName":  CN=Exadmin,CN=1,CN=HTTP,CN=Protocols,CN=SERVER,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=local

The root cause is because the certificate that was installed in IIS did not contain the "servername" in the "subject" field (you have to view the certificate and click the details tab to see this field).

Other errors per this article are:

The SSL certificate server name is incorrect.
ID no: c103b404
Exchange System Manager

The connection was aborted. Ensure that the settings on your default Web site are correct and refresh the Public Folder Tree
ID no: c103b402
Exchange System Manager

Have a good weekend!

Petergal

SBS2003
4 devices - all sync fine

• 2 Cingular 2125 SmartPhones
• 2 Cingular 8125 PocketPC Phones

Install Exchange 2003 Service Pack 2

• 2 Cingular 2125 SmartPhones still sync
• 2 Cingular 8125 PocketPC Phones error with 0x80830003

Solution (workaround):
On the 8125 device(s), click start -> settings -> connections -> connections.  Cingular appears to have renamed “My ISP” to “MEdia Net”.  Click “Edit My Proxy Server” under “MEdia Net” and UNCHECK “This network uses a proxy server to connect to the internet”.  By default it was set to “wireless.cingular.com”.  Soft reset the device.

Note we believe this issue to be related to 0x8503001A (IIS compression settings) but has been unconfirmed.