{"id":1662,"date":"2016-01-30T16:00:51","date_gmt":"2016-01-30T15:00:51","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1662"},"modified":"2016-01-30T17:07:35","modified_gmt":"2016-01-30T16:07:35","slug":"data-protector-8-0-windows-change-user-account-dp-services","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/01\/data-protector-8-0-windows-change-user-account-dp-services\/","title":{"rendered":"Data Protector 8.0 Windows &#8211; change user account for DP services"},"content":{"rendered":"<p>In fr\u00fcheren Versionen vom Data Protector war es recht einfach den User Account f\u00fcr die Data Protector Dienste zu \u00e4ndern. Mit Data Protector 8.0 und der neuen Datenbank sind mehrere Schritte notwendig um den Benutzer zu \u00e4ndern. Die Schritte wurden in einer Testumgebung verifiziert.<\/p>\n<ul>\n<li>Data Protector Dienste mit <code>omnisv -stop<\/code> beenden.<\/li>\n<li>In den lokalen Sicherheitsrichtlinien den neuen Benutzer in &#8222;Annehmen der Clientidentit\u00e4t nach Authentifizierung&#8220; hinzuf\u00fcgen.<\/li>\n<li>In den lokalen Sicherheitsrichtlinien den neuen Benutzer in &#8222;Ersetzen eines Tokens auf Prozessebene&#8220; hinzuf\u00fcgen.<\/li>\n<li>In den Data Protector Diensten den neuen Benutzer eintragen (Application Server, CRS, IDB, IDB connection pool).<\/li>\n<li>\u00c4ndern des Benutzers in der Datei <code>userlist<\/code> vom Data Protector (zum Beispiel: <code>C:\\ProgramData\\OmniBack\\Config\\Server\\users\\userlist<\/code>).<\/li>\n<li>\u00c4ndern des Benutzers in der Datei <code>pg_ident.conf<\/code> (zum Beispiel: <code>C:\\ProgramData\\OmniBack\\Server\\db80\\pg<\/code>).<\/li>\n<li>\u00c4ndern des Benutzers in der Datei <code>idb.config<\/code> (zum Beispiel: <code>C:\\ProgramData\\OmniBack\\Config\\Server\\idb<\/code>).<\/li>\n<li>Explizites Hinzuf\u00fcgen administrativer Rechte f\u00fcr den neuen Benutzer auf den OmniBack Ordner (zum Beispiel: <code>C:\\ProgramData\\OmniBack<\/code> und <code>C:\\Program Files\\OmniBack<\/code>).<\/li>\n<li>Data Protector Dienste mit <code>omnisv -start<\/code> starten.<\/li>\n<\/ul>\n<p><b>Update 20.01.2016:<\/b> Falls nach diesen \u00c4nderungen der hpdp-idb Dienst nicht starten sollte, so m\u00fcssen noch Berechtigungen ge\u00e4ndert werden. Der neue AD Benutzer muss auf den Folder db80 berechtigt werden. Danke an Jim Turner f\u00fcr diesen Hinweis.<br \/><img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/01\/ADuser.png\" alt=\"ADUSER\"\/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In fr\u00fcheren Versionen vom Data Protector war es recht einfach den User Account f\u00fcr die Data Protector Dienste zu \u00e4ndern. Mit Data Protector 8.0 und der neuen Datenbank sind mehrere Schritte notwendig um den Benutzer zu \u00e4ndern. Die Schritte wurden in einer Testumgebung verifiziert. Data Protector Dienste mit omnisv -stop beenden. In den lokalen Sicherheitsrichtlinien [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[1],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"de","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-qO","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1892,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/migrate-dp-8-xx-dp-8-xx-hardware-ms-windows-operating-system\/","url_meta":{"origin":1662,"position":0},"title":"Migrate DP 8.XX to DP 8.XX using new hardware or different MS Windows operating system","date":"26. M\u00e4rz 2014","format":false,"excerpt":"{:en}The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3262,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/12\/migrate-dp-9-0x-dp-9-0x-hardware-microsoft-windows\/","url_meta":{"origin":1662,"position":1},"title":"Migrate DP 9.0X to DP 9.0X using new hardware and Microsoft Windows","date":"8. Dezember 2016","format":false,"excerpt":"{:en}I already wrote several articles on how to migrate the internal database to a new hardware, new Data Protector version, or new operating system (see link). With the introduction of PostgreSQL as internal database for Data Protector and compared to previous versions (DP 6 and DP 7), some more steps\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"writedb","src":"https:\/\/i1.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/12\/writedb.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3086,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/06\/omniofflr-offline-restore-data-protector-internal-database\/","url_meta":{"origin":1662,"position":2},"title":"OMNIOFFLR &#8211; Offline Restore Data Protector Internal Database","date":"1. Juni 2016","format":false,"excerpt":"{:en} In one of my previous articles I briefy informed about EADR for Data Protector 9.06 on Windows 2012 R2 - please refer to https:\/\/www.data-protector.org\/wordpress\/2016\/05\/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06\/. However, if you don't need EADR as a complete recovery option and the preparation for disaster recovery for the IDB is required only, then you\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/06\/offlr1.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1160,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/09\/recover-cell-server-reviewed\/","url_meta":{"origin":1662,"position":3},"title":"Recover Cell Server &#8211; Reviewed","date":"19. September 2012","format":false,"excerpt":"{:en}In previous posts it is documented how to recover a server using Enhanced Automated Disaster Recovery Option. Tis applies to the Cell Server too, as this server might be the most important server in a case of a disaster. For the cell server there are several options available to do\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1628,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/10\/australia-www-ifost-org-au\/","url_meta":{"origin":1662,"position":4},"title":"Greetings from Australia &#8211; www.ifost.org.au","date":"14. Oktober 2013","format":false,"excerpt":"{:en}I recently had a email conversation with Greg Baker, a Data Protector guy from Australia. Greg shares his DP knowledge and offers trainings. Im proud to post some links which might be important and invaluable for you too. Links: http:\/\/www.ifost.org.au\/dataprotector\/dp8db-hack.pdf - some information to solve DP 8.0 IDB corruption http:\/\/dataprotector.eventbrite.com.au\/\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4340,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/09\/appserver-issues-when-upgrading-to-10-x\/","url_meta":{"origin":1662,"position":5},"title":"AppServer Probleme beim Upgrade auf 10.x beheben","date":"26. September 2018","format":false,"excerpt":"{:en}The AppServer has become an integral part of Data Protector. When it fails neither user authentication, scheduling or reporting will work. A critical issue has been identified that may cause upgrades to fail and\/or run-time issues caused by invalid data stored in the jce_service_description and jce_service_property tables in the Data\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1662"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/comments?post=1662"}],"version-history":[{"count":4,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1662\/revisions"}],"predecessor-version":[{"id":2890,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1662\/revisions\/2890"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1662"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1662"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1662"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}