OEM Preinstallation of dSupportSuite

[csc]

Hey,

I want to install dSupportSuite while installing Windows in Audit mode (as administrator login, before the out of box experience process and first user account is created) but not have it email me a New Install email (yet) or create the identity within the dCloud (yet). It would do these steps when the user runs the OOBE experience (turns on the computer for the first time).

Currently I can currently place the installer within the scripts directory for an automated install but it is a pain to build each installer individually, it would be nicer to be able to preinstall dSupportSuite and have it trigger a new identity to the dCloud only when the OOBE is run. I don't want to see identities for computers I haven't sold yet in my dCloud, but I do want to specify the identity so it installs automatically from OOBE.

Perhaps the best way to do this is to create a command line switch within the installer for client name, phone and email as well as the client identity, so a generic installer could be placed on my windows installation disks.

For now the easiest way to go about this would be to create a command line switch that surpresses the New Install email as well as the dCloud login, and another command line switch to trigger the New Install email and dCloud login which could be run from SetupComplete.cmd

Thanks,
Ray

[vmhs]

I second this.

dsupportinstaller.exe /clientid="CUST - WS" /userdetail="Customer name,8675309,email@example.com" /verysilent

[laplandz]

+1 for this, would also be useful for changing the client ID when needed.

Sent from Tapatalk

[csc]

+1 for this, would also be useful for changing the client ID when needed.

Great point! If you're using an RMM platform you can push the installation to the client machine, or push an update for the client ID.

[csc]

dsupportinstaller.exe /clientid="CUST - WS" /userdetail="Customer name,8675309,email@example.com" /verysilent

Good example, but one more command line switch would be needed to delay the actual installation of the software. Add "/Preinstall" which would delay the dCloud installation and the New Install email for purposes of being installed during the windows preinstallation phase (audit mode).

[Nick]

probably going to SHOCK everyone by popping in this thread today and by what I'm doing

I second this.

dsupportinstaller.exe /clientid="CUST - WS" /userdetail="Customer name,8675309,email@example.com" /verysilent

lol vmhs


ok here's the bone I'm throwing today. gotta make a road trip and no time to test what I just coded. first person to tell me if thse new features work or not, gets a Foolish IT "Guinea Pig" silk touch sweat wicking comfortable as you can imagine polo style shirt. winner can PM me with your shirt size and shipping address. Only Large, XL, 3XL, and 4XL available. Yes, 4XL. Not sure what I was thinking when I made that order, just not that your average tech was in a Small/Medium, and that many of us can get a little large sitting behind a desk all day

just released v3.9.21, added command line parameters: (NOT setup executable parameters, these are for dSupportSuite.exe itself, as it lives inside %programfiles...)

/set
enables usage of these other new parameters - required

/clientid=
set local client id, note this does not create a new one, nor does it check to confirm if it is valid, it just configures dSS to use that client ID on the 'local' machine no matter what

/newclientid=
set local client id, also creates the id on your server if it doesn't already exist. note this does not check for duplicates, if the id does exist, it enables it (even if it was disabled previously)

/clientname=

/clientphone=

/clientemail=

examples:

Code: Select all

dSupportSuite.exe /set /newclientid=my client id /clientname=my client name /clientphone=8675309 /clientemail=foo@bar.com

I guess my best recommendation to bring it altogether is to create a new custom (not generic) installer, with a generic/standard/default client ID and config, embedding some dummy client data and skipping configlite prompt, etc. so the setup executable can be deployed with the /verysilent parameter. then you can come back and script dSupportSuite.exe from the installation directory with these command line parameters at a later time. (oobe, whenever)

You can also get the new install email with the existing switch /newinstallemail and you can just tack that on the end (note it should come LAST), like

Code: Select all

dSupportSuite.exe /set /newclientid=my client id /clientname=my client name /clientphone=8675309 /clientemail=foo@bar.com /newinstallemail

caveats: parentheses cannot be used in the phone number string, they will be automatically stripped; but dashes can. quotes aren't necessary to encapsulate strings with spaces in them, but they won't hurt either. all parameters should run silent, but the newclientid may present file transfer progress bars briefly. again, if using /newinstallemail it should come LAST on the command line.

[vmhs]

OK, I now have a "clientID changed by commandline" install running on my laptop.

I'll take the XL (thanks to http://reddit.com/r/keto)

Good work.

edit: looks like the newinstall email may not have sent. investigating

[csc]

This is a great addition, but it leaves something to be desired. If a /PreInstall command line parameter was created it would be much more automated when formatting many computers at the same time. /PreInstall would differ in the following ways:

1. A generic installer could be used during Audit Mode (not silent)
2. The technician enters the ClientID, Name, Phone and Email of the customer.
3. Nothing happens, the appropriate registry entries are made but there is no NewInstall email or any contact AT ALL with the dCloud.
4. The finalizing of the installation (New Install) email and client creation on the dCloud is done when the application is run the first time.
5. I would then script it to run with /FinalizeInstall which does not display a GUI and is completely silent from the command line.

This would be ideal. I imagine it would be a little out-side-of-the-box but it would save a lot of time!

Thanks,
Ray

[vmhs]

At least with what is available now, I set it as an unpaying customer by default, then I can use my screenconnect client and run the command:

dSupportSuite.exe /set /newclientid=my client id /clientname=my client name /clientphone=8675309 /clientemail=foo@bar.com /newinstallemail

Once I know they want to pay. no need to log on or anything.

[csc]

Great point vmhs, but this is also assuming you have command line or terminal access on demand!