Hello @Acf2,   Windows Hello is just a MFA/Single Sign-On system in the Windows ecosystem, for your client machines. In SAS 9.4, the main and supported SSO method (specially on windows) is Kerberos/IWA/NTLM.    Since Kerberos is a requirement in Windows Hello, for as long as you configure Kerberos/IWA in SAS, SAS will have no trouble with the Authentication Method in your clients machines. The servers on Windows and SAS are able to pickup the Kerberos TGT ticket.   https://learn.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/deploy/on-premises-cert-trust ... View more

Hello @sa_spartan ,   it is possible to zip and move any file. Just mind the fact that, by doing that, you will create discrepancies between SMC and the actual metadata backups.   I would like to encourage you, in this case, to either increase disk storage, configure the metadata backups to another storage with enough capacity for your retention requirements, or to reduce the retention time of 30 days to a lower number.   Please mind that your regular storage backups will still backup your metadata backups and you can still restore from there, but it might not be as simple as the restore through SMC. ... View more

Hello @WenjieZhou2021 ,   I would check first the permissions on both files and path of folders: first the unix permissions, then, if you have ACLs, please do check those as well. It will tell you if you have permissions with  your user. ... View more

Hello Pierre,   I do agree with @SASKiwi , those are excellent guides and tools, they can give you some good information.   When you are migrating to new servers, you will need to think of several important aspects:   - It is a brand new installation, which will require an study of the design/architecture (even if it is the same) with risk mitigation, improvements & an assessment of current issues. This will lead you to work packages and a clear view of your requirements, for all your infrastructure, hardware, network, integrations, the OS and the SAS application and content.   - You will need a clear view as well of all the customizations in the OS configuration, SAS configuration, the storage configuration, firewalls, and your content as well. You might need to trace back through your Change Management system, unless you have all well documented, then there should be no issues, since M7 is similar to M8.   - SMU is a great tool, however I would not always recommend it: you will migrate a lot of things "as-is" which can initially look easy and convenient, but it will move "as-is" all the issues and garbage. When it is possible (when it is not required by one or more of your pieces of SAS Software, such as Customer Intelligence or other) I strongly suggest to do a Manual Promotion. It might seems more arduous in the beginning, but you are definitely more in control and the system will be cleaner.    All in all, if you want a complex & expensive system such as Grid to be well migrated, if you feel confident, go ahead, with good planning. If not, you might want to consider to involve the professional services of a Solutions Architect & a SAS Deployment specialist from SAS or a partner. Always consider that a good planning and set of requirements will take longer than a deployment/migration, and it is worth it. You want to minimize troubleshooting and re-deployments. ... View more

Hello @shoin ,   I work on several Zero trust environments. I am aware what you are talking about.  SAS 9 has limited possibilities vs SAS Viya.   In SAS 9 your best options are either IWA/Kerberos SSO (plarform wide) or, else, for the web, to place a reverse proxy upfront with the MFA of your choice which will then allow access to the SAS web (where the users will need to authenticate one last time).   There is another option, not really supported by SAS Tech Support, and also for the web, which is to implement SAML through Shibboleth. If you are interested about this option, you can see this paper wrote by @MikeRoda : https://support.sas.com/resources/papers/proceedings15/SAS1385-2015.pdf    SAS Viya has more options, integrated within the design.  ... View more

Hi, What I see there is that your JavaScript or CSS has been tampered with. The origin can be multiple reasons, like: - someone added some, creating a conflict - someone modified them, creating the conflict - the browser is translating, which can influence and generate conflicts - the browser has a module that is influencing - there is a reverse proxy or there is a modification in SAS Web Browser (Apache) that might rewrite or not grant access to some file - there are permissions set at the OS level that is not granting permissions to some file - a rebuild/redeploy process tampered some JS or CSS - we cannot leave aside the chance this might be caused by a bug, but I did not hear anything of it in SAS, so chances are low The best way to see if there are js calls or CSS labels in conflict is to use the Web Dev tools as you show in one if your screenshots. Those should be able to show quickly any conflict. If you cannot find out or resolve in your own, I’d like to encourage you to reach out to the colleagues at SAS Technical Support to give it a look together with you. Best regards, Juan ... View more

Hello @Tomasz_Barnas , @Berux ,   I will give you the architectural considerations. Towards implementation, feel free to visit the documentation at SAS.   Please note, SAS OLAP server is a 9.4 technology, not available in SAS Viya (3.5 or 4).   This being said, any tool can access SAS Viya capabilities via Rest APIs, and or SAS Jobs (also accessible via Rest APIs). When in SAS 9.4, you would need common http requests and/or the usage of SAS Stored Processes - which can be published in the web application SAS Stored Processes and/or as webservice.   In this sense, PowerBI or any other tool can use the capabilities from SAS Viya (more capabilities) and of SAS 9.4   I hope this helps to give you some direction about what aspect of the documentation to look into. ... View more

That helps.   It seems to me as the user does not have permission to their expected SASUSER library. The SASAdmin should look into granting the right permissions to the expected folder.   ... View more

Hi there. Unfortunately we cannot see the full message of the error. If you can share more information, it would help. This being said, it could be a problem of port numbers (network & firewalls), or  permissions or anything.   I would like to suggest you to check the logs of the Object Spawner that spawns your SASApp Workspace Server, for more information, and try to run the WorkspaceServer.bat WorkspaceServer.sh executable from your server machine.   Best regards, Juan ... View more

I am personally not sure that your versions of ansible or Jinja are the right ones.   This is based on https://documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/p1gclfomj2px4ln1094gh8tj52mj.htm#n0va0q92zx5uvbn18u7bl46zhivo   Did you check those with SAS Technical Support? Might be wise, to be sure.   These kind of errors normally come from invalid pre-requirements and/or incompatibilities between versions and Operating Systems. ... View more

Hi there!   Yes it is, there are several pieces of code available. An example:   https://support.sas.com/documentation/cdl/en/lrmeta/63180/HTML/default/viewer.htm#p1k9zipe59ha2an1pq34gu143lay.htm   See Example: Listing Logins and Their Associated Identities and Authentication Domains   Let us know if it works for you! ... View more

Hello, could you get also the output for:   python3.10 -m pip show ansible   Or similar. The versions might be different of what you would expect.   https://documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/p1puupgtsay2r5n1h6k11n6lpl97.htm  ... View more

Hello Manesh,   I can see in which direction you want to address your question(s), but I cannot understand what is exactly the question or the problem. Missing some verbs, the issue/log, a description of your current setup, etc.   For now, but I am going to give long shots since I cannot understand you yet: Indeed, Auth domains with the same name are not a good idea. You cannot re-use the username on different account tabs either. All must be unique, else it won't work.   Please let us know if this helps or if you need more. If you do, please help us by rephrasing your question(s)! 🙂   Best regards, Juan ... View more