Q2008D = Do 'scheduled OSU' really work?

OSU works fine. You have entered the PIN Vault manually and checked all your PINs, right? Then the next thing is to initiative and OSU manually. Assuming that works fine, the scheduled ones should work fine.

Thanks for the reply Rick, but with all due respect, maybe you don't understand what I am trying to do? Perhaps I wasn't clear? This is the option to allow Quicken to do a OSU AUTOMATICALLY when Quicken may not even being used. There's an option that allows you (supposedly) to give the Pin value once you reboot Windows so when the time comes (at 6 AM), one need to be at the machine to give the PIN. This is the point that isn't working; after the Windows reboot, it isn't taking my PIN correctly. Specific to your comments:

No, no need for checking ALL the PINDs. After going thru the dialog to set up a scheduled OSU, Quicken sez you need to reboot Windows to obtain the PIN if you don't choose the manual method. Upon rebooting, Quicken comes up with a small dialog asking for the vault PIN, and allows me only two times to enter it before throwing up saying it's invalid. But it isn't! Manually doing OSU within Quicken using the vault PIN is fine; it's just trying to give it after the required reboot of Windows isn't working.

No, I want Quicken to do this at 6 AM, no manual stroking.

I haven't had a problem doing a manual OSU (Q2008 DL, USA, Vista home basic). That's how I've been used to doing things.

Once I saw this thread I tried to set up Q for doing an OSU automagitically. Entering the password during this setup yielded an error, so I did it again (same password as when manually updating). Same error. However, shutting down the computer and restarting it gives me the prompt for the PINvault password, and (WOW!!) it takes it. This has appened several times now (fooling with things other than Quicken), and I am now waiting for Q to perform the autimatic OSU.

I can't figure out what I might have done differently than you did, Andrew, but so far and up to this point, Q is doing what it promised (I think!).

OK, I use that feature every day and it works fine. What I was trying to do is give you a framework for debugging your problem.

Yes, there is a need. OSU uses the same PIN Vault as the manual initiation method. The first thing you need to do is confirm that your PINs for each account is correct. Manual or automatic doesn't matter at this point. You can confirm this after entry by doing individual updates for each account. That means going to the register and clicking on the "update" button in each account. You should only have to enter the Pin Vault password, not the individual account PIN.

Right. The next step after you confirm that your PINs are correct and work when manually initiated for each account is to kick off a OSU for all accounts manually. You do that by clicking on the "Update" button in the tool bar or by using the Online / One Step Update menu item. This will ask for the same PIN Vault password that the automatic OSU asks for. Again, you should not be entering individual accounts PINs - just the one Pin Vault password.

Only if you get everything above working are you ready to make the automatic unattended download work. If you can't make these manual steps work, it sounds like your PIN Valut is corrupted. I would blow it away and recreate it.

I do recall that there are problems with scheduled updates with Quicken files that have a password. I do not recall any problems with scheduled updates with Quicken files that have no password.

Nuts, I forgot to mention. Scheduled updates use the last Quicken file you had open before the scheduled update occurs. If that's the file that had the password, that might be the source of the problem.

Rick, John, Han - thank you all as usual for your kind replies. I did take the password off my QDF file John, and retried process without success. Rick - I am loath to delete and recreate the vault; this isn't THAT big a deal, but I fear you might be right in that I've tried all options you three have given me (including resetting the vault pin), but no joy. Han - glad it worked for you ultimately!

Not that big a deal. I've lived with manual OSU updates for a dozen years or so...I just stumpled across this a day or so ago, and I thought it might be neat if I could get it work.

Happy New Year to you 3.

"Andrew" wrote in news:xtZcj.12$ snipped-for-privacy@newsfe09.lga:

Sorry about it not working for you. I'm probably going to take off the automatic OSU, and keep doing it manually. Doing it late at night isn't giving me the data because some FI are late supplying it (TIAA for example).

Happy New Year to all!

Which is why I want to do it at 6 AM - about an hour before I come down here as I am doing now early Friday morning! I may bite the bullet this weekend and delete/recreate the vault as Rick had suggested if I am glutten for punishment.

Well, screw it I said, and recreated the vault. Since one doesn't have to go through ACCOUNT REACTIVATION when deleting./recreating the pin vault, it wasn't as bad as I originally thought it might be. And despite the fact that it seemed to be doing *manual* OSUs fine, indeed when I rebooted Windoze, it seems to have take the vault PIN fine on start up this time around (Thanks Rick - and I did take the password off the QDF file as John had suggested).

So, we'll see if it really works at 6 AM tomorrow morning; then, I want to put the password BACK on the QDF file because I don't like the idea of leaving that unprotected in a house of 4 others.

Stay tuned.

Regards -

- Andrew

Scheduled OSU worked, now onto whether or not putting the password back on the QDF file still allows it to work.

------------------------------------------- Regards -

- Andrew

Well, as I think John Pollard mentioned, apparently there ARE "issues" as to whether or not one has a password on the fileset in question. Without the password assigned, the scheduled OSU works fine. An ICON appears in the system tray indicating I have transactions to process. However, when I put the password on the fileset, it doesn't download properly, and a little icon shows up in my system tray telling me I have had problems.

So, I am not sure if this is a "bug" or a "feature". Since I would think if a password is on the file when one sets up the scheduled OSU, it should not be a security issue to program the update to ignore the password. So I did report it as a "bug" and I'll see what the response is from Intuit.

"Andrew" wrote in news:nzuej.2$ snipped-for-privacy@newsfe11.lga:

It is my feeling that is is not a bug. If you consider the data important enough to require a password, than just having the user account active should not defeat the Quicken fileset's password, and that is what you are asking for, I think.

Just my opinion!

Han - I understand your point; that is why I too am not 100% sure either. But I tend to think it's a bug. "Works as coded" as opposed to "works as designed" as we say in operating system development.

I view the password facility as a means of keeping other HUMAN eyes off the data, not the components of Quicken. As I said, one had to be IN the program to set up the scheduled OSU anyway, so I don't see why having a password on the fileset should prevent the other COMPONENT of Q (ie: the scheduled OSU code) to prevent it from doing its download thing even if it is at a later point in time.

And if there is indeed a difference of opinion, then there should be a user option to go one way or the other; hell - I'll even throw you a bone and say to make your way the default given such an option!! But give me the option!

Happy New Year my friend.

------------------------------------------ Regards -

- Andrew

"Andrew" wrote in news:irwej.3$ snipped-for-privacy@newsfe11.lga:

Well, let's hope that Intuit will chime in somewhere on this subject (I understand they don't monitor this NG - the days of Bruce Lee are long gone.)

Happy, healthy and successful 2008 to you too!

Having people not have a password on their data to use a feature of Quicken seems like a really bad idea to me!

I believe it is a bug also, and I think Intuit has already acknowledged it several months ago in the Quicken forums.

I don't think the bug was present in the earliest versions of Quicken that had Scheduled Updates (but I'm going on memory here).

"...and I think Intuit has already acknowledged it several months ago in the Quicken forums."

John - I don't follow the Q forums very much (should I?), as most of what I glean about Q I get from this NG here. But I did try to do a few searches before I posted the 'bug' report as a good citizen and didn't find anything in return. Of course, that is only as good as the keywords and search mechanisms. I haven't heard from them yet.