STATEMGR.EXE from SS Scripting Toolkit

[Dennis Payne]

STATEMGR doesn't retain variables for some reason. Does it only work on specific machines?

I've tried it on BL20pG2, DL380G3, and an Evo D510 SFF that I use for testing... none return any errors, but none retain info at all.

In theory, I should get "Phase: 4" every time I type "statemgr /r phase" after I've typed "statemgr /w phase 4" right?

I get "phase: 0" every time.

Where does statemgr store its info?

Thanks

[Ken Henault]

Statemgr stores the data in the NVRAM on ProLiants. It only works under DOS.

It returns the value as an errorlevel. Try the following batch file.


statemgr /w phase 4
statemgr /r phase
if errorlevel 4 goto itworks
echo did not work
goto exit
:itworks
echo it works
:exit

[Dennis Payne]

Thanks for the NVRAM tip... but the implementation you gave is pretty much identical to what I'm doing, and it still returns 0 every time - both from the prompt and in errorlevel form in the batch file.

Anybody else having problems using it on blades specifically?

[Riollet]

Hi,

I have exactly the same problem as explained below. Did you find a solution since you posted your message?

----------------

I was using statemgr from the smartstart scripting tool dos v241 in a very efficient manner to automate servers installation.
I am currently "migrating" my master from a Windows 98 boot version to a WinPE version. That's why I use now the new version of statemgr from the SmartstartScriptingToolKit for WinPE (Win32 edition) and it doesn't work.

On a server already installed with Windows 2003 when I type the following command to write the value 4 in the variable called Phase:

statemgr /w phase 4

I get

Message:
dwIOCTL:467476 Last Error was:6
phase:4

And when I typed the following command to read the value of the variable:

statemgr /r phase

I get a 0 instead of the value I wrote earlier (4)

dwIOCTL:467472 Last Error was:6
phase:0


It also happens when I use the "-" instead of the "/" like "statemgr -w phase 4" instead of "statemgr /w phase 4"

If I boot on a Proliant DL380 G4 from my WinPE CDROM and type the same commands, I get the same problem.

If I boot from a bootable floppy and type the same commands with the old version of statemgr, it works fine.

[Jeff Easton]

Dennis,

I posted a similar question a week or so ago. Look farther down on the page.

Your two servers both contain the Broadcom NIC. I've rolled my own DOS boot disk that will load the Netflex, Intel 100, Intel 1000 or Broadcom NIC driver depending on the server model. If I boot this disk on a DL-380-G3 or -G4, State Manager fails as you describe. Conrep also doesnt work. If I boot the disk on a server using the other three NIC's, State Manager and Conrep work ok.

I think there is some conflict between the Broadcom Q57.dos driver and the smart start scripting tools, but I've pretty much decided its not a memory issue.

I've since added the intel NDIS driver for PXE and put this disk on a PXE server. When I PXE boot the same DL-380-G3 or -G4's that previously failed, the tools now work when using the PXE NIC driver.

[Riollet]

Hi,

My problem seems to be fixed now.
I updated the server with CP004479 which is version 7.80 of my network card (NC 7782 Gigabit Ethernet NIC).
The previous version installed was 7.40

The statemgr command now works on my W2K3 server. (I now need to make it work when I boot with WinPE).

[Riollet]

I recreated a WinPE image from scratch following the W32 Ed Best Practices Guidelines document in the Smart Start Scripting Toolkit. Statemgr is now working correctly when I boot with WinPE.

I am not sure where the problem was as I didn't do the WinPE image myself but the reasons probably were one of the following:
-The WinPE image was made with a Windows 2003 instead of a Windows XP SP2 CD.
-The WinPE image was created with the mkimg command without the /PnP /WMI options.

[Fred Heeks]

Hi everyone - I realise this thread has been dead for a while but I've experienced the same thing on a DL380 G7 just recently and was hoping that someone might be able to clue me in.

I use a WinPE disk to build the server and keep track of where in the batch file the process is with the statemgr.exe program.

However, whereas it works perfectly on G3's, G4's, G5's and G6's I've got some G7's to test now and it doesn't work.

If I use statemgr.exe /w testParameter 10

it shows a successfull message:

testParameter:10 

but if I then try and read the value back I always get 0:

statemgr.exe /r testParameter

testParameter:0

Any idea why this doesn't work on the G7's?? I've updated to the latest Proliant Support Pack and latest Smartstart Scripting Toolkit for Windows but it still doesn't work.