search for: domain_

...036476082-4153129556-3089177936-1005' is **NOT** the same > user as 'Fred' with the SID-RID > 'S-1-5-21-2025076216-3455336656-3842161122-1005' > > You need to change the domain SID on the new PDC to match the SID on the > windows machines. Denis, is this a _new domain_ (with the same name)? Or just a _new server_ where you placed the profiles. If it's a _new domain_, then Rowland is surely right and it is an SID problem. But you talked about a _new server_. Please be more clear about your environment. Regards, Marc

...RID 'S-1-5-21-4036476082-4153129556-3089177936-1005' is **NOT** the same user as 'Fred' with the SID-RID 'S-1-5-21-2025076216-3455336656-3842161122-1005' You need to change the domain SID on the new PDC to match the SID on the windows machines. >> Denis, is this a _new domain_ (with the same name)? Or just a _new >> server_ where you placed the profiles. If it's a _new domain_, then >> Rowland is surely right and it is an SID problem. But you talked about a >> _new server_. Please be more clear about your environment. >> Regards, >> Marc...

...the SID-RID 'S-1-5-21-4036476082-4153129556-3089177936-1005' is **NOT** the same user as 'Fred' with the SID-RID 'S-1-5-21-2025076216-3455336656-3842161122-1005' You need to change the domain SID on the new PDC to match the SID on the windows machines. Denis, is this a _new domain_ (with the same name)? Or just a _new server_ where you placed the profiles. If it's a _new domain_, then Rowland is surely right and it is an SID problem. But you talked about a _new server_. Please be more clear about your environment. Regards, Marc > Yes, you're right, I must clarify...

...D 'S-1-5-21-4036476082-4153129556-3089177936-1005' is **NOT** the same user as 'Fred' with the SID-RID 'S-1-5-21-2025076216-3455336656-3842161122-1005' You need to change the domain SID on the new PDC to match the SID on the windows machines. > > Denis, is this a _new domain_ (with the same name)? Or just a _new > server_ where you placed the profiles. If it's a _new domain_, then > Rowland is surely right and it is an SID problem. But you talked about a > _new server_. Please be more clear about your environment. > Regards, > Marc Yes, you're ri...

...or is a well known SID only allowed once? Is it allowed to uses spaces in groupnames, e.g. "domain admins"? Afaik groups with spaces are not posix conform. In Samba-Developers-Guide.pdf included with samba 3.0 page 72f. In the document well known groups have special names starting with DOMAIN_. Can Windows clients recognize these names and translate them into localized groupnames, like "user" or "power users" in english and "Benutzer" and "Hauptbenutzer" in german? Tilo

...'S-1-5-21-4036476082-4153129556-3089177936-1005' is **NOT** the same user as 'Fred' with the SID-RID 'S-1-5-21-2025076216-3455336656-3842161122-1005' You need to change the domain SID on the new PDC to match the SID on the windows machines. >>> Denis, is this a _new domain_ (with the same name)? Or just a _new >>> server_ where you placed the profiles. If it's a _new domain_, then >>> Rowland is surely right and it is an SID problem. But you talked about a >>> _new server_. Please be more clear about your environment. >>> Regard...

...the SID-RID 'S-1-5-21-4036476082-4153129556-3089177936-1005' is **NOT** the same user as 'Fred' with the SID-RID 'S-1-5-21-2025076216-3455336656-3842161122-1005' You need to change the domain SID on the new PDC to match the SID on the windows machines. Denis, is this a _new domain_ (with the same name)? Or just a _new server_ where you placed the profiles. If it's a _new domain_, then Rowland is surely right and it is an SID problem. But you talked about a _new server_. Please be more clear about your environment. Regards, Marc Yes, you're right, I must clarify a lit...

Le 08.12.2014 21:06, Marc Muehlfeld a ?crit : > Hello Denis, > > Am 08.12.2014 um 20:25 schrieb (lists) Denis BUCHER: > >> We have perfectly working roaming profiles on Samba 3.3.10 (SuSE) with Windows 7 clients. We configured our new server with same domain name, Samba 4.1.11 (Debian). On the new server, for newly created profiles, it works perfectly, we can login, logout,

HI, I am trying to setup winbind on Samba 3.0.2 running on Red Hat AS 3.0. I have completed most of the steps of setting up winbind successfully but when it came for me to login in using the AD account username and password, it didn't allow me to login. the error message i am getting is incorrect password or check username. During the setup i tested the wbinfo -u command and i was

Enable cpufreq support in Xen for AMD Operton processors by: 1) Allowing the PowerNow! driver in dom0 to write to the PowerNow! MSRs. 2) Adding the cpufreq notifier chain to time-xen.c in dom0. On a frequency change, a platform hypercall is performed to scale the frequency multiplier in the hypervisor. 3) Adding a platform hypercall to the hypervisor the scale the frequency multiplier and reset

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''