If you have Windows 2000 Service Pack 4, you can install TeamViewer 1 up to TeamViewer 8. If you have Windows 98, Windows Millennium, or Windows NT 4.0 SP6a, you can install TeamViewer 1 up to TeamViewer 6. You can install and use TeamViewer from the newest down to the oldest operating system. To make sure you are installing the latest version, download the latest TeamViewer. This is actually not a problem because you can easily download the application from its official website. If that error pops up when installing on a particular computer with the same operating system, it means that your installer is now damaged or corrupt. If you are installing TeamViewer on computers with Microsoft Windows XP then I don’t think that error is related to compatibility. However ive also seen references such as start msiexec /i teamviewer_host.TeamViewer 5 Setup Installer Corrupted: Invalid opcode
The documentation suggests that an example script msiexec.exe /i "X:\TeamViewer_Host.msi" /qn APITOKEN= ASSIGNMENTOPTIONS="-group Test_Group -grant-easy-access" Does this mean that if I deploy Teamviewer using the MSI package that it will not update unless I install a later version of the MSI over the top of the existing install? What if the device Policy says to update the client? Is deploying the Setup (exe) now a requirement for auto updating or policy based updating? If so are there Mass Deployment instructions for the Setup file?Ĭould somone provide clarification on the installation options for the MSI as well? It must be updated with the Windows Installer again.". The first stumbling block was reading "Auto update in TeamViewer is not longer available, if you are using the msi file for installation. The inital plan was to deploy the MSI package as outlined in the 'Mass Deployment' document. Some clarification is needed the help document is very poorly written.
Or install using the Setup package (no indication is this is for mass deployment though) and then assign using the TeamViewer.exe or the MSI afterwards.įirst issue is trying to determine if I should be using the MSI or the Setup exe (as ive done in the past).
Ive read through the changes and it now appears that you can install and assign in one step using the MSI. With the release of TV 13.2 things have become more of an issue. The second step runs the assignment tool with our API key and joins the install to TV management console.
We start by installing the Setup (exe) host package using the custom id appended to the end of the file name and installed silently by using the \S switch. Ive been deploying TV 13.1 using PDQ Deploy and the Assignment Tool since its release with no issues.
0 kommentar(er)
