Jump to content

BeenThereB4

Member
  • Posts

    225
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by BeenThereB4

  1. Are you or do you plan to have all your computers logging in as members of this domain? In the meantime, place these two files in the same directory and run the bat file on the client computers. You can rename the bat file to a short name. Make sure that the AutomaticUpdate service is running on the client and not disabled. Edit: Forgot to point out that you must edit the reg file to point to your server name! update.zip
  2. Latest word is that the PID checking in 2120 and up was such a disaster that Microsoft has reverted to tried and true blacklisting of known pirated keys. We'll all see what happens in RC2.
  3. Do you mean how to: Click on Start - Then Administrative Tools - then Computer Management?? Edit: No I think not. Maybe: Start - Run - MMC - Add --- File -- Add Remove Snap In --- Group Policy Object Editor
  4. Once again (Allanoll, where are you? Please insert sarcastic remark about searching.) --- use the search function -- asked and answered!
  5. This sounds like piracy, which is not condoned here. Anyway, we're defering to RyanVM's take on this until further releases can shed more light.
  6. Don't know then, because "legit" is in the eye of the beholder (Microsoft). As RyanVM says, let them straighten it out.
  7. I disagree. The topic as I see it (as started by gosh) is: Was the change in PID checking in SP2 build 2120 a bug, or increased checking by intent, or a combination of both? The evidence mounts to point towards the last: a buggy attempt to implement increased checking.
  8. I would be imaging the Compaq partition onto the drive, rather than creating it. This takes care of the type 12 automatically. Some versions (if not all) of ghost work under WinPE. Usually the partition is so small, you can have several images right on your CD. Ghost can be automated thru the command line.
  9. Hmmmm, build 2126 is just as restrictive about PIDs as 2120 or possibly more so. Looking less and less like 2120 was just a mistake.
  10. You might try having the autoit script start the install, that way the script does everything and then exits -- freeing up runonce to go on. Alternately, you could start the install from your batch file without a "wait", and then the script. In the second case, you might want to start /wait the script so that runonce knows to pause.
  11. Just made an XPcreate CD with all the current patches per GreenMachine's list. All is fine!
  12. Worst of all, Autopatcher is very old news. Like a lot of recent posts on this forum, a search would reveal that the supposed "news" was discussed here long ago. (Another example would be "Color in batch files" and on and on) That's why Allanoll (who does know what he's talking about and does use the search) has links to it in his sig)
  13. This is most likely an error in winnt.sif (I know it says inf, but most likely it's wrong). As a test, remake your winnt.sif from scratch or omit it (best of all). Then let us know.
  14. I must point out that with SUS and the proper settings on the SUS server and the clients, it's all automatic. It works the same as when you set up a client to auto-update from the WindowsUpdate site, except only the SUS server does the downloads from the Internet. The clients all auto-update from the SUS server. You are taking a coffee break while your peers are manually downloading updates and authoring GPOs.
  15. Of course it updates the clients! Otherwise, what would be the point. At least for Win2000 and XP clients, you just use some registry entries on the clients to point them to the SUS server. Easy as pie.
  16. If you have some technical expertise, you want to install SUS on your server. It's free from Microsoft.
  17. Ah Ha! It's looking like I may be the correct one after all.
  18. Good one, gosh! For a minute, I thought you were wrong. But, I've looked at your stuff and I know that you are a deeper thinker than that. You were right!
  19. Yep, it's a Trial Balloon to lure hackers and crackers into giving their thoughts and techniques away. You can be sure the delay in the final release is related to the "problems" with 2120.
  20. According to info in TweakUi, it can be easier than this for most "Special Folders". Simply Right Click on any "Special Folder", then drag to it's new location and select "Move Here". XP is smart enough to auto-fix the registry, etc. Will not work for the whole Documents and Settings folder, but will work for most subfolders.
  21. The downloaded drivers sometimes act as if they were loaded from CD. When it refers to CD, it really wants to be pointed to the location of the expanded drivers. Simple, huh!
  22. Normally case would not be relevant, but as a test I would match the case that is found in driver image path as a test: (I cannot think of anything else) System32\DRIVERS\WinRT.sys Match the capitalization exactly. If that does not work, usually a sys file is just another extension for an exe. Try renaming it to WinRT.exe and running it manually.
×
×
  • Create New...