Remote server administration tools for the streaming media services

Updating from these earlier platforms directly to Windows Server R2 is not supported. For more information about how to copy these files, see the table in the "Files that you should copy" section. For more information about migrating these settings, see the Windows Media Services Upgrade and Migration Guide:. The following table lists the files that you should copy together with their descriptions and their default locations on the Windows Media server.

The Windows Media Services namespace file stores the configuration settings for the Windows Media server. The Remote Server Administration Tools feature in Server Manager provides role administration tools that let administrators remotely manage servers that are running Windows Server R2.

The Streaming Media Services role is not supported by this feature. For more information, click the following article number to view the article in the Microsoft Knowledge Base:. The server is running Windows Media Services 4. You are updating the server to Windows Server R2.

Restart Server Manager. To do this, follow these steps: Stop the Windows Media Services service. To do this, type the following command at a command prompt: net stop wmserver Copy the backed-up ServerNamespace.

To do this, type the following command at a command prompt: net start wmserver Full installation option notes To remove the Streaming Media Services role from active use, follow these steps: Under Roles Summary in Server Manager, click Remove Roles.

File Description Default path ServerNamespace. The copying of log files is optional. For more information, click the following article number to view the article in the Microsoft Knowledge Base: How to install Windows Media Services Remote Server Administration Tools for Windows Server R2 Note You can also administer a server remotely from a separate Windows Media server that is running the full installation option of Windows Server R2.

Need more help? Expand your skills. Get new features first. Was this information helpful? HI Team, H ope you all doing great. Your response is appreciated.

Regards, M. I have the same question Report abuse. Details required :. Cancel Submit. Avinash, Thank you for writing to Microsoft Community Forums. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Thanks again! Thanks for you post — it helped me to eventually get these tools installed.

As a dinosaur not yet well-versed in using PowerShell, your script was very useful. Very useful post! Thanks mate! I needed to read until the bottom. The WSUS regkey finally made my day. Open the Group Policy Editorr gpedit. I get the installation completed successfully. How to get these in installed status? I get this after when I try to install AD components.

ALready did trick with regkey and gpedit. Ok, problem solved. Connecting workstation to hotspot solved the issue. Thank you for the very clear and useful information. Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty.