Does this work across reboots? What if you have to manually shut down the PP software; can the limited user restart it?
I have a pretty typical install on my desktop with a sysadmin account that admins the machine and two limited user accounts that are actually used day-to-day. I can not figure out how to make this work. I install the software as the sysadmin, and give it my credentials, but then when I log in as a user I don't even see the software, and if I manually find the exe I can get it running, but it won't log me in even though it says it's registered to my email account. I've tried everything. Install as user, unregister and register as user. Nothing. It just says No User on the task notifier. Anyone run into this? The only solution I've come up with is to make my user accounts admins, but that's totally unacceptable.
I've confirmed this is a non-working configuration. (v3.0.3 on WinXP Starter)
I made my regular login an admin, installed and configured PP, then changed my login back to standard user. It worked until I rebooted.
After I rebooted the software still loads, but the P: drive does not appear. I can open preferences and see that I'm logged-in and everything, but P: does not mount.
Here's the really strange part: using PP preferences or the web access I can share directories from my local machine and even configure active backup, but I still can't see the P: drive.
This does leave us with an interesting possibility: I can configure backup of certain directories from this standard login to my PP drive, but since the PP itself can't be mounted, I can't propagate any viruses accidentally (though an infected file could be propagated).
I have the same issue. Has anyone found a soultion yet? It would be nice to be able to run this as a service.
Sorry, no. I'm still running as an admin user. It just doesn't work as a limited user.

RSS



OK, you want to know how I made this work? It's ridiculous, but I made everyone an admin, the I went into each account and installed the pogoplug desktop software (ignore the files that you can't overwrite because it's mostly going to install in the same place, but there's obviously something that's account-specific and only works if you're an admin during the install [it won't prompt for credentials if you aren't]). Then configure the preferences for each account. When you have them all working you can then knock the users back down to limited accounts. Broken a little?