init

01_Instruktionen/azureforeducation.microsoft.com.url

@@ -0,0 +1,2 @@
+[InternetShortcut]
+URL=https://azureforeducation.microsoft.com/devtools

01_Instruktionen/learn.microsoft.com.url

@@ -0,0 +1,2 @@
+[InternetShortcut]
+URL=https://learn.microsoft.com/en-us/training/browse/?expanded=azure&products=azure-active-directory-domain

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/Azure/Azure AD Connect Sync and Cloud Sync.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://www.youtube.com/watch?v=aAZ4QXV7Wy0

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/Azure/Comparing Group Policy, Config Manager and Intune.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://www.youtube.com/watch?v=kyABkzwvJEc

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/Azure/MS Renames.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://m365maps.com/renames.htm

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/DNS/Theorie DNS.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://www.zytrax.com/books/dns/ch2/index.html#history

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/LDAP/Theorie LDAP.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://www.zytrax.com/books/ldap/ch2/index.html

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/Samba/Samba and GPO.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://samba.tranquil.it/doc/en/samba_fundamentals/about_gpo.html

02_Unterrichtsressourcen/03_Fachliteratur&Tutorials/Schema/Active Directory Schema.url

@@ -0,0 +1,5 @@
+[{000214A0-0000-0000-C000-000000000046}]
+Prop3=19,11
+[InternetShortcut]
+IDList=
+URL=https://www.youtube.com/watch?v=cudOfPfz98Q

04_Übungen/00_Einstiegsfragen.md

@@ -0,0 +1,55 @@
+# M159 - Einstiegsfragen
+
+Diese Fragen dienen zum aktivieren des Vorwissens in das Thema Active Directory Domain Services. Wer noch kein Vorwissen hat kann folgende Ressourcen nutzen. 
+
+[What is a Windows Domain Controller](https://www.youtube.com/watch?v=cTe5GsyhKUk)
+
+[3.1_Verzeichnisdienst.pdf](https://tbzedu.sharepoint.com/:b:/s/campus/students/EV49o9w43SxPnOcZ3v2Ey-EBLgUQozyJoiiHvBe9Ur0H5g?e=m0k9q6)
+
+## Fragen
+
+1. Aus technischer Sicht ist ein Verzeichnisdienst nichts anderes als
+
+2. Nennen Sie 4 Kernaufgaben eines «Directory Services»
+
+3. Nennen Sie 5 Objekte (Ressourcen), welche in einem Directory vorkommen können 
+
+4. Nennen Sie 5 Merkmale eines «Directory Services»
+
+5. Zusammenhang zwischen Objekt, Attribut und Wert 
+   Kreuzen Sie die korrekten Antworten an: 
+
+   ·	Benutzerattribute sind Eigenschaften von Computern 
+   ·	Benutzerattribute haben einen Namen und einen Wert 
+   ·	Das Benutzerpasswortattribut bestehend aus Namen und Wert ist ein Benutzerattribut 
+   ·	Der Vorname ist ein Benutzerattribut 
+   ·	Druckerobjekte haben keine Attribute 
+
+6. Was ist eine Objektklasse?
+
+7. Nennen Sie zwei Nachteile eines «Directory Services»
+
+8. Beschreiben Sie eine IT-Situation, welche einen «Directory Service» verlangt
+
+9. Beschreiben Sie eine IT-Situation, welche keinen «Directory Service» verlangt
+
+10. Beschreiben Sie, was ein lokaler Administrator ist
+
+11. Beschreiben Sie, was ein Domänenadministrator ist
+
+12. Was ist die Aufgaben des Domänenkontroller’s? 
+
+13. Wofür steht die Abkürzung DC? 
+
+14. Wofür steht die Abkürzung OU bzw. OE? 
+
+15. Was bedeutet „On-Premisis“? 
+
+
+
+## Lösungen
+
+[Einstiegsfragen](https://gitlab.com/ch-tbz-it/TE/m159/-/tree/main/L%C3%B6sungen?ref_type=heads)
+
+
+

README.md

@@ -1,92 +1,50 @@
-# m159
+# M159 - Directoryservices konfigurieren und in Betrieb nehmen
+
+Herzlich willkommen im Modul 159! 
 
 
 
-## Getting started
+## Version der Modulidentifikation
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+13.08.2021, V3 ([Modulbaukasten ICT-BCH](https://www.modulbaukasten.ch/module/159/3/de-DE?title=Directoryservices-konfigurieren-und-in-Betrieb-nehmen)).
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
 
-## Add your files
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+## Kurzbeschreibung des Moduls gemäss Modulidentifikation
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
 
-```
+*Directoryservices konfigurieren, Directorystrukturen implementieren, Benutzerdaten verwalten, Sicherheitseinstellungen nach Vorgabe vornehmen, Synchronisation sicherstellen, Directoryservices testen und an Betrieb übergeben.*
-cd existing_repo
-git remote add origin https://gitlab.com/ch-tbz-it/Stud/m159.git
-git branch -M main
-git push -uf origin main
-```
 
-## Integrate with your tools
 
-- [ ] [Set up project integrations](https://gitlab.com/ch-tbz-it/Stud/m159/-/settings/integrations)
 
-## Collaborate with your team
+## Aufbau der Unterlagen zum Modul
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- 01_Instruktionen
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- 02_Unterrichtsressourcen
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+  - 01_Bilder
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+  - 02_Präsentationen
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+  - 03_Fachliteratur&Tutorials
 
-## Test and Deploy
+- 03_Aufgaben
+- 04_Übungen
+- 
 
-Use the built-in continuous integration in GitLab.
 
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
 
-***
+### 01_Instruktionen
 
-# Editing this README
+Hier erfahren Sie wie das Modul aufgebaut ist und durchgeführt wird.
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+### 02_Unterrichtsressourcen
 
-## Suggestions for a good README
+Hier finden Sie sämtliche Unterlagen, welche Sie für die Bearbeitung und Lösung der Aufgaben benötigen. Es wird jeweils bei den einzelnen Aufgaben auf die erforderlichen Inhalte unter Fachliteratur & Tutorials hingewiesen. 
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
 
-## Name
+### 03_Aufgaben
-Choose a self-explaining name for your project.
 
-## Description
+Hier finden Sie die einzelnen Aufgaben für die Bewertung Ihrer Modulnote.
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
 
-## Installation
+### 04_Übungen
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
 
-## Usage
+Übungen welche zum Verständnis verschiedener Themen dienen
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.