Showing posts with label dell. Show all posts
Showing posts with label dell. Show all posts

11 May 2009

Management Pack Dell: Regional settings bug

[Update: Dell will only deliver a 4.0 with this bug corrected. No intermediate release. We signed an NDA to get a hand on the 4.0 beta, but i left the company before having it. The 4.0 should be released by the end of july.]

I have an open issue with the Dell Management Pack and our regional settings. I found out the bug, the resolution, but now Dell ask me to wait for the MP V4.0 because i am the only one to report this bug.

I guess that we are not the only one to have this bug, and it's about people not going through opening a case at Dell. I will expose the issue here, hoping others will realize they are affected too. My goal is to have Dell releasing a corrected version before 4.0 that will be out in months.

The Bug is for DellStorageDiscovery.vbs:

Source: Health Service Modules
Event number: 21405

The process started at 09:29:38 failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0 Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DellStorageDiscovery.vbs" {XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX} {XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX} agent.mydomain.com Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1821\ One or more workflows were affected by this. Workflow name: Dell.Connections.DellStorage.Discovery Instance name: agent.mydomain.com Instance ID: {XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX} Management group: FIRSTMG

------
The badly function is (in red the problem):
Function CheckVBScriptEngine()
Dim bIsCompatV, var
Const VBSCRIPT_MIN_VERSION = 5.6
var = ScriptEngineMajorVersion & “.” & ScriptEngineMinorVersion
If (CInt(var)) < biscompatv =" False" biscompatv =" True"> 0 Then
CheckVBScriptEngine = Err.Number
Else
CheckVBScriptEngine = bIsCompatV
End If
End Function

The corrected function is:
Function CheckVBScriptEngine()
Dim bIsCompatV, var, sep, WshShell
Set WshShell = WScript.CreateObject(”WScript.Shell”)
sep = WshShell.RegRead(”HKCU\Control Panel\International\sDecimal”)
Const VBSCRIPT_MIN_VERSION = 5.6
var = ScriptEngineMajorVersion & sep & ScriptEngineMinorVersion
If (CInt(var)) < biscompatv =" False" biscompatv =" True"> 0 Then
CheckVBScriptEngine = Err.Number
Else
CheckVBScriptEngine = bIsCompatV
End If
End Function

PS: I also have a similar bug with the Microsoft ISA 2006 Management Pack. Microsoft acknowleged the bug and is going to deliver a new release.

13 April 2007

BartPE: inject Perc4 or Perc 5 driver inside a windows

if you want to inject a Perc 5 or Perc 4 driver inside a windows (the real one, not bartpe), i added these features to the famous VMSCSI plugin for BartPE:
http://gollum123.free.fr/fixvmscsi/

Useful to restore a server on another hardware:
-boot with bartpe
-restore with ghost or another tool
-inject the Perc5 or Perc4 driver in the windows you restored with ghost
-reboot, it's working out!

If you are restoring from another hardware (a good reason to inject different driver !), you may need to do a fixmbr : mbrfix /drive 0 fixmbr /yes

BartPE: adding LSI Dell PERC 5 driver with Windows XP Source

If you need to build a bartpe with a Windows XP source, but on a server with a Perc 5 (5/E, 5/i,...) SAS Raid server (PowerEdge 1950 / 2950), the Dell driver won't work. The CD will stop booting saying perc_sas.sys is missing.

The solution is to use the LSI logic driver that meet this chipset.
I put it here:
http://gollum123.free.fr/LSI_XP_perc5/