So I’ve been seeing more and more things with planned release version of 10.2. I’m waiting on a fair amount of simple fixes that have this for the release version. (which for what it’s worth is frustrating that we have have to make the big jump from 10.1 to 10.2 to fix bugs, I feel like simple bug fixes should be in smaller impact patches, just my 2 cents)
Anyways, does anyone know what the planned release for 10.2 is? The planned release versions don’t help us in any type of planning sense if we don’t know when the versions are scheduled to come out. I thought I heard somewhere that it was in October?
Is there a posted release schedule somewhere that I just can’t find? (highly possible, I seem to have a hard time finding anything on epicors website(s))
I have about 3 SCRs that have a planned fix for 10.2. I’m starting to think that the support team puts that as a catch-all when they can’t figure out how to fix the issue. We’re on 10.1.400 but none of the changes to .500 or .600 have applied to us. I figure if I’m going to do a major upgrade, I might as well wait for them to actually fix our issues in 10.2, but nobody seems to know when that will be.
aidacra
(Nathan your friendly neighborhood Support Engineer)
3
10.2.100 Multi-tenant SaaS Cloud is planned for the week before the US Thanksgiving holiday, with on-premise GA occurring shortly after our Cloud GA.
Like Nathan said. Also, the Dedicated Tenant first wave will be that weekend too. Those companies who defer to the second half will convert 10.2 in the middle of February.
I’m one of them…. Having issues with authentication and binding methods. Raised a support case, it was quickly closed as the support agent admitted they didn’t really know the answer.
We always use Windows SSO, which works perfect in 10.1.400.31.
Trying to do the same in 10.2, running /HH or /MES or /CLASSIC all work. Epicor opens without any prompt for username or password if the user is setup with domain and domainID in user account setup.
The 10.2 shell won’t open without prompting for username/password. Using my windows AD credentials does work, but it’s an extra step which I assume isn’t supposed to be there. I really struggle to get my head around the various different authentication methods. The only way I got it to work in its current state was to go into IIS Manager and manually turn on Windows Auth in the ERP102100 website.
Bart, there is also a circular dependency in the help files relating to Data Discovery IMHO. It asks you to manually update sysconfig.json in the root of the EDD website, but the EDD website isn’t created by the tooling until step 7 or later when you press deploy…? Am I missing something?
Data Discovery
Epicor Data Discovery (EDD) is a Business Intelligence solution intended to provide an extremely easy to use sense-making, data exploration, data visualization experience. EDD is a major component of the overall Epicor Data Platform which encompasses a broad set of capabilities for managing, accessing, sharing, cleansing, visualizing, and extracting insights from data created by or related to Epicor created data.
Use these steps to install Epicor Data Discovery.
Prior to installing the Data Discovery extension, configure Token Authentication. First, you need to set up Data Discovery to use the Epicor ERP account:
* In Epicor Administration Console, in the tree view, expand your Epicor ERP server node.
* In the Actions pane, click Configure Token Authentication.
* In the Token Authentication Settings dialog box, select the Enable Token Authentication checkbox
* In the Lifetime (sec): field, set the token lifetime greater than 0, and click Generate to create the Sign Key.
Update the sysconfig.json file with the correct Token Server:
* In the root of the EDD website, locate the sysconfig.json file.
* In the ep.token nodes set the restUri parameter to point to the TokenResources.svc on the correct Erp server.
Update the web.config file with the correct Authentication Server:
* In the root of the EDD website, navigate to the REST folder and locate the web.config file.
* In the appSettings node, set the EnableAuthorization parameter to true and set AuthServer to point to the correct Ice/Erp server.
c.
d.
e.
f.
g.
h.
i.
j.
k.
When complete, recycle IIS.
Verify the following fields:
* In the Admin Console, right-click on your Application Server and select Application Server Configuration. Select the Application Server > Application Server Setup tab.
* Verify that the Https Endpoint Binding field is set to HttpBinaryWindowsChannel.
* In the Server Information section, verify that the Enable RESTful Services check box is selected.
* Click OK.
Select the Epicor Data Discover tab.
Use this sheet to install a new Data Discovery extension or select an existing extension. You can also update the current Data Discovery extension.
o To install a new Data Discovery extension, click the New button. Enter the Deployment Name for this Data Discovery extension. Be sure to enter a name that helps you identify each Data Discovery extension available on your system. The fields on the Data Discovery sheet activate for data entry.
* To update the Data Discovery extension, enter the new values in the fields on this sheet.
Get the ticket open on the second. A lot of activity going on in setup - questions on changes.
As to the first. Windows Auth in IIS should NOT be set for the shell, etc. The core app server is not a vanilla html site serving up pages that requires IIS to protect it. That’s what that IIS setting does for you. The E10 biz logic is exposed via WCF to the rich client and WCF handles Windows Auth itself with IIS being ‘anonymous’. You will get a screen pop if you turn on windows auth in IIS for the vanilla app server.
I hope that helps. If you have ANY questions along these lines, be sure to ask as a new question we can have @josecgomez save off. There is a lot of information in the online help - search for bindings. Anything lacking (i am sure there is something you can help point out) I can have appended.
@markdamen/@Bart_Elia do you have a solution for the password/ username pop-up. we do use SSO also, and do have the same issue. probably it can be solved by tuning the settings, but I don’t know which one yet,
you can start 10.2 in /active /classic /shell mode…
