• Prompts Local Administrator password, Azure AD Global Administrator user, Azure AD Domain name and Password
• Starts downloading ASDK (Takes about a minute)
• Extracts ASDK (Takes about half an hour)
• Mounts CloudBuilder.vhdx
• Copy required files and folders to C:\ from CloudBuilder.vhdx (Takes about 5 minutes)
• Dismounts CloudBuilder.vhdx
• Registers a scheduled job to watch setup progress to fix following configurations
  • Creates Internal Virtual switch (as a workaround since Azure VM does not allow MAC spoofing)
  • Sets predefined IP address to new NIC connected to Virtual Switch
  • Connects BGPNAT01 VM's NAT adapter to new virtual switch
  • Either Enables Internet Connection Sharing (ICS) or configures NAT** to allow Azure Stack Fabric VMs to access Internet. This option is configurable with $ICS variable (Default installation uses ICS)
  • Unregister the scheduled job once it is done.
• Runs InstallAzureStackPOC.ps1 with predefined parameters.

• Creates an Azure VM with 256GB OS disk and 4 x 128GB data disks with 64GB additional disk for downloads all as Managed disk and on Azure Premium Storage.
• Post script using custom script extension to configure some setup prerequisites.
  • Install Hyper-v Failover Cluster, IIS and tools, and AD powershell and tools.
  • Installs latest Nuget Package provider.
  • Some CredSSP settings
  • Renames local admin back to Administrator
  • Restart computer

 

In order to accomplish this task, understanding how IPAM work is the key fact and it requires serials of steps to be completed. These steps may also apply for IPAM on Windows Server 2012 but it is not tested.

Requirements

• IPAM can manage Domain controllers, NPS, DNS, and DHCP servers running Windows Server® 2008 or later.
• GPOs are used for managing clients (it is recommended method however manual provisioning is also possible)
• "DHCP Failover Cluster" role is in place
• "File Server" and "File Server Resource Manager" sub roles installed on "DHCP Failover Cluster"

Steps of the deployment

Following 4 steps are required to start managing your "DHCP Failover Cluster" in IPAM.

• Configure VCO (Virtual Computer Object) attributes.
• Apply IPAM GPO for DHCP to all members of the cluster.
• Give IPAMUG read rights to shared DHCPAudit log folder.
• Make DHCP Cluster as a managed DHCP node in IPAM.

Configure VCO (Virtual Computer Object) attributes

When you try to add a computer from IPAM console, IPAM runs several checks on the computer object in AD to make sure that the version is supported version.

Have you ever tried to add your "DHCP Failover Cluster" workload's VCO to IPAM manually? Then you must be familiar with the following error message!

This message always pops up irrelevantly from OS the version. Yes, it's weird error message but can be tricked very easily by just changing the computer object attributes.

Open adsiedit.msc and find the VCO right click and hit properties. In the properties of the VCO find operatingSystem and operatingSystemVersion attributes. In my case DHCP-Cluster below is one of my cluster node.

In adsiedit.msc find the one of the cluster node and copy/take note values of operatingSystem and operatingSystemVersion. In my case DHCPCLS1 below is one of my cluster node and the operatingSystem attribute is set to "Windows Server 2012 R2 Datacenter" and operatingSystemVersion is set to "6.3 (9600)". 

Set values and make sure that you use appropriate values copied on previously.

Apply IPAM GPO for DHCP to all members of the cluster

"DHCP Failover Cluster" is not a typical and supported IPAM deployment, in this scenario the target is to manage the Virtual DHCP role in IPAM. IPAM uses GPOs to set the required configuration on managed computers. IPAM adds computer's account to the security filtering of the relevant GPO whenever you set machine on IPAM console as managed. Since the only computer will be added from added in IPAM console is VCO, cluster nodes must be accompanied to VCO in order to nodes to receive settings in GPO.

Open Group Policy Management console, select IPAM GPO for DHCP. Go to security filtering and all of the cluster member nodes.

Give IPAMUG read rights to shared DHCPAudit log folder

Ensure that IPAM's computer account can access to daily DHCP logs shared on DHCP cluster role. To share a folder from Failover cluster manager make sure that File Server" and "File Server Resource Manager" sub roles installed.

Open Failover Cluster Manager console, go to Roles, right click on DHCP cluster role object and select Add File Share

Make DHCP Cluster as a managed DHCP node in IPAM

Since all prerequisites have been configured. Now it's time to start managing your "DHCP Failover Cluster" with IPAM. Open IPAM management console go to Server Inventory and add your "DHCP Failover Cluster" (VCO Name). Set Manageability Status to Managed and select DHCP server from Server type.

Make sure the GPO applied successfully before refreshing or start managing your new "DHCP Failover Cluster" on IPAM Console.

Conclusion

IPAM is promising gadget with of course some missing features although lots of advantages over the competitors. But I believe that "DHCP Failover Cluster" management functionality will be available out-of-box. Until that point this workaround can be used for managing your "DHCP Failover Cluster" workloads in IPAM.

Hope it helps!

Yagmur Sahin

• Database size constraints (limitations of WID)
• Availability constraints

Requirements

• Local admin rights
• Enterprise edition of the SQL server not earlier than SQL 2008 R2

Check current configuration of the Database

Before you start moving the database from WID to SQL, run Get-IpamDatabase powershell cmdlet to check the current configuration.

Creating new database and assign the required permissions

Since the IPAM service is running as "NT AUTHORITY\NETWORK SERVICE", this account has to be configured with the below required permissions in the database configuration otherwise if you are not Planning to su SQL authentication. In order to overcome this requirement create login new login with the default configuration as followed.

• Membership to db_datareader, db_datawriter, db_ddladmin roles and "Alter database" & "view database state" permissions are required on the database

Open SQL Management Studio, right click logins and create new login "NT AUTHORITY\NETWORK SERVICE"

Right click the Databases, click New Database and create new IPAM Database

Once you have IPAM Database created, expand new database and then expand security, right click the Users and hit the New User

In the "Database User - New" window select user type to Windows user and type "NT AUTHORITY\NETWORK SERVICE" to User name and Login name fields.

Once the user created, open the properties of the "NT AUTHORITY\NETWORK SERVICE", in the "Database User - NT AUTHORITY\NETWORK SERVICE" window, select membership and assign db_datareader, db_datawriter, db_ddladmin roles as shown below

In the same window, select securables and grant "Alter database" & "view database state" permissions to "NT AUTHORITY\NETWORK SERVICE"

Moving the Database

Now database is ready to move after the required database permissions are set. Run the following PowerShell command to move the database from WID to SQL.

Move-IpamDatabase -DatabaseServer <ServerName> -DatabaseName <DatabaseName> -DatabasePort <SQL ServerPort, default 1433> -DatabaseAuthType Windows

Example: 

Move-IpamDatabase -DatabaseServer IPAM1 -DatabaseName IPAMDB -DatabasePort 1433 -DatabaseAuthType Windows

Note that this is a one-way operation once the database moved to SQL, cannot be reverted back to WID but off course can be moved to another SQL instance. 

Verify the database configuration

Run Get-IpamDatabase powershell cmdlet to verify that the database configuration information now show that the database is running on SQL server.

Automating the database creation and permissions assignments

Optionnally following SQL script can used to simplify the process.

USE [master]

CREATE DATABASE [IPAMDB]

GO

CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS

GO

USE [IPAMDB]

CREATE USER [NT AUTHORITY\NETWORK SERVICE] FOR LOGIN [NT AUTHORITY\NETWORK SERVICE]

GO

ALTER ROLE [db_ddladmin] ADD MEMBER [NT AUTHORITY\NETWORK SERVICE]

ALTER ROLE [db_datareader] ADD MEMBER [NT AUTHORITY\NETWORK SERVICE]

ALTER ROLE [db_datawriter] ADD MEMBER [NT AUTHORITY\NETWORK SERVICE]

GRANT ALTER TO [NT AUTHORITY\NETWORK SERVICE] AS [dbo]

GRANT VIEW DATABASE STATE TO [NT AUTHORITY\NETWORK SERVICE] AS [dbo]

GO

Run backups on regular basis however database recovery model can be set to simple if no database "point in time recovery" is required for IPAM database.

ALTER DATABASE [IPAMDB] SET RECOVERY SIMPLE

GO

Hope it helps!

• Sunucu ve istemci kurulumlarinin tek bir araç ve prosesin takip edilerek yapilmasi
• Imaj olusturma prosesini otomatiklestirerek, istemci ve sunucu kurulumlarinda zaman kazanci
• System Center Configuration Manager 2007 R2 entegrasyonu ile tamamen otomatik dagitim (Zero Touch) destegi
• Lite Touch dagitim ile SCCM olmayan ortamlarda da istemci ve sunucu kurulumlarinin otomatik yapilabilmesi
• WAIK, WDS gibi Windows dagitim araçlarinin daha verimli ve kolay kullanilabilmesine yardimci oluyor

Indirmek için ;

https://www.microsoft.com/downloads/details.aspx?FamilyID=696dd665-9f76-4177-a811-39c26d3b3b34&displaylang=en