Networking

From Zero to Complete IP Inventory in 5 Seconds: The Multi-Host VBScript | Lazy Admin Blog

Posted on March 20, 2026 Updated on April 15, 2026

Manually documenting IP addresses, MACs, and DNS settings is the definition of “busy work.” This VBScript automates the entire process. It reads a list of servers from a text file, queries each one via WMI, and builds a professional Excel report in real-time.

How to Use This Script

Prepare the Input: Create a text file (e.g., servers.txt) and list your hostnames or IP addresses, one per line.
Save the Script: Save the code below as IPAddressInventory.vbs.
Run: Double-click the .vbs file. When prompted, provide the full path to your text file (e.g., C:\Scripts\servers.txt).
Requirement: You must have Microsoft Excel installed on the machine where you run the script.

The VBScript Code

VBScript

			
' Save as IPAddressInventory.vbs
' Input: Text file with Hostnames/IPs
' Output: Excel Spreadsheet (IP_Addresses.xlsx)
On Error Resume Next
Const FOR_READING = 1
'--- File Input ---
strSrvListFile = InputBox ("Please enter the server list file path OR UNC file path" & vbCrLf & "Eg: C:\Scripts\server.txt" & vbCrLf & "Eg: \\servername\scripts\server.txt","File Input location")
Set objFSO = CreateObject ("Scripting.FileSystemObject")
Set objReadFile = objFSO.OpenTextFile (strSrvListFile, FOR_READING)
'--- File Output ---
strOutput = objfso.GetParentFolderName(strSrvListFile) &"\"
'--- Error Handling ---
If Err.Number <> 0 Then
   WScript.Echo "Please Enter a Valid file Name"
   Err.Clear
   WScript.Quit
End If
'--- Excel Object Creation ---
Set objExcel = CreateObject ("Excel.application")
objExcel.Visible = True
Set objWorkbook = objExcel.Workbooks.Add()
Set objWorksheet = objWorkbook.Worksheets("Sheet1")
x = 1
y = 1
'--- Define Headers ---
objWorksheet.Cells (x, y).value = "S.No"
objWorksheet.Cells (x, y+1).value = "Server Name"
objWorksheet.Cells (x, y+2).value = "Description"
objWorksheet.Cells (x, y+3).value = "IP_Address"
objWorksheet.Cells (x, y+4).value = "Subnet"
objWorksheet.Cells (x, y+5).value = "MACAddress"
objWorksheet.Cells (x, y+6).value = "Gateway" 
objWorksheet.Cells (x, y+7).value = "Preffered DNS"
objWorksheet.Cells (x, y+8).value = "Primary DNS"
objWorksheet.Cells (x, y+9).value = "Secondary DNS"
objWorksheet.Cells (x, y+10).value = "Additional DNS 1"
objWorksheet.Cells (x, y+11).value = "Additional DNS 2"
objWorksheet.Cells (x, y+12).value = "WINS Primary"
objWorksheet.Cells (x, y+13).value = "WINS Secondary"
objWorksheet.Cells (x, y+14).value = "DNS Suffix"
objWorksheet.Cells (x, y+15).value = "DNS Suffix Order"
objWorksheet.Cells (x, y+16).value = "Remarks"
s = 1
Do Until objReadFile.AtEndOfStream
    k = 0
    arrComputer = objReadFile.ReadLine
    strServer = Split (arrComputer, ",")
    objWorksheet.Cells (x+1, y).value = s
    objWorksheet.Cells (x+1, y+1).value = strServer(k)
    Set objWMIService = GetObject ("winmgmts:" & "!\\" & strServer(k) & "\root\cimv2")
   
    '--- Query Network Information ---
    If Err.Number = 0 Then
        WScript.Echo strServer(k) &": Inventoring"
        Set colAdapters = objWMIService.ExecQuery("Select * from Win32_NetworkAdapterConfiguration Where IPEnabled = True")
            
        For Each objAdapter in colAdapters
            objWorksheet.Cells(x+1, y+2).Value = objAdapter.Description
            
            ' IP Address Logic
            If Not IsNull(objAdapter.IPAddress) Then
                For i = LBound(objAdapter.IPAddress) To UBound(objAdapter.IPAddress)
                    If Not InStr(objAdapter.IPAddress(i),":") > "0" Then
                        objWorksheet.Cells(x+1, y+3).Value = objAdapter.IPAddress(i)
                    End If
                Next
            End If
            ' Subnet Logic
            If Not IsNull(objAdapter.IPSubnet) Then
                For i = LBound(objAdapter.IPSubnet) To UBound(objAdapter.IPSubnet)
                    If objAdapter.IPSubnet(i)<> "64" Then
                        objWorksheet.Cells(x+1, y+4).Value = objAdapter.IPSubnet(i)
                    End If
                Next                     
            End If
            
            objWorksheet.Cells(x+1, y+5).Value = objAdapter.MACAddress
            ' Gateway Logic
            If IsNull(objAdapter.DefaultIPGateway) Then
                objWorksheet.Cells(x+1, y+6).Value = "Gateway Not Set"
            Else
                For i = LBound(objAdapter.DefaultIPGateway) To UBound(objAdapter.DefaultIPGateway)
                    objWorksheet.Cells(x+1, y+6).Value = objAdapter.DefaultIPGateway(i)
                Next
            End If 
            ' DNS Logic
            If IsNull(objAdapter.DNSServerSearchOrder) Then
                objworksheet.Cells(x+1, y+7).Value = "DNS Not Set" 
            Else
                For i = LBound(objAdapter.DNSServerSearchOrder) To UBound(objAdapter.DNSServerSearchOrder)
                    objWorksheet.Cells(x+1, y+7).Value = objAdapter.DNSServerSearchOrder(i)
                    y = y + 1
                Next
            End If
            y = 1
                  
            objWorksheet.Cells(x+1, y+12).Value = objAdapter.WINSPrimaryServer
            objWorksheet.Cells(x+1, y+13).Value = objAdapter.WINSSecondaryServer
            objWorksheet.Cells(x+1, y+14).Value = objAdapter.DNSDomain
            
            ' Suffix Logic
            If IsNull(objAdapter.DNSDomainSuffixSearchOrder) Then
                objworksheet.Cells(x+1, y+14).Value = "Suffix Order NA" 
            Else
                For i = LBound(objAdapter.DNSDomainSuffixSearchOrder) To UBound(objAdapter.DNSDomainSuffixSearchOrder)
                    objWorksheet.Cells(x+1, y+15).Value = objAdapter.DNSDomainSuffixSearchOrder(i)
                    x = x + 1
                Next
                x = x - 1
            End If
                  
            x = x + 1
            WScript.Echo strServer(k) &": Completed" 
        Next
    Else
        ' Error Handling for Offline Servers
        objWorksheet.Cells(x+1, y+16).Value = Err.Number & "_" & Err.Description 
        WScript.Echo strServer(k) &": "& Err.Description
        Err.Clear
        x = x + 1
    End If
    s = s + 1
Loop
'--- Formatting and Saving ---
Set objRange = objWorksheet.UsedRange
objRange.EntireColumn.Autofit()
objExcel.ActiveWorkbook.Saveas strOutput & "IP_Addresses.xlsx"
MsgBox "Operation Completed Successfully " ,,"IP Address"

		

Key Features of the Script

Automatic Excel Formatting: It uses UsedRange.Autofit() to ensure the data is readable as soon as the file opens.
WMI Integration: It queries the Win32_NetworkAdapterConfiguration class directly from the remote machine.
Multi-Adapter Support: If a server has multiple enabled NICs, the script loops through each to capture all configurations.
Remark Logging: If a machine is unreachable, the error code and description are written directly into the Excel “Remarks” column so you know which servers to check manually.

This entry was posted in Scripts and tagged Asset Management, Automation, Excel, Inventory Automation, IP Address Management, Network Inventory, Networking, Server Administration, SysAdmin Tools, VBS, VBScript, Windows Script Host, WMI, WMI Query.

No Reboot Required: Configuring Dell iDRAC via RACADM | Lazy Admin Blog

Posted on October 16, 2015 Updated on March 23, 2026

Configuring the Integrated Dell Remote Access Controller (iDRAC) is usually a “Day 1” task performed in the BIOS. But what if you’ve already deployed the server and realized the NIC isn’t configured, or the IP needs to change?

By using the Dell RACADM (Remote Access Controller Admin) utility, you can modify network settings, reset credentials, and pull system health logs directly from the command line without a single second of downtime.

Getting the Tools

To start, download the Dell EMC OpenManage DRAC Tools. This package includes the RACADM executable. You can install this on the local server or on your management workstation to manage servers over the network.

1. Remote RACADM (From your Workstation)

If you have the current credentials but need to change settings remotely, use the -r (remote), -u (user), and -p (password) flags.

Example: Get System Information

Bash

racadm -r 10.1.1.1 -u root -p calvin getsysinfo

Note: If you get an SSL certificate error, the command will still run. To force the command to stop on certificate errors for security, add the -S flag.

2. Local RACADM (From the Server OS)

If you are logged into the Windows or Linux OS on the Dell server itself, you don’t need credentials. The tool communicates directly with the hardware via the IPMI driver.

Example: Quick Network Setup

Bash

			
# Check current config
racadm getniccfg
# Set a new Static IP, Subnet, and Gateway
racadm setniccfg -s 192.168.1.50 255.255.255.0 192.168.1.1

3. Deep Configuration (The Config Group Method)

For more granular control (like setting DNS servers or the DRAC name), you can target specific configuration groups.

The “Lazy Admin” DNS Setup Script:

Bash

			
racadm config -g cfgLanNetworking -o cfgNicIpAddress 172.17.2.124
racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.252.0
racadm config -g cfgLanNetworking -o cfgDNSServer1 172.17.0.6
racadm config -g cfgLanNetworking -o cfgDNSRacName MyServer-iDRAC
racadm config -g cfgLanNetworking -o cfgDNSDomainName corp.company.com

		

4. SSH / Serial RACADM

If you are already connected to the iDRAC via SSH, you don’t need to repeat the racadm command prefix. Simply type racadm and hit enter to enter the RACADM shell:

Bash

			
admin@idrac-web-01: racadm
racadm>> getsysinfo
racadm>> serveraction powercycle

Why this is a “Lazy Admin” Win

Instead of walking to the cold aisle with a crash cart or waiting for a 20-minute reboot cycle, you can script the iDRAC configuration of an entire rack in seconds.

#DellEMC #PowerEdge #iDRAC #SysAdmin #DataCenter #RACADM #Infrastructure #ITOps #LazyAdmin #ServerManagement

This entry was posted in Windows and tagged Command Line, Dell, iDRAC, Networking, OpenManage, PowerEdge, RACADM, Remote Management, Server Hardware, SysAdmin Tools.

vSphere Ports & Connections: The Infrastructure Roadmap | Lazy Admin Blog

Posted on October 8, 2015 Updated on March 23, 2026

In a locked-down enterprise environment, the “Any-to-Any” firewall rule is a myth. To manage ESXi effectively, you need to poke specific holes in your hardware and software firewalls.

The Core Management Ports

These are the “must-haves” for basic connectivity between vCenter, the vSphere Client, and the Host.

Port	Protocol	Source	Destination	Purpose
443	TCP	Management Workstation	vCenter / ESXi	vSphere Client / SDK: The primary port for the Web Client and API access.
902	TCP/UDP	vCenter Server	ESXi Host	vCenter Agent (vpxa): vCenter uses this to send data to the host and receive heartbeats.
902	TCP	Management Workstation	ESXi Host	VM Console: Required to open the “Remote Console” (MKS) to a virtual machine.
80	TCP	vCenter / Workstation	ESXi Host	HTTP: Used for redirecting to 443 and for some legacy file downloads.

Advanced Feature Ports

If you are using specific vSphere features like vMotion, HA, or specialized storage, you need these additional ports open:

1. vMotion (Live Migration)

8000 (TCP): Required for vMotion traffic.
2049 (TCP/UDP): If using NFS storage for the virtual disks.

2. vSphere High Availability (HA)

8182 (TCP/UDP): Used by the Fault Domain Manager (FDM) agent for inter-host communication and election of the master host.

3. Provisioning & Deployment

69 (UDP): TFTP, used for PXE booting ESXi for Auto Deploy.
4012 (TCP): Used by the Auto Deploy service.

4. Troubleshooting & Monitoring

22 (TCP): SSH access to the ESXi Shell.
161 / 162 (UDP): SNMP polling and traps for hardware monitoring.

Troubleshooting “Host Disconnected”

If your host shows as “Not Responding” in vCenter, check these three things in order:

Ping: Can the vCenter server ping the ESXi management IP?
Port 902: From the vCenter server, try to telnet to the host on port 902 (telnet <host-ip> 902). If it fails, the heartbeat can’t get through.
DNS: VMware is extremely sensitive to DNS. Ensure forward and reverse lookups work for both the vCenter and the Host.

Lazy Admin Tip 💡

Don’t memorize every port! Use the VMware Ports and Protocols Tool (the official online matrix). It allows you to select your source and destination products and generates a custom firewall rule list for you.

A high resolution pdf can be downloaded here Connections and Ports in ESX and ESXi

#VMware #vSphere #Networking #SysAdmin #Firewall #DataCenter #ESXi #ITOps #LazyAdmin #Connectivity

This entry was posted in VMware and tagged ESXi, Firewall, IT Infrastructure, Networking, Ports, SysAdmin, Troubleshooting, vcenter, vmotion, VMware.

The Ultimate Robocopy Command for Large-Scale Migrations | Lazy Admin Blog

Posted on June 16, 2015 Updated on March 23, 2026

If you need to move huge files while keeping a close eye on progress, this is the syntax you want. It includes logging, multi-threading for speed, and the ability to resume if the network drops.

The “Power User” Command

DOS

			
robocopy "D:\Source_Data" "E:\Destination_Data" /s /e /z /mt:32 /tee /log+:"C:\Logs\MigrationLog.txt"

Switch Breakdown: Why We Use Them

Switch	What it does
/s /e	Copies all subdirectories, including empty ones.
/z	Restart Mode: If the connection drops mid-file, Robocopy can resume from where it left off instead of starting the file over. Essential for 100GB+ files!
/mt:32	Multi-Threading: Uses 32 threads to copy multiple files simultaneously. (Default is 8). Adjust based on your CPU/Disk speed.
/tee	Writes the status to the console window and the log file at the same time.
/log+:	Creates a log file. Using the `+` appends to an existing log rather than overwriting it—perfect for multi-day migrations.

How to Monitor Progress in Real-Time

Because we used the /tee and /log+ switches, you have two ways to monitor the status:

The Console: You’ll see a rolling percentage for each file directly in your Command Prompt.
Tail the Log: Since the log is being updated live, you can “tail” it from another window (or even remotely) to see the progress without touching the active copy session.

Lazy Admin Tip (PowerShell):

Open a PowerShell window and run this command to watch your Robocopy log update in real-time as files move:

Get-Content "C:\Logs\MigrationLog.txt" -Wait

Important Notes for Huge Files

Disk Quotas: Robocopy doesn’t check destination space before starting. Use dir or df (if using Linux targets) to ensure you have enough room.
Permissions: If you need to copy NTFS permissions (ACLs), add the /copyall switch.
Bandwidth: Running /mt:128 (the max) can saturate a 1Gbps link. If you’re copying over a live production network, stick to /mt:8 or /mt:16.

#WindowsServer #Robocopy #DataMigration #SysAdmin #ITInfrastructure #StorageAdmin #TechTips #LazyAdmin #CloudMigration

This entry was posted in Windows and tagged Data Center, File Transfer, IT Operations, Migration, Networking, PowerShell, Robocopy, Storage, SysAdmin Tools, Windows.

RDP Rescue: How to Fix Remote Desktop Issues Without a Reboot | Lazy Admin Blog

Posted on June 15, 2015 Updated on March 23, 2026

If you can reach a server via ping or the VM console but RDP is failing, you can often “kick-start” the service by toggling specific registry keys. This forces the Terminal Services stack to re-read its configuration without dropping the entire OS.

1. The Firewall Check

Before diving into the registry, ensure the Windows Firewall isn’t blocking Port 3389. If you have console access, try disabling it temporarily to rule it out.

Quick Command: netsh advfirewall set allprofiles state off

2. The “Deny” Toggle (The Most Common Fix)

Sometimes the registry says RDP is allowed, but the service isn’t honoring it. Toggling the value can reset the listener.

Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

fDenyTSConnection: Should be 0. (If it’s already 0, change it to 1, refresh, then back to 0).
fAllowToGetHelp: Should be 0 to ensure Remote Assistance isn’t conflicting.

3. WinStation Listeners (RDP & Citrix)

If the main switch is on but the specific “listener” is disabled, you’ll get a “Connection Refused” error.

For Standard RDP: Path: HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp

fEnableWinStation: Must be 1. Toggle this (1 -> 0 -> 1) to reset the listener.

For Citrix Servers (ICA): Path: HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\ICA-Tcp

fEnableWinStation: Must be 1.

4. Port Verification

Ensure the server is actually listening on the standard port. If someone changed the RDP port for “security,” your connection will fail.

Path: HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp

PortNumber: Should be 3389 (Decimal).

Test it from your workstation: tnc <ServerIP> -port 3389 (PowerShell) or telnet <ServerIP> 3389

5. The Winlogon Block

In rare cases, the entire Winlogon station for terminal services is disabled at the software level.

Path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

WinStationsDisabled: Must be 0. If set to 1, no one can log in via RDP regardless of other settings.

Lazy Admin Tip 💡

If you can’t get to the console, you can change these registry keys remotely from your workstation! Open Regedit, go to File > Connect Network Registry, and enter the target server’s name. You can perform all the toggles mentioned above without ever leaving your desk.

#WindowsServer #RDP #SysAdmin #Troubleshooting #ITOps #TechTips #Networking #RemoteDesktop #LazyAdmin #ServerManagement

This entry was posted in Windows and tagged IT Support, LazyAdmin, Networking, RDP, Registry, Remote Desktop, SysAdmin, Terminal Services, Troubleshooting, Windows Server.

Master the Forest: Top Active Directory Interview Questions & Answers | Lazy Admin Blog

Posted on May 17, 2015 Updated on March 23, 2026

Part 1: The Logical vs. Physical Structure

Understanding how AD is organized is the first step in mastering the service. Interviewers often look for the distinction between how objects are managed (logical) and how traffic flows (physical).

Logical Components

These define the administrative boundaries and hierarchy:

Forest: The uppermost boundary. It contains one or more trees that share a common schema and global catalog.
Tree: A collection of domains that share a contiguous namespace (e.g., corp.com and dev.corp.com).
Domain: The primary unit of replication and security. All objects in a domain share a common database (ntds.dit).
Organizational Unit (OU): Containers used to organize objects within a domain. OUs are primarily used to delegate administration and apply Group Policy.

Physical Components

These define how AD exists on hardware and over the network:

Domain Controllers (DC): The servers that host the AD database and handle authentication.
Sites: A grouping of IP subnets connected by high-speed links. Sites are used to control replication traffic and ensure users log on to a local DC rather than one across a slow WAN link.

Part 2: The Core “Under the Hood” Mechanics

The Active Directory Database

The database is stored in %systemroot%\ntds as ntds.dit. Key files include:

edb.log: Transaction logs (changes are written here first).
res1.log / res2.log: Reserve logs to ensure the system can write to disk if space runs out.
edb.chk: The checkpoint file that tracks which transactions have been committed to the database.

The Global Catalog (GC)

The GC is a partial, read-only replica of every object in the forest. It allows users to search for resources (like a printer in another domain) without needing to query every single DC in the forest.

SYSVOL Folder

The SYSVOL folder is a shared directory on every DC that stores the domain’s public files, including:

Login scripts (Netlogon share).
Group Policy Templates.
It is kept in sync across all DCs using the File Replication Service (FRS) or DFSR.

Part 3: Protocols and Naming

LDAP (Lightweight Directory Access Protocol)

LDAP is the language used to talk to Active Directory. It follows the X.500 standard and uses TCP/IP.

Distinguished Name (DN): The full path to an object (e.g., CN=JohnDoe,OU=Sales,DC=corp,DC=com).
Relative Distinguished Name (RDN): Just the object’s name (e.g., JohnDoe).
UPN (User Principal Name): The “email-style” login name (e.g., johndoe@corp.com).

Part 4: Essential Admin Tools

Tool	Purpose
ADSIEdit	A low-level “registry editor” for Active Directory objects and attributes.
LDP	A tool for performing LDAP searches and operations manually.
Repadmin	The go-to command-line tool for diagnosing replication health.
Netdom	Used for managing trust relationships and joining computers to domains via CLI.
Dcpromo	(Legacy) The command to promote or demote a Domain Controller.

Common Interview Scenario: “My Replication is Broken”

Answer: I would start by checking connectivity between sites. Then, I would use repadmin /showrepl to see which naming contexts (Domain, Configuration, or Schema) are failing. I’d also check the DNS SRV records to ensure the DCs can find each other.

#ActiveDirectory #SysAdmin #WindowsServer #ITJobs #TechInterview #Microsoft #Networking #ITOps #LazyAdmin

This entry was posted in Active Directory, Interview Questions, Windows and tagged Active Directory, DNS, Group Policy, Interview Prep, IT Career, LDAP, microsoft, Networking, SysAdmin, Windows Server.

Configuring Cisco NIC Teaming on UCS B200-M3

Posted on May 7, 2015 Updated on April 14, 2026

For Windows-based Cisco UCS B-Series blades, native teaming is often handled via the Cisco-specific driver contained in the UCS Windows Utilities ISO. Here is how to install and manage teams via the Command Line Interface (CLI).

Prerequisites

Download the Windows Utilities ISO from Cisco.com.
Choose either the B-Series Blade or C-Series Rack-Mount software bundle.
Ensure you have Administrator privileges on the Windows target.

Phase 1: Installing the NIC Teaming Driver

The driver is installed using the enictool. You must point it to the directory containing the .inf files from the ISO.

Open Command Prompt as Administrator.
Run the following command:DOSenictool -p "C:\path\to\drivers" Example: C:\> enictool -p "c:\temp"

Phase 2: Creating and Configuring the Team

Once the driver is active, you can group your logical interfaces into a team.

Identify your connections: Use ipconfig or ncpa.cpl to find the exact names (e.g., “Local Area Connection”).
Create the Team:DOSenictool -c "Connection 1" "Connection 2" -m [mode]

Mode Reference Table

Mode ID	Description	Best Use Case
1	Active-Backup	Basic redundancy; one link stays idle.
2	Active-Backup (Failback)	Redundancy; always reverts to the primary link when healthy.
3	Active-Active	Transmit Load Balancing; uses both links for outgoing traffic.
4	802.3ad LACP	Link Aggregation; requires specific configuration on the Fabric Interconnect/Switch.

Example (Active-Backup):

C:\> enictool -c "Local Area Connection" "Local Area Connection 2" -m 1

Phase 3: Management Commands

To Delete a Team:C:\> enictool -d "Local Area Connection" "Local Area Connection 2"
To View All Options:C:\> enictool /?(Use this to fine-tune Load Balancing hash methods and advanced failover settings.)

#CiscoUCS #NICTeaming #SysAdmin #DataCenter #Networking #WindowsServer #TechTutorial #LazyAdmin #ServerAdmin #Infrastructure

This entry was posted in Cisco UCS, Windows and tagged B200-M3, Blade Server, Cisco UCS, Driver Installation, Enictool, LACP, Load Balancing, Networking, NIC Teaming, Windows Server.

🏗️ CLI Command Hierarchy & Navigation

Posted on April 20, 2015 Updated on April 15, 2026

The CLI is organized like a file system. You move “down” into specific modes to manage objects and “up” to return to the global level.

EXEC Mode (#): The top-level mode. From here, you can access all other sub-modes.
Navigation Commands:
- scope <object>: Moves into a sub-mode for an existing object (e.g., scope chassis 1).
- enter <object>: Similar to scope, but used to enter or create an object’s mode.
- exit: Moves up one level in the hierarchy.
- top: Jumps immediately back to the EXEC mode prompt.

🛠️ Common Management Commands

Target	Command	Purpose
Chassis	`show chassis [inventory/status/psu]`	View physical chassis health and components.
Servers	`show server [inventory/cpu/memory/status]`	Audit blade or rack-mount hardware specs.
Fabric	`show fabric-interconnect [a/b] [inventory]`	Check the state of your Fabric Interconnects.
Faults	`show fault [detail/severity]`	List active system alarms and errors.
Logs	`show sel [chassis-id/blade-id]`	View the System Event Log for specific hardware.

💾 The Transactional Model (Commit Buffer)

Unlike many traditional CLIs, UCS Manager uses a transactional model. When you make a configuration change (like set or enable), the change is stored in a temporary buffer and is not live until you explicitly save it.

Modify: set addr 192.168.1.50
Verify: show configuration pending (Optional)
Apply: commit-buffer
Discard: discard-buffer (If you made a mistake)

#CiscoUCS #CommandLine #SysAdmin #DataCenter #Networking #Cisco #ITPro #LazyAdmin #TechTutorials #UCSM

This entry was posted in Cisco UCS and tagged Cisco UCS, CLI, Command Reference, Data Center, Fabric Interconnect, Networking, SysAdmin, Transaction Model.

How to Change the Static IP Address of a Windows Domain Controller

Posted on April 11, 2015 Updated on April 15, 2026

Whether you are re-IPing a subnet or moving a server to a new VLAN, changing a Domain Controller’s IP address requires more than just updating the NIC settings. If DNS records don’t update correctly, users won’t be able to log in, and replication will fail.

Prerequisites

Credentials: You must be a member of the Domain Admins group.
Access: Log on locally to the system console. If you lose network connectivity during the change, you may need to boot into DSRM to recover.

Step-by-Step: Changing the IP Address

Open Network Connections: Right-click My Network Places (or Network in newer versions) and click Properties.
Edit Adapter: Right-click your Local Area Connection and select Properties.
TCP/IP Settings: Double-click Internet Protocol (TCP/IP).
Update Addresses:
- Enter the new IP address, Subnet mask, and Default gateway.
- Update the Preferred and Alternate DNS servers.
- Note: Usually, a DC points to itself (127.0.0.1) or a partner DC for DNS.
WINS (Optional): If your environment still uses WINS, click Advanced > WINS tab and update any static WINS server entries.
Apply: Click OK until all dialog boxes are closed.

Critical Step: Post-Change Registration

Once the IP is changed, Windows needs to tell the rest of the domain where the DC is now located. Do not skip these commands.

Open a Command Prompt and run:

Register DNS Records:DOSipconfig /registerdns This forces the DC to update its ‘A’ (Host) record in DNS.
Fix Service Records:DOSdcdiag /fix This ensures that vital SRV records (which clients use to find the DC) are updated to point to the new IP.

Potential Pitfalls: Mapped Drives and Hardcoded IPs

Changing the IP settings won’t affect shared permissions, but it will break any connection made via IP address rather than hostname.

Avoid This: net use g: \\192.168.0.199\data (This breaks after the change).
Do This: net use g: \\DC1\data (This continues to work regardless of the IP).

The LazyAdmin Lesson: Always use DNS names (Hostnames) for your resources. It saves you from manual updates every time a server moves!

ActiveDirectory #SysAdmin #WindowsServer #Networking #IPAddress #ITPro #DNS #Troubleshooting #LazyAdmin #ServerAdmin

This entry was posted in Active Directory, Windows and tagged Active Directory, dcdiag, DNS, Domain Controller, ipconfig, Networking, Static IP, SysAdmin Guide, Windows Server 2003.