Thinreg /nodesktoprefresh

Similar Questions

• VMware failure of Thinreg

  Hello

  I'm following this article (deploy ThinApp and AppLink packets together - VMware ThinApp Blog - Blogs from VMware) to try to package together the three applications (needs B and C).  I have change everything needed in the document, but during the installation of the application a msi, I get the error

  VMware ThinApp Thinreg tool - cannot save C:\...\AppB.exe:

  What I need to activate thinreg somewhere - I don't think so that it records all the previous exe very well.

  Thank you

  I wrote this blog long back and remember to work for 2 applications.

  Have you added that names both dependence ThinApp EXE (B and C) in the file table? (Step 7). Also, check that the sequence number is equal to 3.

• thinreg.exe/u vs uninstall.vbs

  Hi all

  I'm trying to understand how registration/deregistration of ThinApps work best.

  Today, we use 'thinreg.exe' to record a ThinApp during logon with the help of a PowerShell script that uses the user's group membership.

  ----------------------------

  Start-Process - FilePath \\server\thinapplibraryshare\thinreg.exe - ArgumentList "/ q" "\\server\thinapplibraryshare\funnythinapp.exe'"«-attendez. "

  ----------------------------

  So, the part of logon works quite nice.

  When it comes to logoff unsubscribe us just all thinapps during logoff using "thinreg/u".

  ----------------------------

  Start-Process - FilePath \\server\thinapplibraryshare\thinreg.exe - ArgumentList "/ q/u '" \\server\thinapplibraryshare\funnythinapp.exe'"'-wait.

  ----------------------------

  That works as well in most cases.

  But I recognized that over time some apps don't get uninstalled correctly.

  The difficulty that we always ran '% AppData%\Thinstall\Unregister\funnythinappfolder\uninstall.vbs' from inside the users session.

  Over time and after some testing I find that by using the 'uninstall.vbs' seems to be more reliable.

  So I decided to simply trigger all the "uninstall.vbs" at the close of session by using the following script.

  ----------------------------

  $thinapps = get-ChildItem-Path $env: appdata\thinstall\unregister-Recurse - include uninstall.vbs

  foreach ($uninstall in $thinapps) {Start-Process $uninstall - wait}

  ----------------------------

  This is not implemented if far cause there is one left issue I'm trying to understand.

  ----------------------------

  What is the difference between doing the unreg with "thinreg/u" and trigger the 'uninstall.vbs '?

  Thanks a lot for helping me to understand this.

  Best regards

  Simon

  Thinreg.exe/u need to run uninstall.vbs. Why is not as stable as execution of uninstall.vbs I do not know. In order to understand that we need more investigation... But in course of execution uninstall.vbs should be OK...

• Thinreg saves only a single shortcut among several

  I created a package for Websense Email Security 7.3, which has several shortcuts that connects with different executables in the program folder files. When I run a thinreg against the main executable file it does not create the shortcut for this and none of the others. If I install using the MSI file, it installs all the shortcuts. Package.ini attached. Any help would be appreciated.

  I found I can save each shortcut using thinreg manually, but the deployment of SCCM I'd really rather just register against a single object and get all the shortcuts.

  Have you tried to register multiple entry points using the command below:

  thinreg.exe /a ThinAppPath\ * .exe

• ThinReg deleted user of authorized groups

  Hi guys!

  We will start by describing the situation:

  App name: Firefox

  Groups permit = APP VIRTUAL FIREFOX

  ThinApp YOUR: 4.7.3

  Logon script: thinreg.exe \\foo\exe\firefox\firefox.exe

  I have registered the application for users with thinreg (streaming delivery) with a defined logon script to the AD user object, so each time a user connects, logon script is run (well, obviously). But then I removed a user from the only authorized group, APP VIRTUAL FIREFOX.

  The user still has the icon but it has no more to reach the anymove of the application, he receives a message from Inbox saying permission denied.

  So here are a few questions for you guys:

  -At the time of connection, if the application is already registered with thinreg, how thinreg will react? Will try to save, but stop because the application is already registered?

  -In my case, the user has deleted groups, but the icon is still there. I thought that thinreg what unregister the application if the user has not authorized and more. So when you want to cancel the registration of the application, that you guys are doing?

  This unregistring thing the application each time to login is a huge head in my opinion. I know thinreg loads itself into memory and then unload. I can't ignore the overhead created by this process (especially for the VDI environment) and I don't want to deploy the thinapp SDK on the workstations.

  I'd be happy to hear about the solution, you guys, put in place in your business!

  Thanks for your replies!

  tllp

  > In my case, the user has deleted groups, but the icon is still there. I thought that thinreg what unregister the application if the user has not authorized and more. So when you want to cancel the registration of the application, that you guys are doing?

  You think well, thinreg must be cancelled at the request if the user is no longer a part of the any groups mentioned in the PermittedGroups parameter. The unregister will not happen if ThinReg is executed with the parameter /k or /keep or /keppunauthorized. The only reason why it may fail to do so, otherwise is that if the uninstall/unregister script is missing on the computer (this script is generated during the process of registration of ThinReg for the same application), the location of the script located at HKEY_CURRENT_USER\Software\Thinstall\ThinReg\%InventoryName%_SomeNumber, InventoryName package/ini and when SomeNumber is a value. or the path of the script is located at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\, the file is called Uninstall.vbs.

  Thank you.

• Package does not create shortcuts (thinreg)

  I'm trying to package the windows administrative tools and create the fine package, but when I sign with Thinreg I can't see the shortcuts in the start menu.  If I navigate to the startmenu folder I can see shortcuts and if I run them it runs the thinapp program.  Is it something simple, I'm missing here that I can create shortcuts on the desktop and they spread out very well but I obviously don't want cluttering up the desktop with all of these shortcuts.

  Thank you

  To create a shortcut on the start menu, change the threshold in the package.ini for each EXE for

  Shortcuts = % admintools. %Select% programs

  If you want to create several shortcuts for different EXE, you can create them in a folder in the start menu:

  Shortcuts=%AdminTools%;%programs%\FOLDERNAME

  Rebuild the ThinApp running the build.bat file, delete no matter what tray existing sandbox and test.

• .dat or .msi in the ThinReg login script?

  When I create a ThinApp, I create an msi file, and sometimes ThinApp creates the .dat rather than the .exe file. I'm a bit puzzled as what to put in my login script that works ThinReg. Can I put \\server\path\xxx.dat or \\server\path\xxx.msi? Or is it important? Thank you.

  You use the exe (No .dat or msi) for ThinReg.

  The MSI file will contain ThinReg itself and that's why he recorded the ThinApp (ThinReg) when the MSI is installed.

  Please see this post on the use of login script ThinReg:

  http://blogs.VMware.com/ThinApp/2008/10/ThinApp-thinreg.html

• ThinReg without creating icon?

  Hello

  Is there a switch for ThinReg DO NOT create icons? We want the file associations, but not of icons created (on the desktop or in the start menu).

  THX.

  You can comment on the shortcuts = line for each entry point. For example.

  Front

  [Microsoft Access 2010.exe]
  Source=%ProgramFilesDir%\Microsoft Office\Office14\MSACCESS. EXE
  Shortcut = Microsoft Office Pro more 2010.dat
  Icon=%systemroot%\Installer\{90140000-0011-0000-0000-0000000FF1CE}\accicons.exe
  Types of files =.accda.accdb.accdc.accde.accdr.accdt.accdu.accdw.ade.adn.adp.mad.maf.mag.mam.maq.mar.mas.mat.mau.mav.maw.mda.mdb.mdbhtml.mde.mdn.mdt.mdw.wizhtml
  ObjectTypes = Access.ACCDAExtension; Access.ACCDCFile; Access.ACCDCFile.14; Access.ACCDEFile; Access.ACCDEFile.14; Access.ACCDRFile.14; Access.ACCDTFile; Access.ACCDTFile.14; Access.ACCFTFile; Access.ACCFTFile.14; Access.ADEFile; Access.ADEFile.14; Access.Application; Access.Application.14; Access.Extension; Access.Extension.14; Access.MDBFile; Access.MDEFile; Access.MDEFile.14; Access.Project; Access.Project.14; Access.WebApplicationReference.14
  Shortcuts=%programs%\Microsoft Office

  After

  [Microsoft Access 2010.exe]
  Source=%ProgramFilesDir%\Microsoft Office\Office14\MSACCESS. EXE
  Shortcut = Microsoft Office Pro more 2010.dat
  Icon=%systemroot%\Installer\{90140000-0011-0000-0000-0000000FF1CE}\accicons.exe
  Types of files =.accda.accdb.accdc.accde.accdr.accdt.accdu.accdw.ade.adn.adp.mad.maf.mag.mam.maq.mar.mas.mat.mau.mav.maw.mda.mdb.mdbhtml.mde.mdn.mdt.mdw.wizhtml
  ObjectTypes = Access.ACCDAExtension; Access.ACCDCFile; Access.ACCDCFile.14; Access.ACCDEFile; Access.ACCDEFile.14; Access.ACCDRFile.14; Access.ACCDTFile; Access.ACCDTFile.14; Access.ACCFTFile; Access.ACCFTFile.14; Access.ADEFile; Access.ADEFile.14; Access.Application; Access.Application.14; Access.Extension; Access.Extension.14; Access.MDBFile; Access.MDEFile; Access.MDEFile.14; Access.Project; Access.Project.14; Access.WebApplicationReference.14
  ; Shortcuts=%programs%\Microsoft Office

  This will keep the file associations and the object, but not create shortcuts in the folder start Menu\All Programmes\Microsoft Office

  Phil

• Two problems of thinreg against the .msi deployment

  Hello

  There are two things I can accomplish with .msi deployment but not with thinreg and two of them have to do with what appears after registration in "Add / Remove Programs ' in Control Panel.

  With the .msi deployment, I get an entry in the Panel "adding / deletion" which shows the correct icon for the application (i.e., the Photoshop icon) as well as the name of the manufacturer which can be specified through the MSIManufacturer variable in the package.ini.

  With the deployment of thinreg, I get an entry in the Panel "addition / deletion" that displays an icon (the same icon for all applications of thinregged) GENERIC and not specific to the correct application icon. Furthermore, the manufacturer field is empty.

  How is it possible to have the same functionality as the deployment .msi regarding the icon and the fields of manufacturer of control panel adding entries with the deployment of thinreg / remove programs?

  Thank you

  C3

  Currently is not possible. You can file a feature request

• Thinreg 4.5 incompatible with the previous version?

  We have recently updated since version 4.04 to 4.5. With the new version of thinreg.exe, we are unable to cancel the registration of the requests that are made using version 4.04. When we use thinreg version 4.04 unsubscribe works very well. Thinreg version 4.5 is compatible, I think it should, but it looks like there is an isue.

  Hello

  It seems that this issue has been recently reported by another client and was corrected internally.  Waiting for the next version I you need to use the version of Thinreg which comes with 4.0.4 if I'm not mistaken this version can be used to register and unregister packets time 4.0.4 and 4.5.

  Jonathan

• thinreg.exe error messages

  Hello

  In some cases, ThinReg.exe displays error messages and warnings on the desktop of the client computer. These messages can be confusing to our end users. We tried the option "/ quiet", but it does not prevent these error and warning messages.

  An example:

  A virtual application was provided to a client computer. The user has accidentally deleted the desktop icon. A < Virt.Applivcation.exe > ThinReg.exe/u' displays the warning: "errors occurred while uninstalling < Virt.» Application.exe >. Some files or registry keys can remain. "The user must leave the area by clicking on the OK" "button.

  Question:

  Could you provide an option that allows to direct all warnings and error messages in a log file. No errror box or warning message appears in the event that this option has been activated. This would allow us to transfer the log file in a central location and have it analyzed by an administrator.

  You have any other suggetions how the warning and error messages could be deleted?

  / Achim

  I asked around and switch/q should suspend this message. It seems that the functionality of / q is now defective.

• ThinReg and shortcuts

  I tested VMWare View with ThinApp. I Thinapp had Office 2007 and copied the exe files to a network share location. Also, I copied the ThinReg.exe file to this share. I created a login script that runs thinreg to save Office applications. When I look at execution of script thinreg statement runs without error. I can look in "Add/Remove Programs" and see the Office as (VMWare ThinApp) installation. My problem is that I see no shortcuts. I created a roaming profile with folder redirection.

  When I open a document, it opens Word 2007 so I know he sees the app. Why can't I see no shortcuts?

  Thank you.

  Hi snowmizer,

  I hope that you have captured all the shortcuts that are necessary before the postscan process. OK I'll tell you how to do this.

  1. make the prescan to a clean machine.

  2. installation of Microsoft office 2007

  3. go in the C; \program files\office 12 directory

  4. here you will see icons for all the applications of sup of 2007 office, such as Word 2007, Excel 2007, Outlook 2007 etc.

  5 right-click on the icon and send the shortcut on the desktop. This way send all needed shortcuts on the desktop.

  6. can run applications with these shortcuts and make sure they are properly launched.

  7. now make analysis post and at the ports of entry, you will find all of these shortcuts for exe files. They are selected by default.

  8 complete the postscan and build binaries for all the office 2 k 7 package.

  9. then register all exes including files exe for shortcuts

  10. When you have registered with the thinreg utility exe files you will find all the shortcuts on the desktop of your computer.

  To do this, and I am sure that you will get all the shortcuts. I hope this information is useful.

  Thank you and best regards,

  Patricia S.

• Thinreg.exe location

  I need to save files in a view using ThinApp deployment. I guess that the registration file is done using thinreg.exe on the network share where the application. When I try to run thinreg.exe, I get the message that the file is basically not found.

  Where is the thinreg.exe?

  When you install the tools of ThinApp, thinreg is installed in C:\Program VMware ThinApp\thinreg.exe. You can copy from there and put it on any place you want.

• The use of SMS for ThinReg an application with elevated permissions

  I ran a very specific scenario that left me speechless for awhile. I thought I'd share incase any who found themselves in the same position. Here's the scenario:

  I have a ThinApp application that resides on a network share. I used "PermittedGroups = domain users" in the package.ini to ensure the application was used only on campus for purposes of licensing. I tried ThinReg the application for all users (.\thinreg.exe/r/a network\appname.exe) on about 300 computers using SMS. Most of these users are local administrators on their computers , but not all. Therefore, in cases where the user is not a local administrator, the registration script would fail. The great advantage of SMS gives us when deploying applications is that we can elevate permissions and perform the installation under the local SYSTEM account. With MSI and these that works beautifully, but in this scenario, there is not. The problem is that the local SYSTEM account is not a member of the group "Domain users" and therefore was not allowed to run (or ThinReg) executable file. I've thought about it a while and decided to add the domain group "Computers in the domain" to the PermittedGroups list. To my disappointment, it does not solve the problem. After much trial and error, I changed the Package.ini to read PermittedGroups = domain users; SYSTEM

  It worked! SMS is able to raise the installation so that account SYSTEM and the application successfully ThinReg. "Domain users" are able to run the application, while local users are not. I even tried to create a new user account called SYSTEM on my test XP machine to see if I could it crazy that way, but the OS won't let you create a user account with this name. I'm not entirely sure why this works; the PermittedGroups = parameter is designed to contain groups, not users. If someone saw, I would be happy to hear it. If not, hope it can help someone.

  ~ spence

  Hey Spence,

  Interesting. What version of ThinApp did you use? We changed Thinreg in 4.0.1 so it doesn't look like PermittedGroups when you use the switch/a, for exactly the reason why you have described. Of course, PermittedGroups is always checked when executing.

• Thinreg error: "cannot save...". "

  Hello.

  I'm testing Thinapp and always gets the error "unable to save...". "while executing"thinreg.exe c:\temp\applicationname.exe ".

  The error only occurs when the PermittedGroups option is set in package.ini.

  Are there opportunities to enable logging or debugging, because I have no idea why I get this error?

  Thank you

  robbe1874

  You will get this error with Thinreg 4.0.1 - 2866 when you use thinreg without the option "/ a" and you are not a member of a groups listed in PermittedGroups. When you use PermittedGroups, I suggest using Thinreg 4.0 - 2200, which doesn't have this problem.