Network share as a Publishing Point source
From: Ravi Raman (ravira_at_Online.microsoft.com)
Date: Thu, 23 Sep 2004 18:48:14 -0700
Its great that you could make it work!
You are right in that adding to Administrators group is
much easier, but you are giving the "WMServer" user
Administrative access - a very high privilege. The
article keeps security as a high priority - and therefore
suggests steps that result in not giving permissions any
more than necessary for Windows Media Services to
>From a security perspective, it is better to run the any
service under a non-Admin account unless the service
absolutely requires Admin access.
-- This posting is provided "AS IS" with no warranties, and confers no rights. >-----Original Message----- >I have the remote share working now. Not all of the >permissions for the new logon account were enabled so the >service couldn't start. I discovered that there's a much >easier way to give the logon account the permissions it >needs than going through and enabling each permission in >the article: when you create the logon account just put >the account in the Administrators group and it picks up >everything it needs. > >Thanks for your help. >Steve > >>-----Original Message----- >>Have you actually checked this section where both the >>machines are in a workgroup: >>http://www.microsoft.com/windows/windowsmedia/howto/arti cl >e >>s/SourcingRemoteContent.aspx#serverremotedeviceorbothinw or >k >>groups >> >>So, what account is your service currently running under? >>Did you create a new wmserver account? >> >>Thx, >>Ravi >>-- >>This posting is provided "AS IS" with no warranties, and >>confers no rights. >>>-----Original Message----- >>>I tried setting up a remote share for WM9 Services, >>following the >>>article below that David Chen gave to Blake Crosby on >>9/16/2004, but >>>had trouble from the start. I mapped a directory on a >>remote computer >>>to the drive letter "Z:" at the WM9 Server. The remote >>computer and >>>the WM9 Server are in the same Workgroup. But when I >try >>to create a >>>publishing point referencing this remote directory, the >>mapped letter, >>>Z, does not show up in the pull down menu that drops >from >>the browse >>>window. If I type Z:\ into the source field anyway, I >get >>the message, >>> "The URL you specified is not valid." If instead of >>using "Z:\" I >>>enter the \\D3\c, which Z maps to, I get the same >>message. I've tried >>>rebooting. I know the share is working because on the >WM9 >>Server I can >>>see the share when I open My Computer, and I can rename >>files on the >>>share from a command window at the WM9 Server using just >>the drive >>>letter Z:\. >>> >>>This problem seems a long way before any issues about >>clients having >>>correct rights to access the remote share - the thrust >of >>the article >>>- since there are no clients in the picture yet. At any >>rate, I have >>>disabled the WMS NTFS Authorization for the WM9 Server, >>as per the >>>article, and enabled it for the publishing points not >>using the >>>remote share. At the remote computer I have allowed >>Everyone all >>>permissions on the share, just to get the share working >>for now. >>> >>>Thanks for any help on this, >>>Steve Adams >>>. >>> >>. >> >. >