I figured out #1. I needed to stop the task agent first. Then had to chnge the Epicor ICE service's logon to the new "permanent" domain id.
I'm doing a virgin install of E10, and have successfully got it up and running. However, During the initial install and setup, I had to use my domain id for several of the install and setup tasks.
Now my domain id is set for the MANAGER account, and is used for the Epicor ICE Service task login. My dommain account requires regular password changes, so using it for Services logins is eventually going to fail.
I had the IT folks create a special domain account that wont have a password expiration. But I can't seem to change the E10 user MANAGER domain id. I get the old "Row has been modified by another user and couldn't be updated." error. Even when logged in as another user with Security Manager enabled.
So a couple of questions:
1. How to change the domain user for the MANAGER account. Obviously E10 accounts can exist w/o a domain & user id, like the "print" E10 user that is just used for the System Agent.
2. When creating the App Pools, is the user id & pw required just to make the pool? Or is it needed every time the App runs?
3. The Epicore Ice Service requires a login that is also an E10 User Account. Is that correct? Or was it just needed to create the Task Agents?
4. How do most people handle the manager account? We're part of a big parent corp - but only we use E10 - and have varying IT people that need to have MANAGER type access to E10. Just give them generic accounts to launch E10, and then have them "Switch user" to the manager account?
5. Same as #4, but for the Epicor Admin Console program. IT folks might need to stop and restart the Task Agents.
Thanks in advance,
Calvin
BTW -
* Our Endpoint method is "Windows"
* We have a two server system. One for the E10 App server, and one for the SQL server.
* Clients will run E10 client via published Web App (not the E10 Web extension) from the App Server.