Please wait for the Windows Modules Installer.

One of my windows 2008 didn’t come after reboot. Upon checking the console, saw a message stating “Please wait for the Windows Modules Installer.”. Had to bring up the server at the earliest. It took about an hour, tried reset but server was getting back on to same page. Application team was eagerly waiting for it to come back. Started looking for alternative methods to bring it up.

When checking server was pinging and able to shared folders. Hence, connected to the server from services.msc using the option “Connect to another computer..”

Disabled “Windows Module Installer” service and restarted the server.

Bang, server was back on its home page.

Thanks,

WintelAdmin

PowerShell for Administrators – Coming Soon

PowerShell essentials for administrators coming soon on WintelAdmin to help with your daily operations.

Stay Tuned…..

WintelAdmin.com

IBM DB2 error SQL5005C during server startup.

Upon windows server hosting DB2 reboot you will get an error message “SQL5005C”. This actually refers to “The operation failed because the database manager failed to access either the database manager configuration file or the database configuration file.” This is due to DB2 database utility (such as db2start, db2icrt, restore, or many others) requires that the database manager write to or read from either the database manager configuration file or the database configuration file, and the database manager was unable to access the configuration file.

This is fixed by performing the below steps:

1. Log in to the machine as system administrator.
2. Remove the db2systray by performing the following steps:
a. Windows Start –> All Programs –> IBM DB2 –> Command Line Tools –> Command Window Administrator.
b. db2systray -clean
3. Log off and log in to the machine.

Thanks,
WintelAdmin

Ping multiple server and display IP with status.

This script will ping multiple server available in servers.txt and display IP with status.
Copy below contents and save as filename.vbs and create a servers.txt will all server names one per line.

************************************************************************************************************

Const ForReading = 1
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set objShell = CreateObject(“WScript.Shell”)
If not objFSO.FileExists(“servers.txt”) THEN
wscript.echo “Please create a file named ‘servers.txt’ with one PC name to be pinged per line,”&_
vbcrlf&”with a hard return at the end of each line.”
wscript.quit
end if
tempobj=”temp.txt”

Set objTextFile = objFSO.OpenTextFile(“servers.txt”, ForReading)
logfile=”results.csv”
Set ofile=objFSO.CreateTextFile(logfile,True)
strText = objTextFile.ReadAll
objTextFile.Close
wscript.echo “Ping batch starting, please be patient. This could take some time to”&_
vbcrlf&”finish, depending on the number of hosts to check. You “_
&”will be “&vbcrlf&”notified upon the completion of this script.”
ofile.WriteLine “,”&”Ping Report — Date: ” & Now() & vbCrLf
arrComputers = Split(strText, vbCrLF)
for each item in arrcomputers
objShell.Run “cmd /c ping -n 1 -w 1000 ” & item & ” >temp.txt”, 0, True
Set tempfile = objFSO.OpenTextFile(tempobj,ForReading)
Do Until tempfile.AtEndOfStream
temp=tempfile.readall
striploc = InStr(temp,”[“)
If striploc=0 Then
strip=””
Else
strip=Mid(temp,striploc,16)
strip=Replace(strip,”[“,””)
strip=Replace(strip,”]”,””)
strip=Replace(strip,”w”,” “)
strip=Replace(strip,” “,””)
End If

If InStr(temp, “Reply from”) Then
ofile.writeline item & “,”&strip&”,”&”Online.”
ElseIf InStr(temp, “Request timed out.”) Then
ofile.writeline item &”,”&strip&”,”&”No response (Offline).”
ELSEIf InStr(temp, “try again”) Then
ofile.writeline item & “,”&strip&”,”&”Unknown host (no DNS entry).”

End If
Loop
Next
tempfile.close
objfso.deletefile(tempobj)
ofile.writeline
ofile.writeline “,”&”Ping batch complete “&now()
wscript.echo “Ping batch completed. The results will now be displayed.”
objShell.Run(“””C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office\excel.exe “””&logfile)

************************************************************************************************************

Thanks,
WintelAdmin

VMware Tools is no more depended on vSphere/Esxi release.

VMware tools 10.0.0 is now no more dependent on vSphere release/Esxi builds. I think this is the first time when VMware released VMware Tools separately. As per release note its backward compatible, compatible with Esxi 5.0 and also compatible with Workstation 12.0 and VMware Fusion 8.0. It will allow to get the latest new features and enhancements made to the VMware tools faster to the customers.

You can download and install the latest version of VMware Tools from Here.

Thanks,
WintelAdmin

Windows could not finish configuring the system.

Recently, I was installing Windows 2008 R2 on a HP ProLiant DL380 Gen9 server. Found that the server was throwing an error message stating “Windows could not finish configuring the system.”. When you click on “OK”, servers gets automatic reboot and shows again the same error.

When searched on google, I found that this error message occurs with Windows Server 2008 R2 operating systems if the system contains a registry key that is larger than 8 kilobytes (KB). A Hotfix for this problem is available from Microsoft

KB981542

In my case it was during a clean install of Windows OS, hence it was fixed following the steps listed below:

When you find the error message stating that the “Windows could not finish configuring the system” appears on your screen:

1. Hold down the SHIFT key and press F10 (SHIFT + F10) to open command prompt.
2. At command prompt type: cd oobe (& press Enter).
3. Then type: msoobe (& press Enter).
4. Finally Restart your computer.

You will see your machine back with CTRL+ALT+DEL screen.

Thanks,
WintelAdmin

Windows 2012 Network Share: The specified network name is no longer available

Shares created on Windows Server 2012 R2 are are inaccessible from Windows XP, Windows Server 2003 or Windows Server 2008.

When you try to access the share you will get an error message stating “The specified network name is no longer available”. Windows 2012 will not accept traffic from an older operating systems.

In rorder to fix the issue, a registry setting on Windows Server 2012 R2 must be modified as listed below:

Back up the Registry Hive/Key and make the following change:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\DependOnService

Original Value: SamSS Srv2

Change to: SamSS Srv

Note: Just delete the 2

After making the change, reboot Windows Server 2012 R2

Note: You may also need to reboot the clients/servers involved

Thanks,
WintelAdmin

VB Script to collect Windows server hardware details on multiple machines.

VB Script to collect Windows server hardware details. Script will Collect Serial Number, Make, Model, OS, CPU, RAM, Drive details on multiple servers remotely.

Copy below contents and save as filename.vbs and create a machines.txt will all server names one per line.

 

***********************************************************************************************************************

Option Explicit

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

Const PATH_TO_INPUT = “Machines.txt”
Const PATH_TO_OUTPUT = “MachineInventory.csv”

Dim fso
Set fso = WScript.CreateObject(“Scripting.FileSystemObject”)

Dim shl
Set shl = WScript.CreateObject(“WScript.Shell”)

Dim input
Set input = fso.OpenTextFile(PATH_TO_INPUT)

Dim output
Set output = fso.CreateTextFile(PATH_TO_OUTPUT, True)

output.WriteLine “Hostname,Serial Number,Make,Model,BIOS Version,Operating System,CPU,Memory (MB),Disk Drives”

Dim wmiService
Dim wmiResults

Dim hostname
Dim make
Dim model
Dim biosversion
Dim operatingSystem
Dim serialNumber
Dim cpu
Dim memory
Dim drives

Dim line
Dim exec
Dim pingResults
While Not input.AtEndOfStream
line = input.ReadLine
hostname = “”
make = “”
model = “”
biosversion = “”
operatingSystem = “”
serialNumber = “”
cpu = “”
memory = “”
drives = “”

Set exec = shl.Exec(“ping -n 2 -w 1000 ” & line)
pingResults = LCase(exec.StdOut.ReadAll)

If InStr(pingResults, “reply from”) Then
WScript.Echo “Reply From: ” & line
On Error Resume Next

Set wmiService = GetObject(“winmgmts:\\” & line & “\root\CIMV2”)

If Not Err.Number = 0 Then
output.WriteLine line & “,Error: ” & Err.Description
WScript.Echo line & “,Error: ” & Err.Description
On Error GoTo 0
Else
On Error GoTo 0
hostname = line

Set wmiResults = wmiService.ExecQuery(“SELECT * FROM Win32_BIOS”, “WQL”, wbemFlagReturnImmediately + wbemFlagForwardOnly)

Dim item
For Each item In wmiResults
serialNumber = Trim(item.SerialNumber)
biosversion = Trim(item.SMBIOSBIOSVersion)
Next

Set wmiResults = wmiService.ExecQuery(“SELECT * FROM Win32_ComputerSystem”, “WQL”, wbemFlagReturnImmediately + wbemFlagForwardOnly)

For Each item In wmiResults
make = Trim(item.Manufacturer)
model = Trim(item.Model)
Next

Set wmiResults = wmiService.ExecQuery(“SELECT * FROM Win32_OperatingSystem”, “WQL”, wbemFlagReturnImmediately + wbemFlagForwardOnly)

For Each item In wmiResults
operatingSystem = Trim(item.Name)
operatingSystem = Split(operatingSystem, “|”)(0)
memory = Round(Trim(item.TotalVisibleMemorySize) / 1024, 2)
Next

Set wmiResults = wmiService.ExecQuery(“SELECT * FROM Win32_Processor”, “WQL”, wbemFlagReturnImmediately + wbemFlagForwardOnly)

For Each item In wmiResults
cpu = Trim(item.Name)
Next

Set wmiResults = wmiService.ExecQuery(“SELECT * FROM Win32_LogicalDisk WHERE DriveType=3”, “WQL”, wbemFlagReturnImmediately + wbemFlagForwardOnly)

For Each item In wmiResults
drives = drives & Trim(item.DeviceID) & ” ” & Round(Trim(item.Size) / (1024^2), 2) & “;”
Next

output.WriteLine hostname & “,” & serialNumber & “,” & make & “,” & model & “,” & biosversion & “,” & operatingSystem & “,” & cpu & “,” & memory & “,” & drives
WScript.Echo hostname & “,” & serialNumber & “,” & make & “,” & model & “,” & biosversion & “,” & operatingSystem & “,” & cpu & “,” & memory & “,” & drives
End If
Else
output.WriteLine line & “,No Response”
WScript.Echo line & “,No Response”
End If
Wend

output.Close
input.Close

Set wmiService = Nothing
Set wmiresults = Nothing

***********************************************************************************************************************

 

Thanks,

WintelAdmin

 

WintelAdmin.com Completes 5 Years.

 
I am very much exited and proud to announce that WintelAdmin.com has now completed 5 Years. As stated earlier, it all started on 28th June 2010 when I wrote my first post at Winteladmin.com. Bit late but, I am very happy to announce that WintelAdmin.com is celebrating its fifth anniversary with its loyal readers! Sincere thanks to all readers, friends and well-wishers. Special thanks to speedhost.in for their exceptional support on very hard time.
 
affiliate_show_banner.php_180-e1328512765947
 
 Thanks,
WintelAdmin

Forcibly remove failover cluster feature.

Forcibly remove failover cluster feature.

I was asked to take a clone of Windows 2008 server and release it to appliation team as a replacement server for another standalone Windows 2008 server. Clone was successfully completed and found that the source of the clone is a cluster node. Hence, I had to remove the filover cluster. As this was a virtual server I had the liability of disconnecting it from network and conencted using local admin account. Unfortunately, it was not allowing to uninstall cluster, it required AD authentication. Taking the server back to network and trying to remove the cluster was challenging as this had the possibilities of impacting the existing cluster setup. Sever Manager will not allow you to remove the cluster feature as its still a part of a cluster. Hence, I was then able to find a work around using the registry.

1. Take the complete backup of the registry.
2. Locate HKLM\CurrentControlSet\Services\
3. Delete the keys “ClusDisk” & “ClusSvc”
4. Now try uninstalling the Failover CLustering.
5. You will be prompted with “Have you removed this server from the cluster?”. Yes, I’ve removed this server from the cluster or No. I still need to remove this server from the server.”
6. Click on “Yes, I’ve removed this server from the cluster.”
7. Reboot the server.

You now has the liability of adding the same feature back and setup a new cluster.

Thanks,
WintelAdmin