The first step in managing a Windows server in Address Manager is to create a DDW
server.
To create a DDW server you must install DDW software on a stand-alone Windows
server. The server should not be a domain controller and should not be running DNS
or DHCP services.
Note: Windows Server 2012 R2Microsoft .NET Framework 3.5
must be installed and enabled as a Windows feature on servers running
Windows Server 2012 R2 prior to installing BlueCat Address Manager for
Windows Server (DDW) v8.1.0 or greater.
Installing DDW software
To install DDW software on the Windows server, you must use a Windows user account
that has sufficient permissions to install and start Windows services, and to access
the system through the Event Viewer.
Note: Customers upgrading from a patched version
of DDW software may experience an upgrade failure when upgrading to BlueCat
Address Manager for Windows Server (DDW) v8.2.0. For a workaround to this issue,
refer to Knowledge Base article
5977 on BlueCat Customer Care.
DDW User Account
Installing the DDW software on a Windows server creates and starts a Windows service
called the Proteus DNS and DHCP Manager Service (Proteus DDW service).
This service must run as a user account. If you create a user account for the
service, you must grant the account the Log on as a service user right to the
local machine, or you can use the Local System account. The user account can be a
Domain or local user account, depending on whether the server is a member of a
domain.
You should configure the following settings on the selected Windows user account:
- Clear User must change password at next login.
- Select User cannot change password , and Password never
expires.
- Clear Account is disabled.
Once you have configured these settings you can install the DDW server
software.
Note: For more details on the DDW Server Authentication Credentials
required to manage Windows DNS and DHCP servers, refer to Knowledge Base article
3834 on BlueCat Customer
Care.
To install the DDW server software: