• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2121
  • Last Modified:

Windows Media Player in Windows Server 2003

I have recently upgraded Windows Server 2003 to SP1 with Windows Media Player.  I would like to run videos with cinepak or indeo codecs.  They run fine on WMP 10 on XP, but aren't recognized wihen I try to run them on WS 2003.  How can I upgrade WMP to recognize these codecs?  Alternatively, does anyone know of a media player I can use with WS2003 and terminal services that will run these codecs?
Thanks,
Brigham
0
brigham
Asked:
brigham
  • 3
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Hi brigham,

Your fix is described in this post:  http://www.moviecodec.com/topics/5611p1.html

Jeff
TechSoEasy
0
 
brighamAuthor Commented:
Jeff,
Thanks for your excellent suggestion.  This is what I did:

I moved the file iccvid.dll to my system32 folder windows/system32.
1.  Then ran the registry editor - go to start, run, then regedit.exe. Navigated to the key HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Drivers32.
I scrolled down a little on the right noticed the pattern string value name:vidc.[fourcc] with value:[name of codec file].
A)  I went to edit, pick new, string value. Named it vidc.cvid.
B)  Then double clicked it and for value put iccvid.dll.
2.  Next, I went to the key ("folder") just above that (HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/drivers.desc).
A)  I went to edit, pick new, string value. Named it iccvid.dll.
B)  Then double clicked it and for value put "Cinepak Codec by Radius Inc.", without quotes.

It worked great for me as the Administrator, but the codec isn't available for anyone else.  I get the original "codec" error message if I login as a regular user.  How can I fix this?

Many thanks,
Brigham
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I just reread their methodology... and I'm not sure why it would be stored in the System32 directory when all the other codecs are in the Windows directory.  The permissions in the System32 directory shouldn't be much different... but I would guess that they might be more restrictive -- plus it would make sense to have the codec reside where the others are.

Try moving it to the Windows directory (C:\Windows), make sure it inherets the permissions associated with that directory (essentially you want AUTHENTICATED USERS to have Read & Execute) and then go in and change your registry entries accordingly.

Jeff
TechSoEasy
0
 
brighamAuthor Commented:
Jeff,
I tried your suggestion.  It didn't work; perhaps because we are primarily using terminal services.  Other users still cannot access the WMP configuration that I can as Administrator.  For me, it works fine at the server console or via terminal services.  Others cannot get the codec to work.  It does not seem to be a permission problem.  Please let me know if you have any other thoughts.
Thanks,
Brigham
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
When a user connects to TS, you are going to have a problem because you probably don't have enough video capability for multiple connections... ideally you want to push out that processing to the remote machine to keep the load off of your server.  Thats probably why you get inhibited video capabilities for Terminal Server clients.

So, even if you resolve the permissions issues... is there any reason you MUST have the video play within the TS shell?  I didn't realize that's what you were attempting and I've never really heard of trying to deploy video in such a way because Terminal Services really doesn't provide the proper protocols or experience for such use.  Essentially the picture (desktop) being shown to a remote user is a bitmap which is cached on the remote machine... if you start running video through that protocol the cache will eventually lock up.

I guess I thought you were using a VPN connection originally... but you really should look at using Windows Media Services which can push the codec out to the user as well... check out:  http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03mngd/25_s3wms.mspx

Jeff
TechSoEasy
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now