Reply to thread

Message

<blockquote data-quote="floepie" data-source="post: 205509" data-attributes="member: 59663">For those who run Vista and MP under a limited user account, here's little tip that will help to avoid any strange db and other config problems while reducing config and app load times.&nbsp; When MP installs itself, it doesn't create all the files it will need to operate properly.&nbsp; This doesn't happen until the first config is run and saved.&nbsp; And, if you run the config as an admin immediately following MP installation, formation of duplicate databases and other auxiliary files may arise.&nbsp; So, my suggestion is to not perform the configuration process immediately following the installation (as an admin).&nbsp; Then, go into the Mediaportal folder in both \Program Files\&nbsp; &nbsp; and&nbsp; &nbsp; \Program Data\ and add your username to the security properties of those 2 folders and grant yourself write and edit permissions.&nbsp; Then, in the advanced button, you will see an option to propagate permissions for all the child files and folders so that the permissions of the Mediaportal directories will be inherited not only for existing files but for all future files as well.&nbsp;&nbsp; Finally, configure MP under your limited user account.&nbsp; This way, all your data and configs will exist together where they would be if you were running as an admin, thereby preventing various files appearing in the user's VirtualStore folder.</blockquote>

[QUOTE="floepie, post: 205509, member: 59663"] For those who run Vista and MP under a limited user account, here's little tip that will help to avoid any strange db and other config problems while reducing config and app load times. When MP installs itself, it doesn't create all the files it will need to operate properly. This doesn't happen until the first config is run and saved. And, if you run the config as an admin immediately following MP installation, formation of duplicate databases and other auxiliary files may arise. So, my suggestion is to not perform the configuration process immediately following the installation (as an admin). Then, go into the Mediaportal folder in both \Program Files\ and \Program Data\ and add your username to the security properties of those 2 folders and grant yourself write and edit permissions. Then, in the advanced button, you will see an option to propagate permissions for all the child files and folders so that the permissions of the Mediaportal directories will be inherited not only for existing files but for all future files as well. Finally, configure MP under your limited user account. This way, all your data and configs will exist together where they would be if you were running as an admin, thereby preventing various files appearing in the user's VirtualStore folder. [/QUOTE]

Verification