search for: mainscreen

...f files as well. If all files that match BMDTMP\devmgr\devmgr\dmv\*.class are deleted before trying the rmdir, everything works fine, but if the whole directory structure is attempted to be deleted, it fails every time. The odd thing is the error message that is reported is on the BLDTMP\devmgr\dmv\MainScreen$InvokeManagementAppTask.class file, but the file that is left in this heirarchy is BLDTMP\devmgr\dmv\MainScreen$AutoDiscoverAction.class and it's parent directories. It also is odd that the error is for creating a file, although I am trying to delete a heirarchy. Anyone have ideas as to what is...

>> idmapping does not work for AD Domain Controllers. > >It does ;-) > Does that mean that the warning in the docs is out of date? Does it work on the version of Samba in the Stretch repository (Samba 4.5.12), or do I need to find a repo with a more recent build? >>Other pages >> suggest many of the winbind parameters are simply ignored and I can >> confirm this

I have questions regarding the operation of AD and integrating NIS or LDAP with it. I have a small heterogenous network consisting of various computing devices running either Windows 10 pro or a flavour of Linux. I am setting up a NAS box running Debian Stretch and Samba 4.5.12 to be the central file server and authenticator for the network, including LDAP aware software such as owncloud. I have

Thanks for your reply Rowland. > The id ranges are what you choose, reading this may help: > > https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member#Setting_up_a_Basic_smb.conf_File > > >/Is there any working way of controlling those ranges, />/given idmap breaks stuff? / > What do you mean 'idmap breaks things' ? > Sorry, should have made it