The Experts below are selected from a list of 3 Experts worldwide ranked by ideXlab platform
James Sabovik - One of the best experts on this subject based on the ideXlab platform.
-
Integrating application and presentation virtualization (Terminal Services)
Microsoft Virtualization, 2009Co-Authors: Thomas Olzak, Jason Boomer, Robert M. Keefer, James SabovikAbstract:Two file-based methods can be employed for distributing Remoteapp Programs to users. The first is to create a Windows Installer package file (.msi), which can then be distributed and installed in a manner like traditional locally installed Programs. The second is to create a Remote Desktop Protocol file (.rdp) that launches the remote application without the need to perform an install. Terminal Services allows for the easy creation of a Windows Installer package file, commonly referred to as an .msi file. This method installs the Remoteapp to appear like a conventional local installation. The method is chosen by users who want to make the virtualization aspect of the Remoteapp Program nearly invisible to end users. Once the .msi file is created, one can distribute it to an enterprise via existing distribution methods, such as Microsoft System Center Configuration Manager or through an Active Directory Group Policy Object. Terminal Services has its own file type for running a Remoteapp Program that Windows recognizes and treats appropriately. The file type is .rdp, which stands for Remote Desktop Protocol. This is a standalone executable that can be accessed from a simple file share or dropped on a client PC.
Thomas Olzak - One of the best experts on this subject based on the ideXlab platform.
-
Integrating application and presentation virtualization (Terminal Services)
Microsoft Virtualization, 2009Co-Authors: Thomas Olzak, Jason Boomer, Robert M. Keefer, James SabovikAbstract:Two file-based methods can be employed for distributing Remoteapp Programs to users. The first is to create a Windows Installer package file (.msi), which can then be distributed and installed in a manner like traditional locally installed Programs. The second is to create a Remote Desktop Protocol file (.rdp) that launches the remote application without the need to perform an install. Terminal Services allows for the easy creation of a Windows Installer package file, commonly referred to as an .msi file. This method installs the Remoteapp to appear like a conventional local installation. The method is chosen by users who want to make the virtualization aspect of the Remoteapp Program nearly invisible to end users. Once the .msi file is created, one can distribute it to an enterprise via existing distribution methods, such as Microsoft System Center Configuration Manager or through an Active Directory Group Policy Object. Terminal Services has its own file type for running a Remoteapp Program that Windows recognizes and treats appropriately. The file type is .rdp, which stands for Remote Desktop Protocol. This is a standalone executable that can be accessed from a simple file share or dropped on a client PC.
Jason Boomer - One of the best experts on this subject based on the ideXlab platform.
-
Integrating application and presentation virtualization (Terminal Services)
Microsoft Virtualization, 2009Co-Authors: Thomas Olzak, Jason Boomer, Robert M. Keefer, James SabovikAbstract:Two file-based methods can be employed for distributing Remoteapp Programs to users. The first is to create a Windows Installer package file (.msi), which can then be distributed and installed in a manner like traditional locally installed Programs. The second is to create a Remote Desktop Protocol file (.rdp) that launches the remote application without the need to perform an install. Terminal Services allows for the easy creation of a Windows Installer package file, commonly referred to as an .msi file. This method installs the Remoteapp to appear like a conventional local installation. The method is chosen by users who want to make the virtualization aspect of the Remoteapp Program nearly invisible to end users. Once the .msi file is created, one can distribute it to an enterprise via existing distribution methods, such as Microsoft System Center Configuration Manager or through an Active Directory Group Policy Object. Terminal Services has its own file type for running a Remoteapp Program that Windows recognizes and treats appropriately. The file type is .rdp, which stands for Remote Desktop Protocol. This is a standalone executable that can be accessed from a simple file share or dropped on a client PC.
Robert M. Keefer - One of the best experts on this subject based on the ideXlab platform.
-
Integrating application and presentation virtualization (Terminal Services)
Microsoft Virtualization, 2009Co-Authors: Thomas Olzak, Jason Boomer, Robert M. Keefer, James SabovikAbstract:Two file-based methods can be employed for distributing Remoteapp Programs to users. The first is to create a Windows Installer package file (.msi), which can then be distributed and installed in a manner like traditional locally installed Programs. The second is to create a Remote Desktop Protocol file (.rdp) that launches the remote application without the need to perform an install. Terminal Services allows for the easy creation of a Windows Installer package file, commonly referred to as an .msi file. This method installs the Remoteapp to appear like a conventional local installation. The method is chosen by users who want to make the virtualization aspect of the Remoteapp Program nearly invisible to end users. Once the .msi file is created, one can distribute it to an enterprise via existing distribution methods, such as Microsoft System Center Configuration Manager or through an Active Directory Group Policy Object. Terminal Services has its own file type for running a Remoteapp Program that Windows recognizes and treats appropriately. The file type is .rdp, which stands for Remote Desktop Protocol. This is a standalone executable that can be accessed from a simple file share or dropped on a client PC.