{"id":500,"date":"2011-05-09T16:07:14","date_gmt":"2011-05-09T14:07:14","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=500"},"modified":"2015-12-10T10:25:12","modified_gmt":"2015-12-10T09:25:12","slug":"cannot-connect-to-the-scm-omniinetpasswd","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/05\/cannot-connect-to-the-scm-omniinetpasswd\/","title":{"rendered":"Cannot connect to the SCM – omniinetpasswd"},"content":{"rendered":"

Bei der Push Installation des Data Protector Clients auf einen Windows 2008 Server kann es zu nachfolgender Fehlermeldung kommen. Im Internet oder in der Dokumentation zu Data Protector findet sich eine Anleitung was zu tun ist, der Vollst\u00e4ndigkeit aber auch hier aufgef\u00fchrt.
\nCannot connect to the SCM (Service Control Manager) on client xxx.yyy - Access is denied.<\/code>
\nZum Auflisten des konfigurierten Benutzers das List Kommando ausf\u00fchren.
\nomniinetpasswd -list
\nNo users are configured yet.<\/code>
\nZum Hinzuf\u00fcgen eines neuen Benutzers das Add Kommando ausf\u00fchren, das Passwort muss zweimal eingegeben werden.
\nomniinetpasswd -add CCC\\s-backup
\nPlease enter password:**************
\nPlease retype password:**************<\/code>
\nBeim erneuten Auflisten wird der Benutzer angezeigt.
\nomniinetpasswd -list
\ns-backup@CCC<\/code>
\nJetzt muss noch der Benutzer als User w\u00e4hrend der Push Installation eingetragen werden.
\nomniinetpasswd -inst_srv_user CCC\\s-backup
\n<\/code>
\nZur Kontrolle wird noch einmal das list Kommando abgesetzt.
\nomniinetpasswd -list
\n* s-backup@CCC<\/p>\n

(*) Installation Server is using this user's credentials during push installation.<\/code><\/p>\n

Syntax des Kommandos:
\nomniinetpasswd -?
\nUsage synopsis:<\/p>\n

omniinetpasswd -version | -help
\nomniinetpasswd -list
\nomniinetpasswd -add {UserName@Domain | Domain\\UserName | UserName} [Password]
\nomniinetpasswd -delete {UserName@Domain | Domain\\UserName | UserName}
\nomniinetpasswd -modify {UserName@Domain | Domain\\UserName | UserName}
\nomniinetpasswd -[no_]inst_srv_user {UserName@Domain | Domain\\UserName}
\nomniinetpasswd -clean<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

Bei der Push Installation des Data Protector Clients auf einen Windows 2008 Server kann es zu nachfolgender Fehlermeldung kommen. Im Internet oder in der Dokumentation zu Data Protector findet sich eine Anleitung was zu tun ist, der Vollst\u00e4ndigkeit aber auch hier aufgef\u00fchrt. Cannot connect to the SCM (Service Control Manager) on client xxx.yyy – Access […]<\/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":[11],"tags":[106,104,105],"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-84","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":2914,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/03\/zdb-3par-vss-file-system-backup\/","url_meta":{"origin":500,"position":0},"title":"ZDB 3Par – VSS File System Backup","date":"7. M\u00e4rz 2016","format":false,"excerpt":"{:en} Setting up a File System backup using ZDB on 3Par is fairly simple, however there are a couple of challenges that you should be aware of, but we will address those later. ZDB backups are made up of basically three machines: Your application server where the file system resides\u2026","rel":"","context":"In "Common"","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":500,"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 "HowTo"","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":3879,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/03\/data-protector-10-updated-release-a-10-03-build-181\/","url_meta":{"origin":500,"position":2},"title":"Data Protector 10 \u2013 Updated Release A.10.03 (Build 181)","date":"30. M\u00e4rz 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.03 (Build 181)\u00a0has been released on March 30, 2018. While you might expect a Patch Bundle, Micro Focus decided to simplify the upgrade and installation by delivering a full build. Data Protector 10.03 does not require any previous version to install the latest version of Data Protector in a\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4315,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/09\/data-protector-10-updated-release-a-10-10-build-xxx\/","url_meta":{"origin":500,"position":3},"title":"Data Protector 10 \u2013 Updated Release A.10.10 (Build 134)","date":"18. September 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.10 (Build 134)\u00a0has been released on September 17, 2018. The new version is another full install to simplify the upgrade and installation process.This will be the default for all future Data Protector versions. Data Protector 10.10 does not require any previous version to install the latest version of Data\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":935,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/05\/dp-7-0-omnirc-variable\/","url_meta":{"origin":500,"position":4},"title":"DP 7.0 – omnirc – connection abort","date":"4. Mai 2012","format":false,"excerpt":"{:de}Mit Data Protector 7.0 kann es beim Backup zu untenstehender Fehlermeldung kommen. Der Fehler wurde in einem Case best\u00e4tigt. Zur L\u00f6sung kann in der omnirc die Variable OB2INETTIMEOUT=10 auf den betroffenen Clients aktiviert werden. Danke an Dennis Lorentsen der die Information bereitgestellt hat. Error: [Major] From: BSM@cellmanager.local \u201ctest_1\u2033 Time: 01-05-2012\u2026","rel":"","context":"In "Bugs"","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":500,"position":5},"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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/500"}],"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=500"}],"version-history":[{"count":10,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/500\/revisions"}],"predecessor-version":[{"id":2737,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/500\/revisions\/2737"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=500"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=500"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}