During the days of XP, I had many computers with a single administrator user that had no password. Now with vista I find having no password for the administrator a MUST, since its much harder to make it autologin into a passworded user, AND because simple file sharing has been done away with, and thus you must have a passwordless admin if you wish to allow people to access your shared files (outside of public) without a password.

This raises a problem for boinc. The server install option absolutely insists that a password cannot be null .

Ideally this would be fixed so that boinc would work with passwordless admin accounts, but until it is, is there some way I can force it to install with a null password? I would really like it as a service install so that the manager is not constantly running unnecessarily.

---

I do not have a superman complex; for I am God, not Superman!

Hi

I don't have Vista but i would expect that you could copy a boinc folder to that machine and set boinc to run as a scheduled task on startup.

hth
Danny

---

To expand a little on dcdc's idea:

In XP at least (I don't have Vista either), running boinc.exe from a startup shortcut, even minimized, would leave a taskbar entry, which the user might not like and/or could use to interact with.

There are scripts in XP (again, it may be very different under Vista: it seems designed to not let you do stuff) that will run a program hidden; I just tried runhidden.vbs ( http://www.jsifaq.com/SF/Tips/Tip.aspx?id=9390 ), and it works fine on XP. Googling "run hidden vista" might find a better solution?

One disadvantage (or advantage?) is that this will run BOINC.exe as a process, not a service, so it can be stopped easily only from taskmanager, though again there's maybe programs that will do it. Maybe Vista has an analogue of kill.exe?

As I say, runhidden.vbs worked for me as a logged-in user on a local XP machine, so I have nor real idea if it will work under your configuration, but I hope this helps some...

---

Ken

thanks for the suggestions, I will see about doing that in vista... Any ideas on how to make it a service (rather then just hidden) would also be appreciated.
Basically I dont want boincmgr.exe running all the time in the background, (yea I know, its only 2MB big, but still...)

I am getting the feeling that if I want that I will have to recompile it myself...

I really wish someone could come up with an answer as to WHY boinc refuses to allow passwordless service installs? Any developers on board who can answer that one?

---

I do not have a superman complex; for I am God, not Superman!

Just a guess here as I don't have Vista, but maybe install it as a single-user account, then remove the shortcut in the Startup folder, and try creating a service using the boinc.exe client location as explained here:

Create your own user-defined services Windows NT/2000/XP/2003

Any ideas on how to make it a service (rather then just hidden) would also be appreciated.

Create a separate admin account (with a password) to do the installation from? Once BOINC has been installed as a service it shouldn’t care which account is logged in.

---

Any ideas on how to make it a service (rather then just hidden) would also be appreciated.

Create a separate admin account (with a password) to do the installation from? Once BOINC has been installed as a service it shouldn’t care which account is logged in.

Awesome idea, I tried it and I could log it in as a different user without it ruining simple file sharing. (if your vista user is password protected you MUST log in as a valid user to get access to network files).

However, this requires me to choose which user to log in as when I start the computer. Interestingly enough, if I delete the other user and restart it acts as if I installed it in "shared install" mode.

So, thanks, this is the best idea so far. But is there a way to make vista automatically log in a user (who has no password) when there are two active users? If I could do that then this would be a perfect solution with absolutely no drawbacks.

---

I do not have a superman complex; for I am God, not Superman!

I'm not going to get into the advisability of passwordless Admin accounts - that's your business. (Still - don't do it!)

Accounts will be handled automatically by the 6.0 installer. Meanwhile, creating another account for BOINC is the perfect workaround.

To make the account invisible to the startup screen logic, try removing it from the Users group. Create a group for BOINC, and give the BOINC group full control of the installation folder. Make sure you don't install BOINC in Program Files, or UAC may interfere.

This works on XP, I haven't tested on Vista.

---

in xp if you navigate here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList]

and create a dword (value=0) with the same name as the username you want to hide, then it will be hidden.

I use this batch file to create a hidden user account called 'Sandbox':

net user Sandbox Password /add && net localgroup administrators Sandbox /add
echo Windows Registry Editor Version 5.00> c:\hide.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList]>> c:\hide.reg
echo "Sandbox"=dword:00000000>> c:\hide.reg
REGEDIT /S c:\hide.REG
DEL /Q c:\hide.REG

Also, in XP, to make a user automatically log-in in you use Run > 'control userpasswords2'. Don't know whether it's changed in Vista tho...

HTH
Danny

---

in xp if you navigate here:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogonSpecialAccountsUserList]

and create a dword (value=0) with the same name as the username you want to hide, then it will be hidden.

I use this batch file to create a hidden user account called 'Sandbox':

net user Sandbox Password /add && net localgroup administrators Sandbox /add
echo Windows Registry Editor Version 5.00> c:hide.reg
echo [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogonSpecialAccountsUserList]>> c:hide.reg
echo "Sandbox"=dword:00000000>> c:hide.reg
REGEDIT /S c:hide.REG
DEL /Q c:hide.REG

Also, in XP, to make a user automatically log-in in you use Run > 'control userpasswords2'. Don't know whether it's changed in Vista tho...

HTH
Danny

Unfortunately, userpasswords2 does not seem to work in vista. It was a very useful tool in XP.

I will try the hiding technique you mentioned, maybe I can use it to create a sandbox account in vista.

Didactylos:

Thanks for the info about the 6.0 installer. Does that mean that service installations without a password will work? or just that the installer is not gonna ask you anymore (ie, it will automatically choose between the 3 options)

I don't WANT to have a passwordless admin, but vista is forcing my hand, their "security" is such that they tie certain things in with the admin password, and the ONLY way to bypass them is to have a passwordless admin. Really stupid if you ask me. I always make fun of macs, but at least thats something apple got right, you put in your password to install or uninstall stuff, thats it. Security without bother.

As for UAC, its not a problem since I disable it, since its the most useless peice of crap MS came up with to date. I thought it is gonna be incredible... suddenly people would get warning messages like "Porno is trying to install "autodialer" on your computer, this is probably a virus, do you want to allow it"... Instead it just shows a picture of the application with a bunch of alphanumeric digits that say nothing to noone. Useless junk!

---

I do not have a superman complex; for I am God, not Superman!

Thanks for the info about the 6.0 installer. Does that mean that service installations without a password will work? or just that the installer is not gonna ask you anymore (ie, it will automatically choose between the 3 options)

By default, the installer will install as a service without requiring you to mess around with passwords or accounts. It will be entirely automated. If you want to do it manually, you will still need a password for the account you use (that's a Windows limitation - and a sensible one) but I will try to improve the error handling for that case.

UAC is the feature that allows Windows to require passwords for installs and so on, just like the way you describe Macs as working. It's called Admin approval mode. It's not going to be much use if you don't *have* an Admin password, though!

Ideally, you should set up an Administrator password, and a separate (user) account for day to day use (without a password). You can then hide the Admin account from the Welcome screen, and it should log in the user account automatically. UAC will also work correctly, asking for your Admin password when you want to perform Admin functions such as installing software.

I think a clean Vista install is set up something like that, but upgrades are a bit more messy, hence your problems.

---

By default, the installer will install as a service without requiring you to mess around with passwords or accounts. It will be entirely automated. If you want to do it manually, you will still need a password for the account you use (that's a Windows limitation - and a sensible one) but I will try to improve the error handling for that case.

How exactly is it a windows limitation to require a password during install with a PASSWORDLESS account? I have PLENTY of programs that install services without every requiring a password, and thats even when my account IS passworded.

UAC is the feature that allows Windows to require passwords for installs and so on, just like the way you describe Macs as working. It's called Admin approval mode. It's not going to be much use if you don't *have* an Admin password, though!

I am actually USING vista and that is NOT how it works. UAC does NOT request a password, EVER. It requires you to press OK every time you want to open a "sensitive" configuration item. For example, if you try to open the network settings page a popup comes up with a an alphanumeric number, the name "network settings" and the icon it uses... with the options of ok or cancel.. no info is given on what is actually gonna HAPPEN... completely stupid and a waste of time.

Ideally, you should set up an Administrator password, and a separate (user) account for day to day use (without a password). You can then hide the Admin account from the Welcome screen, and it should log in the user account automatically. UAC will also work correctly, asking for your Admin password when you want to perform Admin functions such as installing software.

Except a LOT of programs don't even WORK in user mode... not to mention I can't install things, I can't update things. I have to log in as an administrator 5 times an hour on a regular session... completely impractical.
Oh but wait... here is the most precious thing... I don't know of a single virus that will FAIL to install in user mode!

I think a clean Vista install is set up something like that, but upgrades are a bit more messy, hence your problems.

Why are you assuming I actually UPGRADED to vista? when I say upgrade i meant formatted the PARTITION containing XP64 and installed a clean install of vista... I NEVER do an upgrade installation.. not even for a service pack. If I Want a service pack I slipstream it into the CD and do a clean install WITH the service pack... clean installs are the ONLY way to go.
None of my "problems" occur because of anything I did. They occur because the boinc installer is being STUPID and DEMANDS that I input a password for a passwordless account when trying to install as a service, when every other program that installs services simply installs them... even on computers that ARE password protected, without asking for a password! (example, serv-u FTP, most drivers, etc... I install them perfectly fine on my password protected computers, and I even tried them with password protected vista!)
The "issues" discussed within are problems with circumventing the stpid boinc insaller issue and trying to force it to work as a service without a password.

---

I do not have a superman complex; for I am God, not Superman!

Well, it appears I was wrong, you actually CAN use userpasswords2 on vista (i was typing it wrong)...

So there IS a configuration where it works:

1. Make a new user with a password called boinc.
2. set windows to autologin with your desired user.
3. install boinc in service mode using the boinc user.

---

I do not have a superman complex; for I am God, not Superman!

You don't have a password. That is the beginning and end of your problems.

I guessed that perhaps you had installed Vista as an upgrade because your account and password setup were so daft. If that was your choice, then, obviously, I'm wrong - and you will have to deal with the limitations, or set your computer up more securely.

Sorry, we aren't going to sacrifice security for your convenience.

You can learn about how UAC is supposed to work on TechNet. Don't judge the feature by how it behaves with your insecure setup. If you insist on blaming BOINC for your problems, then forgive me if we ignore you.

---

I was under the impression that this board was a place where like minded people can come together and discuss boinc. This thread specifically is for people to discuss methods of installing boinc as a SERVICE for its various benefits without using a password. If you do not want to engage in such actions, simply don't read this thread. There is no reason to come in here and insult people for desiring a more productive system in a manner that is different then your own.

You don't have a password. That is the beginning and end of your problems.

I guessed that perhaps you had installed Vista as an upgrade because your account and password setup were so daft. If that was your choice, then, obviously, I'm wrong - and you will have to deal with the limitations, or set your computer up more securely.

My password setup is neither daft, nor accidental. I have originally set it up WITH a password, and have opted to remove it later on due to vista's own limitations on password protected accounts (specifically, network file sharing). Their so called security offered no tangeable improvements to security, while completely preventing me from using my computer as I want.

Sorry, we aren't going to sacrifice security for your convenience.

By boinc allowing me to run it as a service without a password; or by me finding a WORKAROUND to run it as a service without a password, YOU are in no way shape or form forced to suffer weakened security. You could still opt to use the password, which is not even needed by boinc to begin with, when you install it. And when v6 comes along as finally FIXES the installer so it correctly sets up the service without user intervention this would be a moot point.

You can learn about how UAC is supposed to work on TechNet. Don't judge the feature by how it behaves with your insecure setup. If you insist on blaming BOINC for your problems, then forgive me if we ignore you.

I read this, it tells me nothing new. It works the same with and without password. It never asks for a password, it merely asks you to press ok or cancel. And it never actually tells you WHAT it is that you ok or cancel. You merely get a an alphanumeric value and a picture and the name of the file. Which is useless for determining what exactly is being done and making and informed decision on weather you should enable it or not!
I am judging this feature and deeming it as useless based solely on it's inability to INFORM a user of what exactly it is that he allows or denys.

---

I do not have a superman complex; for I am God, not Superman!