View BSOD (blue screen) crash information stored in dump files

Description

BlueScreenView scans all your minidump files created during ‘blue screen of death’ crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

http://www.nirsoft.net/utils/blue_screen_view.html

[wpdm_file id=76]

How to Set or Change a Dell PowerEdge Service Tag

Source: http://lonesysadmin.net/2011/03/08/how-to-set-a-dell-poweredge-service-tag/

 

Got a Dell PowerEdge that you replaced the motherboard on, and now it doesn’t have a service tag? Reset it with the asset.com tool, which I’ve conveniently packaged as both a floppy disk image and an ISO for those of us in need. They both use the Windows 7 boot disk DOS and asset_A209.com from ftp.dell.com (renamed to asset.com).

[wpdm_file id=50]

[wpdm_file id=51]

Once you boot from these you can set the service tag with:

asset /s <service tag>

You can also set the asset tag with:

asset <asset tag>

Or clear the asset tag with:

asset /d

Check FSMO Roles

Run the following vbs script to show you the location off the FSMO roles:

 

Set objRootDSE = GetObject("LDAP://rootDSE")

Set objSchema = GetObject _
    ("LDAP://" & objRootDSE.Get("schemaNamingContext"))
strSchemaMaster = objSchema.Get("fSMORoleOwner")
Set objNtds = GetObject("LDAP://" & strSchemaMaster)
Set objComputer = GetObject(objNtds.Parent)
WScript.Echo "Forest-wide Schema Master FSMO: " & objComputer.Name

Set objNtds = Nothing
Set objComputer = Nothing

Set objPartitions = GetObject("LDAP://CN=Partitions," & _
    objRootDSE.Get("configurationNamingContext"))
strDomainNamingMaster = objPartitions.Get("fSMORoleOwner")
Set objNtds = GetObject("LDAP://" & strDomainNamingMaster)
Set objComputer = GetObject(objNtds.Parent)
WScript.Echo "Forest-wide Domain Naming Master FSMO: " & objComputer.Name

Set objDomain = GetObject _
    ("LDAP://" & objRootDSE.Get("defaultNamingContext"))
strPdcEmulator = objDomain.Get("fSMORoleOwner")
Set objNtds = GetObject("LDAP://" & strPdcEmulator)
Set objComputer = GetObject(objNtds.Parent)
WScript.Echo "Domain's PDC Emulator FSMO: " & objComputer.Name

Set objRidManager = GetObject("LDAP://CN=RID Manager$,CN=System," & _
    objRootDSE.Get("defaultNamingContext"))
strRidMaster = objRidManager.Get("fSMORoleOwner")
Set objNtds = GetObject("LDAP://" & strRidMaster)
Set objComputer = GetObject(objNtds.Parent)
WScript.Echo "Domain's RID Master FSMO: " & objComputer.Name

Set objInfrastructure = GetObject("LDAP://CN=Infrastructure," & _
    objRootDSE.Get("defaultNamingContext"))
strInfrastructureMaster = objInfrastructure.Get("fSMORoleOwner")
Set objNtds = GetObject("LDAP://" & strInfrastructureMaster)
Set objComputer = GetObject(objNtds.Parent)
WScript.Echo "Domain's Infrastructure Master FSMO: " & objComputer.Name

 

download link: [wpdm_file id=49]

What is the USC?

The Dell™ Unified Server Configurator is a pre-installed configuration utility that enables systems and storage management tasks from an embedded environment throughout the server’s lifecycle.

Residing on an embedded flash memory card on the system board of supported servers, the Unified Server Configurator is similar to a BIOS utility in that it can be started during the POST (Power On Self Test) sequence and functions independently of the operating system (OS).

Using the Unified Server Configurator, you can quickly identify, download, and apply system updates without needing to search the Dell support site (support.dell.com). You can also deploy an OS with drivers (the USC stores Operating System drivers contained within a driver pack), configure a Redundant Array of Independent Disks (RAID), and run 32 -bit diagnostics to validate the system and attached hardware.

NOTE:
Certain platforms or servers may not support the full set of features provided by the Unified Server Configurator.

Starting the Unified Server Configurator

To start the Unified Server Configurator, press the <F10> key within 10 seconds of the Dell logo being displayed during the system boot process.

The first time you boot the system, the Unified Server Configurator starts with the User Settings wizard displayed so that you can configure your preferred language and network settings.


USC and Diagnostics

Dell has built into the Unified Server Configurator the ability to launch the system DMRK diagnostics.

CE TIP:
Learning about how the USC can be used to launch and utilize the DRMK diagnostics can be an advantage for you when addressing customer issues. Especially those that require diagnostics to be performed to identify the problem, as the diagnostics will always be on the system board, and there is no need to download them from support.dell.com, as long as the USC on the system is viable and functioning.

When launching the DRMK diagnostics please keep in mind the following:

  • The BIOS provides “thunking” mechanism to allow DRMK DOS to run the tools.
  • When the Diagnostics are complete a reboot of the system is required, sometime after initial launch a reboot will not be required.

The process below illustrates how to launch these diagnostics from the USC.

Platform Update Using FTP Repository
1. To perfom the following procedure you need the following.1.     A server booted into the Unified Server Configurator, F10 on P.O.S.T.
2. Select the Diagnostics option from the left menu of the Unified Server Configurator.
3. On the next screen of the USC Diagnostics Launching Wizard, you will see a single option for Run Diagnostics, select this option.
4. You will now see a screen saying the system is “Loading DRMK V8.00,” indicating the system is loading the diagnostic files.
5. The DMRK diagnostics is now loaded, from here the diagnostics is identical in form and function when compared to the media loaded diags.

Platform Update using FTP Repository

With the Unified Server Configurator Dell has provided the ability to update the USC platform, OS driver pack and system diagnostics using an FTP repository. By default the repository would be ftp.dell.com, but customers can create there own FTP repository and point to it for updates. The image below provides a high level overview of how the Platform Update works using an FTP repository.

The process below explains how to initiate a platform update using an FTP repository, like ftp.dell.com.

Platform Update Using FTP Repository
1. To perform the following procedure you need the following.

  1. A server booted into the Unified Server Configurator, F10 on P.O.S.T.
  2. One of the NICs on the server must be connected, and have properly configured access to the internet to gain access to ftp.dell.com.
2. Select the Platform Update option from the left menu of the Unified Server Configurator.
3. On the next screen of the Platform Update Wizard, you will see a single option for Launch Platform Update, select this option.
4. This next screen select an FTP server or USB Key containing the Platform Update Repository files. Select FTP Server, and configure the FTP server address, proxy server information proxy port, proxy type, proxy user name and proxy user password information. Once all the information is populated click the next button to continue.
5. The next screen in the platform updates wizard allows the user to select the available updates on the repository. Notice that this page shows the current version diagnostics, OS Drivers Pack and the USC platform version as well as the versions to be updated to during the update process.
6. Once the user sees this screen, the system is now performing the Platform Updates.
7. Once the system completes each task for the update, the system will now reboot. You will notice on P.O.S.T. that the system will state it is entering system services, this is the normal and expected behavior.

8. Once the system gets to the welcome screen of the USC after the first reboot, it will reboot again. However, upon the second reboot it will default to the normal boot process, as configured in the system BIOS.

!!It is very important that you update the USC itself!!

Download this as a document: [wpdm_file id=”23″]

VBS – Check Folder/File size

Below is an example off a VBS script to monitor the size of a directory or a file. If the size is larger then the size specified it will mail a message with a warning.

Script to monitor a folder:

strFolderToMonitor = "C:\TEST"
intSizeInGB = 12
intSizeInBytes  = (intSizeInGB * 1024 * 1024 * 1024)
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFolder = objFSO.GetFolder(strFolderToMonitor) 

If objFolder.Size > intSizeInBytes Then
  Set objMessage = CreateObject("CDO.Message")
  objMessage.From = "[email protected]"
  objMessage.To = "[email protected]"
  objMessage.Subject = "Folder " & strFolderToMonitor & " exceeded " & intSizeInGB & "GB"
  objMessage.TextBody = "The folder " & strFolderToMonitor & " has exceeded " & intSizeInGB & "GB.  Please panic in an orderly fashion." 

  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.domain.suffix"
  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
  objMessage.Configuration.Fields.Update 

  objMessage.Send
End If

 

Script to monitor a file:

strFileToMonitor = "C:\TEST\TEST.TXT"
intSizeInGB = 30
intSizeInBytes  = (intSizeInGB * 1024 * 1024 * 1024)
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.GetFile(strFileToMonitor)

'If objFolder.Size > intSizeInBytes Then
If objFile.Size > intSizeInBytes Then
  Set objMessage = CreateObject("CDO.Message")
  objMessage.From = "[email protected]"
  objMessage.To = "[email protected]"
  objMessage.Subject = "File " & strFileToMonitor & " exceeded " & intSizeInGB & "GB"
  objMessage.TextBody = "The file " & strFileToMonitor & " has exceeded " & intSizeInGB & "GB." & chr(10) & chr(13) & "Please panic in an orderly fashion." 

  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.domain.suffix"
  objMessage.Configuration.Fields.Item ("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
  objMessage.Configuration.Fields.Update 

  objMessage.Send
End If

 

Or download the files here:

[wpdm_file id=”19″]

[wpdm_file id=”20″]

Windows 2008 Multipath I/O Overview

Adding and removing MPIO support
To install Multipath I/O on a computer running Windows Server 2008, complete the following steps.

To install Multipath I/O
1.Open Server Manager.

To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.

2.In the Features area, click Add Features.

3.On the Select Features page of the Add Features Wizard, select Multipath I/O, and then click Next.

4.On the Confirm Installation Selections page, click Install.

5.When installation has completed, click Close.

Source: http://technet.microsoft.com/en-us/library/cc725907.aspx
Documentation: [wpdm_file id=”18″]