similar to: Samba AD with Microsoft Account

In a related problem. I've tried linking my Office365 account. I get through the sign-in process but when it is attempting to link the device I can an error message stating: *We weren't able to register your device and add your account to Windows. Your access to org resources may be limited.* The domain account I am logged in with is part of the Domain Admins group so I don't think

Yes I have provisioned the samba server as an Active Directory domain controller (I mentioned that in the first e-mail). The reason for linking the two is to provide easy access to additional MS services that won't be hosted internally (e.g. OneDrive, Skype, MS Store). Ultimately I am using this as a private domain at home to simplify device management but I want to continue be able to use

On 11.01.2016 20:37, Rowland penny wrote: > On 11/01/16 19:26, Jean-Philippe Steinmetz wrote: >> Yes I have provisioned the samba server as an Active Directory domain >> controller (I mentioned that in the first e-mail). >> >> The reason for linking the two is to provide easy access to >> additional MS >> services that won't be hosted internally (e.g.

> On 12 Jan 2016, at 01:25, Jean-Philippe Steinmetz <caskater47 at gmail.com> wrote: > > I was able to find this thread that seems to be the same problem I am > having. > > https://social.technet.microsoft.com/Forums/en-US/d861e179-6515-4322-a628-b7e73b2335e8/cannot-add-a-microsoft-account-to-domain-account-with-roaming-profiles?forum=win10itprogeneral > > When

No, that's not normal behavior, and I assume that's what's responsible for those other issues you're experiencing. I suggest you analyze your Samba installation thorougly using the information in the Wiki (there is a lot and in 90% problems can be solved or at least clearly identified with it). If it's just a lab setup, you might consider provisioning a new AD entirely. If you

I was able to find this thread that seems to be the same problem I am having. https://social.technet.microsoft.com/Forums/en-US/d861e179-6515-4322-a628-b7e73b2335e8/cannot-add-a-microsoft-account-to-domain-account-with-roaming-profiles?forum=win10itprogeneral When provisioning a new AD domain controller in samba, I assume the default behavior is that all user profiles are set to roaming? On

On 11/01/16 19:04, Jean-Philippe Steinmetz wrote: > Sure. In short, I am trying to link a Microsoft Account to a domain > profile on the workstation. > > I log in to the workstation with the user profile controlled by the > samba AD server (e.g. MYDOMAIN\MyUser). Then once logged in I attempt > to link an existing Microsoft Account to that user profile. I do this > by

On 11/01/16 19:26, Jean-Philippe Steinmetz wrote: > Yes I have provisioned the samba server as an Active Directory domain > controller (I mentioned that in the first e-mail). > > The reason for linking the two is to provide easy access to additional MS > services that won't be hosted internally (e.g. OneDrive, Skype, MS Store). > > Ultimately I am using this as a private

Viktor is correct. That is what I am trying to accomplish. The reason why I suspect it's a samba issue is because on the workstation I use at my company I am able to successfully link my Microsoft account to the domain profile. The company uses a Windows Server 2008 for Active Directory. So it would stand to reason the only difference here is the type of server being used. Thank you for the

I have been running a small domain for years. I finally decided to move the domain to ad. I am also upgrading the server from Ubuntu i6.04 LTS to 18.04 LTS I installed the new server on a new RAID array and loaded the Ubuntu LAMP stack. I installed samba. I have gone through a few tutorials which offer differing recommendation on some things. All were based on either Debian or Ubuntu. I

Update MAINTAINERS and .mailmap with my @linaro.org address, since I don't have access to my @arm.com address anymore. Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> --- .mailmap | 1 + MAINTAINERS | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.mailmap b/.mailmap index 0fef932de3db..8ce554b9c9f1 100644 --- a/.mailmap +++ b/.mailmap @@

On Wed, 14 Feb 2018 14:53:40 +0000 Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote: > When enabling both VFIO and VIRTIO_IOMMU modules, automatically select > VFIO_IOMMU_TYPE1 as well. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> > --- > drivers/vfio/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

On Wed, 14 Feb 2018 14:53:40 +0000 Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote: > When enabling both VFIO and VIRTIO_IOMMU modules, automatically select > VFIO_IOMMU_TYPE1 as well. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> > --- > drivers/vfio/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

From: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> Now that the infrastructure changes are in place, enable virtio-iommu to be built as a module. Remove the redundant pci_request_acs() call, since it's not exported but is already invoked during DMA setup. Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> --- This conflicts with the multiplatform

From: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> Now that the infrastructure changes are in place, enable virtio-iommu to be built as a module. Remove the redundant pci_request_acs() call, since it's not exported but is already invoked during DMA setup. Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> --- This conflicts with the multiplatform

Add a topology description to the virtio-iommu driver and enable x86 platforms. Since [v2] we have made some progress on adding ACPI support for virtio-iommu, which is the preferred boot method on x86. It will be a new vendor-agnostic table describing para-virtual topologies in a minimal format. However some platforms don't use either ACPI or DT for booting (for example microvm), and will

Add a topology description to the virtio-iommu driver and enable x86 platforms. Since [v2] we have made some progress on adding ACPI support for virtio-iommu, which is the preferred boot method on x86. It will be a new vendor-agnostic table describing para-virtual topologies in a minimal format. However some platforms don't use either ACPI or DT for booting (for example microvm), and will

On Sun, Feb 16, 2020 at 04:50:33AM -0500, Michael S. Tsirkin wrote: > On Fri, Feb 14, 2020 at 04:57:11PM +0000, Robin Murphy wrote: > > On 14/02/2020 4:04 pm, Jean-Philippe Brucker wrote: > > > With the built-in topology description in place, x86 platforms can now > > > use the virtio-iommu. > > > > > > Signed-off-by: Jean-Philippe Brucker

On Sun, Feb 16, 2020 at 04:50:33AM -0500, Michael S. Tsirkin wrote: > On Fri, Feb 14, 2020 at 04:57:11PM +0000, Robin Murphy wrote: > > On 14/02/2020 4:04 pm, Jean-Philippe Brucker wrote: > > > With the built-in topology description in place, x86 platforms can now > > > use the virtio-iommu. > > > > > > Signed-off-by: Jean-Philippe Brucker

What about DC as primary domain controller? No Windows servers. Only clients. On Mon, May 29, 2017 at 5:19 PM, Rowland Penny <rpenny at samba.org> wrote: > On Mon, 29 May 2017 17:01:56 -0400 > Philippe Clérié via samba <samba at lists.samba.org> wrote: > > > Is it normal for a fresh installation of Samba to have empty Default > > Domain Controllers Policy and