GarthMJ

I would disagree with you. Do you really want to give your management the SCCM console, just to look at reports? No, they would generally want them emailed to them. Reports can be pretty too, you need to take time to make them or find either (free or paid) reports. Don't forget that you will need to update those consoles ever 3-4 months when you update to the latest version of CMCB, this is not a great experience for them.

Yes but it will always be out of date, so why not use the reports?

This is to be expected, Reporting is always 100% correct, whereas the console uses cached results.

When you created the SSRS SQL Server instance, did you create it with that name or did you create it with "SSRS", from the screenshot above it look like the later.

I'm not sure what you mean by this. What exactly are you trying to find? i'm not seeing anything wrong with this setup.

What is displayed is the instance name not the database name. This mean you setup your instance as SSRS

Glad everything is working for you now.

That is because CM's SQL requires 8 GB of RAM for itself as a bare min. You will never get CM up with just 4 GB of ram, you will need at least 10GB

I'm guessing but so did you set the system account account to English too? Is the OS English or German?

I believe that this is based on the SSRS server language, once that is changed you might need to re-install your reporting point.

did you check to see if the file exist at the location in question?

No, not without customizing the report and even then Version is not a number it is a string. So you get odd results.

Have you looked at the builtin reporting for SCCM?

When you look on your CAS, do you see the devices? I hope you didn't use the same site code for the new server.

How do you know AD discovery is finding devices? Is the DNS entry correct? Where are you looking at the collection on your CAS? Is your replication healthy?