Azure AD Connect account usage

Azure AD Connect uses 3 accounts in order to synchronize information from on-premises or Windows Server Active Directory to Azure Active Directory. These accounts are:

• AD DS Connector account: used to read/write information to Windows Server Active Directory

• ADSync service account: used to run the synchronization service and access the SQL database

• Azure AD Connector account: used to write information to Azure AD

In addition to these three accounts used to run Azure AD Connect, you will also need the following additional accounts to install Azure AD Connect. These are:

• Local Administrator account: The administrator who is installing Azure AD Connect and who has local Administrator permissions on the machine.

• AD DS Enterprise Administrator account: Optionally used to create the “AD DS Connector account” above.

• Azure AD Global Administrator account: used to create the Azure AD Connector account and configure Azure AD. 

• SQL SA account (optional): used to create the ADSync database when using the full version of SQL Server. This SQL Server may be local or remote to the Azure AD Connect installation. This account may be the same account as the Enterprise Administrator. Provisioning the database can now be performed out of band by the SQL administrator and then installed by the Azure AD Connect administrator with database owner rights.

Cannot Install Windows 2008 R2 Service Pack 1

Description

You are experiencing an error or problem when installing Windows 2008 R2 Service Pack 1. It says "Installation was not successful", error code 0x800f0826.

 

You have followed  the steps in https://support.microsoft.com/en-us/kb/2575082.
SYSTEM and Administrators already have Full Permission on usbstor.inf and usbstor.pnf files.
You have also follow http://windows.microsoft.com/en-ID/windows7/troubleshoot-problems-installing-service-pack to download and run the latest System Update Readiness Tool.
Other than those, you have also try to run sfc /scannow command but no error found.

At c:/windows/inf/Setupapi.dev.log you found a couple of errors similar to:
inf:      Opened INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\compositebus.inf_amd64_neutral_b9280780a8000d4b\compositebus.inf' ([strings])
sto:      {Update Device: ROOT\COMPOSITEBUS\0000}
sto:           Updating installed driver version:
sto:                Driver Version Last     = 6/21/2006,6.1.7600.16385
sto:                Driver Version New      = 6/21/2006,6.1.7601.17514
!!!  sto:           Failed to update driver date. Error = 0x00000005
sto:      {Update Device: exit(0x00000005)}
sto: {Update Device Drivers: exit(0x00000005)} 12:07:37.106
!!!  sto: Failed to update devices for all driver updates. Error = 0x00000005

  inf:      Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\umbus.inf_amd64_neutral_2d4257afa2e35253\umbus.inf' ([strings])
     sto:      {Update Device: ROOT\UMBUS\0000}
     sto:           Updating installed driver version:
     sto:                Driver Version Last     = 6/21/2006,6.1.7600.16385
     sto:                Driver Version New      = 6/21/2006,6.1.7601.17514
!!!  sto:           Failed to update driver date. Error = 0x00000005

Resolution

There's a missing permission on the registry that related to the drivers.

1. Download psexec.exe (http://technet.microsoft.com/en-us/sysinternals/bb897553)
2. Execute the following command from an elevated command prompt – ‘psexec /i /s cmd’
3. When a new command prompt opens execute regedit
4. Navigate to HKLM\SYSTEM\CURRENTCONTROLSET\ENUM\ROOT\COMPOSITEBUS\0000\PROPERTIES\
5. Verify that ‘System’ has ‘full control’ of each subkey. If not force inheritance from the ‘PROPERTIES’ key.
6. Test the install of SP1.