When to Choose VCS Access or Direct Product Access
Topic
Access Methods and Authentication
Environment
Products that support both VCS access and direct product authentication. Applicability, supported workflows, and authentication requirements should be verified using current product documentation and approved support resources.
Summary
Use this article to determine whether a task should be completed through VCS or by logging directly into the product. Selecting the correct access method helps prevent authentication issues and unnecessary credential recovery activities.
Note: If you are able to access the customers VCS account, and the devices are registered, you will be able to access the device UX through Venus and not need those device specific passwords.
Steps
Question
When should I use VCS access instead of direct product access?
Answer
The appropriate access method depends on:
- The product being accessed
- The task being performed
- System connectivity
- Available authentication services
- Product-specific requirements
Some workflows allow access through VCS, while others require direct authentication to the product using product-specific credentials. Always verify the supported access method in current product documentation before attempting access.
Common Scenarios
Scenario 1: VCS Access Is Available
A technician needs to perform a task supported through VCS.
Recommended Action: Use the documented VCS access workflow before attempting direct product access.
Scenario 2: VCS Access Is Unavailable
A technician cannot reach the product through VCS.
Recommended Action: Verify connectivity, service availability, and product documentation. If supported, use the direct product access method.
Scenario 3: Access Works Through VCS but Not Directly
A user successfully accesses the product through VCS but cannot log in directly to the product.
Possible Causes:
- Different account requirements
- Different authentication methods
- Incorrect product credential
- Incorrect account selection
Resolution: Verify direct-access requirements before beginning credential recovery.
Scenario 4: Direct Access Works but VCS Access Does Not
A user can access the product directly but cannot access it through VCS.
Possible Causes:
- VCS connectivity issue
- VCS authentication issue
- Account synchronization issue
- Product-specific configuration issue
Resolution: Review current VCS troubleshooting procedures and product documentation.
KB ID: 000032522
DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.
DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN "AS-IS" AND "AS-AVAILABLE" BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.
The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.