/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Publishing Avaya Cms Supervisor with XenApp

07/10/2012 8625 views

when pulishing the Avaya CMS supervisor using xenapp 6.5 , i m getting the following error

can somebody please suggest, what probably might be the cause behind it. We are streaming the application to server.

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer


  • It states that you need to give authenticated users full control on the folder:

    C:\Program Files\Avaya and C:\Program Files (x86)\Avaya
  • Hello,
    Yes i did read that blog, but it is useful under XA hosted desktop. what i want to achieve is totally different. I have a server where i publish the applications and then access these published applications over a client. So in my case the above method wont work. i even tried giving full permissions to the directory which has been mentioned in the above link. moreover when trying to manually deploy the application using RadeRun.exe in admin account, i m still getting the same error. I believe when deploying the application using the admin account the directories get full permission and there should be no need to provide full permissions to the directories manually

All Answers

0

As Bob mentioned in the above post

You need to give authenticated users full control on the folder:

C:\Program Files\Avaya  and C:\Program Files (x86)\Avaya

Note : You have to manually create C:\Program Files\Avaya folder and give permission

Have you done this?

Answered 07/11/2012 by: jagadeish
Red Belt

-2

The link which is provided by henrik80 should reslove your issue..

Answered 07/10/2012 by: jagadeish
Red Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ