Yes, I found that out, cheers. I really hate using those commands - it feels so unnecessarily complex. I was just wondering if there was a native PowerShell way so I could use AppSense, but at the moment the far and away easiest method looks to be Group Policy Preferences.
On 1 April 2014 20:36, Kuhlman, Donald <[email protected]>wrote: > Don't know if this helps (in a round about way) - but can you do it > using the assoc and ftype commands via Powershell and cmd /c syntax ? > > > > > > [PS] 2014-04-01 14:30:19> cmd /c assoc .doc > > .doc=Word.Document.8 > > > > [PS] 2014-04-01 14:34:09> cmd /c ftype word.document.8 > > word.document.8="C:\Program Files (x86)\Microsoft > Office\Office15\WINWORD.EXE" /n "%1" /o "%u" > > > > Webpage example - > http://technet.microsoft.com/en-us/magazine/ff687021.aspx > > > > Don K > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James Rankin > *Sent:* Tuesday, April 1, 2014 2:16 PM > *To:* [email protected] > *Subject:* [NTSysADM] PowerShell cmdlet > > > > Is there a PowerShell cmdlet that controls file type associations? I'm > thinking not, but just checking in case I've missed something.... > > > > -- > > *James Rankin* > --------------------- > RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization > Practice Analyst - Desktop Virtualization > http://appsensebigot.blogspot.co.uk > -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
