-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Argh! You are correct. I thought this was the one really good article
that Buchan Milne wrote. It seems to have disapeared.
| http://linsec.ca/bin/view/Main/LdapAdvanced
| NO, this article is about LDAP mainly, and says nothing about
|
John H Terpstra wrote:
NT4 does not
replicate or synchronize desktop profiles - nor does Samba. Where on earth
did you obtain the idea that this ought to happen?
Well, I know Samba doesn't replicate profiles.
I just asked what is the best way to do it.
The notion that all roaming profiles are
John H Terpstra wrote:
I thought of this approach:
- keep profile size to the minimum (20-30 megs),
How will you control the size of the profile? I can not see a practical
solution to do this.
Didn't think of it yet.
Several years ago, in a rather big university facility I saw something
like
Tomasz Chmielewski rta:
John H Terpstra wrote:
I thought of this approach:
- keep profile size to the minimum (20-30 megs),
How will you control the size of the profile? I can not see a
practical solution to do this.
Didn't think of it yet.
Several years ago, in a rather big university facility
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
| Hello,
Thinking out loud
hmmm Small storeage area network? Gigabit ethernet might be cheap
enough. Perhaps you could create a Gigabit backbone and basically do a
mirror setup? Would RAID help? Have you been thinking
On Sunday 12 December 2004 06:15, Tomasz Chmielewski wrote:
John H Terpstra wrote:
NT4 does not
replicate or synchronize desktop profiles - nor does Samba. Where on
earth did you obtain the idea that this ought to happen?
Well, I know Samba doesn't replicate profiles.
I just asked what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| Or perhaps I don't understand something?
Just a guess but a BDC is probably going to do the same thing with the
files that the LDAP backend would do. I.E. replicate the data from the
server.
Jim C.
- --
-
Tomasz Chmielewski wrote:
As a consequence, this also means, that on each server there has to be a
copy of a profile of a given user, right?
No, not right. The user roaming profile is stored only on one server.
Maybe you may rename the each SAMBA server in each location in the same
NetBIOS name,
gints neimanis wrote:
Tomasz Chmielewski wrote:
As a consequence, this also means, that on each server there has to be
a copy of a profile of a given user, right?
No, not right. The user roaming profile is stored only on one server.
So what is the sense of having BDCs? I guess the biggest load
Tomasz Chmielewski wrote:
| Jim C. wrote:
|
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| | Or perhaps I don't understand something?
|
| Just a guess but a BDC is probably going to do the same thing with the
| files that the LDAP backend would do. I.E. replicate the data from the
|
On Saturday 11 December 2004 13:06, Tomasz Chmielewski wrote:
gints neimanis wrote:
Tomasz Chmielewski wrote:
As a consequence, this also means, that on each server there has to be
a copy of a profile of a given user, right?
No, not right. The user roaming profile is stored only on one
As a consequence, this also means, that on each server there has to be
a copy of a profile of a given user, right?
No, not right. The user roaming profile is stored only on one server.
So what is the sense of having BDCs?
So distribute the profiles. Where the user's profile is located
Jim C. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| Or perhaps I don't understand something?
Just a guess but a BDC is probably going to do the same thing with the
files that the LDAP backend would do. I.E. replicate the data from the
server.
But how should it be done?
I have read the
13 matches
Mail list logo
