K2 blackpearl Installation and Configuration Guide > Planning Guide > Additional Planning Considerations > Domain Configuration | Send feedback |
Many variables in a network can affect how K2 blackpearl, IIS, Active Directory, Visual Studio, Exchange, Office (including Outlook), and SharePoint are installed and function. Proxy servers, multiple domain controllers, firewalls, and network policies may also affect the manner in which these applications or servers function within their environment.
Incorrect or incomplete DNS settings often cause one or more features of a K2 Server to fail, such as user authentication or Active Directory lookup. It is very important that DNS is setup and functioning correctly and reliably. DNS issues usually result in the K2 Server being unable to resolve users and/or user e-mail addresses against Active Directory.
Delegation (full or constrained): Delegation is required on Windows Servers to impersonate other servers/users/services.
K2 can be installed in single or multiple domain configurations. A domain in a tree configuration may have another tree domain along side with perhaps the added complexity of an external domain. K2 will support these configurations when Kerberos is configured correctly.
The following domain group policy and/or local security settings configurations are required:
System | Item to Configure | Description |
---|---|---|
IIS Server | IIS_WPG Group |
|
K2 Server | Login Account |
|
Client Machines | Internet Access |
|
While infrastructure changes are required by K2, each environment is different and has its peculiarities which must be taken into account. Modifying the infrastructure could have unforeseen results if the changes are not appropriately understood or managed. Given the broad spectrum of underlying infrastructure utilized, it is recommended that a panel or committee with appropriate skill in each area concerned be assembled to outline the underlying infrastructure changes and gauge the impact of the required changes. |