 My name is Nico Buldman. I'm from Univention. I want to give you a short overview on what is possible with Nexcloud and how you can set up Nexcloud in an Active Directory environment and much more better how you can do it easily and more maintainable. Typically, the first thing is scope. The scope is user identities are, let's say, in your Microsoft Active Directory and you want them, those users to be able to log into Nexcloud. The usual step what you are doing is you set up Nexcloud that involves typically a Linux server like Debian or Ubuntu, you install Nexcloud on it, you do all the configuration, you do all the configuration for the L of setup and AD, and finally the user can log in. This typically I estimate would take you one to two hours depending on your environment, the configuration there on your know-how and basically the limits on this. And the challenges are, those are all limited steps, those manual steps there can be quite error-prone and know-how about LDAP and Active Directory is quite helpful for doing such setups. So now let's change some prerequisites for it. The scope is the same and what you change is you download the Nexcloud appliance from the Nexcloud website and this appliance is based on Unvention Corporate Server which is basically a Debian derivative and the advantage here is Unvention Corporate Server already includes all the connections, all the things that you need to connect to an Active Directory server or do other things what I will come up later. The estimated effort for this setup is about 20 minutes and afterwards all the users that you have in your Active Directory can log in to Nexcloud. Benefits here is different scenarios are possible later more and Nexcloud is already configured so that all the users can log in through the central identity management and you can really manage them centrally in your environment. And the scenarios are as you see here the first one that may come up to most of them is a few is you have the appliance based on UCS in an Active Directory environment where UCS is just part of an Active Directory that's called an AD member. You can use all the users that are in your Active Directory system and they can log in. The second option is you want to there are different reasons you want to have two separate domains and just use the users and the groups that are in your Active Directory and you synchronize them to the appliance or to UCS and have two separate environments. The third one is a standalone installation which comes by default when you do not change any settings during the setup and the fourth one is you can even use the appliance or UCS itself Univention Corporate Server to migrate your working and running Active Directory environment and migrate it to Univention Corporate Server and do a drop in replacement without going to your, let's say, Windows clients and changing some settings there you can just change it in place. What we are using here on this is basically everything you know from that world is SAMBO4, LDAP, Kerberos and all this technology that is out there and it's integrated in UCS and next cloud benefits from it because it's just integrated with UCS and using it from there. So that's all for me, just go to the website of next cloud and download the appliance and try it out.