Thread: How to supervise Host authentication on windows server.

I'm organizing V5.2 CCS at the top of the Windows 2003 standard. Due to the configuration of our products in the Windows environment I have clients in a safe domain, which you need to connect to the Member State in another domain, but you have not set any "trust" ", one of the two, therefore you cannot use the operating system authentication. I have read the "Central command and the network operating system domains " on page 46 of the admin guide V5.2, however, is not a person it isn 't Windows such understandable to me.

There is some contradiction in terms for me. MH (Managed hosting) at the central command, the storage (CCS) version 5.2, may be considered by the client, this will be talked to the Management Server domain (MS), a single server to control the HAL (Hardware Abstraction Layer (HAL)-). Let me build a few assumptions and and improve or add to a thread when needed. First is demanding must contain MH connected Member State as the customer accounts with domains that are not visible on the Member States, and therefore is not a network path between nodes and, therefore, the configuration process to register and not be filled in with the MH installed but not connected.

Solution to this problem is creating a path between the domains which allow bi-directional communication in every 1556 port and execute scripts physically configuration of HAL, or uninstall, to produce the link and after that re-install. The authentication process between the MS and the members included in the installation and verified before they can proceed with the installation – if you are not available to complete the installation, unless you are finished manually.

I recommend you open a support case and includes a Symantec representative within list performance of step. for support, for its part, would necessitate a similar access route is open above the node selected for administrative installation client authentication, access to the Internet to download additional software, if not available on the intranet of a previous download and access on the way to console Ms. There will be a faith built, however the program approval does not rest on the domain level. The route is typically based on the firewall.

Approve report data exposed 31.53 from MH again en route to the master under apply as you configure VERITAS security to support CCS. If you cannot secure port 1556 routable interface between nodes using the program to generate a random password using credentials that are used within the host country cannot register the application to the Member States and successful installation.