| MOA
as a thin View4 Client
A few days ago the first real ESXi made its way into my lab.
Hey - now I can test if the MOA-View Client really works ;-)
And indead - it does.
... but so far only the RDP protocol works. Still investigating ....
Anyway ... you can follow the instructions I posted last year - see
Here are some first screenshots of a successful connection.
Kiosk mode is somewhat advanced - but possible. If you need help contact
me.
Regard this as proof of concept only - need more tests ...
Ulli Hankeln
Instructions ...
Screenshots ...
Trouble-shooting:
If anything during connection attempts goes wrong - first of all check
DNS-name resolution.
MOA must be able to address the View-connection-server by name.
Instructions ...
you first must create a MOA 2.4.1 build - see
instructions
You very likely will not need the mass-storage drivers so you may
want to remove them to speed up boot-time.
I would highly recommend to build MOA so that it boots from a USB
device.
This way you can add video and sound drivers for your machines quite
easily.
Additionally download:
mstsc-lodr.exe
vmware-viewclient-4.0.0-210939.exe or newer version
Add both files to ...pebuilder\bartpe\i386\system32
for a View-client 4 in a MOA-kiosk solution use:
lastbatch.cmd edit ...\pebuilder\bartpe\moahome\bin\lastbatch.cmd
@echo off
set mytitle=custom last batch
title %MYTITLE%
COLOR f3
rem adjust next line to set a custom resolution
rem setres h1024 v768 b32
rem adjust next line to change default us-keyboard layout
rem keyboard gr
rem use this to start the crypt server - do not disable
net start cryptsvc
rem next line enables RDP client - do not disable
start /wait mstsc-lodr.exe
rem next line installs the View-client - adjust filename if necessary
start /wait vmware-viewclient-4.0.0-210939.exe /s /v/qn
rem use next line to preset a special server
rem regedit /s view-server.reg
rem next line starts the View-client
"r:\programs\vmware\vmware view\client\bin\wswc.exe"
rem set an action to do when View-client exits ...
rem shutdowns
exit
moa.ini edit .... \pebuilder\bartpe\i386\system32\shell\moa.ini
[BOOT]
defaultCheatCode=lean
defaultRAMdriveSize=8
moahome_ramsize=16
start_sshd=yes
start_vmdks=no
start_vgasafe=yes
start_vmware=no
start_audiosrv=yes
start_eventlog=yes
start_msi=yes
moa_timeout=1
start_explorer=no
start_debug=no
start_kiosk=yes
start_KioskVM=no
start_vcr4moa=yes
start_KioskVMX=Q:\NT4SRV01\Windows-NT.vmx
start_KioskVM2=no
start_KioskVMX2=Q:\w2ksrven\2kas-en.vmx
start_earlybatch=no
start_latebatch=no
start_prenetworkbatch=no
[NETWORK]
default_NetMode=
vmnet1_IP=192.168.52.1
vmnet1_name=VMware Network Adapter VMnet1
vmnet8_IP=192.168.132.1
vmnet8_name=VMware Network Adapter VMnet8
moa_hostname=moa
moa_workgroup=workgroup
[AUTOMOUNT]
mount_tdrive=no
mount_udrive=no
mount_vdrive=no
wim1_mount=no
wim1_path=r:\_sfx_\ws602ripped.wim
in case you want a progressbar

put viewkioskprogress.exe
into ...\pebuilder\bartpe\i386\system32\shell and launch it with
firstbatch.cmd - create a new file
as ...\pebuilder\bartpe\i386\system32\shell\firstbatch.cmd
@echo off
start viewkioskprogress.exe
exit
(the progressbar runs until the process wswc.exe is launched)
When you have done this steps launch moa-setup-tool and run menu
> postprocessing > create bandit ....
top
Screenshots ...

top
|