Theopenem server deployment

jedo19

We have a strict password policy in our organisation, so when I try to run an installer, it doesn't complete because the password is too easy. Is there a way I can force it to move forward (pass stricter password ??) ?

theopenem_admin

It stops the installer? I thought you could ignore the error and continue?

jedo19

No it stops and reverts back, so I can't continue. We enforce 14-character passwords + complexity, so it just reverts and removes the package, Is there a workaround for that?

Greg_E

Which installer, the main TOEMS server installer or the TOEC installer? Asking because I might have a similar issue and want to know where to look for problems when I move from lab to production. My lab has no password policies right now but production requires 8 and must have capital+lowercase and number or symbol

jedo19

Greg_E It is a server install, I don't even get past that install, as I have a domain-joined computer and GPO policies already apply, and I don't want to change the server where I will be running Toems server with a downgraded policy. Hopefully, the team can provide some insight on how to enforce stricter passwords.

Greg_E

jedo19

I'm guessing it is erroring when it sees the toemsadmin account and one of your policies is certainly that password can not have username within. Plus the 14 character requirement mentioned above.

Could you apply a local policy to just that server to change the rule to something more simple? I know, security, but it might be a way around the issue. Not going to say that I fully remember all the parts of the password GPO, might require moving that server to another container, GPO overrides local. You'd need to apply a less secure policy to that new container for things to work.

Maybe in the next version the installer could be changed to allow user input for the default account, or maybe not even have a default account and make it all user input. I have no idea how much work this would take.