#75885 - 2003-07-13 07:46 PM
Re: A problem with @PRIMARYGROUP
|
Howard Bullock
KiX Supporter
   
Registered: 2000-09-15
Posts: 5809
Loc: Harrisburg, PA USA
|
For the domain name you want to use the downlevel or netbios name. You also need to specify the options.
Syntax: EnumObject --name Nail --class domain
|
|
Top
|
|
|
|
#75886 - 2003-07-13 08:33 PM
Re: A problem with @PRIMARYGROUP
|
jacks73
Getting the hang of it
Registered: 2003-04-23
Posts: 58
|
Les I've only got 140 users so i'm under the limit. I've made a failed user a Domainm admin and the script runs fine. @primarygroup can be defined only when an NT4 upgraded user is a Domain Admin. So a possible solution could be to make Everone a Domain Admin
Howard, I will try to run your EnumObject again when I am back at the office in about an hour
|
|
Top
|
|
|
|
#75887 - 2003-07-13 10:10 PM
Re: A problem with @PRIMARYGROUP
|
jacks73
Getting the hang of it
Registered: 2003-04-23
Posts: 58
|
Here's a question? Where, on the server, does KiXtart get the group info from. I assume it is somewhere in the Reg, but does anyone know the key?
|
|
Top
|
|
|
|
#75890 - 2003-07-14 06:13 AM
Re: A problem with @PRIMARYGROUP
|
jacks73
Getting the hang of it
Registered: 2003-04-23
Posts: 58
|
The answer is
Pre-Windows 2000 compatible access Security group.
Quote "@primarygroup can be defined only when an NT4 upgraded user is a Domain Admin."
I added them all to this built-in, and then had to wait for it to get around, but once the domain refreshed the script runs great!
My first domain upgrade is a success! Thank you all for your input. KiXtart.org is my hero!
|
|
Top
|
|
|
|
#75892 - 2003-07-14 09:07 AM
Re: A problem with @PRIMARYGROUP
|
NTDOC
Administrator
   
Registered: 2000-07-28
Posts: 11628
Loc: CA
|
http://is-it-true.org/nt/nt2000/atips/atips70.shtml
Directory Information Tree (DIT). In NT 4.0, the Security Accounts Manager (SAM) database holds all the user, computer, and group information for a domain. Because the SAM is a Registry hive, the Registry's scalability limits the SAM. On Win2K domain controllers, the DIT replaces the SAM. The DIT is based on Microsoft's Jet database engine and is similar to the Jet engine that Microsoft Exchange Server uses. The file ntds.dit, in the \%systemroot%\ntds directory, is the Win2K equivalent of the SAM file. This file stores the bulk of the directory database. In general, the DIT is larger than the SAM because AD holds more information and types of objects than NT 4.0's directory service holds. Within a domain, the contents of the ntds.dit file replicate to all the domain controllers. You might think that you'll see more replication traffic between domain controllers when you migrate from NT 4.0 to Win2K. However, Win2K uses a completely different model for replicating directory changes than NT 4.0 uses.
http://www.netpro.com/forum/messageview.cfm?catid=11&threadid=129
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/AD/windows2000/maintain/adsize.asp
|
|
Top
|
|
|
|
#75893 - 2003-07-14 09:19 AM
Re: A problem with @PRIMARYGROUP
|
NTDOC
Administrator
   
Registered: 2000-07-28
Posts: 11628
Loc: CA
|
Are we mis-understanding? Please tell us you DID NOT make all your users Domain Admins.
|
|
Top
|
|
|
|
#75896 - 2003-07-16 04:39 AM
Re: A problem with @PRIMARYGROUP
|
jacks73
Getting the hang of it
Registered: 2003-04-23
Posts: 58
|
NO NO NO! I Don't have a gazillion Domain Admins!! I was joking that it COULD be a possible solution. My scripts may not be the best, but I'm not stupid.
The reason for the @PRIMARYGROUP as the delimiter was to map the group drives of only the department the user is in and not any other %groupname%_PRIV that the user may belong to. If a user needed another department's Drive, they could map the %groupname%_PUB themselves. Thereby giving everyone a "share drive" that is not one big Dump of forgotten information.
|
|
Top
|
|
|
|
#75898 - 2003-07-16 04:45 AM
Re: A problem with @PRIMARYGROUP
|
Howard Bullock
KiX Supporter
   
Registered: 2000-09-15
Posts: 5809
Loc: Harrisburg, PA USA
|
Did you get the dump to work?
|
|
Top
|
|
|
|
#75899 - 2003-07-16 06:00 AM
Re: A problem with @PRIMARYGROUP
|
jacks73
Getting the hang of it
Registered: 2003-04-23
Posts: 58
|
Jens, I did create depta_priv depta_pub deptb_priv deptb_pub. And by using @primarygroup to pull the group names a user in dept A gets depta_priv and depta_pub and a user in dept B gets deptb_priv deptb_pub but if "b" user also belongs to the "a" group, but it isn't his actual dept then "b" user can map the depta_pub however "b" will not get the depta_priv drive mapped.
Howard, I did get the @primarygroup to work. All of my upgraded NT users needed to be added to the "pre windows 2000 compatible access" built-in group. once I did that The script ran just like it should have.
|
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 657 anonymous users online.
|
|
|