We have been working on a silent installer script to deploy 10.1.500 to 85 full and 55 MES clients.
Our silent install script successfully runs unattended but the user still sees the install dialog box during the process. Is this an issue with the exe or has something changed with the switches? Here is our install script as I received from our IT Specialist
\E10server\ERP10.1.500.0Deployment\ClientInstaller\E10Client.exe DESKTOPICO=YES SILENT=YES SILENTINSTALLS=“E10-Nov16 on E10server!NEWLINE!” TARGETDIR=c:\Epicor\ERP10.1Client SERVERLOC="\E10server\erp10.1.500.0deployment"
Thank you,
Kristine Fierce
Business Systems Analyst
Epicor generates a silent installer file for you, that code appears to be what you posted however your string above appears to be missing the /s command.
Hello,
Thank you for the snippet of code Kristine because it helped me to figure out what was wrong with my Silent Installer file and thankfully it now seems to be working.
Just wondering, does anyone know of a way to modify either the Silent Installer file, or maybe the ERP101500.config file, or possibly another file, in order to silently auto-install a Third shortcut for the Classic/MainMenu view? Or is there a way to prompt a user when they first open the ERP101500 Environment to choose either the Shell or Classic/MainMenu view? (We are using single sign-on if that makes any difference in the answer…)
Thanks for any help anyone can provide on this!
-Heather
aidacra
(Nathan your friendly neighborhood Support Engineer)
4
There are two approaches; either with a runtime switch in the target line of the shortcut or via the .sysconfig file.
To force the modern shell via the shortcut method:
C:\Epicor\ERP10\ERP10.0.xxx\ClientDeployment\Client\Epicor.exe /shell “E10DemoDB.sysconfig”
NOTE:
If you would like to force the classic shell, you would use /mainmenu instead of /shell.
To force modern shell via the .sysconfig file, search for launchtype and change it to Shell (classic is MainMenu):
If you change the .sysconfig file(s) on the server in \epicorserver\ERP10.1.500.0Deployment\Client\config to a specific launchtype, that will be what gets installed on the user workstations. If you already have a number of workstations installed, the workstation’s sysconfig files would have to be manually adjusted (or the .sysconfig file from the server would have to be used to overright what is already on the workstation)
2 Likes
aidacra
(Nathan your friendly neighborhood Support Engineer)
5
there isn’t a way through the client installer itself to force one shell type but that would be a great enhancement request.
Oooh! Thank you! I’ll have to submit that as such!
YES!! I would love it if they would either setup the client installer to also create a Third “Classic/MainMenu” shortcut. Or it would be kinda neat-o if we could place a “Prompt” value here:
<"LaunchType value=“Prompt” options=“Shell|MainMenu|Prompt” />
in the .sysconfig file and then the actual application would prompt you whether you wanted to open the Shell or MainMenu view. You could default your selection as a personalization or keep it set to prompt you every time?
aidacra
(Nathan your friendly neighborhood Support Engineer)
7
I’m not a fan of settings in shortcuts or configuration files as it makes it more challenging in the long run to maintain. Before 10.1.400, items such as SMTP server settings for File > Send., application help, and embedded education had to be set in the .sysconfig files. Whenever there is an option that has to be manually adjusted in a config file or shortcut, it will generate Support calls - and as much as I love speaking with all of you, I’m sure you would rather not contact Support if at all possible.
How about an option like a user record dropdown on the Options tab to force a particular shell type? If there is a user that really prefers one shell over the other, setting the preference once in the database does seem like an easier to maintain in the long-run option. < cough > <-- not like I am suggesting a way to submit this to Support < /cough >
I use Active Directory GPO’s to help facilitate the shortcuts I want deployed, how they are configured, and who gets what. As far as the shortcuts go you can’t beat that method of granular control.
If i need to push new configs to all the workstations that too is done through GPO or a VB script depending on the circumstance.
Epicor doesn’t “provide it all” in their install process but standard system administrator tools can handle the deployment portion of it so they probably view it as a reinventing the wheel sort of thing.