After setting the availability override (How to set Availability Override for a NIC) I want to know more about the performance counters of a NIC. Troubleshooting performance issues on servers sometimes requires more data than your collecting at that point. If your are suspecting the network load or a network issue you want to dive into the performance counter of your network interface card. Some data is already collected by default but for real troubleshooting you need more. By default only the “Network Adapter Bytes Received per Second” are showing in the performance section of the Microsoft Windows Server pane.
For this project i created a new management pack named: Network performance monitoring. Monitoring a lot of performance counters on all of your servers will increase database and network usage enormous so just monitor it for the servers you want to troubleshoot.
To create a performance view of all the by default collected performance data I’m gone create a new view in the the created management pack “Network Performance Monitoring” which is present in the monitoring pane. Right click the Network Performance Monitoring folder and select New => Performance view. In the properties give the view a name an navigate to the Show related data filed. Browse for Network Adapter and click OK two times. In this view all current collected rules are available for the network interfaces. Per server the collected rules are:
- Network Adapter Bytes Send per Second
- Network Adapter Bytes Received per Second
- Network Adapter Bytes Total per Second
By selecting these counter for a specific server you have some information about this NIC. To extend the monitoring of a NIC I’m going to create a few new rules to get more information.
Creating Current bandwidth collection rule:
- Open Authoring pane
- Navigate to Management Pack Objects
- Select Scope in the menu bar
- Select Windows Server 2003 Network Adapter and click OK
- Open Rules
- Right click Rules
- Select Create a new rule
- Select the Network Performance Management pack
- Select Collection Rules
- Select Performance Based
- Select Windows Performance
- Click Next
- Rule name: Network Adapter Current Bandwidth
- Rule Category: PerformanceCollection
- Rule Target: Windows Server 2003 Network Adapter
- Click Next
- Object: Adapter Type
- Enable: Include all instances for this selected counter
- Click browse
- Object: Network Interface
- Select counter from list: Current Bandwidth
- Enable: All instances
- Click OK
- Change interval to 5 minutes
- Click Next
- Ignore the optimization settings
- Click Create.
Within the next few minutes the counter will showup in the created NIC performance view in the monitoring pane.
When you want to add more counters for troubleshooting or performance monitoring, just change the settings in step 20 to 23.
Available counters for network monitoring are found under:
- NBT Connections
- Network Interface
RichCopy is another excellent free tool to replicate files and folders. Its similar to RoboCopy but with rich GUI and extra features.
The way to configure it after installing the App is to setup schedule tasks. In the example below the command line is set to replicate data from dataserver to dataserver2
“C:\Program Files\Microsoft Rich Tools\RichCopy 4.0\RichCopy.exe” “\\dataserver\shared” “dataserver2\shared /P /V /PF”
You can easily restore the database file to its original state using the steps outlined below:
1.Open the %SystemRoot%\Security folder, create a new folder, and then name it “OldSecurity”.
2.Move all of the files ending in .log from the %SystemRoot%\Security folder to the OldSecurity folder.
3.Find the Secedit.sdb file in the %SystemRoot%\Security\Database folder, and then rename this file to “Secedit.old”.
4.Click Start, click Run, type mmc, and then click OK.
5.Click Console, click Add/Remove Snap-in, and then add the Security and Configuration snap-in.
6.Right-click Security and Configuration and Analysis, and then click Open Database.
7.Browse to the %SystemRoot%\Security\Database folder, type Secedit.sdb in the File name box, and then click Open.
8.When you are prompted to import a template, click Setup Security.inf, and then click Open.
A quick Way to mount NTFS drives on ClearOS
yum --nogpgcheck localinstall ntfs-3g-200944-el5i686.rpm
mount -t ntfs-3g /dev/sdf1 /mnt/guest
The DHCP database can be moved or migrated from a Windows Server 2003 server to a Windows Server 2008 server, or from one Windows Server 2008 server to another. The information below details the necessary steps:
Export the DHCP database from a server that is running Microsoft Windows Server 2003 or Windows Server 2008
To move a DHCP database and configuration from a server that is running Windows Server 2003 or Windows Server 2008 to another server that is running Windows Server 2008:
1. Log on to the source DHCP server by using an account that is a member of the local Administrators group.
2. Click Start, click Run, type cmd in the Open box, and then click OK.
3. Type netsh dhcp server export C:\dhcp.txt all , and then press ENTER.
Note: You must have local administrator permissions to export the data.
Configure the DHCP server service on the server that is running Windows Server 2008
1. Click Start, click Administrative Tools, click Server Manager. If needed acknowledge User Account Control.
2. In Roles Summary click Add Roles, click Next, check DHCP server, and then click Next.
Import the DHCP database
1. Log on as a user who is an explicit member of the local Administrators group. A user account in a group that is a member of the local Administrators group will not work. If a local Administrators account does not exist for the domain controller, restart the computer in Directory Services Restore Mode, and use the administrator account to import the database as described later in this section.
2. Copy the exported DHCP database file to the local hard disk of the Windows Server 2008-based computer.
3. Verify that the DHCP service is started on the Windows Server 2008-based computer.
4. Click Start, click Run, type cmd in the Open box, and then click OK.
5. At the command prompt, type netsh dhcp server import c:\dhcpdatabase.txt all , and then press ENTER, where c:\dhcpdatabase.txt is the full path and file name of the database file that you copied to the server.
Authorize the DHCP server
1. Click Start, point to All Programs, point to Administrative Tools, and then click DHCP.
Note You must be logged on to the server by using an account that is a member of the Administrators group. In an Active Directory domain, you must be logged on to the server by using an account that is a member of the Enterprise Administrators group.
2. In the console tree of the DHCP snap-in, expand the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized.
3. Right-click the server object, and then click Authorize.
4. After several moments, right-click the server again, and then click Refresh. A green arrow indicates that the DHCP server is authorized.
You’ve added hardware to a Windows Server 2008 R2 Core installation machine and you want to check the status of it through the GUI by using Device Manager on a remote computer.
The following process allows you to access Device Manager remotely in “Read Only” mode and it assumes that you’ve already configured remote management on your core server through option 4 of sconfig. You’re already able to access the event logs and/or services using Computer Management on a remote computer. When you attempt to access Device Manager remotely, you receive the following error: “Unable to access the computer Make sure that this computer is on the network, has remote administration enabled, and is running the “Plug and Play” and “Remote registry” services.
The error was: Access is denied.” By default, remote access to the plug and play interface is disabled and needs to be enabled with either a GPO or through the local security policy on the core server.
If you have multiple server core machines that you want to enable this on and they’re all in a domain, it’s a best practice to create an OU in your domain for the server core machines, create a GPO, and apply it to the OU.
In this example since I’m in a test environment or if your server core machines are not part of a domain, you’ll need to modify the local security policy. To remotely access the local security policy on your server core machine, launch an mmc console on a remote computer, add the “Group Policy Object Editor” mmc snap-in. Select browse: Enter the server name of you core machine: Go to the following location: Computer Configuration > Administrative Templates > System > Device Installation Select the “Allow remote access to the Plug and Play interface”: Set it to Enabled: Run “gpupdate.exe” on the core server.
You should now be able to use computer management on a remote computer to access “Device Manager” on your server core machine. You will receive the following message stating it is in “Read-Only” mode:
It is important to get the network card configuration right in the parent partition for Hyper-V in Windows Server 2008/R2.
Common problems include:
- A-Records and PTR’s registered for the Parent Partition under multiple IP addresses
- NetBIOS conflicts
- Unwanted traffic going through network cards that you want to dedicate to, for example, VM’s or iSCSI.
These problems have nothing to do with Hyper-V actually. They’re just issues you can face with any server containing more than one network card.
Step #1: Ensure that you have a good naming convention for you network cards
As you can see I have explicitly named by network cards. One for the parent partition, one for the VM’s. If you have one or more network cards for VM’s or iSSCI, name them accordingly.
Step #2 : Ensure that the parent partition uses the right network card
In the image below you can see that the Parent Partition network card is first in the order. This means that network services will attempt to use this interface before the VM NIC #1.
Step #3 : Ensure that the VM or iSCSI NIC does not register itself in DNS
Make sure that the network cards you dedicate for VM external networks do not register themselves in DNS. Just configure the basic IP address and mask. You do not need to include DNS servers etc. Remember, you are more or less turning this network card into a virtual switch.
Note that the “Register this connections addresses in DNS” is left un-ticked. If you built you base OS for the parent partition with all the network cards patched, chances are that you will find more than one address registered for the server in DNS. Ensure that you remove unwanted A-records and PTRs.
Step #4: Ensure that you disable NetBIOS over TCP/IP on the VM network cards