{"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":3238,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2017\/01\/data-protector-systemd-rhel-7\/","url_meta":{"origin":1662,"position":0},"title":"Data Protector with &#8222;systemd&#8220; on RHEL 7","date":"9. Januar 2017","format":false,"excerpt":"{:en} Update 2017\/01\/09: After some discussions with colleagues... you need to know, that for Data Protector clients \"systemd\" is used and only on Cell Manager the legacy mode with \"xinetd\" is leveraged. Even with the legacy mode there is no need to change to \"systemd\", as \"xinetd\" is supported on\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"rhel72","src":"https:\/\/i2.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/12\/rhel72.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":474,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/04\/data-protector-6-2-installation\/","url_meta":{"origin":1662,"position":1},"title":"Data Protector 6.2 Installation","date":"13. April 2011","format":false,"excerpt":"{:en}For all already waiting for... the new version of HP Data Protector (6.2) will be installed as follows on a Windows 2008 box... Screens were manipulated to show all available options. UAC may appear prior installation, depending on the configured settings Welcome Screen When pressing Advanced you can define settings\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"DP62_Install","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2011\/04\/DP62_01.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":500,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/05\/cannot-connect-to-the-scm-omniinetpasswd\/","url_meta":{"origin":1662,"position":2},"title":"Cannot connect to the SCM &#8211; omniinetpasswd","date":"9. Mai 2011","format":false,"excerpt":"{:en}During a push installation of the Data Protector Client to a Windows 2008 box, you may receive following error. In the internet or in the documentation of Data Protector you'll find the needed steps to address this error message. To be complete... it is also posted here. Cannot connect to\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":313,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/01\/eadr-mit-windows-2008-r2\/","url_meta":{"origin":1662,"position":3},"title":"EADR with Windows 2008 R2","date":"21. Januar 2011","format":false,"excerpt":"{:de}In einen fr\u00fcheren Artikel hatte ich \u00fcber die Wiederherstellung eines Windows 2003 Servers mit Data Protector berichtet. Nachdem Windows 2008 auch immer mehr in Rechenzentren betrieben wird zeige ich nachfolgend die Wiederherstellung eines Windows 2008 R2 Servers mit Data Protector und der Enhanced Automated Disaster Recovery Funktion. Vorbereitung: In der\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4083,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/05\/sysbackup-oracle-12c\/","url_meta":{"origin":1662,"position":4},"title":"SYSBACKUP auf Oracle 12c","date":"28. Mai 2018","format":false,"excerpt":"{:en}Starting with Oracle 12c three new administrative roles and users have been introduced to conform the principle of access to the least privilege. The users and roles named SYSBACKUP, SYSDG and SYSKM will be created when the database is created with their account in expired and locked status.\u00a0SYSBACKUP is used\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2363,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/08\/data-protector-patch-bundle-9-04-features\/","url_meta":{"origin":1662,"position":5},"title":"Data Protector 9 &#8211; Patch Bundle 9.04 (Build 104)","date":"5. August 2015","format":false,"excerpt":"{:en}On 2015\/08\/06 HP released patch bundle 9.04 for Linux, HP-UX and Windows, it includes 494 changes for Windows and 439 changes for Linux. With the new bundle some new and important features were introduced (complete list - see patch description): Power-On a VMware virtual machine from 3PAR snapshot or from\u2026","rel":"","context":"In &quot;DP A.09.00&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}]}}