Reply to thread

Message

There can be problems with this under Windows 7 or Vista if you run MP from a non-admin account. In this case, MP Configuration puts MPtray in the registry for the wrong "Current User", namely the admin user you used to run MP Configuration. The way I found to fix this is to deselect MPtray in MP Configuration and then add a shortcut to it in the "Programs - Startup" menu of the user under which MP starts. BTW, this is also the way I start MP on system start. When I used the autostart in MP Configuration, MP would also start on my remote console when I logged in via RDP for maintenance. The link in the Startup menu only starts MP for the user I have set up for autologon on system start.

[QUOTE="rsbrux, post: 819503, member: 49539"] There can be problems with this under Windows 7 or Vista if you run MP from a non-admin account. In this case, MP Configuration puts MPtray in the registry for the wrong "Current User", namely the admin user you used to run MP Configuration. The way I found to fix this is to deselect MPtray in MP Configuration and then add a shortcut to it in the "Programs - Startup" menu of the user under which MP starts. BTW, this is also the way I start MP on system start. When I used the autostart in MP Configuration, MP would also start on my remote console when I logged in via RDP for maintenance. The link in the Startup menu only starts MP for the user I have set up for autologon on system start. [/QUOTE]

Verification