Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    4
  • Views views
    679
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot start ZENworks Loader due to error 1069: the service did not start due to logon failure

AFIQNASRUDDIN19

Hi everyone. Just trying my luck asking here

So our client created a log on as a service group policy and applied it to primary server without adding the .\__z account. So I was not able to start ZENworks loader service due to error 1069: the service did not start due to logon failure. I then tried changing ZENworks loader service logon as local system account. The result is I am able to start ZENworks loader service. But, when I tried changing it back to .\__z account, I still get the same error 1069: the service did not start due to logon failure even after adding .\__z to log on as a service group policy.

If my understanding is correct, the .\__z account should be the default administrator account created during initial setup right? So the password should be the same as default administrator login right? But I am still not able to start the service unless I change the logon as to local system account or any account with admin right.

Appreciate any insight for this matter. Thank you for considering my question

Parents

  • Verified Answer

    0  

    The password for the "__z account" is generated randomly upon install...It is not possible to know it. (Unless you have some tool to retrieve Windows Passwords....)

    However, the password can be changed just like any other Windows Account.  Simply update the PWD info for all of the services that use it.  It is not used outside of the settings in the Windows Services.

    There is also nothing special about this account other than it is a local administrator account.  You can also just set the service to run as a different local administrative user.  Even a Domain Account should work, assuming it has local admin rights.  I know folks who do that because their Domain GPOs block adding local users to the local administrators group.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to   

    Thank you the insight

    It works!

Reply Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.