Windows 2000 server installation !!!

P.s. det er ikke første gang med win 2000 server men første gang med AD.

1) smider brugeren i en ou og sætter det via grouppolicy
2)ved at udlade at angive profile path for brugeren

Tak Space.

Men hvad angår login scriptet, hvor skal det indsættes hvis alle skal køre det samme Script ???

You right click on an OU in Active Directory Users & Computers, select Properties, and Add a new Group Policy.  Have a look down the options and you'll find Scripts entries for Logon and Logoff that can be run by Users and for PC's at Startup and Shutdown (before user logs in).

Klippet fra http://www.experts-exchange.com/Operating_Systems/Win2000/Q_20420238.html

Ja men de fortæller ikke hvor jeg placerer filen login.bat og hvor jeg henter den således at alle brugere kører den ved login ???

The main script directory is in SYSVOL\Scripts (whereever you made your SYSVOL-directory.
Men du kan jo bare lægge det på et share hvor alle har læseadgang

1.I grouppolicy ligger de i en mappe der hedder "Logon", men du kan browse til et tilfældigt share og angive det derfra-også fra grouppolicy.
2. Du behøver ikke at gøre noget. Brugere får ikke deres egne skrivebordsmapper pr. default. Det er noget der skal konfigureres og som hedder noget så uhyggeligt= "Roaming profiles"

Tak Danny.

Det med grupperne er nok en god ide da jeg har nogle brugere hvis login script snart vil ændre sig. Netop fordi de tilhører en bestemt gruppe.  :)

Kort tillægs spørgsmål.

Burde brugerens mappe ikke automatisk blive oprettet i mappen "bruger" når jeg kører dette login script.

net use U: \\min_server\bruger$\%username%

Den skriver at net path ikke eksisterer.

Everyone har fuld adgang !!!

Ja hvis dit script kun skal gælde en bestemt gruppe lægger du personerne i Ouét og loader dit logonscript herfra.
Er du 100% sikker på at servernavnet er rigtigt? kan du bruge underskår?
Ved ikke hvorfor I er så glade for det bruger$ og hvad h.. det gør, hvad gør det?
Hvis du bare laver et share der hedder Bruger og derefter:
net use U: \\servernavn\sharenavn\%username%  så spiller det!!

det med Bruger$ gør at din Mappe er gemt på netværkssteder, således at brugere ikke kan browse sig frem til den !!!

jeg kan godt logge drevet hvis jeg opretter det manuelt fra Serveren på samme sti

dvs at andre brugere ikke kan se mappen , hvis du bruger Bruger$  ?
er det rigtigt forstået?
Jeg har nemlig ikke selv brugt det ,,endnu

Hvis du kan browse dig til serveren fra en loakalpc , få adgang til share og dit servernavn og sharenavn er ok burde det virke.

Jeg kan bruge loginscriptet og det mapper drevet fint, men kan ikke hvis det ikke er oprettet.

Jeg ville mene at det selv burde oprette %username% i mappen Bruger$, og jeg ikke skal gøre det manuelt.

og ja det betyder du ikke kan browse dig frem til drevet når der er et $ lige efter navnet på mappen.  ;)

ja %username% skal oprette en mappe med brugerens navn på shared. altså hvis Brian logger på får han en Brian mappe,,,ikk?

Jeg ved ikke om det virker med bruger$, men det andet virker.

Ja præcis og det burde virke med en mappe der r skjult. for loginscriptet opdager jo ikke den er skjult da den har den direkte sti.

Evryone må jo være nok med fuld kontrol, sidder og spekulerer på om der skal være rettigheder for domain users også.

Nå du deler en mapp på serveren og skrievr i Netlogon net use U: \\Din server navn\mappe navn\%username%  så virker det

theworld, ja og det er jo også det der står højre oppe i debatten, så hvor vil du hen med det ???

Det løser ikke at det ikke virker, for som jeg jo skriver så mapper den fint når bare jeg opretter mappen manuelt !!!


Nogen der har en løsning til min terminalserver, jeg er ved at skifte Domain fra domain 1 til domain 2, men når jeg prøver at ændre domain og indtaster en bruger med adgangsrettigheder, vender den tilbage med "the network path was not found"

så gå ned i RUM og skriv DCPROMO og opret en ny

Hey ...
Du skal migrere dine brugere fra WiNNT, derved kommer alle deres indstilligner med over i windows 2000 ....

Lyder som en god ide, mail mig lige hvis du vil have points. min mail er i min profil.

Tak for hjælpen, kanon der med migrering...  ;)

->Renehansen. Sjovt su accepterer scharups svar uden du ved om det er rigtigt
Nå og hvordan gjorde du så det? Migrering
Havde du opdateret fra NT?

mmmmm...

Ikke at din ide ikke var god nok, men Schaarup´s løsning gav mig en del mindre at tænke på ved at bruge den indbyggede ADMT migrerings mekanisme fra Win 2000 !!!  og det at jeg kan hive filer med over og bibeholde security permissions gør det jo en del nemmere. Hvis du ser efter har jeg bedt ham maile mig, ikke for at få point direkte men for at han skulle forklare mig hvordan jeg skulle gøre det !!!

Det er næsten løst og jeg er ikke 1.sek i tvivl om at dette er den rette løsning.

Men jeg er da ked af hvis du føler at du ikke fik noget ud af at svare på mit spørgsmål, for det er jo ikke det at forummet handler om.  ;)

Vel egentlig heller ikke om point ??? men mere det at kunne hjælpe !!! :)

Jeg ville da også gerne se løsningen hvis det var muligt....

Hehe OK

Nu spurgte du selv så her kommer det.

som jeg skriver er det næsten køreklart mit system, og du må give mig ret i at dette er en bedre løsning.

ikke så meget jeg skal hen og oprette på ny da der er mange brugere på vores gamle server.

Dette er hvad schaarup sendte og jeg har så selv søgt en del information på nettet og mener at alle der skal migrere fra NT4 til Win2k bør følge denne løsning, men det er jo så bare min mening.  :)

ihvertfald endnu engang tak til Schaarup for den info.

Og hvad mine brugere angår så er de nu i det nye domæne, jeg siger ikke at det hele virker endnu, men jeg håber det sidste bliver nemt.. ihvertfald gav det mig grå hår at skulle oprette det hele manuelt.  :)


Date Released: March 2000
The Active Directory Migration Tool provides an easy, secure, and fast way to migrate to Windows 2000 Active Directory service. As a system administrator, you can use this tool to diagnose any possible problems before starting migration operations to Windows 2000 Server Active Directory. You can then use the task-based wizard to migrate users, groups, and computers; set correct file permissions; and migrate Microsoft Exchange Server mailboxes. The tool's reporting feature allows you to assess the impact of the migration, both before and after move operations.
In many cases, if there is a problem, you can use the rollback features to automatically restore previous structures. The tool also provides support for parallel domains, so you can maintain your existing Windows NT 4.0 domains while you deploy Windows 2000.

You can find Admt.exe in the MS Knowledge Base.

How to use

Go to the location where you copied the file and double-click Admt.exe to launch the Setup Wizard.
How to uninstall

?Go to the location where you saved the file and double-click Admt.exe.

?Click Remove All in the Setup Wizard.

Benefits

ADMT provides an effective tool that simplifies the process of migrating users, computers, and groups to new domains. At the same time, ADMT is designed to be flexible so that each organization can use it to implement a migration process that is adapted to its needs. This powerful tool lets you accomplish the following:

?Migrate from Windows NT. You can use ADMT to migrate from Windows NT to Windows 2000. This migration lets you benefit from several important features introduced by Active Directory, including:

?Improved scalability. The improved scalability available in an Active Directory forest-you can have millions of objects-lets you reconfigure your current Windows NT domains into fewer, larger Windows 2000 Active Directory domains. Simplifying your domain structure- frequently, into just one domain-also makes administration of users, groups, and group policy easier.

?Administrative delegation. Consolidating Windows NT resource domains into Active Directory organizational units (OUs) lets you delegate administrative control over specific OUs to administrators who have authority over only part of a domain.

?Trust simplification. If your current domain structure requires a complex mesh of trust relationships, you can benefit from a redesign that lets you use fewer trusts by using the bi-directional transitive trust relationships available in Windows 2000.

?Restructure Windows 2000. You can use ADMT to reorganize your Windows 2000 domain structure. As when you migrate from Windows NT to Windows 2000, migration within Windows 2000 also lets you consolidate multiple domains into fewer domains, and possibly a single domain.

?Tailor the move to your needs. ADMT lets you specify how to handle user, password, computer, group, group membership, security translation, and monitoring options during the migration process.
ADMT Features

ADMT features let you manage domain migration efficiently and fine-tune the results to suit their requirements.

?No need to manually load software onto all those computers.

?When using ADMT to migrate users and groups, you install the ADMT tool, typically on the console in the target domain (the domain into which security principals or resources are being migrated). Beyond that, ADMT requires no additional software installation on the computers in the source domain (the domain from which security principals or resources are being migrated).

?When migrating computers or translating security on resources, ADMT automatically installs services (called agents) on the source computers. This means you do not need to manually load software onto each source computer to perform the migration. Once the agent's task is completed, it uninstalls itself.

?Wizards make it easy. ADMT lets you use a series of wizards, including the User Migration wizard, Computer Migration wizard, Group Migration wizard, Service Account Migration wizard, Trust Migration wizard, and Reporting wizard to simplify various parts of the migration process.

?Options to suit you. Select the appropriate options among the many provided by the various wizards when performing a migration. For example, you can choose to copy users rights assigned in the source domain to the target domain; you can copy groups along with their members to the target domain; you can leave user accounts active in both the source and target domains; you can copy roaming profiles to the target domain for selected user accounts; and so on.

?Restructure groups. Optionally, before migrating groups you can run the Group Mapping and Merging Wizard to map a group in the source domain to a new or existing group in the target domain. This mapping ensures that, when the group's members are migrated from the source domain into the target domain, group memberships will reflect the mapping. You can also merge multiple groups into one group.

?Trial run. By selecting the Test the migration settings and migrate later option, you can run a wizard without actually making any changes in your network. Review the log files and reports generated by the wizards to identify and troubleshoot any potential problems before performing the actual migration.

?Undo. You can undo the most recently performed user, group, or computer migration.

?Users maintain access to resources. During user and group migration, ADMT lets users retain their premigration access to resources such as files, shares, and applications through its sIDHistory feature or by updating those resources to refer to the migrated user. This capability keeps your security structure (the granting and denying of access to resources) intact but conveniently brings it into the new domain.

?Users retain access to Exchange resources. If you need to update security permissions on Exchange mailboxes to reflect the migration, ADMT can also handle that.

?Service accounts migrate too. ADMT also migrates service accounts. Many applications, such as Microsoft Exchange, use service accounts to run services with the same set of credentials on several network computers.

?Putting objects into OUs. In addition to consolidating Windows NT resource domains into Active Directory OUs, ADMT also lets you migrate selected users, groups, or computers to OUs in the target domain. Then, you can use Windows 2000 features to manage these OUs-for example, you can establish group policy configuration settings for a group of computers collected in a given OU.

?Handling trust relationships. A trust relationship connects two domains and lets users in the trusted domain access resources in the trusting domain. To maintain resource access during migration, the same trust relationships must be established in the target domain as exist in the source domain. The Trust Migration wizard does this for you-it compares the trust relationships in the source domain to the trust relationships in the target domain, and then creates in the target domain any trust relationships that exist in the source domain.

?Making use of the new universal group scope. In intra-forest migration (that is, when performing a migration between Windows 2000 domains in the same forest), when global groups are migrated from a native-mode source domain, the groups are created as universal groups in the target domain so that they can contain members from the source domain that have not yet been migrated.Global groups can contain only members from their own domain; universal groups can have members from any Windows 2000 domain in the forest.
ADMT System Requirements

?Target domain. For target domains, ADMT can run on any computer capable of running the Windows 2000 Server operating system.

?Source domain. The source domain must be running either Windows 2000 or Windows NT 4.0.
The primary domain controller (PDC) of a Windows NT 4.0 source domain must have SP4 or higher installed. The ADMT agent (installed by ADMT on the source computers) can operate on computers running Windows NT 3.51 (with SP5); Windows NT 4.0 (with SP4 or higher); or Windows 2000.

P.s. jeg burde måske nok have delt dem lidt ud, jeg var ikke klar over at det med points var så vigtigt herinde.  :)

Pointene er heller ikke så vigtige. Mere at se løsningen når vi nu har fulgt med i supporten på spm. Du kan nok også forestille dig hvorfor nogle er lidt uforstående overfor migration tool Når du ikke har omtalt det før, at du har opgraderet fra Nt.
Men det var da rart at der endelig kom en forklaring - tak for det.