sanbarrow.com ~ View topic - esx-tools-016

Update:
with latest ESX 3.5 u4 you need the updated ViClient

download esx-tools-016.exe
and put these files into R:\src

make sure the VMware-viclient.exe is from version 3.5 u4.

If you got everything boot into a MOA_max and run esx-tools-016.exe (without parameter)
Follow instructions.
When finished you should now have two wim-files:
add2vm-016.wim
add2win-016.wim
Put then into R:\_sfx_

During regular use you only need a MOA-bandit - call esx-tools-016.exe like this
esx-tools-016.exe run

a successful run should add these icons to your desktop

Note: you only need the two wims in CD-only builds - if you use a persistant home with "moa-is-at-home.tag" you do not need them !

Joined: 08 Dec 2008 Posts: 68

max build, clean tc container, installed:

vmware 6.5.2 as written in http://sanbarrow.com/moa241.html
(two shortcuts on desktop - is it right and only cosmetic mess?)

esx-tools-016.exe as written here

Result: orpaned powershell shurtcut, missing vitoolkit...

Tried more than twice... the same reproduceable effect. What may be wrong for me?

Hi

the two dublicated icons ...
The one named with the original names are created during first installation of the Workstation and ViClient.
The ones with the short names like "vmware" and "viclient" are created by MOA-bootup at later times. If you delete the ones with the long names everything will be fine.
I should mention that in the howto Embarassed

ABout the powershell and vitoolkit ... are only the icons wrong or is the function also missing ?
Did you provide the setup-files for both while doing the esx-tools-first setup ?

Joined: 08 Dec 2008 Posts: 68

Hi, glad to meet you again! MOA rocks, anyway! Smile

The shortcut points to X:\I386\SYSTEM32\windowspowershell\v1.0\powershell.exe

No powershell.exe exists on R:

Hi
that link should be ok.

Joined: 08 Dec 2008 Posts: 68

R:\add2win\system32>dir /s
Volume in drive R has no label.
Volume Serial Number is 2879-FB40

Directory of R:\add2win\system32

08/23/2009 05:34 PM <DIR> .
08/23/2009 05:34 PM <DIR> ..
09/23/2005 07:28 AM 83,456 dfshim.dll
08/23/2009 05:30 PM <DIR> drivers
09/23/2005 07:28 AM 270,848 mscoree.dll
09/23/2005 07:28 AM 150,016 mscorier.dll
09/23/2005 07:28 AM 74,240 mscories.dll
08/23/2009 05:30 PM <DIR> MUI
09/23/2005 07:28 AM 32,768 netfxperf.dll
08/23/2009 05:30 PM <DIR> windowspowershell
5 File(s) 611,328 bytes

Directory of R:\add2win\system32\drivers

08/23/2009 05:30 PM <DIR> .
08/23/2009 05:30 PM <DIR> ..
0 File(s) 0 bytes

Directory of R:\add2win\system32\MUI

08/23/2009 05:30 PM <DIR> .
08/23/2009 05:30 PM <DIR> ..
08/23/2009 05:30 PM <DIR> 0409
0 File(s) 0 bytes

Directory of R:\add2win\system32\MUI\0409

08/23/2009 05:30 PM <DIR> .
08/23/2009 05:30 PM <DIR> ..
09/23/2005 07:29 AM 6,144 mscorees.dll
1 File(s) 6,144 bytes

Directory of R:\add2win\system32\windowspowershell

08/23/2009 05:30 PM <DIR> .
08/23/2009 05:30 PM <DIR> ..
0 File(s) 0 bytes

Total Files Listed:
6 File(s) 617,472 bytes
14 Dir(s) 5,017,432,064 bytes free

R:\add2win\system32>

There are missing files ...
looks like the installation of powershell during esx-tools-016 setup failed for some reason ?

Can you do a test ?
Start MOA - run "esx-tools-016.exe run"
and try to install Powershell again ?

Joined: 08 Dec 2008 Posts: 68

WindowsServer2003-KB926141-x86-ENU.exe

Setup Error: the system cannot find the path specified. OK.

I may upload somewhere a filtered procmon output Logfile.PML (1.754KB) Can you help analyzing it?

Joined: 08 Dec 2008 Posts: 68

Yet another strange thing with my MOA: the Vmware Workstation serial number does not persist. When I try to start a machine, vmware asks me for it, once after each reboot...

LevT
you use an different version - the setup for esx-tools-016 handles the
WindowsServer2003-KB926139-v2-x86-ENU.exe

Thats why the setup does not prepare it.
The version you mentioned seems to be a newer one - I never tested with that ...

Ulli

Joined: 08 Dec 2008 Posts: 68

Okay thank you!
It was my fault

esx-tools-16 look like fully working now for me

Joined: 08 Dec 2008 Posts: 68

Oh no -(

some strange things for me last

1. Using the max build, the powershell and the viclient do not start after reboot without first
"esx-tools-016.exe run"

2. As i mentioned above, the Workstation serial number does not persist. When I try to start a machine, vmware asks me for it, once after each reboot...

#1 - hey - that is the expected behaviour.
You start dotnet-support by running
esx-tools-016.exe run

If you are sure that you want dotnet-support at each boot - create a file named R:\bin\lastbatch.cmd and put the line
esx-tools-016.exe run
into it.
Personally I create a desktop icon to do this on demand only.

#2
MOA looks for a VMware-Workstation license at boot.
You should export your VMware-license as a registry patch and name it vmware-license.reg

Look here - how to export the registry
http://sanbarrow.com/how-to-add-ws-to-moa.html

research Joined: 09 Feb 2007 Posts: 559

The esx-tools is now, I think, very hard to use because VMware doesn't give use the oportunity to download the old stuff.

-VMware-Vim4PS-1.0.0-113525.exe
-VMware-VIRemoteCLI-3.5.0-104314.exe
-VMware-vix-disklib-e.x.p-99191.i386.exe

Now, VMware is full vSphere and vCenter with all new clients.

Maybe I'm wrong, but I simply need VIClient to connect to the ESXi 3.5 server at work. I'll create a package for .NET2 (or use Joakim LODR) and install VIClient on the fly!

Are those no longer available ?

ok - its time for an update then

for now - ignore those missing ones

only the correct viclient from ESX 3.5u4 and the powershell version are mandatory