laplandz wrote:@Ray - are you referring to a "run-once" type config/template?
If i'm reading it correctly, you want to install a Template (not a clientID) as a generic installer which generates the ClientID upon launch, this ClientID is pre-set as per a unique identifier (in your case through PCRT as a Device ID)
You would than need to re-apply the client information (config lite) through a registry patch if the customer re-installs? This is the bit that confuses me, If the Template-generic-installer generates the same ClientID, wouldn't you receive an e-mail to say so? Thus allowing you to reg-patch the missing config lite details?
Am i miles off target here?
I just posted a big detailed list to address this point, and I used "submit" and it didn't seem to post at all. I'm going to type this out again, sorry if it is a double post I just can't find my first post.
1. Boot the brand new PC (out of the box) to WinPE using PXE.
2. In WinPE, use my OS selector to configure the installation type (picture attached)
3. The computer boots into "Audit Mode" and selects everything automatically (oem themes, activation, tweaks, drivers, updates, apps)
4. The technician has a moment now to customize the computer for the client. This step is the manual installation process of dSupportSuite.
5. The computer is resealed, turned off, and placed on the shelf for resale. Recovery media is created for the customer to return the computer to the same state.
6. The customer will turn it on, it will display "please wait while your computer turns on the first time" and it will have the default windows prompt for username, password, wifi password, ect.
7. Now dSupportSuite finalizes the installation, along with all the other scripts I included. This is the first time it pings the dCloud.
So to relate this back to dSupportSuite, during Step 4 the technician will use the generic installer with the /opk or the /preinstall switch. dSupportSuite will prompt for the unique client ID. This is where I enter the asset tag. It will NOT prompt for the name, phone and email because I don't know who I am selling the machine to yet. dSupportSuite will PREINSTALL so it will NOT send the "New Install" email, and it will not register in the dCloud. For all intents and purposes, assume that for some strange reason there is no Internet for Step 4. It will be an offline installation which will connect to the internet during Step 7. Once the customer has the machine in their hands, I will update their asset tag to the appropriate template and I will include a reg file for Name, Email and Phone. If I do not do this, and that information is not found within the Client ID it will prompt the customer once.
@vmhs - Not quite, I do not want to install a template I want to preinstall a client ID. It will not "generate" the Client ID, I will enter it manually during step 4. I want this to be the only manual part of the installation process. You are correct that I would reg-patch the missing config lite details, which would be stored on the dCloud, and applied during the first launch.