• BOINC_Data\symbols\advapi32.pdb\F759D3F1C6614313B07C84BC33F02E4D2\advapi32.pdb - modified 6 Feb 2009, created 12 Dec 2013
  
  compared to: F:\Symbols2\advapi32.pdb\0075E37A13F84D4E8DDDDA6BAA5F58712\advapi32.pdb - modified 18 Jul 2009, created 7 Dec 2013
  
  
• BOINC_Data\symbols\dbghelp.pdb\6AD43BA6261A40E8A812FA07EABD0E191\dbghelp.pdb - modified 14 Nov 2007, created 12 Dec 2013
  
  compared to: F:\Symbols2\dbghelp.pdb\6AD43BA6261A40E8A812FA07EABD0E191\dbghelp.pdb - modified 14 Nov 2007, created 7 Dec 2013
  
  
• BOINC_Data\symbols\dnsapi.pdb\F01111D1A3974A80837B62ABD17FBF112\dnsapi.pdb - modified 4 Mar 2011, created 12 Dec 2013
  
  compared to: F:\Symbols2\dnsapi.pdb\80377DF78C6040C1A011BEC9E4A9DBD92\dnsapi.pdb - modified 4 Mar 2011, created 9 Dec 2013
  
  
• BOINC_Data\symbols\fltLib.pdb\3792070439264076A609BE9E8271B75F1\fltLib.pdb - modified 15 Apr 2008, created 12 Dec 2013
  
  compared to: F:\Symbols2\fltLib.pdb\ED1106F705D34BFA8D9661D395DE5F6C1\fltLib.pdb - modified 16 Feb 2007, created 7 Dec 2013
  

I only have one qwexion:

1. why the duplication of PDB folders w/ in the SymStores?
2. why the discrepency in the versioning between the SymStores (inferred from the the modified dates and recent, albeit different, create dates)?
3. if I create a NTFS reparse point, i.e., junction / symbolic-link, of F:\Symbols2 as BOINC_Data\symbols, will it still duplicate the PDB folders within differing GUID lookin' sub-folders?
4. can I incorporate BOINC symstore like so:_NT_SYMBOL_PATH=srv*F:\Symbols2*http://boinc.berkeley.edu/symstore/*http://msdl.microsoft.com/download/symbols (or do I need to use a semicolon delimiter between the two server URL's)?

I'm uncertain about implementing the BOINC symstore whatsoever, given that the contents there are packed.

Domain controllers separate local user accounts from Domain accounts. BOINC is not designed to make the sandboxed accounts in Active Directory, but in the local user accounts. Domain Controllers do not have local accounts because they must run Active Directory in order to authenticate users logging on to the network. Ergo, BOINC v6, with its sandboxed accounts, cannot run on Domain Controllers.

On the client side, local user accounts and settings are ignored when the user logs on to the domain, therefore the sandboxed accounts are not seen when run in an Active Directory environment. Since BOINC is not authorized in Active Directory to make Domain accounts, or Domain Global Groups, or even Universal Groups, the sandboxed accounts can only be run when not logged on to the domain.