Jump to content

IcemanND

Patron
  • Posts

    3,252
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by IcemanND

  1. You need to add the drivers to the image and preferably sysprep the box before capturing. If you sysprep the box you can add a driver folder to the image or on the network and have sysprep look there for the drivers.
  2. Ok, personally I go for Robocopy, but how about a utility that can copy a single source to multiple destinations? I have to make 20 copies of a thumb drive and Doing one at a time just sounds depressing.
  3. It is installed as a printer just delete the printer, either manually or via VBScript.
  4. IPC$ is a default share created by the OS. And if there are no other shared folders created that is the only thing to connect to. It is after an account name and password on the Windows 2000 system that has access to that share.
  5. open CMD window and type gpresult. if you want more information you can use the /v switch for verbose logging. But be sure to make the CMD window's buffer size larger first as the verbose report is larger than what will fit. You can use verbose /? to get all of the options.
  6. Yep, or you can create an ISO of the boot media and boot from the ISO. You will either need to change the default boot order in the VM's BIOS, or press ESC during the VM's power on to get the boot menu. Then you can capture just like you normally do on a physical box.
  7. Add the mass storage controller drivers for the physical machine to the vmware image. capture that image with ghost or your other favorite imaging software and deploy to the physical machine.
  8. It might help to post to the correct forum since this is a driver issue not an XP issue. MOVED. Also, as those webcam's are normally directly connected to the USB bus you will likely find that it will not work without SP2 as is is with many USB devices. MS greatly enhanced USB functionality in SP2.
  9. You can't. Well not exactly. If windows sees a folder already exists in the doc & settings folder with the same name as the user that is being created it will create a new profile folder. I have solved this two ways. 1. reload log in as that user, restart then log in as another user with admin rights and copy the old profile folder contents into the newly created folder <username.machinename>. 2. Move the user folder out of doc 7 settings before logging in and having the default profile created. then log in have the profile created folder will just be named <username>. If you use an image instead that knows of these users then you can do what you want because the user SID will be the same when you drop the image back down. But otherwise a new user SID is created each time.
  10. Group policy works from the top down. Any policy applied at an OU will apply to all objects in that OU and sub-OU's unless inheritance is blocked in the a sub-OU. The machines that are not getting the policies, do the policies show up when you run gpresult? are they in the same Ou as machines that work? Any errors in the event logs concerning group policies? Are they on the same subnet as working machines?
  11. Standard Windows Remote Desktop, all you have to do is set it up to connect on the second computer once and then you can connect to it any time you want. Though if someone else is on it it will result in you kicking them off unless you replace a couple off files to allow multiple users on the machine.
  12. By reloading I was referring to reinstalling the OS, only after you disconnect whatever device you had attached that is taking up the letters C-H, probably a card reader of some sort is my guess.
  13. Possible, yes. easy, no. worth the possible headaches usually not. You are better off reloading the machine so that the boot drive ends up being C: rather than trying to go through the registry and replacing every reference of I: to C:
  14. Doesn't matter, you can still use the VistaPE out of the WAIK and the diskpart utility to extend the partition.
  15. Merge two topics together. Please don't start a new topic when you already have one going with the same issue.
  16. The only guaranteed way to get them all is to either back them up manually, run multiple programs and merge the directories or use the original drivers. I wrote a driver backup utility which is available here in the forums and it is a real pain in the a** to deal with all of the different possible ways that a manufacturer can decide to install there drivers.
  17. or you could use VistaPE to extend the partition.
  18. This problem should go away if you have SP3 installed in your image. More info can be found at in KB931760
  19. I've also finished updating my guide and used both the current and the last version of the WAIK in my testing of the document and had no problems with deploying the image. No changes where made to the how to make and deploy other than additions. A co-worker is proof reading and testing to make sure I didn't miss anything and it should be posted later next week when he is done.
  20. Knew I had this information somewhere. Try this before you partition you drive. 1. Launch regedit 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT 3. On the Edit menu, point to New, and then click DWORD value. 4. Type LessThan4GB as the new entry name. 5. Right-click LessThan4GB, and then click Modify. 6. In the Edit DWORD Value dialog box, click Decimal. 7. In the Value data box, type 0, and then click OK. 8. Repeat steps 3 through 7 to add the following registry entries: • Between4_8GB • Between8_32GB • GreaterThan32GB Each registry entry must have a value of 0. 9. Exit Registry Editor. now partition, format and deploy your image and see if this helps.
  21. You failed to mention what Service Pack is in your initial XP build.
  22. Unfortunately that is very reliant on what you do/want. And this is just for starters. I'm sure you have services running that could be turned off also but those run under various svchost proceses. If it was my machine here is what I would kill: searchindexer ccsauth windowssearch ituneshelper rrservice tvtsched searchprotocolhost searchfilterhost scheduler_proxy ipodservice printscreen rrpservice tvt_reg_monitor_svc mdm mDNSResponder awaysch applemobiledeviceservice msmsgs Ones I don't recognize that are worth a further look: ashserv ashwebsv ashdisp odhost acsvc ccc You also appear to have some form of SQL running, if it is not needed turn it off. There are also a number of other thinkpad/lenovo/ibm proccesses running that you will have to look at individually and decide if you want to leave them running.
  23. Ahh, yes. The lovely default process overload of Lenovo's build. Yes you can turn off a lot of that stuff. Get Autoruns - from http://technet.microsoft.com/en-us/sysinte...s/bb963902.aspx and select those you don't need and either disable them or delete their entries.
×
×
  • Create New...