Yea, I saw that part, but I'm not interested in users being able to update the program themselves. That's MY job :)
It really kinda makes me grit my teeth in anger that they haven't fixed this yet. Especially when it seems like it would be so easy. At the very least, they could make the perm changes automatically. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] Sent: Wednesday, October 26, 2005 2:47 PM To: [email protected] Subject: Re: [ActiveDir] OT: QuickBooks 2005 permissions If you scroll down a little farther on that page you'll find a post on how to get it to also update as non admin. Part one last night [just getting it to run] worked even on the 2006 version with the new SQL backend [Sybase SQLanywhere mind you] But yes, even in 2006 it still requires admin /power user rights. Crawford, Scott wrote: > Actually, it was just pointed out to me that I copied and pasted > correctly, but when I was applying the perm to > HKLM\Software\Classes\CLSID\{E53C85D6-E6D9-4BCF-A632-72062A99AA7F}, that > key didn't exist and I instead applied it to > HKLM\Software\Classes\CLSID\{E53C85D6-E6D9-4BCF-A623-72062A99AA7F} (just > change A632 to A623. Apparently that's the difference between > QuickBooks Pro and QuickBooks Premium. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Susan Bradley, > CPA aka Ebitz - SBS Rocks [MVP] > Sent: Tuesday, October 25, 2005 7:29 PM > To: [email protected] > Subject: Re: [ActiveDir] OT: QuickBooks 2005 permissions > > I will have to try that on the 2006 beta. The last time I tried to do > 'just' certain Classes roots that I saw in filemon/regmon it would not > load. > > I also had to do \common files\Intuit > > If it works I'll update the instructions > http://www.sbslinks.com/lua2.htm > > > Crawford, Scott wrote: > >> A few weeks ago, there was some mention of the required permissions to >> run Quickbooks as a non-admin user. According to this site: >> http://www.quickbooksgroup.com/webx/[EMAIL PROTECTED]@ the >> perms needed are Users:W to the following locations: >> HKLM\Software\Intuit >> HKLM\Software\Classes\QuickBooks.CoLocator.1 >> HKLM\Software\Classes\CLSID\{E53C85D6-E6D9-4BCF-A632-72062A99AA7F} >> C:\Program Files\Intuit >> >> Whenever I've tracked these things down, I just give users full >> > control > >> to the needed locations instead of trying to determine the exact perms >> needed. Furthermore, I generally apply the perms to the root of the >> apps folder. For example, I'll grant the perms at the root Intuit >> folder instead of chasing down the one or two files that actually need >> to be modified. This tends to eliminate future problems when somebody >> uses some new function of the app that hasn't been tested and it needs >> to write to a different file. Anyway, I thought some of you might be >> interested. I just tried it here and all seems good. >> List info : http://www.activedir.org/List.aspx >> List FAQ : http://www.activedir.org/ListFAQ.aspx >> List archive: >> > http://www.mail-archive.com/activedir%40mail.activedir.org/ > >> >> > > -- Letting your vendors set your risk analysis these days? http://www.threatcode.com List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
