> I've written a script to install all critical updates but i have a small > problem.
You re-wrote the win2ksp4-updates.bat and/or winxpsp1-updates.bat scripts?!? Were the scripts included with unattended deficient in some way? > the dotnetfx.exe update ran with this command > dotnetfx.exe /q:a /c:"install /l /q" winxpsp1-updates.bat contains the following command for the dotnet update todo.pl ".reboot-on 194 %Z%\updates\common\%WINLANG%\dotnetfx.exe /q /c:\"install /q\"" > silently installs fine but 1 thing is does is create a asp user account. Yes, the dotnetfx.exe creates the ASP.net user account. Yes I regularly delete this account from my personal machines. I have seen no I'll effects from deleting this user account, but I also am not yet using DotNet applications that would require the ASP.net user account. > By creating this account the pc now has 2 accounts and therefor stops > the user from auto logon. I am at least slightly confused. What does having 2 accounts have to do with auto logon? Are you by chance using WinXP Home and utilizing the fact that XP Home chooses not to show the welcome screen if only one user exists? This mis-feature should not be confused with auto logon. Auto logon is defined by 4 registry keys, HKLM\software\Microsoft\Windows NT\Winlogon\ AutoAdminLogon=1 DefaultUserName=Foo DefaultPassword=Bar DefaultDomain=FooBar If AutoAdminLogon does not = 1 then the reset of the keys are ignored. If it does = 1 then the other 3 keys are used to determine the username/password and domain (if any) to use when attempting to auto logon. > My question is can i stop it from creating that account I don't think you can keep it from creating the account. Its going to be created if dotnet is installed. > and if i can't > stop it from installing the account can i delete the account without > stuffing up dotnetfx.exe. The account can definitely be deleted, as far as deleting it without breaking *ANY* dotnet application, I don't know. I would imagine that someday deleting that user would be looked upon as a mistake. > I've got a vbs script that will delete a user account but i would perfer > it if the account wasn't created in the first place. > Has anyone else tryed this and have any ideas? I think the source of the evil is that you are relying on a misfeature instead of allowing unattended to use the true AutoLogon settings in the registry. Is this related to the "Allow administrator password to be blank" thread from a few days ago? If so I'd recommend you set the administrator password to a known value, "password" for example, and then change it to /blank/ as a last step in unattended. ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
