Karolin Seeger wrote: > Hi, > > On Wed, Jun 10, 2009 at 12:01:46PM +0900, OPC oota wrote: >> Now,TOSHARG-PDC.xml translate to Japanese finished. >> >> and Some bug found. >> >> --------------------------------------------------------------------------------------------------- >> <listitem><para> >> <indexterm><primary>Nexus.exe</primary></indexterm> >> Management of users and groups via the User Manager for Domains. >> This can be done on any MS Windows client >> using the <filename>Nexus.exe</filename> toolkit for Windows 9x/Me, >> or using the SRVTOOLS.EXE package for MS >> Windows NT4/200x/XP platforms. These packages are available from >> Microsoft's Web site. >> </para></listitem> >> >> SRVTOOLS can't run on Windows Vista/Windows 7. >> >> SSO implementations utilize centralization of all user account information. >> Depending on environmental >> complexity and the age of the systems over which a SSO solution is >> implemented, it may not be possible to >> change the solution architecture so as to accomodate a new identity >> management and user authentication system. >> ---------- >> accommodate? >> >> >> Many SSO solutions involving legacy systems consist of a new super-structure >> that handles authentication on >> behalf of the user. The software that gets layered over the old system may >> simply implement a proxy >> authentication system. This means that the addition of SSO increases >> over-all information systems complexity. >> Ideally, the implementation of SSO should reduce complexity and reduce >> administative overheads. >> >> >> converge when the SAML 2.0 standard is introduced. A few Web >> access-management products support SAML today, >> but implemention of the technology mostly requires customization to >> integrate applications and develop user >> ------------ >> implementation? >> >> interfaces. In a nust-shell, that is why FIM is a big and growing industry. >> ---------------- >> In a nutshell ? >> >> >> New to Samba-3 is the ability to use a backend database that holds the same >> type of data as the NT4-style SAM >> database (one of the registry files)<footnote><para>See also <link >> linkend="passdb">Account Information >> Databases</link>.</para>.</footnote> >> - >> period duplicate >> >> >> Domain member machines have a machine trust account in the domain accounts >> database. A special procedure >> must be followed on each machine to effect domain membership. This >> procedure, which can be done >> only by the local machine Administrator account, creates the domain machine >> account (if it does >> not exist), and then initializes that account. When the client first logs >> onto the >> >> --------- >> logon >> to? >> >> to log onto the domain.</para></listitem> >> ------- >> logon to? >> <listitem><para>Placing Windows 9x/Me clients in user-level security >> &smbmdash; if it is desired to allow >> all client-share access to be controlled according to domain >> user/group identities.</para></listitem> >> <listitem><para>Adding and managing domain user >> accounts.</para></listitem> >> </itemizedlist> >> >> <note><para> >> <indexterm><primary>roaming profiles</primary></indexterm> >> >> >> >> MS Windows XP Home Edition does not have the ability to join any type of >> domain >> security facility. Unlike MS Windows 9x/Me, MS Windows XP Home Edition also >> completely >> lacks the ability to log onto a network. >> -------- >> logon to? >> >> >> Workstation Machine Trust Accounts work only with the domain (or network) >> SID. If this SID changes, >> domain members (workstations) will not be able to log onto the domain. The >> original domain SID >> -------- logon to? >> >> can be recovered from the secrets.tdb file. The alternative is to visit each >> workstation to rejoin >> it to the domain. >> >> >> <sect2> >> <title>Cannot Log onto Domain Member Workstation After Joining Domain</title> >> -------- Logon to? >> <para> >> <indexterm><primary>schannel</primary></indexterm> >> <indexterm><primary>signing</primary></indexterm> > > thanks a lot for reporting! :-) > > The first issues should be fixed by commit ad0d8032 in master. > I am not sure about the "log onto" things. At least according to my > dictionary, > it seems to be right. Maybe one of the native speakers would like to > comment... > > Cheers, > Karolin > >
I believe either is acceptable English. I originally had "logon to" but the copy editor changed it. cheers, John T. -- John H Terpstra "If at first you don't succeed, don't go sky-diving!" -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
