I have a few D520s that I can't get to startup the Deployment Client. I load up my KBE, it gets to the point where it should be starting the client and letting me get access to the scripted installations etc, but instead this tall, blank, rectangular window pops up and the Y:\kta\startup.bat script is at "mshta Y:\hta\rpc_upload_inventory.hta" hanging. The cursor idling.

Whats the deal with this empty window? What could be causing this issue?
Answer Summary:
Found that the systems that worked had between 2 and 4GB of memory. Assuming 512 MB just isn't going to cut it. Found that the systems had enough memory to at least start the USB Flash Drive KImage process. The UFD KImage process doesn't start up the Deployment Client, and so I am guess that is why this method should work where the normal online Deployment Client method failed.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3
How much ram does the machine have?
Answered 03/16/2012 by: dchristian
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
512 MB 0_o

Probably not enough eh?
Answered 03/16/2012 by: muebel
Tenth Degree Black Belt

Please log in to comment
0
512 is the min required.

Problem is if your using integrated video, it takes some of the ram.

That'll drop you below the 512...
Answered 03/16/2012 by: dchristian
Red Belt

Please log in to comment
0
The three with the issue were part of a group of 10.

The other 7 in the group were able to start the deployment client and run a scripted installation.

I will check into any differences in the integrated video, but I suspect there won't be.
Answered 03/16/2012 by: muebel
Tenth Degree Black Belt

Please log in to comment
0
Found that the systems that worked had between 2 and 4GB of memory. Assuming 512 MB just isn't going to cut it. Found that the systems had enough memory to at least start the USB Flash Drive KImage process.

The UFD KImage process doesn't start up the Deployment Client, and so I am guess that is why this method should work where the normal online Deployment Client method failed.
Answered 03/20/2012 by: muebel
Tenth Degree Black Belt

Please log in to comment
1
I created a seperate boot enviroment just for older models. Unfortunately we hold on to very old machines. Just load the drivers needed for PXE for just that model in kbe_windows_x86 and recache. Create a new boot enviroment as you normally would. This worked for me on our GX240s.
Answered 03/29/2012 by: dugullett
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share