Home » Posts tagged 'Windows 2008'

Tag Archives: Windows 2008

Send-MailMessage : Unable to connect to remote server Line

Send-MailMessage -to “reciever@domin.com” -from “sender@domain.com” -Subject “Subject Info” -Body “Content” -SmtpServer “Server Name”

Was not able to send mail from a Windows 2008 server and the error message displayed is as listed below:

Send-MailMessage : Unable to connect to the remote server
At line:1 char:17
+ Send-MailMessage <<<< -to someone@somedomain.com -from “DhimantR@someDomain.com” -subject ” Troubleshooting” -Body “Some Text or file attachement” -sntpserver “smtpserver”
+ CategoryInfo : InvalidOperation: (System.Net.Mail.SmtpClient:SmtpClient) [Send-MailMessage], SmtpException
+ FullyQualifiedErrorId : SmtpException,Microsoft.PowerShell.Commands.Send MailMessage

Found that the the block was in McAfee, when Powershell was excluded from McAfee. Send mail was success.

Steps to exclude Powershell in McAfee is listed below:

  1. Right click on McAfee icon.
  2. Click on Virus Scan Console.
  3. Double click on Access Protection on VirusScan Console.
  4. On Access Protection tab.
  5. Go to Anti-Virus Standard Protection.
  6. On right hand side, double click on Prevent mass mailing worms from sending mail.
  7. On process to exclude tab, add PowerShell.exe at the end.
  8. Click OK.
  9. Click apply on Access Protection.
  10. Click OK.

Thanks,
WintelAdmin

Cannot open programs unless “Run As Administrator

One of the application was recently installed on Windows 2012 Server, when I click on the short cut its gives an error message stating ” … has stopped working. Windows can check online for a solution to the problem”.  Further, it gives options to check online for a solution and close the program or close the program.

To my surprise, it was found that the application opens by clicking on “Run as Administrator”. Later, clicking “Run as admin” every time was annoying. Hence, the application was set to run as administrator by default following the steps listed below:

Right click the program and select Properties

Under the compatibility tab, select Run this program as an administrator

Click Apply and OK

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

Verify WMI for MS Cluster issues

In a cluster environment, WMI is often used to share information and notification within the nodes. Some of the cluster issues/error due to the WMI is as listed below:

“RPC Server Unavailable” error.
Access is Denied.
The computer ‘Node1’ could not be reached.
Failed to retrieve the maximum number of nodes for ‘{0}’.
The computer does not have the Failover Clustering feature installed. Use Server Manager to install the feature on this computer.
Note: first confirm you have installed the Failover Clustering feature on this node

In above case we need to make sure that the WMI is working fine and this can be confirmed following the steps listed below:
Make sure that the WMI service is up and firewall settings.

1. Launch CMD
2. Type “WBEMTest” (without quotes”).
3. The Windows Management Instrumentation Tester will launch
4. Select Connect
5. Namespace: Root\MSCluster
6. Select Connect and if you see more options available, it means you are connected and WMI is working
7. Click on Query and enter SELECT * from MSCluster_Resource to confirm (any error shown represents WMI issue).

Thanks,
WinteAdmin

Delete Old Files

Batch script to delete X days old file from specified location. Where is X is number of days.

@echo off
REM Remove files backup older than X days
Echo Deleting Bak file….
forfiles /p “Folder Path” /s /m *.bak /c “cmd /c Del @path” /d -X
Exit

Note:
Folder Path= Replace with target folder.
Replace X with no of days (Eg :3 for 3 days old)

Thanks,
WintelAdmin

VMware Virtual Machine Reporting from VSphere

VMware PowerCLI is a powerful utility to generate virtual machine information and status. This is very cool and handy tool. I use to generate VMTools status, Datacenter and ESX host name information.

Command to connect vCenter:

Connect-VIServer vcenter1, vcenter2, vcenter

Initialize VMTools Version:
New-VIProperty -Name ToolsVersion -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Config.tools.ToolsVersion’ -Force

Initialize VMTools Status:
New-VIProperty -Name ToolsVersionStatus -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Guest.ToolsVersionStatus’ -Force

Verify VMTools status on all virtual machines and export the output to excel:
Get-VM | Select Name, ToolsVersion, ToolsVersionStatus | Export-Csv -NoTypeInformation -UseCulture -Path C:\Temp\VMToolsInfo.csv

Export VM name, cluster and ESX Host:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}}, @{N=”ESX Host”;E={Get-VMHost -VM $_}} | Export-Csv -NoTypeInformation C:\temp\VM_CLuster_Host-.csv

Export VM name and Cluster name:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}} | Export-Csv -NoTypeInformation C:\temp\test-VM_CLuster.csv

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

RDP issue, Port No 3389 not listed under netstat

Came across an issue, where users were unable to connect to the Windows 2008 using RDP. When checked the RDP port 3389, its not listed under netstat -ano. Therefore, tried uninstalling the remote desktop services and reinstalled it multiple times. Was still unlucky and issue persists.

Finally was able to fix the issue by deleting the terminal services connection and recreating it.

1. Open “Remote Desktop Host Configuration”.

2. Delete the RDP-tcp.

3. Create a new RDP listener.

Voila! was able to connect to RDP instantly.

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

 


Visitors Count

Subscriber Count

    3803
March 2017
M T W T F S S
« Feb    
 12345
6789101112
13141516171819
20212223242526
2728293031