WinRar as RemoteApp using Remote Desktop Services
Dear Team,
I am using RemoteApp feature on Windows 2008 R2 SP1 with Remote Desktop Services.
I published Microsoft Office 2010, Adobe Reader and WinRar for users desktops...
All applications are working as expected except WinRar.
User are able to open any compressed document but are not able to compress (Add to Archive). The feature "Add to Archive" is not available for the user when he select a folder and needs to compress it. I tried WinRar and add to Archive manually, but still no success.
The feature (Take Over Client Extensions) is used when creating the .msi packages, the user can open any file directly by double click on the file.
How can I solve the WinRar issue?
WinRar on the RDS host is fully functional, I can right click and add to archive any folder/document.
Thank you.
Regards,
I am using RemoteApp feature on Windows 2008 R2 SP1 with Remote Desktop Services.
I published Microsoft Office 2010, Adobe Reader and WinRar for users desktops...
All applications are working as expected except WinRar.
User are able to open any compressed document but are not able to compress (Add to Archive). The feature "Add to Archive" is not available for the user when he select a folder and needs to compress it. I tried WinRar and add to Archive manually, but still no success.
The feature (Take Over Client Extensions) is used when creating the .msi packages, the user can open any file directly by double click on the file.
How can I solve the WinRar issue?
WinRar on the RDS host is fully functional, I can right click and add to archive any folder/document.
Thank you.
Regards,
ASKER
Dear Filipe,
I installed WinRar on the RDSH using control panel\Install Application on Remote Desktop Services mode.
It's available for all users.
Please advise.
Thank you.
I installed WinRar on the RDSH using control panel\Install Application on Remote Desktop Services mode.
It's available for all users.
Please advise.
Thank you.
Ok.
I'm assuming you add the change user /Install command and then when installation finished the change user /Execute.
If you don't know what it the status you can see the current mode by using: change user /Query.
Is Winrar 64bit version? the fact you are able to do everything except to compress leads to an issue specifically with the Winrar application.
I would advise you to use another method to install Winrar by creating a .msi (Windows Installer) package for the terminal application. This thus is to be installed on the user machine just like an ordinary application. Give it a try with a single user and see how Winrar is behaving.
After the installation, the user will have Winrar available in the Start menu or on the desktop.
This will make the file association with the proper file extensions on the local computer.
I'm assuming is not the nice to have solution since there is some extra effort, but, you may then deploy the msi package via Group Policy and make it available for all users.
Hope it helps,
Rgds,
GFilipe
I'm assuming you add the change user /Install command and then when installation finished the change user /Execute.
If you don't know what it the status you can see the current mode by using: change user /Query.
Is Winrar 64bit version? the fact you are able to do everything except to compress leads to an issue specifically with the Winrar application.
I would advise you to use another method to install Winrar by creating a .msi (Windows Installer) package for the terminal application. This thus is to be installed on the user machine just like an ordinary application. Give it a try with a single user and see how Winrar is behaving.
After the installation, the user will have Winrar available in the Start menu or on the desktop.
This will make the file association with the proper file extensions on the local computer.
I'm assuming is not the nice to have solution since there is some extra effort, but, you may then deploy the msi package via Group Policy and make it available for all users.
Hope it helps,
Rgds,
GFilipe
ASKER
Hello Filipe,
Yes, I am using WinRar 64 bit version.
I already mentioned above that I created a .msi packages in RemoteApp console for all my applications, then I deployed the packages using group policy\software installation for all users.
This has been done along with (Take Over Client Extensions).
In the RDSH server I am able to compress but not from the user clients.
What would you advise?
Regards,
Yes, I am using WinRar 64 bit version.
I already mentioned above that I created a .msi packages in RemoteApp console for all my applications, then I deployed the packages using group policy\software installation for all users.
This has been done along with (Take Over Client Extensions).
In the RDSH server I am able to compress but not from the user clients.
What would you advise?
Regards,
ASKER
Dear Filipe,
change user /Query = Status
Application EXECUTE Mode is enabled...!
Please advise.
Regards,
change user /Query = Status
Application EXECUTE Mode is enabled...!
Please advise.
Regards,
Hi,
Indeed you mentioned and it is correct if .msi package, along with the take over client extensions, this should be ok.
So lets dig in to Winrar:
We have two issues with Winrar as far as I can see:
- Context Menus (Right click and add to archive);
- Manually no able to compress;
Context menus:
According to Winrar license help file they state 2 types of licenses:
. A single computer USAGE license. The user purchases ONE license to USE the WinRAR archiver on ONE computer;
. A multiple usage license. The user purchases a number of usage licenses for use, by the purchaser or the purchaser's employees on the same number of computers.
Also if you have no license at all Winrar will behave as Single computer Usage License.
What license type do you have?
If in your case are you are using the single computer usage license there are several solutions:
1. please check a detailed turnarround for a similar issue you have:
http://virtualengine.co.uk/2012/move-machine-based-context-menus-to-per-user-part-i/
2. If this is a licensing problem you can also try the 7-Zip that is Free under GNU licensing.
Manually not able to compress:
This is intriging, can you please detail a bit more? when you open winrar, is the "Add" button greyed when you select a file or folder?
Do you have the button available but it does not work? or an error is displayed?
Let us know so we can understand if it is a license issue or any other specific program.
Rgds,
GFilipe
Indeed you mentioned and it is correct if .msi package, along with the take over client extensions, this should be ok.
So lets dig in to Winrar:
We have two issues with Winrar as far as I can see:
- Context Menus (Right click and add to archive);
- Manually no able to compress;
Context menus:
According to Winrar license help file they state 2 types of licenses:
. A single computer USAGE license. The user purchases ONE license to USE the WinRAR archiver on ONE computer;
. A multiple usage license. The user purchases a number of usage licenses for use, by the purchaser or the purchaser's employees on the same number of computers.
Also if you have no license at all Winrar will behave as Single computer Usage License.
What license type do you have?
If in your case are you are using the single computer usage license there are several solutions:
1. please check a detailed turnarround for a similar issue you have:
http://virtualengine.co.uk/2012/move-machine-based-context-menus-to-per-user-part-i/
2. If this is a licensing problem you can also try the 7-Zip that is Free under GNU licensing.
Manually not able to compress:
This is intriging, can you please detail a bit more? when you open winrar, is the "Add" button greyed when you select a file or folder?
Do you have the button available but it does not work? or an error is displayed?
Let us know so we can understand if it is a license issue or any other specific program.
Rgds,
GFilipe
ASKER
Thank you dear Filipe for your reply,
Actually, I am using a single license for WinRar X64.
For point number 1- If I logged in locally on the RDSH, I can right click any file or folder then click "Add to Archive..", but this option is not available when I use WinRar as RemoteApp from a client machine, right click Add to Archive is not available.
For point number 2- Manually compress.
I opened WinRar application from a client, The Add button is not grayed out, I click on it.
But I am not able to browse to the folder or file need it to compress it (archive it).
If someone send me an archived file, I can click on it and open it, no issue with the extract option.
How can I uninstall WinRar from an RDS host?? Is it like normal application (Program Features\Uninstall).
For installation, I need to use the Change user /install and /execute.
Please advise.
Thank you.
Actually, I am using a single license for WinRar X64.
For point number 1- If I logged in locally on the RDSH, I can right click any file or folder then click "Add to Archive..", but this option is not available when I use WinRar as RemoteApp from a client machine, right click Add to Archive is not available.
For point number 2- Manually compress.
I opened WinRar application from a client, The Add button is not grayed out, I click on it.
But I am not able to browse to the folder or file need it to compress it (archive it).
If someone send me an archived file, I can click on it and open it, no issue with the extract option.
How can I uninstall WinRar from an RDS host?? Is it like normal application (Program Features\Uninstall).
For installation, I need to use the Change user /install and /execute.
Please advise.
Thank you.
Hi,
For your information:
When you install package using the MSI, you can remove the package using the App-V Client Console (sftcmc.msc) or an SFTMIME command, but that won't remove the entry in Programs and Features.
The MSI is a seperate component that doesn't really have any relation to the App-V package, other than that's how the package was added to the client.
To remove the package:
You can either remove the package by using program and features (I would advise this method - but also remove the GPO from the OU's). Or you can uninstall via GPO to each client (by using the uninstall feature in GPO - delete de software package it will ask you if you want to uninstall the program from clients where you will select yes uninstall from clients.)
If for some reason, after the installation the program is still available to the clients then you should use the App-V Client Console (sftcmc.msc) and first do the Change user /install. Once finished add the /execute.
Hope this helps,
Rgds,
GFilipe
For your information:
When you install package using the MSI, you can remove the package using the App-V Client Console (sftcmc.msc) or an SFTMIME command, but that won't remove the entry in Programs and Features.
The MSI is a seperate component that doesn't really have any relation to the App-V package, other than that's how the package was added to the client.
To remove the package:
You can either remove the package by using program and features (I would advise this method - but also remove the GPO from the OU's). Or you can uninstall via GPO to each client (by using the uninstall feature in GPO - delete de software package it will ask you if you want to uninstall the program from clients where you will select yes uninstall from clients.)
If for some reason, after the installation the program is still available to the clients then you should use the App-V Client Console (sftcmc.msc) and first do the Change user /install. Once finished add the /execute.
Hope this helps,
Rgds,
GFilipe
ASKER
Dear Filipe,
Please note that I am not using Application Virtualization (App-V). I didn't mention an App-V Infrastructure.
I am using pure RDS environment with RemotApp built-in feature.
The App-V client agent is not installed on the client machine. No App-V.
Please advise.
Regards,
Please note that I am not using Application Virtualization (App-V). I didn't mention an App-V Infrastructure.
I am using pure RDS environment with RemotApp built-in feature.
The App-V client agent is not installed on the client machine. No App-V.
Please advise.
Regards,
Hi,
If that is the case then you can follow the procedure mentioned to remove the package:
change user /install (I should mention that Server will be unavailable for users on this mode)
I would remove Winrar by using program and features (but also remove the GPO from the OU's otherwise will be installed afterwards on user logon).
Once Uninstall is finished get server again into execution mode:
change user /execute
This should do it.
I've been doing some extra checking and indeed it seems for both point 1 but also point 2 that this is a Winrar issue with licensing since the application is user based with this licensing.
Rgds,
GFilipe
If that is the case then you can follow the procedure mentioned to remove the package:
change user /install (I should mention that Server will be unavailable for users on this mode)
I would remove Winrar by using program and features (but also remove the GPO from the OU's otherwise will be installed afterwards on user logon).
Once Uninstall is finished get server again into execution mode:
change user /execute
This should do it.
I've been doing some extra checking and indeed it seems for both point 1 but also point 2 that this is a Winrar issue with licensing since the application is user based with this licensing.
Rgds,
GFilipe
ASKER
Thank you Filipe for your help.
So what do you suggest to do with WinRar?
Will we use below link or we will use 7-Zip instead.?
http://virtualengine.co.uk/2012/move-machine-based-context-menus-to-per-user-part-i/
Indeed this is a WinRar issue, How can we solve it?
Regards,
So what do you suggest to do with WinRar?
Will we use below link or we will use 7-Zip instead.?
http://virtualengine.co.uk/2012/move-machine-based-context-menus-to-per-user-part-i/
Indeed this is a WinRar issue, How can we solve it?
Regards,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It could be that Winrar on the RDS host is not installed for all users? Could be that it was installed only for the user that performed the installation.
Rgds,
GFilipe