Jeff Ulatoski

Hi @Levi Hayes, @D81, and @hatem Shahudh, Thank you all for sharing your experiences and solutions in such detail. Levi, I especially appreciate the thoroughness of your findings and the inclusion of screenshots—they're incredibly helpful for others who might face similar challenges. Levi, I sent you a private message to coordinate a meeting so we can discuss your experience, the product, and your idea about the YouTube video. To everyone else, thank you for contributing to this thread. Your collaboration is exactly what makes this community so valuable. We’re always working to improve, and your feedback is crucial in helping us refine both our product and our documentation. Thanks @Holly Lehman for connecting us! Best regards, Jeff Ulatoski App Volumes Product Manager, Omnissa

Hi @Levi Hayes, I appreciate your persistence in finding a solution, and I’m truly sorry that our support couldn’t provide the assistance you needed during this process. My team and I will be following up internally with our support team leaders to address your feedback. I would also like to schedule a follow-up meeting with you personally. As a product manager, anything related to the product is my concern, and I’m very interested in hearing more about your experience—not just with this specific issue, but with our overall product and support. I’ll send you a private message so we can coordinate our calendars for a Zoom call. Thank you again for your understanding, patience, and diligence in finding a solution. Jeff Ulatoski App Volumes Product Manager, Omnissa

Hi @Levi Hayes, Thank you for the update, and I'm glad to hear that support has reached out to you. I appreciate your cooperation in providing the necessary information and linking this page to help our team get up to speed. I’ll ensure that the support team is aware of your request for a troubleshooting session, and my team will stay closely involved to make sure everything moves forward smoothly. If you could share the full log file with the support team, that would be very helpful in diagnosing the issue more accurately. Thank you again for your patience and collaboration. We’re committed to resolving this as quickly as possible. Best regards, Jeff Ulatoski App Volumes Product Manager, Omnissa

Hello @Levi Hayes Thank you for the detailed update. It sounds like you've taken all the necessary steps on your end, including ensuring that the account has administrative privileges, verifying file path permissions, and removing any potential GPO interference. I apologize for the difficulties you've faced with opening a support case and for the premature closure of the previous case—this is certainly not the level of service we aim to provide. Given the persistence of the issue despite these measures, it’s clear that further investigation is needed. I’m escalating this matter internally to ensure that you receive the support you need. I'll also make sure that your concerns about the support ticket process are addressed, so this doesn’t happen again. I will coordinate with our support team to reopen the previous case or ensure that a new one is created immediately. In the meantime, I’ll keep you updated on any progress or additional steps we might need from you. Thank you for your continued patience, and I assure you that we’re committed to resolving this issue. Best regards, Jeff Ulatoski App Volumes Product Manager, Omnissa

Hello @Levi Hayes and @Dmartinez81, Thank you for bringing this issue to our attention, and I apologize for the frustration it's caused. Our engineering team is currently investigating the error related to the self-signed certificate generation during the App Volumes Manager installation. Based on the information you've provided, our engineering team believes the issue may be related to file permissions, specifically when the App Volumes Manager attempts to create the CVPowershell.key file in the Manager/config/ directory. This error typically occurs when the user account running the installation lacks the necessary privileges. We recommend double-checking the permissions on the directory mentioned in the log (C:/Program Files (x86)/CloudVolumes/Manager/config/) and ensuring that the user account running the App Volumes Manager installation has the necessary permissions to write to the CVPowershell.key file i and location. To help us assist you more effectively, could you please confirm if you have administrative privileges on the Windows machine where you're installing the App Volumes Manager? Additionally, if you haven’t already done so, I highly recommend opening a support ticket with Omnissa. This will allow our team to work with you directly and review any logs that might help diagnose the issue more quickly and precisely. We are here to support you and will continue to monitor this thread for any updates. I’ll keep you posted as we learn more. Best regards, Jeff Ulatoski App Volumes Product Manager, Omnissa