Have done up a blog specific to what I have done - have a read if anyone is interested,
http://damonjohns.wordpress.com/2013/08/16/how-to-deploy-windows-8-enterprise-file-type-associations/ Cheers Damon From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, 15 August 2013 9:42 PM To: [email protected] Subject: [mssms] RE: Windows 8 File Associations & OSD Well that wouldn't be too hard to put in PowerShell. :) We are piloting Win8 in the next few weeks, I may play around with this some. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, August 14, 2013 10:36 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Windows 8 File Associations & OSD Oops, my fault: It's not PowerShell, it's DISM: Dism.exe /Online /Export-DefaultAppAssociations /? DEFAULT ASSOCIATIONS COMMANDS: /Remove-DefaultAppAssociations - Removes the default application associations from a Windows image. /Import-DefaultAppAssociations - Imports a set of default application associat ions to a Windows image. /Get-DefaultAppAssociations - Displays the list of default application associations from a Windows image. /Export-DefaultAppAssociations - Exports the default application associations from a running operating system. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Johns, Damon (DoJ) Sent: Wednesday, August 14, 2013 7:14 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Windows 8 File Associations & OSD After 3 hours of searching I have finally come across this - 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 http://technet.microsoft.com/en-us/library/hh825038.aspx So it would seem that you need to create an exported xml file which you can apply with group policy. Scripted changes to the registry no longer work for Windows 8 file types as there is a hash check in place. Not sure if it will work or not - am going to have a go in the lab this afternoon. I have been unable to find a posted power shell script option - although I'm sure they exist. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Thursday, 15 August 2013 9:26 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Windows 8 File Associations & OSD There are some PowerShell scripts to import and export associations, so you should be able to configure the associations the way you want, then export them and deploy them later. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Wednesday, August 14, 2013 3:40 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Re: Windows 8 File Associations & OSD Has anyone researched and implemented a way to stop Windows 8 Enterprise from using Modern/Metro Apps to load certain file types when using copyprofile or similar when sysprepping for a capture? Some of the file types I'm referring to are .mp3 .wav .wmv .jpg .bmp etc. It's our preference to have these open using Windows Media Player or Windows Picture Viewer. I can set the file associations on a Hyper V base image but when I run sysprep and set the copyprofile option to true in the unattend.xml it resets these settings back to default. I don't mind this occurring on say a Surface Pro which is a tablet and a user may want to take advantage of the modern apps, but for our desktop users it not really appropriate as the Modern/Metro Apps don't always integrate/communicate with some of the traditional desktop apps. I'm finding that our users are having consistently swap between the Modern UI and the traditional desktop or we are been asked to make the change in file associations for them. Thanks in advance for any replies / comments Cheers Damon ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
