Monthly Archives: December 2013

Dell: How to install Server Administrator on Windows 2012 Server Core Edition

Posted on by

Do the following to install Server Administrator on a Server Core. Once installed, you can launch OMSA using a supported remote browser.

1. Enable WOW component. Run the following command from the Server Core command prompt:

 dism /online /enable-feature /featurename:ServerCore-WOW64

2. Install x64 Server Administrator. Run the following command to install

Msiexec /i SysMgmtx64.msi

3. Disable WOW: Run the following command to disable WOW feature.

 dism /online /disable-feature /featurename:ServerCore-WOW64

4. Reboot the system.

Note: Disabling or enabling the WOW component would require system reboot.

5. Server Administrator is installed. You can launch the Server Administrator from a remote device as Server Core does not have the user interface

DiskPart has encountered an error: The media is write protected.

Posted on by

During the creation of a new disk, the error “The media is write protected” pops up.

Check if the disk (or volume) is in a read-only state:

DISKPART> attributes disk
Current Read-only State : Yes
Read-only : Yes
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

If the disk or volume is in a read-only state, clear the attribute with the following command:

 

attributes disk clear readonly

attributes volume clear readonly

Go ahead with the creation of the new disk

Copy vswitch information between ESX servers

Posted on by

Below is a script to copy vswitch information from a source ESX server to a destination ESX server.

All vswitch, network and vlan information will be copied.

# Define Variables 
$VCServer = "vc-server" 
$cred = Get-Credential

# Connect server 
$VC = Connect-VIServer -Server "$VCServer" 

#$VISRV = Connect-VIServer (Read-Host "Please enter the name of your VI SERVER")
$BASEHost = Get-VMHost -Name (Read-Host "Please enter the name of your existing server as seen in the VI Client:")
$NEWHost = Get-VMHost -Name (Read-Host "Please enter the name of the server to configure as seen in the VI Client:")

$BASEHost |Get-VirtualSwitch |Foreach {
   If (($NEWHost |Get-VirtualSwitch -Name $_.Name-ErrorAction SilentlyContinue)-eq $null){
       Write-Host "Creating Virtual Switch $($_.Name)"
       $NewSwitch = $NEWHost |New-VirtualSwitch -Name $_.Name-NumPorts $_.NumPorts-Mtu $_.Mtu
       $vSwitch = $_
    }
   $_ |Get-VirtualPortGroup |Foreach {
       If (($NEWHost |Get-VirtualPortGroup -Name $_.Name-ErrorAction SilentlyContinue)-eq $null){
           Write-Host "Creating Portgroup $($_.Name)"
           $NewPortGroup = $NEWHost |Get-VirtualSwitch -Name $vSwitch |New-VirtualPortGroup -Name $_.Name-VLanId $_.VLanID
        }
    }
}

 

disabling autonegotiate on the Dell iDRAC

Posted on by

Dell iDRAC devices tend to have problems negotiating with a switch port that’s at 1000mbit/auto – the device is limited to 100mbit. The quickest way to get it working is to disable auto and just go 100/Full.

/admin1-> racadm getconfig -g cfgNetTuning
cfgNetTuningNic100MB=2
cfgNetTuningNicFullDuplex=1
cfgNetTuningNicMtu=1500
cfgNetTuningNicAutoneg=1
/admin1-> racadm config -g cfgNetTuning -o cfgNetTuningNicAutoneg 0
Object value modified successfully
/admin1-> racadm racreset
RAC reset operation initiated successfully. It may take a few
 minutes for the RAC to come online again.

After a minute or so from it’s reboot it should pop right up on the network.

source: http://tacticalvim.wordpress.com/2013/03/07/disabling-autonegotiate-on-the-dell-idrac/

Finding and changing the MTU in Windows 7/2012

Posted on by

In computer networking, the maximum transmission unit (MTU) of a layer of a communications protocol is the size (in bytes) of the largest protocol data unit that the layer can pass onwards. MTU parameters usually appear in association with a communications interface (NIC, serial port, etc.). …

 

To find the MTU for Windows 7, type the following command at a DOS prompt:

netsh interface ipv4 show subinterfaces

 

To change the MTU for an adapter use the following command example:

netsh interface ipv4 set subinterface “Local Area Connection” mtu=1458 store=persistent

 

The following table summarizes the default MTU sizes for different network media.

 

  Network             MTU (bytes)
   -------------------------------
   16 Mbps Token Ring        17914
   4 Mbps Token Ring          4464
   FDDI                       4352
   Ethernet                   1500
   IEEE 802.3/802.2           1492
   PPPoE (WAN Miniport)       1480
   X.25                        576

How to enable or disable DNS updates in Windows 2000 and in Windows Server 2003

Posted on by

http://support.microsoft.com/?id=246804

SUMMARY

Depending on the configuration and services that are running on a particular computer, different components perform DNS updates. There is no centralized way, such as a tool or registry keys, to manage the DNS update behavior of all components. This article describes each component and how to modify that particular component’s behavior.

The article also discusses how to disable DNS updates in Microsoft Windows Server 2003. By default, client computers that are running Windows Server 2003 have DNS updates enabled.

INTRODUCTION

The following components perform DNS updates:

  • Dynamic Host Configuration Protocol (DHCP) Client service
    These updates apply to all Windows 2000-based computers.
  • DNS Server service
    These updates apply to Windows 2000-based DNS servers only.
  • Net Logon service
    This updates apply to Windows 2000-based domain controllers only.
  • Remote access client
    These updates apply to Windows 2000-based remote access clients only.

Note After you change one of these components by modifying the registry keys that are listed in this article, you must stop and restart the affected services. Sometimes, you must restart the computer. These instances are noted.

 

Forward and reverse per adaptor

To disable A and PTR resource record registrations that are performed for a specific adaptor by the DHCP Client service, use the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Interface name>\DisableDynamicUpdate

Data type: REG_DWORD
Range: 0 – 1
Default value: 0

This disables DNS update registration on this adaptor. With DNS update, DNS client computers automatically register and update their resource records whenever address changes occur.

   Value   Meaning

   --------------------------------------------

   0       Enables DNS update registration

   1       Disables DNS update registration

Note For DNS updates to operate on any adaptor, it must be enabled at the system level and at the adaptor level. To disable DNS updates for a particular adaptor, add the DisableDynamicUpdate value to an interface name registry subkey, and then set its value to 1. To disable DNS updates on all adaptors in a computer, add the DisableDynamicUpdate value to the following registry subkey, and then set its value to 1:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Windows 2000 does not add this entry to the registry. You can add it by editing the registry or by using a program that edits the registry.

To make the changes to this value effective, you must restart Windows 2000.

Reverse per adaptor

There is no mechanism to disable PTR resource record registrations on a per-adaptor basis.