Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Silent Install

Not available for Steam versions

Running any app installer via a command line with /s switch will silently install.

Adding /noreboot will not reboot the machine post-install.

After any install (manual or silent) is done, the Stardock Activation window is shown as well as the config UI or the app:

If your desire it to have an end-to-end silent install \ activation, in your script after the silent install, you would include the following before any silent activation.

taskkill /f /im Fences.exe
taskkill /f /im SdDisplay.exe

If you are installing over an existing install, it is important to reboot at the earliest possible convenience.

Silent Activation 

Not available for Steam versions

Most of Stardock's current applications can be activated via the command prompt. The command line option will activate the application without exposing the application or activation UI.

If you are deploying a Stardock product from an image, it must be done so unactivated. Activation must happen on the destination PC.

Command line example

Start11
"C:\Program Files (x86)\Stardock\Start11"\SASUpgrade.exe -prodId=2663 -prodName="Start11" -company="Stardock" -ver="1.0" -email="USER@USER.COM" serial="PRODUCTKEYGOESHERE"

Variables

prodId
The internal Stardock product ID is unique to every product line

prodName
The Stardock issued product name. This must be accurate. (Example: Fences4 <-note no space in name and version)

company
For Stardock products, this will always be “Stardock”. Do not enter your company name or the activation will fail.

version
The version being installed.

serial
The serial \ product key for the registration.

email
Email address of the account the current registration is activated under or the email account it is to be attached to if activating for the 1st time

If this is the 1st time a registration is being activated, take great care in what email address is chosen as it will be tied to that email address henceforth. For enterprise deployments, it is HIGHLY recommended that a generic (e.g. stardockLicensing@YourDomain.com) is used to avoid proper name email address credentials and their inherent problems.

Stardock Product IDs

‘ProdID’ and ‘ProdName’ table for command line activation

Product

ProdName

ProdID

Cursor FX 4

CursorFX

2651

Curtains

Curtains

2654

DeskScapes 10

DeskScapes

2646

DeskScapes 8

DeskScapes

2268

Fences 2

Fences2

2240

Fences 3

Fences3

2628

Fences 4

Fences4

2664

Fences 5

Fences5

2675

Groupy

Groupy

2644

Groupy 2

Groupy2

2670

Launch 8

Launch8

2276

Modern Mix

ModernMix

2271

Multiplicity 3 KM/KVM/Pro

Multiplicity

2283

Multiplicity 4

Multiplicity

2684

ObjectDock

ObjectDock

1169

ObjectDock 3

ObjectDock

2682

Sound Packager 10

SoundPackager

2653

Space Monger

SpaceMonger

2625

Start 10

Start10

2623

Start 11 v1

Start11

2663

Start11 v2

Start11

2674

Start 8

Start8

2267

Tiles

Tiles

1942

WindowBlinds 11

WindowBlinds

2667

WindowsBlinds 10

WindowBlinds

2630

WindowBlinds 8

WindowBlinds

2272

WindowFX

WindowFX

2245

Activaiton Verification

If a command line activation was successful, a product-specific license.sig file will be created in the app-appropriate folder in\ProgramData\Stardock. For example, a successful Start11 activation will have a license.sig file created in:

\ProgramData\Stardock\Start11

Example Video

The example video below is for Fences but can be used for any of the apps above:

https://cdn.stardock.us/support/uploads/sdComPromptAct.mp4

  • No labels