Jump to content

eeark

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by eeark

  1. Run Sysprep and use the reseal option. Sysprep is in the deployment tools package.
  2. for /R %T in (*.*) do copy %T foldername or something similar - look at the help for the for command and also for the copy command. The /R switch tells the for command to walk the directory tree.
  3. That's not weird. It's always been like that. WU doesn't check whether your Windows would activate before letting you update.
  4. As long as you are using the same hardware you can install and activate as many times as you want. The problems come when you change hardware. One copy of Windows will activate on two or three DIFFERENT hardware configurations, or it will activate on the SAME hardware configuration any number of times.
  5. Hiya Long time lurker... first post I'm trying to make an unattended XP Home CD. I was having trouble with logging on automatically using AutoLogon=Yes in winnt.sif, then realised that XP Home doesn't normally allow you to logon with the "Administrator" account. So now I'm trying the method of adding a user account with net user, then changing the Registry setting to logon automatically with that user account. I have a batch file called useraccounts.cmd which is called from cmdlines.txt. It looks like this: net user tempuser tempass /add net localgroup Administrators tempuser /add net accounts /maxpwage:unlimited REGEDIT /S autologon.reg EXIT Trouble is, the user "tempuser" is not added to the Administrators group - it remains a "Limited User". That means my main batch file does not run when he logs on. I inserted a Pause command to check what was going on, and the system gives an error 1317 "the specified user does not exist" after the net localgroup command, even though the net user command completes successfully! And ideas? Cheers eeark!
×
×
  • Create New...