We see a number of customer support issues related to the EminentWare service, many indicating that the EminentWare service fails to start. As you might have noticed, the EminentWare installation creates an account that the service runs under. It is named something of the form: 'ewdgssvc-XXXXX'. Modifying this account (either directly or indirectly via Group Policy) can leave the service in an un-startable state.
Here are a few troubleshooting items that might help get the service started. They all assume you are on the machine where you've installed the EminentWare server:
1) Ensure that the service account has the 'Logon As Service' user right. Many organizations disable this right for security reasons. The ewdgssvc-XXXXX account is truly a service account and thus needs to have this user right enabled in order for the EminentWare service to function.
2) Ensure that the password for this account hasn't changed. The password for this account is a randomly generated string of at least 12 characters, and is encrypted and stored using Microsoft's Data Protection API services on the EminentWare server. On occasion, users will change the password for this account, which causes the account logon to fail.
3) Two Local Security Policies must be properly configured. On the EminentWare server machine, use 'secpol.msc' to launch the Local Security Policy Snapin, and browse to 'Local Policies > Security Options.'
- Verify that 'Network access: Do not allow storage for credentials or .NET Passports for network authentication' is set to 'Disabled'.
- Verify that 'Network access: Sharing and security model for local accounts' is set to 'Classic - local users authenticate as themselves'.