hesoyam's questions

I badly need your clever advice!

The thing is I am trying to extend on-premises active directory to Azure. And one of my coworkers mentioned that if it’s over 100,000 items then you’ll want to install to full SQL server and installer really is not very well designed for such installations. Therefore I moved to custom installer.

On the first look, the process for doing this should be quite straightforward as it’s just an installing the Azure Active Directory Connect tool onto a server and then, creating the domain in the Azure portal and then waiting for Azure AD connect to Sync.

Troubles came when I did well through the 99% of the way and Synchronization process was finished. I just wasn’t able to login to the SQL server.

The only heads up is the small red bar which appears under service account name/service account password.

I am wondering in what way should I spin-up windows VM for Azure from generalized image, in order to add custom settings (from what I know it's impossible to customise the VM which was deployed from Azure market place)

That would be great if you could share a kb/guide which is describing PowerShell actions because AzureRM doesn't support GUI for now, and I am not really strong in the shelling.

I am building a new sub-cluster, thereby I am facing few questions.

1. Which technology is more efficient for "boosting throughput" ? (Will be great if you can provide any comparison) As far as I done my google job, there are two technology's which provides additional paths inside one NIC. Link Aggregation Control Protocol and Multipath I/O. It would be great if some one can provide me with any benefits or drawbacks of these technology.

(I am asking the second qestion from curiosity , just want to hear your opinion)

2. Which connection is preferable (Ethernet of FC)?

I heared that Ethernet connection is slower when it comes to comparing Ethernet and FC.