The first is the command (dnscmd) . This is the executable
that will perform the work based upon the given parameters, shown in Figure 13 - 3 .
Figure 13-3
The second section, as shown next, is for the location of the DNS server ($DNS_Server) and the zone
($DNS_Zone) that the record will be added to:
Insert dns server /recordadd dns zone here
The last section includes the name ($Cluster_Name) and the IP address ($Cluster_IP) of the ??? A ??™
record that will be created. (See Figure 13 - 4 .) At this point, you may be wondering why the DNS record
and the user have been created from the command line and not through the GUI. At the end of this
chapter we bring all of these separate scripts together to show how using PowerShell to automate
common tasks saves time and reduces errors in the deployment of Single Copy Clusters.
Verify the ??? A ??™ record was created by using nslookup , as shown in Figure 13 - 5 .
Chapter 13: Single Copy Clusters
369
Figure 13-4
Figure 13-5
Part III: Working with PowerShell in a Production Environment
370
The next step is to configure the network interfaces on both servers. By default the first network
connection on any server is always named ???Local Area Connection ??? . Each additional network connection
appends a numeral to the connection name.
Pages:
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520