Does on-premises OneDrive for Business ***REQUIRE*** an Organization ID for synchronization to local systems?

Question

We have an on-premises SharePoint 2013 SP1 deployment in our lab.  We access the server through three methods: direct LAN access inside the firewall, over the Internet via Forefront TMG, and over the Internet via DirectAccess.  In all three access
cases, almost everything functions exactly as expected.
One exception is OneDrive for Business (the on-premises version).  After creating my MySite, I can browse my OneDrive for Business, upload/download files, preview documents, share with other SharePoint users, etc.  That stuff works properly. 
But if I click the Sync link to establish a synchronization connection between my OneDrive for Business and my desktop system, the "We're getting things ready to sync..." dialog gets overridden by a OneDrive for Business error box - "We can't
connect to the specified SharePoint site...".
We see this behavior whether inside or outside the firewall.  I am logged into Windows, Office 2013 applications, and SharePoint using the same credentials: my Windows domain account.
Running Wireshark and Fiddler on my workstation, I see conversations being sent to live.microsoft.com when I click on the Sync link.  This leads me to believe that *ALL* such sync connections are established by looking up the user's account in the Microsoft
cloud (even if the credentials are for an on-premises domain) and, further, that because of this, businesses must create an official in-cloud Organization ID for their domain even if they are not actually using Office365 services (e.g. even if they are only
using on-premises SharePoint) if they want to sync with on-premises OneDrive for Business.
I have seen almost zero documentation about this, and certainly nothing that states that you MUST register for an Organization ID even if you are only using on-premises SharePoint and on-premises OneDrive for Business, yet this seems to be the behavior I
see and that theory seems to be supported by my network traces.
So...
1) Can anyone confirm or deny this theory, or at least give a lot more detail about how SharePoint attempts to "find" the service when you click on the Sync link?
2) If you HAVE successfully set up on-premises OneDrive for Business and have NOT had to register an Organization ID, can you please share the details of how you configured things?
Many thanks for any help or pointers...
tkarp

Answer 1

I Just checked pre-requisites for Onedrive on-prem:
To support OneDrive for Business document libraries in SharePoint Server 2013, you must have:
A SharePoint Server 2013 My Site Host.
Configured the User Profile Service application.
The user must have an existing My Site with the personal site collection created.
To support synchronizing document libraries to a user's client workstation with the OneDrive for Business Windows Sync client, you must have:
Either
Office 2013 Standard or Office 2013 Professional Plus, or the stand-alone OneDrive for Business Windows Sync client.
An Office 365 subscription that includes the Office 2013 applications.
Client workstations running Windows 7 or Windows 8.
If you have to purchase Office 365 then you will need Organization ID which will be required for Document SYNC, or yous should have Office 2013 installed on system.
If this helped you resolve your issue, please mark it Answered