2012 RemoteApp: file associations windows 8 only?

I am currently testing RemoteApp and it currently looks like the only way to setup file associations is to set "Specify default connection URL" under RemoteApp and Desktop Connections. This setting requires at least 2012, 8, or RT. Is there any way to
get this to work in windows 7? This is a feature we would really like to use.

Hi skeiffer_,
I will provide an example for you, in this case Adobe Reader XI as a RemoteApp with .pdf file association on Windows 7 client PC. You may use it as a general pattern for other RemoteApps.
1. On the client PC, in the user's registry, we need to add the following (contents of .reg file below):
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Classes\Adobe.Reader.XI]
"AppUserModelId"="Microsoft.Windows.RemoteDesktop"
"EditFlags"=dword:00100000
[HKEY_CURRENT_USER\Software\Classes\Adobe.Reader.XI\DefaultIcon]
@="C:\\Users\\Public\\Documents\\RemotePackages\\AcroRd32.ico,0"
[HKEY_CURRENT_USER\Software\Classes\Adobe.Reader.XI\shell]
[HKEY_CURRENT_USER\Software\Classes\Adobe.Reader.XI\shell\open]
[HKEY_CURRENT_USER\Software\Classes\Adobe.Reader.XI\shell\open\command]
@="\"mstsc.exe\" /REMOTEFILE:\"%1\" \"C:\\Users\\Public\\Documents\\RemotePackages\\AcroRd32.rdp\""
[HKEY_CURRENT_USER\Software\Classes\.pdf]
@="Adobe.Reader.XI"
[HKEY_CURRENT_USER\Software\Classes\.pdf\Adobe.Reader.XI]
[HKEY_CURRENT_USER\Software\Classes\.pdf\Adobe.Reader.XI\ShellNew]
2. We need to make sure two files are present on the local PC:
C:\Users\Public\Documents\RemotePackages\AcroRd32.ico
C:\Users\Public\Documents\RemotePackages\AcroRd32.rdp
The above two files are downloaded to the client PC from the 2012 RDWeb feed automatically when you set up a connection in RemoteApp and Desktop Connections in the control panel. Once it has been set up you may right-click on one of the RemoteApp shortcuts
to find the path where the files are stored so that you may copy them to where you need them.
Usually the path will be something like C:\Users\<username>\AppData\Roaming\Microsoft\Workspaces\<GUID>\Icons and \Resource, but it may be different depending on if redirected folders are in use.
You may use group policy preferences, scripting, installer exe, etc. as methods to copy the files and create the necessary registry entries on the client PCs/user profiles.
If you need to associate a second file extension with the same RemoteApp, for example .fdf for Adobe Reader XI, you could duplicate the last three registry entries and change them to the new extension (.pdf to .fdf in this case).
-TP
Hi,
this worked fine for me.
Thanks Dominik

Similar Messages

2012 RemoteApp: file associations Emal links and Send to Mail Recipient.

Hello
Is it possible to get Outlook 2013 Remote app to open when you use "send to Mail Recipient"and click email to links?
/Andreas
/Andreas

Hi,
Thank you for posting in Windows Server Forum.
As per my research, the way you are trying to open Outlook 2013 RemoteApp is not possible.
Thanks for your understanding and support!
Regards.
Dharmesh Solanki
TechNet Community Support

RemoteApp file associations for non-domain computers

I have a customer with a simple AD domain, and some joined and some workgroup computers, all windows 8.1 pro. I want to connect them to my remote app service. We want to create a "default connection" for this remote app service, specifically for
the file type associations. We tried using the default connection group policy, but credentials are a problem. The remote app service has its own domain. So the "default connection" created by the group policy is trying to use the local logon credentials.
Is there a way to specify what default credentials are to be used for the remoteapp "default connection" using credential manager? Or is there a better way to accomplish remote app file type associations all together using non-domain joined Windows
8.1 and 2012R2 remote app on a different domain?

Hi,
For your case, you can try the following way. You can create the RDP file as what you want and then publish that RDP file as RemoteApp with default user credentials. When non-domain joined system will get access to RD Web they will launch the RemoteApp as they
are using the other apps, the RDP file App will first get connect to the RDS Farm server name which is displayed and try to resolve that name through gateway or any other method which is configured. Once got resolve it will use the default user credentials
to connect to that user and then the user can use that RDP file to connect to the respective Server.
Apart for file type association you can go through the detailed article for more information.
Windows Server 2012 RemoteApp and Desktop Connections: Default Connections and File Type Associations
http://blogs.msdn.com/b/rds/archive/2013/05/21/windows-server-2012-remoteapp-and-desktop-connections-default-connections-and-file-type-associations.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Default File Associations - Windows 8 - override?

Hello,
will the following Policy override the already set file associations?
Computer Configuration\Administrative Templates\Windows Components\File Explorer\Set a default associations configuration file
I am asking because I want to add some file associations and it would be terriable, if all other associations would be deleted. Cant find anything documented.

Hi,
Based on my understanding, if we associate specific file type or protocol with default applications in the file, this default association should overwrite previous associations
set to these file types or protocols.
Besides, if this group policy is enabled, the file will be processed and default associations will be applied at logon time.
However, even if this policy is enabled, users will still be able to override default file type and protocol associations.
Regarding this setting, the following article can be referred to for more information.
Windows 8: Associate a file Type or protocol with a specific app using GPO (e.g:default mail client for MailTo protocol)
http://blogs.technet.com/b/mrmlcgn/archive/2013/02/26/windows-8-associate-a-file-type-or-protocol-with-a-specific-app-using-a-gpo-e-g-default-mail-client-for-mailto-protocol.aspx
Best regards,
Frank Shen

No file association for PDF files

I have installed Adobe Reader on my Nokia E70 (Series 60 3rd edition). I am able to open PDF files, provided they are very small ;-) directly from within Adobe Reader, but not via File Manager. Does anyone know how to set the file association of .PDF extension to open with Adobe Reader?
Cheers
-- Mike --

>It worked for me but the solution was not an intuitive one. Seems like Adobe should work out this kink for future customers.
The fact that you had a problem suggests that it's your system, not Adobe that is the root cause. A successful and undamaged installation WILL create the proper file associations, and will even use the correct version icon for older files (in Windows, though, only one version of the application -- the last one installed -- will be associated with the open command from Explorer or Bridge).
Peter

No file association for ID CS3

I have a fairly new Windows XP box and have configured my Adobe the same way as on my last computer: Full CS3 Design Premium installation, plus ID CS2 (for compatibility reasons). All of my .indd files are associated with ID CS2. Okay, I guess it must be because I installed CS2 2nd.
No problem. I just went into Windows Explorer to change the file association to ID CS3. But ID CS3 is not listed in the program list. So I browsed to C:\Program Files\Adobe\Adobe InDesign CS3\InDesign.exe and clicked okay. But the association does not change. The icon and program association remain ID CS2. One last tidbit: In Windows Explorer, if I right-click an .indd file to "open with", the only program available is ID CS2.
All the above applies to Bridge as well as Windows Explorer.
I have to open my .indd files by starting ID CS3 and opening from w/in the program or by dragging a file to the open program window. If I'm in Bridge and I forget and double-click on a file, it loads ID CS2 and then tells me I can't open the file.
I assume something happened in the Registry that shouldn't have (or didn't happen that should have), but I don't understand why Windows won't let me manually associate the file type.
Any ideas on how to help Windows find ID CS3 without reinstalling the program?
Thanks,
-David

>It worked for me but the solution was not an intuitive one. Seems like Adobe should work out this kink for future customers.
The fact that you had a problem suggests that it's your system, not Adobe that is the root cause. A successful and undamaged installation WILL create the proper file associations, and will even use the correct version icon for older files (in Windows, though, only one version of the application -- the last one installed -- will be associated with the open command from Explorer or Bridge).
Peter

File associations in Bridge CC after updating to CC 2014

I am facing a problem with the file association settings in Bridge CC after having updated my other creative suite programs to version CC 2014.
In previous version I had the option when opening eg. PDF file to chose "open with", and then chose Illustrator or Photoshop. This option is no longer available. When using the Preference menu under file association I can only change the default settings to be either Acrobat or for some reason Firefox. When browsing for Illustrator or Photoshop and choosing the program the PDF file will only open in Illustrator or Photoshop as default not Acrobat as it is suppose to. Does anybody have a solution to this problem.

Thank you for the answer, but is doesn't fix the problem. The explorer settings lets me open pdf files in Acrobat, Illustrator or Photoshop.
The problem is that Bridge doesn't allow me to open pdf files in Illustrator.
When trying to solve the problem by altering the file type association settings, browsing and choosing Illustrator CC 2014, the pdf files will then open by default in Illustrator, and this is not what i want. I want the option to chose, open with Illustrator, and still have Acrobat as the default program.
Anybody know how to fix this?

RemoteApp 2012 and File Type Associations

Hi, All :),
the scenario is like this - 2 x Server 2012: one as the RD Connection Broker and RD Web Access and one as the RD Session Host (clients are Windows 7). ALMOST everything works: there is one collection, several applications, all successfully thrown into
the RemoteApp and Desktop Collections by GPO (Powershell script - http://gallery.technet.microsoft.com/ScriptCenter/313a95b3-a698-4bb0-9ed6-d89a47eacc72/).
But one thing doesn't work - file type associations. Well, I want the client without, for example, Office installed to open the RemoteApp application (Excel) by clicking on the XLSX file. When looking at the application properties -> File Type Associations
-> Current Associations column, I see the name of the collection, which includes Excel ... but it does not work. After updating the RemoteApp and Desktop Connections on the client, the RDP file with Excel noticed a new line:
remoteapplicationfileextensions: s:. csv,. xls,. xlsx,. xltx
How do I make it work? I know that in RemoteApp on Server 2008R2 you could export the MSI file that took care of File Type Associations, but what to do in case of Server 2012?

Unfortunately, the feature to install file type associations for RemoteApp programs in your GPO-pushed RemoteApp and Desktop Collection is only supported on Windows 8 clients. Several improvement were made over the old MSI-based file type associations, and
those improvements rely upon changes in the Windows 8 OS.
Ultimately file type associations are controlled with registry keys, all of which are documented on MSDN. RemoteApp programs are pretty much the same as any other local program, except the file type is associated with mstsc.exe with some special parameters.
Although the way we register those file type associations in Windows 8 won't work for you, the way the old MSIs used to register them would. You could in theory register the RemoteApp file type associations yourself in the same way that one of the old MSIs
would have done (you could use some sort of GPO-pushed script on the clients).
The easiest way to do this would be to track down one of those old MSIs, install it, and do a before-and-after view of the registry to see what changes it makes.
Hope that helps,
Travis Howe | RDS Blog: http://blogs.msdn.com/rds/default.aspx

Quick Time Hijacks Windows File Associations Only From Web Browsers

It took me 6 hours this morning to conclusively prove that Quick Time (latest version) isn’t playing well with web browsers on my Windows XP Pro (SP3) machine (nothing new here I guess).
I develop web sites which get their content from local hard or DVD/CD drives (as opposed to from the internet). All my Windows file associations for audio/video file types point to Windows Media Player (WMP) so that when one of my web pages looks for a file type of say .mpg or .mp3, WMP is opened and the file is played. Pretty straight forward and has worked fine for years.
Some time in the last few months (and I now strongly suspect after a Quick Time update) my browsers (all of them….. IE, Firefox, and Chrome) started opening Quick Time instead of WMP when my HTML goes to open any media file type. I’ve checked my Windows file associations which all still point to WMP. I also note that when I open one of my media files from a file utility such as Windows Explorer or my aftermarket file utility (as opposed to from a browser), they correctly open in WMP. So…….. its only from browsers that QT hijacks my intended media player.
In Internet Explorer I’ve gone to “Manage Add-Ons” and “disabled” Quick Time. This in fact causes QT not to be opened but instead a blank web page appears containing only the browser’s little error box with a big red X in it which usually means a picture file is missing…… WMP is not launched even though it is enabled in Manage Add-Ons and QT is disabled.
The only way I’ve found to fix this problem is to uninstall Quick Time in which case everything works fine. (My objection to Quick Time as my default media player is that even the latest version doesn’t reliably play video created for Windows file types.)
Can anyone tell me how to make Quick Time co-exist on my computer without hijacking my attempts to get at WMP from browsers?
The only reason Quick Time has existed on my computer in recent years is so I have access to iTunes. I’ve uninstalled both Quick Time and iTunes till I find a solution to this problem which means iTunes isn’t selling me anything in the mean time.

I'm having the same issue that Quicktime hijacks file associations.
I recently reinstalled my copy of Windows 7 64-bit and have installed basically hardly anything on it. I have however installed iTunes (+Quicktime) for my iPhone and Winamp (and not even loaded Windows Media Player).
Basically when I uninstall Quicktime, I can just type an url in the IE8 address bar with the .mp3 extension and download and save the file there and then. Only after installing Quicktime the browser will open the .mp3 in the window and play it embedded with the Quicktime player.
This is something I do NOT want, and I am really ****** off that Quicktime just takes over this feature without asking me first!!
That being besides the point really because I also cannot find the option in Quicktime's settings to undo this!!
When I go to Quicktime's settings -> Browser -> MIME types
It just shows that .mp3 is linked to Winamp (like I want it to be), but it still opens as a Quicktime Control Object.
Reinstalling IE8, resetting its settings, disabling the iTunes & Quicktime addons, even removing the Quicktime Control Object class from the registry... Nothing worked!
http://www.archive.org/details/testmp3testfile
Here you can find an mp3 file to use for testing.

File associations not roamed using Remote Desktop Server 2012 R2 Standard

Hello everyone,
As the title mentions, some File Associations does not seems to roam on a RDS 2012 R2 server. We use the following configuration:
Windows Server 2012 R2 Remote Desktop Server(s)
Roaming Profiles to a user based network share
Delete cached copies of Roaming profiles [Computer GPO]
So there is no local stored profile after logoff.
Exclude directories in roaming profile [User GPO]
We only exclude "$Recycle.Bin" for testing. So all other profile settings (Local, LocalLow, Roaming) should be roamed.
With the above settings, some associations are, after logoff and logon not remembered. For example .pdf is always restored to MS Word even if Acrobat Reader is chosen as default program.
When we do not delete the cached copy of the Roaming profile [Computer GPO], the file associations are remembered after logoff and logon.
We did a little of research:
When changing the default application for PDF files to Acrorobat Reader, the setting for this user in the registry is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice
Hash: BTWAFQFaLiw=
ProgId: AcroExch.Document.11
After logging off, the NTUSER.DAT for this users does contains the same settings. I guess the settings are successfully roamed to the shared roaming folder.
But after login, the settings are set back to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice
Hash: mj3iGjB82bU=
ProgId: AppX86746z2101ayy2ygv3g96e4eqdf8r99j
My suggestion is these settings are not restored in the cached roaming profile.
Someone who recon this and knows if there is a solution for this issue?
Using a Association Configuration File (DISM) with the Computer GPO Setting "Set a default association configuration file", we can set the default program for the users. But this is a global Computer GPO setting and not all users must have the same
default programs.
Using this setting is no option for our environment.
Hope Someone can help us.

Hi,
For this you can make one separate group for all that users and applied the policy setting which you want to setup. But as per me, windows uses the Local and LocalLow folders for application data that does not roam with the user. Usually this data is either
machine specific or too large to roam. Maybe your thought would be a workaround.
More information.
Deploy Roaming User Profiles
https://technet.microsoft.com/en-us/library/jj649079.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

File associations in Windows 8.1 for applications on a network location

Hi,
From Windows 7 to Windows 8 it has been done alot of changes regarding file file assocations. It seem that the main reason was security and was "patched" by having Windows read the hash for the applications instead of where the application was
located.
but there seem to be some major hicups and there is limited info on the web covering these issues.
First issue: when running: Dism /Online /Export-DefaultAppAssociations:\\Server\Share\AppAssoc.xml and then creating a GPO configuration pointing to
thi XML file. With this feature only common file extensions is supported and when users are changing to another computer, these settings is not possible to syncronize using roaming profiles.
Second issue: In the appassoc.xml file applications must be either appid(metro app) or common application on local harddrive to be registered and not a .EXE
file on a network location.
It seems a little strange if this is the case and if there is no other options for administratos to set file associations in more flexible ways. Does anyone have some more info on
this topic other than these link:
https://technet.microsoft.com/en-us/library/hh825038.aspx?f=255&MSPPError=-2147217396
http://blogs.technet.com/b/mrmlcgn/archive/2013/02/26/windows-8-associate-a-file-type-or-protocol-with-a-specific-app-using-a-gpo-e-g-default-mail-client-for-mailto-protocol.aspx
https://keithga.wordpress.com/2013/11/13/file-associations-in-windows-8/

Hi Primeid,
You could use Group policy for file associations or you could deploy the xml file during image deployment. However as you mentioned that the file associations only applies to common application on local hard drive or metro app.
http://blogs.technet.com/b/mniehaus/archive/2014/01/10/configuring-file-associations-in-windows-8-1.aspx
http://blogs.technet.com/b/mrmlcgn/archive/2013/02/26/windows-8-associate-a-file-type-or-protocol-with-a-specific-app-using-a-gpo-e-g-default-mail-client-for-mailto-protocol.aspx
We understand your confusion about this, but we hope you understand that using network location for file association deployment is highly insecure and it is out of our recommendation since the content in that network location could be changed without any
notification or permissions constraint.
Thanks for your understanding.
Regards
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

File Associations in 2012 R2 RDS Server using Roaming Profiles

Background Information
We recently moved from using 2008 R2 RDS servers to 2012 R2 RDS Servers. All of our users
have roaming profiles. When we migrated from the old terminal servers to the
new terminal servers, the users got completely new profiles. The only thing
moved from their old profiles were documents and items on their desktops. We
have multiple PDF viewers/editors installed on our RDS servers. Mostly due to
the cost difference between Adobe Acrobat and other, cheaper products that a
lot of our users can get away with using that don't need the functionality of
Adobe Acrobat.
The Problem
Ever since moving to the new 2012 R2 RDS servers, whenever our users log off terminal
server, the next time they log in their default PDF Viewer association doesn't
load, and they have to go through the process of choosing a default PDF viewer.
This only occurs when there's more than one PDF viewer installed on the server.
We've tested it with only one PDF viewer program, and the setting remains after
logging off and back on. The problem we've found is that the registry key that
houses the default user choice:
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice
when set during the session, to Adobe Acrobat 11 for example, reads as such
inside that registry key. For example, the Progid key will say
Acrobat.Document.11 and this setting will persist until the user logs off. Upon
logging off and back on to the terminal servers, if you look at that same
Progid key, it has been converted in to a Hash value, and the Operating System
is unable to read the hashed value and determine what that user's default PDF
Viewer choice is, causing them to have to go through the process of setting it
again.
Things we've tried
We created a GPO that runs a script that exports the registry key upon log off that has
the non-hashed value, and have it set to import that value on log on. However,
by default this registry key has the DENY WRITE permission applied to it, so
when the system tries to import the registry key through the login script it is
unable to do so.
Summary
This issue only started happening once we moved over to 2012 R2 RDS servers. It only
occurs for users using Roaming Profiles. It only occurs when we have multiple
PDF Viewers installed on the servers. Any insight on why this is happening or
how to resolve it would be greatly appreciated.

I would use GPP to push the value, 'not hashed'. You can give right to the registry too, so like adding everyone group to that registry branch. (https://technet.microsoft.com/en-ca/library/cc753092.aspx)
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

Windows 8 Smart File Association Concept

I have a feature for providing to Microsoft. See the following:
We know Windows 8 tries to integrate the desktop and the touch interfaces into one OS. However, I think Microsoft forgets to update "Windows File Association," accordingly. For example, our Windows 8 can install
these apps: Adobe Reader for desktop and Adobe Reader Touch. Unfortunately, you can set .pdf file association to only one of them in Win8.
Why not if you use the "mouse" or "keyboard" to open a .pdf file in File Explorer, Win8 invokes Adobe Reader for desktop? And why not if you use your finger to open a .pdf file in File Explorer by touching,
Win8 invokes Adobe Reader Touch?
This concept should be not difficult to be implemented, for example, Windows File Association could provide two kinds of default app setting for one file type. One kind is keyboard/mouse, and another kind is touch.
I hope Microsoft can consider this concept in its future Windows.

Hi,
Thanks for your suggestion, If you have any suggestion or feedback to Microsoft Products, you can refer to the link below to provide your suggestion.
https://connect.microsoft.com/
Roger Lu
TechNet Community Support

Slowness when connecting to RemoteApp configured in Windows 2008 R2 Server using RDP file

Dear All,
When connecting to a RemoteApp configured in Windows 2008 R2 with less privileged user it takes ~20 seconds to connect.
Initial connection to
application takes about 20-30 seconds and once loaded, subsequent RemoteApp connection takes
2-3 seconds. i.e. if there is a disconnected session available in the server it connects quickly otherwise it takes long time.
I am seeing this issue with Windows 2008 Server, when I connect to a Windows 2012 Server RemoteApp gets
connected quickly. Also if I try with higher privileged user (like RemoteAdmin) connection is quick. The user I am trying is having lot of group policies set to limit user access to file system, desktop and registries.
If I keep UAC settings to minimal level connection happens quickly(i.e. solves this issue). But I am
not supposed to change the server UAC setting. It seems this has something to do with the list of group policies set for the user.
Any suggestion to avoid this first time connection delay for less privileged users for connecting to RemoteApp (in Windows 2008 Server).
Thanks
Bachuu

Hi Bachu,
Thank you for posting in Windows Server Forum.
First of all, if you are using RD Gateway serve then I would like you to
uncheck the “Bypass RD Gateway server for local address” under RemoteApp Manager Checkbox and notify the result.
Configure Remote Desktop Gateway Settings
Also like you to update the RDP client version to RDP 8.1 and then check the result. In addition,
I will suggest you to check that you have proper certificate in place. You can enable certificate revocation checking on RD Gateway client. Might due to this, you are facing issue. Please notify that you find any certificate related warning. Refer below article
for information.
How to Enable Certificate Revocation Checking on a Remote Desktop Gateway Client
Hope it helps!
Thanks.
Dharmesh Solanki

2012 RemoteApp: file associations windows 8 only?

Similar Messages

Maybe you are looking for