Sap logon pad v800 is not able to use landscape file generated by v700

Shubham Prajapati 60 Reputation points
2026-09-27T10:32:56.36+00:00

Hi 

Recently we have created new AVD windows 11 machine and in that we are using SAP logon pad v800. Earlier we had windows 10 machine and logon pad v700 something. In windows 11 when user is login with same fslogix profile he is not able to see the system details which he added manually. I'm suspecting this because of landscape file containing header like genarted by v770. We have one common landscape file also for all users that was containing the same text genearted by v770 and we were getting the error message whenever we try to open the log on pad as soon as we remove that genarted by v700 line that error was resolved.

Do we have any solution for this?

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Taz 10,126 Reputation points MVP Volunteer Moderator
    2026-09-27T14:02:19.7866667+00:00

    Hi Shubham,

    The issue is most likely not that SAP GUI 8.00 cannot read a landscape file generated by 7.70. SAP GUI 8.00 uses the same SAP UI Landscape XML format, and SAP states that the SAPUILandscape.xml and SAPUILandscapeGlobal.xml files are the supported configuration files.

    The more important issue in your case is the user-specific SAPUILandscape.xml stored in the FSLogix profile. SAP Logon keeps manually added connections in this file, while centrally supplied connections can be stored in SAPUILandscapeGlobal.xml.

    On the Windows 11/SAP GUI 8.00 host, check:

    %APPDATA%\SAP\Common\

    Look for:

    SAPUILandscape.xml
SAPUILandscapeGlobal.xml

    If the user's old 7.70 profile contains a problematic/corrupted SAPUILandscape.xml, back it up and let SAP GUI 8.00 create a new one. Do not delete the global file if it contains your centrally distributed systems.

    SAP also documents that the migration to the new landscape format happens only once, so carrying an old configuration forward can leave you with an incompatible or incorrect user configuration.

    Since removing the generated by v770 header makes your common file load, I would rebuild that landscape file with SAP GUI 8.00 rather than manually editing only the header. SAP specifically warns that manually created landscape XML can become inconsistent.

    Also check whether the user's FSLogix profile is preserving an old SAPUILandscape.xml while the new machine is using a different global landscape file. That would explain why the centrally defined systems work differently from the systems the user previously added manually.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.