Hi, With Samba 3 and Windows XP, it used to be possible to install he printer drivers on the Samba server, so when an XP workstation joined the domain, it would find the printer drivers automatically. Does such a functionality exists with Windows 7? 64 bits? 32 bits? Thanks in advance, Olivier --
On 2016-04-26 09:02, Olivier Nicole wrote:> Hi, > > With Samba 3 and Windows XP, it used to be possible to install he > printer drivers on the Samba server, so when an XP workstation joined > the domain, it would find the printer drivers automatically. > > Does such a functionality exists with Windows 7? 64 bits? 32 bits? > > Thanks in advance, > > Olivier >Yes. Same as Samba 3, actually. And with an Active Directory domain you can use Microsoft's management UI to add/configure printer drivers. -- Mit freundlichen Grüßen, / Best Regards, Sven Schwedas Systemadministrator TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz Mail/XMPP: sven.schwedas at tao.at | +43 (0)680 301 7167 http://software.tao.at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160426/0096b40f/signature.sig>
Sven Schwedas <sven.schwedas at tao.at> writes:> [1:multipart/signed Hide] > > > [1/1:text/plain Hide] > > On 2016-04-26 09:02, Olivier Nicole wrote: >> Hi, >> >> With Samba 3 and Windows XP, it used to be possible to install he >> printer drivers on the Samba server, so when an XP workstation joined >> the domain, it would find the printer drivers automatically. >> >> Does such a functionality exists with Windows 7? 64 bits? 32 bits? >> >> Thanks in advance, >> >> Olivier >> > > Yes. Same as Samba 3, actually. And with an Active Directory domain you > can use Microsoft's management UI to add/configure printer drivers.Sorry, I failed to mention it is Samba 3 + Windows 7. I cannot seem to make it work the way it worked for Windows XP. Olivier
Gerben Roest
2016-Apr-26 08:14 UTC
[Samba] primary group gets set to 100 on Samba AD server after a while
Hi, using Samba 4.4.2, on the Samba AD server the users have their primary group at 513 (domain users) but after a non-fixed time they get set to 100, like: [root at sambaserver:~]# id john uid=6032(DOMAIN\john) gid=513(DOMAIN\domain users) groups=513(DOMAIN\domain users),1013(DOMAIN\sales) <few minutes> [root at sambaserver:~]# id john uid=6032(DOMAIN\john) gid=513(DOMAIN\domain users) groups=513(DOMAIN\domain users),1013(DOMAIN\sales) <few minutes> [root at sambaserver:~]# id john uid=6032(DOMAIN\john) gid=100(DOMAIN\domain users) groups=100(DOMAIN\domain users),1013(DOMAIN\sales) then when I "net cache flush" do: they're back at 513... only for a while. The Linux workstations always see the users at 513, this only happens on the Samba server itself. This can happen with intervals of a few minutes, but I've also seen it being "stable" for a few hours. any ideas? thanks, Gerben
Jonathan Hunter
2016-Apr-26 21:48 UTC
[Samba] primary group gets set to 100 on Samba AD server after a while
I had similar (ish) issues. Are you using winbindd and rfc2307 UIDs/GIDs? I had to implement both of the above on my DC to resolve this. (Neither of which I /wanted/ to do.. but since switching over and running 'net cache flush' etc., the problem hasn't reoccurred) On 26 April 2016 at 09:14, Gerben Roest <g.roest at grepit.nl> wrote:> Hi, > > using Samba 4.4.2, on the Samba AD server the users have their primary > group at 513 (domain users) but after a non-fixed time they get set to > 100, like: > > > [root at sambaserver:~]# id john > uid=6032(DOMAIN\john) gid=513(DOMAIN\domain users) > groups=513(DOMAIN\domain users),1013(DOMAIN\sales) > > <few minutes> > > [root at sambaserver:~]# id john > uid=6032(DOMAIN\john) gid=513(DOMAIN\domain users) > groups=513(DOMAIN\domain users),1013(DOMAIN\sales) > > <few minutes> > > [root at sambaserver:~]# id john > uid=6032(DOMAIN\john) gid=100(DOMAIN\domain users) > groups=100(DOMAIN\domain users),1013(DOMAIN\sales) > > then when I "net cache flush" do: they're back at 513... only for a while. > > The Linux workstations always see the users at 513, this only happens on > the Samba server itself. This can happen with intervals of a few > minutes, but I've also seen it being "stable" for a few hours. > > any ideas? > > thanks, > > Gerben > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein
Reasonably Related Threads
- primary group gets set to 100 on Samba AD server after a while
- primary group gets set to 100 on Samba AD server after a while
- primary group gets set to 100 on Samba AD server after a while [SOLVED]
- Samba 4.4.2 as AD server: clients OK but server fails "wbinfo -K"
- dovecot problem with 4.4.3, not with 4.4.2