SAP Windows
Installing SAP on Windows Server follows SAP’s standard installation flow using the Software Provisioning Manager (SWPM), against a supported database, with Windows-specific conventions for users, services and file systems.
Installing SAP on Windows means a supported Windows Server at the right patch level, domain or local users, file systems, and SWPM with media from the Maintenance Planner. SWPM installs the ASCS, the database instance or connection and the primary application server as Windows services managed in SAP MMC. S/4HANA's database is HANA on Linux.
- Watch out: Antivirus locking SAP files during install/run.
Prerequisites
- A supported Windows Server version at the required patch level.
- A supported database (note: S/4HANA requires HANA, typically on Linux, so pure-Windows S/4HANA app tiers connect to a HANA DB).
- Required domain/local users and file systems.
- SWPM and the correct media via Maintenance Planner.
The installation flow
On Windows you run SWPM, which guides you through installing the central services (ASCS), the database instance (or connection), and the primary application server. It creates the SAP services, users and directory structure, and finalises the system so it can be started via the SAP MMC or services.
Windows specifics
- SAP runs as Windows services (managed via SAP MMC).
- User accounts follow Windows/domain conventions.
- Watch file-system permissions and antivirus exclusions on SAP directories.
Verify
After install, confirm the services start, you can log in via SAP GUI, and a basic transaction works. Check the installation and work-process logs if startup fails, most Windows issues are permissions or service configuration.
Common pitfalls
- Antivirus locking SAP files during install/run.
- Permission issues on SAP directories.
- Assuming full S/4HANA on Windows, the database is HANA on Linux.