Supported Windows Versions
Version | Supported | New Installations | Recommendation |
---|---|---|---|
Windows Server 2008 | No | No | Migrate to Windows Server 2016 or 2019. |
Windows Server 2008 R2 | No | No | Migrate to Windows Server 2016 or 2019. |
Windows Server 2012 | No | No | Migrate to Windows Server 2016 or 2019. |
Windows Server 2012 R2 | Yes | No | Migrate to Windows Server 2016 or 2019. |
Windows Server 2016 | Yes | Yes | |
Windows Server 2019 | Yes | Yes |
Preparation
Secure Boot
For the installation of the SIP drivers on Windows Server 2016 and Windows Server 2019, Secure Boot must be deactivated.
For details on how to do this, consult the documentation on your virtual environment.
Proxy Server
Some applications (git for example) require the explicit configuration of a proxy, as they do not read the windows proxy settings.
The proxy server can be identified as follows:
netsh winhttp show proxy
Basic OS Installation
Install the basic OS from the ISO file.
Note: install the version with the full graphical interface.
Requirements for Handover for Installation
The following tasks must be complete:
- Network Configuration (IP Address, Netmask, Gateway, DNS)
- NOTE: make sure the address is either static, or reserved in DHCP
- Hostname and Domain or Workgroup configured
- Local Administrator Account
- Activated remote desktop
- Hypervisor Guest Tools installed (Hyper-V Tools or VMWare Tools, or other)
- Machine has internet access to download the required software.
Windows Updates
Make sure all windows updates are installed. Once this is done, it is recommended to switch off windows updates and run windows updates manually when needed.
Before you run windows updates on a production machine, you should always ensure you have a complete backup or snapshot of the machine.
Windows updates have, in the past, broken perfectly running systems. The number of patches retrieved in a typical update make it almost impossible to find the offending package in a broken installation.
YOU HAVE BEEN WARNED!
Don'ts
The following are no-nos, do NOT do this:
- Badly behaved real-time virus scanners installed
- The jtel server is a real-time communications system, virus scanners which impact real-time access to files on the file system or the network are to be avoided.
- Whilst we cannot recommend a particular commercial virus scanner - the out of the box windows defender is fine to use.
- Automatic Windows Updates enabled
- Do not do this. See warning above.
- Automatic Windows Defender Updates via Group-Policy in Domain enabled
- Windows Defender is OK to use - see above.
- However, make sure the domain group policy does NOT pull windows defender updates during the operation hours of the call center.
- Group Policy - Automatic Logout enabled
- Deactivate this. The user running the jtel software should NOT be logged out when the system is running.
- User Account Control enabled
- Switch it off!
- If it is on (forced) by group policy, then make an exception for this machine.
Do's
- Group Policy - Run Applications as a Service
- The account running the jtel software MUST be allowed to run applications as a service.
- Software Installation
- The accound running the jtel software MUST be allowed to install software and perform software updates.
- Windows Firewall
- Leave it activated!
If jtel or a certified partner is performing the installation for you, this is the point where you should hand over the system.
Software Installation
Install a decent browser
Windows server still ships with internet explorer activated and no good browser installed.
The first task is to fix this.
We recommend using chrome, but if you prefer firefox or edge, that's perfectly OK too.
Note - make sure you set the default browser - the commands below will not work otherwise!
Tests
Nach einem Neustart sollte nun folgendes geprüft werden:
- Das System ist über RDP erreichbar.
- Es ist für den Projekt-Techniker möglich, sich über einen Remote Desktop Client als jtel-Benutzer an das System anzumelden.
- Der Projekt-Techniker kann in einer solchen Sitzung einen Prozess als Administrator starten.
Installiert der Kunde die Betriebssysteme, so ist dies üblicherweise der Übergabepunkt an den Projekt-Techniker.
Anpassung des Betriebssystems
Folgende weitere Anpassungen erfolgen nun auf der Windows Maschine durch den Projekt-Techniker:
- Java
- Compiler-Bibliotheken
- https://cdn.jtel.de/downloads/redist/vcredist_9.0_x86_9.0.30729.4148.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2010_x86_10.0.30319.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2012_x64_11.0.61030.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2012_x86_11.0.61030.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2015_x64_14.0.24123.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2015_x86_14.0.24123.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2017_x64_14.16.27027.exe
- https://cdn.jtel.de/downloads/redist/vcredist_2017_x86_14.16.27027.exe
- https://cdn.jtel.de/downloads/redist/ww_icl_redist_ia32_2017.1.143.msi
- https://cdn.jtel.de/downloads/redist/ww_icl_redist_intel64_2017.1.143.msi
- Cygwin Umgebung. Die Installation erfolgt in mehreren Schritten:
- https://www.cygwin.com/setup-x86_64.exe
- "Install from Internet"
- Zielverzeichnis: C:\Cygwin
- Package directory:
C:\Cygwin\packages
- Select Packages:
openssh (Bereich "Net")
ncftp (Bereich "Net")
curl (Bereich "Net")
wget (Bereich "Web")
- https://www.cygwin.com/setup-x86_64.exe
- Git Pre-Requisites:
- https://cdn.jtel.de/downloads/tools/Git-2.16.2-64-bit.exe
WICHTIG: Git Credential Manager NICHT installieren
- https://cdn.jtel.de/downloads/tools/Git-2.16.2-64-bit.exe
- GIT Client:
- https://cdn.jtel.de/downloads/tools/TortoiseGit-2.6.0.0-64bit.msi
Name: jtel Support
E-Mail: support@jtel.de
- https://cdn.jtel.de/downloads/tools/TortoiseGit-2.6.0.0-64bit.msi
- Text-Editor Notepad++
- MySQL ODBC Connector:
HINWEIS: Wegen Speicher-Probleme in den neueren MySQL Treibern wird empfohlen, mit der Version 5.2.7 zu arbeiten. Auch in den neuesten 8.x ODBC Treibern treten Speicherprobleme auf, wenn Verbindungen zu der Datenbank abbrechen. - Google Chrome:
- Windows Explorer Einstellungen:
- Explorer starten (Win+E)
- "Ansicht" bzw. "View" ... "Optionen" bzw. "Options"
- "Alle Ordner anzeigen" bzw. "Show all folders" aktivieren
- "Dateinamenerweiterungen" bzw. "File name extensions" aktivieren
- Explorer starten (Win+E)
- CMD Einstellungen:
- "Defaults" bzw. "Defaults" wählen
- "Quick-Edit Modus" deaktivieren. Dies muss sein, damit Dienste die als cmd laufen nicht durch ein Mausklick unterbrochen werden.
- "Layout" die beiden Werte "Breite" auf 125 einstellen.
- "Layout" den Wert "Höhe" im Bereich "Fenstergröße" auf 50 einstellen
Alle Downloads
https://cdn.jtel.de/downloads/java/jdk-8u202-windows-x64.exe https://cdn.jtel.de/downloads/redist/vcredist_9.0_x86_9.0.30729.4148.exe https://cdn.jtel.de/downloads/redist/vcredist_2010_x86_10.0.30319.exe https://cdn.jtel.de/downloads/redist/vcredist_2012_x64_11.0.61030.exe https://cdn.jtel.de/downloads/redist/vcredist_2012_x86_11.0.61030.exe https://cdn.jtel.de/downloads/redist/vcredist_2015_x64_14.0.24123.exe https://cdn.jtel.de/downloads/redist/vcredist_2015_x86_14.0.24123.exe https://cdn.jtel.de/downloads/redist/vcredist_2017_x64_14.16.27027.exe https://cdn.jtel.de/downloads/redist/vcredist_2017_x86_14.16.27027.exe https://cdn.jtel.de/downloads/redist/ww_icl_redist_ia32_2017.1.143.msi https://cdn.jtel.de/downloads/redist/ww_icl_redist_intel64_2017.1.143.msi https://www.cygwin.com/setup-x86_64.exe https://cdn.jtel.de/downloads/tools/Git-2.16.2-64-bit.exe https://cdn.jtel.de/downloads/tools/TortoiseGit-2.6.0.0-64bit.msi https://cdn.jtel.de/downloads/tools/npp.7.5.6.Installer.exe https://cdn.jtel.de/downloads/tools/mysql-connector-odbc-5.2.7-win32.msi (Englisch) https://www.google.com/chrome/browser/desktop/index.html?system=true&standalone=1&platform=win64&hl=en (Deutsch) https://www.google.com/chrome/browser/desktop/index.html?system=true&standalone=1&platform=win64&hl=de
Wenn Chrome installiert und als Standardbrowser eingerichtet ist, können Sie folgende Befehle nutzen um alle Downloads (bis auf Chrome) automatisch zu starten:
start https://cdn.jtel.de/downloads/java/jdk-8u202-windows-x64.exe start https://cdn.jtel.de/downloads/redist/vcredist_9.0_x86_9.0.30729.4148.exe start https://cdn.jtel.de/downloads/redist/vcredist_2010_x86_10.0.30319.exe start https://cdn.jtel.de/downloads/redist/vcredist_2012_x64_11.0.61030.exe start https://cdn.jtel.de/downloads/redist/vcredist_2012_x86_11.0.61030.exe start https://cdn.jtel.de/downloads/redist/vcredist_2015_x64_14.0.24123.exe start https://cdn.jtel.de/downloads/redist/vcredist_2015_x86_14.0.24123.exe start https://cdn.jtel.de/downloads/redist/vcredist_2017_x64_14.16.27027.exe start https://cdn.jtel.de/downloads/redist/vcredist_2017_x86_14.16.27027.exe start https://cdn.jtel.de/downloads/redist/ww_icl_redist_ia32_2017.1.143.msi start https://cdn.jtel.de/downloads/redist/ww_icl_redist_intel64_2017.1.143.msi start https://www.cygwin.com/setup-x86_64.exe start https://cdn.jtel.de/downloads/tools/Git-2.16.2-64-bit.exe start https://cdn.jtel.de/downloads/tools/TortoiseGit-2.6.0.0-64bit.msi start https://cdn.jtel.de/downloads/tools/npp.7.5.6.Installer.exe start https://cdn.jtel.de/downloads/tools/mysql-connector-odbc-5.2.7-win32.msi
Sicherstellen der Namensauflösung
Da nicht unbedingt damit zu rechnen ist, dass alle Rechnernamen und IP Adressen zuverlässig durch die DNS Server des Kunden immer in beiden Richtungen aufgelöst werden können (oft hat der Kunde keine Ahnung, wie er das verwalten soll), sollte auf jede der Maschinen des jtel-Systems auch die Hostdatei entsprechend angepasst sein, dass alle Maschinen des Systems dadurch bekannt sind. Dafür muss die Datei C:\Windows\System32\drivers\etc\hosts
als Administrator editiert werden. Das könnte dann so aussehen:
# Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 192.168.1.10 acd-lb acd-lb.example.com 192.168.1.10 acd-store acd-store.example.com 192.168.1.21 acd-dbm acd-dbm.example.com 192.168.1.22 acd-dbs acd-dbs.example.com 192.168.1.22 acd-dbr acd-dbr.example.com 192.168.1.31 acd-jb1 acd-jb1.example.com 192.168.1.32 acd-jb2 acd-jb2.example.com 192.168.1.40 acd-tel1 acd-tel1.example.com