No matter how sophisticated the technology is , It still takes people !
Connect to the iSCSI array1
Now that you have the initiator software installed, you need to tell it where to look for mountable volumes. Start the initiator configuration by going to the Control Panel and choosing the iSCSI Initiator option. From the initiator, choose the Discovery tab, shown .
The iSCSI initiator’s Discovery tab.
On the Discovery tab, click the Add button under the Target Portals box. This will open the Add Target Portal dialog box, shown .
The Add Target Portal dialog box.
In the Add Target Portal dialog box, provide the name or IP address of your iSCSI array. The default communication port for iSCSI traffic is 3260. Unless you have changed your port, leave this as is. If you have configured CHAP security or are using IPSec for communication between your client and the array, click on the Advanced button and make necessary configuration changes. The Advanced Settings dialog box
Advanced options for connecting to your iSCSI array.
Back on the Add Target Portal, click the OK button to make the initial connection to the iSCSI array. Note that, at this point, you’re not connecting to an actual volume, but only to the array in general.
The target portal has been added to the initiator.
First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N
When you are debugging the Orchestrator related issues in mid/large deployments , it is expected that the server.log file rotates rapidly. In this case we need to increase the log file size and the rotation interval. Below are the steps to make changes to the config file to capture large number of files for troubleshooting. Config File Location : Appliance deployment: /etc/vco/app-server/log4j.xml Windows deployment: <install_Location>\app-server\conf\log4j.xml Steps: 1. Edit the file log4j.xml 2. Locate the <appender class="org.apache.log4j.RollingFileAppender" name="FILE"> section 3. Increase the size of the log file to 10 MB <param name="MaxFileSize" value="10240KB"/> 4. Increase the number files to be retained before rotation <param name="MaxBackupIndex" value="5"/> Cheers :-)
DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997. Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy. Remember that old test server that you built two years ago that caught fire before it could be used? Probably not. DNS still remembers it though. There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening. Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying. What happened?" This post should help us figure out when the first issue will happen and completely avoid the second. We'll go through how scavenging is setup then I'll give you my best practices. Scavenging s