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
    175
  • Views views
    426
  • Users 0 members are here
  • +1 person also asked this people also asked this
  • 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

Run windows OO flow across domain.

prasanna54

Dear Experts,

We have Operation Orchestration Central, RAS and studio in one domain1 and we have to run Windows flows with PowerShell script in domain2, but we are not able to connect Windows Server through WinRM.

WinRM port is blocked in Domain2. 

Is there any solution available to run flows cross domain or can we install any OO module in Domain 2 and connect it to Domain1 for running flows.

Please suggest.

Thanks

Prasanna

  • Verified Answer

    +1

    hiho,

    you can install a RAS in Domain 2 and register it in Central in Domain 1. Assign a different worker group to RAS in Domain 2.

    Now - inside your flow - add a detection where you need to do your operation (FQDN etc) and assign the worker group to the subflow or operation. You also may take care of different credentials for each domain.

    Regards Rene

  • 0 in reply to 

    Thanks Greetz for prompt reply, we will install RAS in Domain 2 and confirm.

    Regards

    Prasanna

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.