need a Teamviewer script for Win7PE_SE

Load drivers:

exec !=drvload.exe X:WindowsSystem32DriverStoreFileRepositoryatiilhag.inf_x86_neutral_1d882551ede2c65batiilhag.inf
exec !=drvload.exe X:WindowsSystem32DriverStoreFileRepositoryigdlh.inf_x86_neutral_2d255f193700d214igdlh.inf
exec !=drvload.exe X:WindowsSystem32DriverStoreFileRepositorynv_lh.inf_x86_neutral_bbe628dbdd6fce25nv_LH.inf

Switch to admin:

REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonSpecialAccountsUserListGuest=#0
REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonAutoAdminLogon=1
REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonDefaultUserName=LsaSetupDomainAdministrator
REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonDefaultPassword=""
REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonForceAutoLogon=1
REGI HKLMSOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorerStartMenuLogOff=0
EXEC !=net start gpsvc
// weird, site posting problem - below there shoul no space between system32 and tsdiscon
EXEC !=%SystemRoot%System32 tsdiscon.exe
WAIT 10000
REGI HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonForceAutoLogon=0

relaunch as system:

KILL EXPLORER.EXE
// Again there should be no space between system32 and tskill
exec !=%windir%system32 tskill explorer
exec !%windir%system32psexec -i -d -s explorer
// you can load drivers here instead
//exec !=drvload.exe X:WindowsSystem32DriverStoreFileRepositorynv_lh.inf_x86_neutral_bbe628dbdd6fce25nv_LH.inf
//exec !=cmd.exe /c drvload.exe X:WindowsSystem32DriverStoreFileRepositoryatiilhag.inf_x86_neutral_1d882551ede2c65batiilhag.inf
//exec !=cmd.exe /c drvload.exe X:WindowsSystem32DriverStoreFileRepositoryigdlh.inf_x86_neutral_2d255f193700d214igdlh.inf
//WAIT 2000
//EXEC !dragwin.exe
//EXEC !=net stop UxSms
//EXEC !=net start UxSms

.

Edited by SIW2, 14 June 2012 - 01:23 AM.

I need a working Teamviewer script for Win7PE_SE. I already found one, but Teamviewer doesn't start and doesn't even throw an error.

Has anyone a working script?

I'm only using Teamviewer Version 6 but the architecture is a 32 bit application with an option to use 64 bit WOW to run its 32 bit app on top of a 64 bit operating system.

The base 64 bit winpe.wim you can pull out of the WAIK does not include the WOW subsystem and official documentation says adding it to the image is not supported.

However the Win7PE_SE project and the Make_PE3 project appear to unofficially hack WOW into a 64 bit winpe image using Win7 install media or the currently installed OS to pull bits from. So its possible it might work in a 64 bit winpe image.

That said.

The general opinion seems to be that unless you plan to launch the actual windows installer while in winpe, most seem to say "Why" and "There is no reason to build a 64 bit image" The other reasons are along the lines of if you need driver support and only 64 bit drivers are available.. then they recommend make a 64 bit winpe boot image. This led to some launch confusion as some officials with Microsoft said 32 bit winpe could be used to deploy a 64 bit "image" but not to "install" a 64 bit version of the operating system. I presume this is because 32 bit handles large enough numbers to access the blocks in a typical hard drive image, or assumes the image will be less in size than 2 GB which is the limit for a VHD which imaging tools like ImageX might use. After its deployed and the OS is booted the native 64 bit tools could then be used to claim more of the disk space by expanding the file system.

Personally I wanted to add Teamviewer to a Macrium winpe image. They make available a 32 or 64 bit builder in their Professional edition to create bootable media by downloading the WAIK for you from Microsoft and then adding the product to the base winpe.wim image and wrapping that in a bootable recovery.iso file format. Rather nicely, if you already have the WAIK installed, the builder recognizes this and does not attempt to download the WAIK kit again from Microsoft.

You can open the iso and pull out the winpe.wim image from the sources dir and boot it anyway you like, could be plastic cd, could be usb, could be WDS, or I use windows nloader pxeboot pulled out of the base winpe.wim with tftpd64 on a pc.

As for Teamviewer itself if you boot in a 32 bit winpe image, there are less variables since it is a native 32 application. You cannot remove the 64 labeled files in Teamviewer because that will cause a dependency error when starting, even in a pure 32 bit boot environment.. just leave it alone and don't try to prune it.

The BartPE people have reported previously Teamviewer worked on winpe. BartPE is getting old and was created only for winpe 32 bit, there is no BartPE for 64 bit that I'm aware of.. so they seem to know what they are talking about.

The BartPE people mentioned using Teamviewer Portable is a good choice, because it will accept its configuration options from a Teamviewr.ini and tv.ini configuation files. The Teamviewer.ini file tells the application to "import" its settings from a file, which means it will look for them in a tv.ini file in the same directory. The tv.ini file is created by customizing a configuration while in teamviewer control panel, Options and Advanced and then exporting it to a file and naming it tv.ini

So far the only subversion of Teamviewer6 Portable I can confirm starts up properly is 6.0.10511

You must remember to configure network interface statically assigned or dhcp and start the network [ wpeutil InitializeNetwork ]

If the network is not started Teamviewer will not start, it will silently return a command prompt.

Teamviewer.exe takes "connect to" command line options, but that is all, the rest is in the tv.ini file.

It takes a good long pause before starting, but it does start, the thing to remember is -- be patient it is worth the wait

There are some other options that are nice:

there is auto hide for the connected box

there is direct lan connect using IP only, (if it is switched to accept exclusively it will display the current interface IP instead of a TeamViewer ID)

outbound connections from winpe work, inbound even with [ wpeutil DisableFirewall ] does not work, using direct lan connect

inbound connections using the normal Teamviewer ID code protocol does work, ven with the firewall up (which is the default for winpe)

You can leave direct lan connect [disabled/accept] and it will display a regular TeamViewer ID code.

You can look at the screen and collect the TV ID and password or preconfigure the [password] but you cannot send the TV ID code to your teamviewer account, there is a Wizard built into the TV control panel to do that after its started but no way to automate that I can find. I would prefer a stand alone application that let me provide account username and password to send the TV ID code from the command line, so it could be scripted, but so far that does not exist.

If you have the Commerical Teamviewer license, support suggested you could configure a custom Quickconnect version of Teamviewer to send the TV ID to your teamviewer account list -- but i have not tested this

In short there are a lot of attractive Teamviewer options.

The CD site BartPE guys seem to be testing later Teamviewer 6 Portable subversions and reported similar failures, after 10511 they don't work (but I have not tested them).

I noticed the "unable to switch user log messages" but do not think they are relevant, or if they are now, the enforcement in later editions is a recent change in policy. To be clear, the problem did exist in 10511 but did not stop it from proceeding to run anyway.

Getting version 6.0.10511 is pretty much a task on your own because Teamviewer website distributes older versions, but only the latest subversion of the older versions.. and currently for latest version 6 it does not work in winpe.

Edited by John Willis, 05 September 2012 - 03:42 AM.

#26 Guest_Boot_Monkey_*

#27 SIW2

#28 MedEvil

#29 SIW2

#30 amalux

#31 John Willis

1 user(s) are reading this topic