first commit
This commit is contained in:
11
projects/sbx/20241211-Max-Meeting-Kerio2M365.md
Normal file
11
projects/sbx/20241211-Max-Meeting-Kerio2M365.md
Normal file
@@ -0,0 +1,11 @@
|
||||
|
||||
## Notes
|
||||
|
||||
- max tested already the migration with a test mailbox
|
||||
- test next the migration of some (public) project folders
|
||||
|
||||
|
||||
## teams phone
|
||||
|
||||
- do it after the mail migration
|
||||
- upgrade and not a downgrade
|
||||
104
projects/sbx/disney-workshop.md
Normal file
104
projects/sbx/disney-workshop.md
Normal file
@@ -0,0 +1,104 @@
|
||||
|
||||
The Disney Method is a structured brainstorming technique that uses three distinct perspectives—**the Dreamer, the Realist, and the Critic**—to develop and refine ideas. Here's a workshop plan tailored to an MSP dealing with automation, standardization, and improving efficiency for companies with 20-30 employees:
|
||||
|
||||
---
|
||||
|
||||
## **Workshop Plan: Disney Method for MSP Process Improvement**
|
||||
|
||||
### **Preparation**
|
||||
- **Duration**: 4-5 hours (including breaks)
|
||||
- **Participants**: Include key employees from management, tech teams, and support teams to ensure diverse perspectives.
|
||||
- **Materials**:
|
||||
- Whiteboards, sticky notes, markers
|
||||
- Large paper for mapping ideas
|
||||
- Timer
|
||||
- Projector (if needed for presentations)
|
||||
- **Environment**: Arrange the space into three distinct zones or corners (labeled Dreamer, Realist, and Critic).
|
||||
|
||||
---
|
||||
|
||||
### **Agenda**
|
||||
|
||||
#### **1. Introduction (15 minutes)**
|
||||
- **Objective**: Explain the goals of the workshop and the Disney Method.
|
||||
- Share the current challenges (automation, standardization, efficiency).
|
||||
- Define success: actionable, realistic solutions.
|
||||
- **Icebreaker**: Quick activity to build rapport (e.g., "What's one innovation you love and why?").
|
||||
|
||||
---
|
||||
|
||||
#### **2. Stage 1: The Dreamer (45 minutes)**
|
||||
- **Purpose**: Generate bold, creative ideas without limitations or concerns.
|
||||
- **Setup**:
|
||||
- Move participants to the *Dreamer Zone*.
|
||||
- Ask them to imagine an ideal version of the company where everything is perfect.
|
||||
- **Prompt Questions**:
|
||||
- "What does a fully automated and standardized MSP look like?"
|
||||
- "What if we had infinite resources—how would we solve our process issues?"
|
||||
- "What would be the most exciting thing we could offer our customers?"
|
||||
- **Activity**:
|
||||
- Brainstorm ideas in groups.
|
||||
- Write down every idea (no evaluation!).
|
||||
- **Output**: A large pool of ideas.
|
||||
|
||||
---
|
||||
|
||||
#### **3. Stage 2: The Realist (1 hour)**
|
||||
- **Purpose**: Refine the ideas into practical, actionable solutions.
|
||||
- **Setup**:
|
||||
- Move participants to the *Realist Zone*.
|
||||
- Review the ideas generated in the Dreamer stage.
|
||||
- **Prompt Questions**:
|
||||
- "How can we implement this idea step-by-step?"
|
||||
- "What resources do we need, and what resources do we have?"
|
||||
- "Which ideas can be executed within our current constraints?"
|
||||
- **Activity**:
|
||||
- Split into small teams, each working on 2-3 Dreamer ideas.
|
||||
- Develop actionable plans, timelines, and resource requirements.
|
||||
- **Output**: A set of actionable plans for the most promising ideas.
|
||||
|
||||
---
|
||||
|
||||
#### **4. Stage 3: The Critic (1 hour)**
|
||||
- **Purpose**: Identify risks, challenges, and weaknesses in the plans.
|
||||
- **Setup**:
|
||||
- Move participants to the *Critic Zone*.
|
||||
- Examine the actionable plans developed in the Realist stage.
|
||||
- **Prompt Questions**:
|
||||
- "What could go wrong with this idea?"
|
||||
- "Are there more efficient alternatives?"
|
||||
- "How can we mitigate these risks?"
|
||||
- **Activity**:
|
||||
- Groups present their plans.
|
||||
- Other participants play the role of the critic and provide constructive feedback.
|
||||
- Revise plans based on feedback.
|
||||
- **Output**: Polished and realistic action plans.
|
||||
|
||||
---
|
||||
|
||||
#### **5. Synthesis & Action Plan (45 minutes)**
|
||||
- **Purpose**: Consolidate the best ideas into a strategic roadmap.
|
||||
- **Activity**:
|
||||
- Prioritize ideas based on impact and feasibility.
|
||||
- Assign ownership to key team members for each initiative.
|
||||
- Set timelines for implementation.
|
||||
- **Output**:
|
||||
- A finalized action plan, ready for execution.
|
||||
|
||||
---
|
||||
|
||||
#### **6. Closing & Next Steps (15 minutes)**
|
||||
- Summarize the outcomes of the workshop.
|
||||
- Gather feedback from participants.
|
||||
- Share follow-up plans, including timelines and responsibilities for implementing ideas.
|
||||
|
||||
---
|
||||
|
||||
### **Post-Workshop Follow-Up**
|
||||
- **Document outcomes**: Share a summary with participants and stakeholders.
|
||||
- **Schedule check-ins**: Regular meetings to review progress on implementation.
|
||||
- **Celebrate wins**: Acknowledge milestones and successes to maintain momentum.
|
||||
|
||||
---
|
||||
|
||||
This approach ensures balanced creativity, practicality, and critical thinking to address your company's challenges effectively.
|
||||
42
projects/sbx/knowledgebase.md
Normal file
42
projects/sbx/knowledgebase.md
Normal file
@@ -0,0 +1,42 @@
|
||||
## Introduction
|
||||
|
||||
Our current knowledgebase is very unorganized. And nobody knows where to find something.
|
||||
So the idea is to completely restructure the folder structure.
|
||||
|
||||
## Idea
|
||||
|
||||
- Put everything existing into an folder `/old`
|
||||
|
||||
## Hannah's Pre-Work
|
||||
|
||||
### Layout an Beta orientiert
|
||||
|
||||
Allgemeine Ordner Struktur:
|
||||
Standardordner:
|
||||
- Backup: (Veeam)
|
||||
- Drucker: (Scanner…)
|
||||
- Firewall:
|
||||
- Sophos (XG)
|
||||
- VPN (PSK, Site2Site)
|
||||
- Internet/Provider: (Telekom, 1&1)
|
||||
- WLAN (Pre-Shared Key)
|
||||
- Mail: (M365, O365, CI-Sign, User E-Mails, SBX-Support)
|
||||
- Server: (MSA, SVN)
|
||||
- ILO
|
||||
- Switche
|
||||
- VM-Ware
|
||||
- Systemgeräte: (Türklingel, Türschließanlagen, Monitoring, ISO, Softbox Handy)
|
||||
- NAS
|
||||
|
||||
Firma spezifisch:
|
||||
- Standorte (Nürnberg, Olching etc.)
|
||||
- Telefonie
|
||||
- Apple
|
||||
- Programme/Dienste: Adobe, Anmeldungen, nextcloud, zoom, TeamViewer, ClickShare, Dark Trace
|
||||
- (User Geräte): Produktkey, (Monitoring) AD
|
||||
- Lokale windwos benutzer
|
||||
- Offene Passwörter die man sortieren könnte: BETA
|
||||
- Apple
|
||||
- (Office)
|
||||
|
||||
|
||||
18
projects/sbx/raci_matrix-automation.md
Normal file
18
projects/sbx/raci_matrix-automation.md
Normal file
@@ -0,0 +1,18 @@
|
||||
|
||||
## Zyklisch
|
||||
|
||||
- Temp Folder regelmaessig loeschen; sowohl Windows und Mac. Linux macht sowas selber
|
||||
- Unuetze Daten regelmaessig loeschen, die sich aber ansammeln; Download Ordner, Papierkorb, sonstiges (muss mit Kunden geklaert werden)
|
||||
-
|
||||
|
||||
## Neu
|
||||
|
||||
- [sophos-vpn-provisioning](https://docs.sophos.com/nsg/sophos-firewall/20.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/RemoteAccessVPN/IPsecSSL/SophosConnect/RAVPNSConConfigureProvisioningFile/index.html)
|
||||
- PXE Boot im Buero
|
||||
- Windows init Installation Automatisierung bei Faellen wo Intune nicht geht:
|
||||
- Powershell Desired State Configuration (declarative)
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
21
projects/sbx/raci_matrix-monitoring.md
Normal file
21
projects/sbx/raci_matrix-monitoring.md
Normal file
@@ -0,0 +1,21 @@
|
||||
## Zyklische Aufgaben
|
||||
|
||||
- An Patch/Update Tagen alle fehlgeschlagenen Patches/Updates ueberpruefen
|
||||
-
|
||||
|
||||
## Optmierung bestehender Systeme
|
||||
|
||||
### Backup Monitoring
|
||||
|
||||
Bestimmte Geraete/Services lassen sich nicht optimal in unsere bestehende Monitoring Loesung integrieren (aktuell NinjaOne).
|
||||
Dies betrifft nach aktuellem Wissensstand:
|
||||
- Veeam Backup Status Meldungen und Backup Reports
|
||||
- Synology Hyper Backup (Ist keine native Syn Applikation, weshalb SNMP nicht dafuer unterstuetzt wird von Syn)
|
||||
- Statusmeldungen zu nativen Synology Funktionen/Eigenschaften wie automatischen Updates, fehlenden Updates, Probleme bei Festplatten koennen ueber SNMP integriert werden, aber das Monitoring und die Benachritigung sind nur suboptimal.
|
||||
|
||||
Diese Systeme sind kritisch und Ihre Dysfunktionalitaet kann zu grossen Problemen fuehren.
|
||||
Daher muessen wir eine Monitoring Loesung findnen, welche uns mindenstens sofort Benachrichtigt, wenn es zu kritischen Problemen bei diesen Systemen kommt.
|
||||
|
||||
### NinjaOne
|
||||
|
||||
- Alle fehlgeschlagenen Windows Updates ueberpruefen und die Fehler manuell bereinigen. Wenn die Updates wieder fehlschlagen, herausfinden warum dies geschieht. Damit dies nachhaltig zuverlaessig funktioniert. Es kann nicht sein, dass wir standardmaessig ueber 100 Meldungen haben bei denen OS Patches fehlgeschlagen sind.
|
||||
9
projects/sbx/sbx-host-update-cycle.md
Normal file
9
projects/sbx/sbx-host-update-cycle.md
Normal file
@@ -0,0 +1,9 @@
|
||||
Softbox has a general update cycle:
|
||||
|
||||
| Host | Cycle |
|
||||
| --------------- | ------------------------- |
|
||||
| Windows Clients | 3rd Thu of each Month |
|
||||
| Linux/Win Server | 3rd Sat of each Month at 2:00 am |
|
||||
| Linux Server | scan every day at 1:30 pm |
|
||||
|
||||
which is directed to [[windows-update-cycle]].
|
||||
42
projects/sbx/sbx-linux-server-status.md
Normal file
42
projects/sbx/sbx-linux-server-status.md
Normal file
@@ -0,0 +1,42 @@
|
||||
A table of linux machines showing their OS, existence of unattended-upgrade config files, auto-update and -upgrade status and uptimes (changes dynamically)
|
||||
Some linux hosts are missing which have been added to a later time. (date of creation: 2024-03-15)
|
||||
|
||||
| Device | Organization | OS | unattended disabled | Manual update and reboot | Comment |
|
||||
| -------------------- | -------------------------- | ------------------- |:-------------------:|:------------------------:| ------------------------ |
|
||||
| beta-srv-svn01 | Beta Film | Ubuntu 22.04.2 LTS | 1 | yes | n/a |
|
||||
| bzt-srv-app01 | BZT | Ubuntu 20.04.3 LTS | 0 | | n/a |
|
||||
| cloud | Softbox | Ubuntu 22.04.4 LTS | 0 | | n/a |
|
||||
| cloud | BVV | Ubuntu 20.04.6 LTS | 0 | | n/a |
|
||||
| gg-dmz-cloud01 | Gym Gruenwald | Ubuntu 22.04.2 LTS | 0 | yes | n/a |
|
||||
| gg-dmz-web01 | Gym Gruenwald | Ubuntu 20.04.3 LTS | 0 | yes | n/a |
|
||||
| git | Phytron | Ubuntu 20.04.6 LTS | 0 | | n/a |
|
||||
| gitlab | BVV | Ubuntu 22.04.2 LTS | 0 | | n/a |
|
||||
| grav | Gymnasium Grünwald | Debian 11 GNU/Linux | 0 | yes | n/a |
|
||||
| mac-srv-gl01 | MACCON GmbH & Co. KG | Ubuntu 20.04.2 LTS | 0 | | n/a |
|
||||
| mac-srv-nc01 | MACCON GmbH & Co. KG | Ubuntu 22.04.4 LTS | 0 | | n/a |
|
||||
| mahara.vhs-bayern.de | BVV | CentOS ?? | 0 | | n/a |
|
||||
| mail-gw1 | BVV | Ubuntu 20.04.6 LTS | 0 | | n/a |
|
||||
| moodle | BVV | Ubuntu 16.04.7 LTS | 0 | | Linux Policy |
|
||||
| mn-cloud-01 | maier.neuberger | Ubuntu 20.04.3 LTS | 0 | yes | n/a |
|
||||
| neo-srv-ubt01 | NEOsphere Biotechnologies | Ubuntu 22.04.4 LTS | 0 | | Gitlab key error |
|
||||
| neo-srv-ubt02 | NEOsphere Biotechnologies | Ubuntu 22.04.4 LTS | 0 | | Gitlab key error |
|
||||
| nextcloud | 03 Arch. GmbH | Ubuntu 22.04.2 LTS | 0 | | n/a |
|
||||
| nextcloud | Heilmaier | Ubuntu 18.04.6 LTS | 0 | | n/a |
|
||||
| ns2 | BVV | Ubuntu 20.04.6 LTS | 0 | | dns server. DO NOT TOUCH |
|
||||
| peb | BVV | Ubuntu 20.04.6 LTS | 0 | | n/a |
|
||||
| pve (NO UPDATES) | Softbox | Debian GNU/Linux 12 | 0 | | Linux Policy |
|
||||
| rproxy2 | BVV | Ubuntu 20.04.6 LTS | 0 | | n/a |
|
||||
| SRV-APP04 | Allude | Ubuntu 16.04.5 LTS | 0 | | n/a |
|
||||
| st20mapp-p016 | studio2010 GmbH & Co KG | Ubuntu 22.04.4 LTS | 0 | | DO NOT TOUCH |
|
||||
| st20mapp-p017 | studio2010 GmbH & Co KG | Ubuntu 22.04.4 LTS | 0 | | DO NOT TOUCH |
|
||||
| sv-dmz-nc-1 | Grundschule Grasslfing | Ubuntu 22.04.4 LTS | 0 | yes | n/a |
|
||||
| vzby-srv-web01 | Verbraucherzentrale Bayern | Ubuntu 22.04.2 LTS | 0 | yes | n/a |
|
||||
| web4 | Softbox | Ubuntu 22.04.4 LTS | 0 | | n/a |
|
||||
| web5 | Softbox | Ubuntu 22.04.4 LTS | 0 | | n/a |
|
||||
| wiki | 03 Arch. GmbH | Ubuntu 22.04.2 LTS | 0 | | n/a |
|
||||
| Z-CLOUD-01 | Phytron GmbH | Ubuntu 22.04.3 LTS | 0 | yes | n/a |
|
||||
| z-jira | Phytron GmbH | Debian GNU/Linux | 0 | yes | n/a |
|
||||
|
||||
|
||||
Notes:
|
||||
- 22.03.24 - sv-dmz-nc-1: after the update of mariadb, mariadb wouldnt start again. Had to manually change `/etc/mysql/mariadb.conf.d/50-server.cnf` file. See <https://github.com/MariaDB/mariadb-docker/issues/560>
|
||||
5
projects/sbx/sbx-myrules.md
Normal file
5
projects/sbx/sbx-myrules.md
Normal file
@@ -0,0 +1,5 @@
|
||||
## Rules to follow
|
||||
|
||||
- Keep Autotask updated: Every Evening
|
||||
- Be at 8 o'clock in the office!
|
||||
- Less procrastination
|
||||
4
projects/sbx/sbx-proxmox-test-server.md
Normal file
4
projects/sbx/sbx-proxmox-test-server.md
Normal file
@@ -0,0 +1,4 @@
|
||||
|
||||
mac-address:
|
||||
- 00:19:99:b9:9a:a2 of interface enp8s0f0
|
||||
- 00:19:99:b9:??:?? of interface enp8s0f1
|
||||
14
projects/sbx/sbx-unattendedWinstall.md
Normal file
14
projects/sbx/sbx-unattendedWinstall.md
Normal file
@@ -0,0 +1,14 @@
|
||||
## Source
|
||||
|
||||
- [unattended Winstall - Github](https://github.com/memstechtips/UnattendedWinstall)
|
||||
- [answer files](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/update-windows-settings-and-scripts-create-your-own-answer-file-sxs?view=windows-11)
|
||||
- [unattended-generator](https://schneegans.de/windows/unattend-generator/)
|
||||
|
||||
## Meeting Michael (17.01.2025)
|
||||
|
||||
The steps we want to implement:
|
||||
1. Win 11 OS autoinstall - the idea is to use Microsoft's own "Answer files"
|
||||
2. AD coupling - it probably possible to also use the Answer files for this
|
||||
3. Ninja Agent Installation - again, use answer file
|
||||
4. SW Installation - User NinjaOne
|
||||
5. OS and SW Configuration and Personalization - Use NinjaOne
|
||||
Reference in New Issue
Block a user