We have a problem when after upgrading to 10.2.500.2 the client install is opening in Shell mode but we need it to be Active Homepage.
I know there is a setting in the sysconfig file that can be updated on the deployment server (and which we have) however this does not get applied to the user since this setting is in the “userSettings” section of the file which I understand does not get overwritten.
How can we force all existing Epicor clients to use the Active Homepage login style?
Hi Guys. Any suggestions on this?
What kind of control do you have over the users PC’s? You can change their shortcuts to have the /active flag at the end, and then it will start with active homepage regardless of their settings.
Thanks Evan.
I guess they do have some control over the computers, at least with AD. So yes they could probably update the icons if they all in the same place and the user has not moved or copied it.
I was hoping there is a way to affect the sysconfig file. I reckon they could probably push out the updated config file via AD but that will obviously overwrite any user settings saved in their local sysconfig file.
I bet you could push out a script that only changed the necessary lines in the config file.
that most certainly can be done, or just update the one on the server and let auto update take care of it. If the shortcuts are an issue, GPO can take care of that.
Hi Geoff,
If you look at the shortcuts target, you might find a /shell parameter
/Active will use the Active Homepage and /Classic will load the classic style I beleive.
No the current shortcuts definitely do not have any switches for login type.
What happened was that the old sysconfig on the deployment folder had the login type set to “Shell” but on version 10.2.300.8 this did not seem to be an issue since the users were logging in and getting Active homepage. It is as though the client ignored that setting on that version.
Then when we upgraded to 10.2.500.2 the client used this value and logs into Shell. Even though I updated the sysconfig on the deployment server to Active the client sysconfig still has Shell in it. This does not get overwritten during the upgrade because it is in the userSettings section of the file. New installs are no problem.
I think the best way is to push out the updated sysconfig via GPO or something and just overwrite the client config file.
Thanks for all the suggestions though.
You could also execute a PowerShell script on login. I haven’t tested this one but did something similar to update the help URL successfully, so it should give you an idea. It saves the original and updates only one thing so you won’t change any other options that may have been previously set.
# Load Epicor Config File
$cfg = New-Object System.Xml.XmlDocument
$cfgFile = "C:\Epicor\ERPDT\Client\Config\SaaS.sysconfig"
$cfg.Load($cfgFile)
# Save Original Config
$strDT = Get-Date -Format "yyyyMMddHHmmss"
$cfg.Save($cfgFile + "_" + $strDT)
# Find Launch Type Setting
$LT = $cfg.SelectSingleNode("//LaunchType")
# Update Launch Type
$LT.value = "Shell"
# Save
$cfg.Save($cfgFile)
Thanks Mark!
Will give that a shot as well.
Hey Mark you just gave me an idea! Now I know how I can automate the HH profiles to generate .sysconfig’s for themselves 
doh!