Creating End User Projects For Channel Partner
This KB Article is designed to demonstrate the workflow partners should follow to request their End Users run a DPACK performance capture in their data centers, create projects of their End User's data once the DPACK collector has completed, and share DPACK analysis with End Users.
- All End User data is private to their account in the DPACK portal. As a partner, you are granted a license to be shared that data is the End User delegates you as a viewer.
If an End User doesn’t currently have a DPACK account, you are also given the option to invite them to use DPACK and create an account. By doing so, you initiate a “request DPACK capture” that will establish you as a viewer of the performance data collected during this request.
If you are a managed service provider where you act as the outsourced IT department for the End User, you will automatically be given the option to run DPACK on their behalf as part of the request DPACK capture process.
Access the DPACK 2.0 portal (https://dpack2.dell.com) and login with your account credentials.
If you have never logged into DPACK 2.0 before, go to https://dpack2.dell.com/register and request your account be created or contact your Dell Sales Team and request they register you to the DPACK portal.
To begin a request capture process, click “Request DPACK Capture” button on dashboard.
To begin End User lookup in DPACK portal, enter End User’s email address and click “Search for Contact” button.
DPACK will try to search for an End User's email address. If the user does not have an account on DPACK, we give you the opportunity to create one for them. Make sure that “Account Name”, “First Name”, and “Last Name” contain user information before clicking the “Send Request” button.
Alternately, if an End User has previously been registered to the DPACK portal, click the “Send Request” button.
The DPACK portal will send email notifications to the email addresses for both the requester (partner) and End User. Within the notification message, there will be direct links to download the DPACK collector software for the End User’s account. If the End User did not have a DPACK account in Step 4, they will also receive an account activation message from DPACK containing details on how to activate their portal account and setup their password.
NOTE: If the requesting partner wants the DPACK collector run data to be streamed to their account, it is important that the End User download the DPACK collector software using the links provided in these email messages. Additionally, the partner email address should always be listed as a CC recipient in the DPACK capture request messages sent from the DPACK portal. This allows partners to run DPACK on behalf of their End Users in situations where that is requested or needed.
Step 6: Download, extract and run DPACK collector
End User should be able to download the DPACK collector software using the links provided in the email previously sent to them, extract and execute the collector, configure DPACK (including adding all remote servers), and begin data capture.
NOTE: End User should verify the system consultant’s information in DPACK matches partner information before beginning configuration.
The DPACK collector software will automatically stream the collector run data back to the DPACK servers by default (can be changed when DPACK is started). These streamed collector runs are automatically added to a project and can be viewed once the DPACK software has started. To view a project, click on the project name listed on your dashboard.
DPACK project data will be available in two different views, Environment View and Performance View.
The data streaming process employed by the DPACK portal is encrypted by the DPACK collector software and transmitted over TCP port 443 (HTTPS) to the DPACK servers. The data transmission process is seamless and adds little to no overhead to the DPACK software performing the End User's collector run. There are instances where the data transmission fails and the streaming data fails. In the event of these rare instances, the DPACK collector will continue to collect performance data and at the end of the designated performance collection period, DPACK will generate an SIOKIT file that can be uploaded to the DPACK portal using the "Upload IOKIT" button on the dashboard.