Jump to content


anyweb

Root Admin
  • Posts

    9,108
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by anyweb

  1. anyweb

    deploy Windows XP

    without the boot images you wont be able to boot so yes you have to add the boot images. please take everything as it is in the guide, step by step
  2. It's been a three year long ride. Windows Vista was released January 2007, and its reception by the press was very negative, which made sure public perception was very negative as well. Sales were slow, people wanted Windows XP, and businesses didn't care about Vista either. Microsoft needed something that would make the world forget about Vista, and it needed it fast. The journey is over: Windows 7 has gone RTM. via > http://www.osnews.com/story/21879/Windows_...omplete_Hit_RTM video of the sign off >
  3. anyweb

    deploy Windows XP

    you must do these bits first Create a Package from Definition for the ConfigManager Client complete the following Step (step 3). Create distribution point and then update it complete the following Step (step 4) and then do all of this > Deploy XP part 2 and you must extract the contents of the ISO to a folder and use that folder as the xp install package otherwise you won't install anything
  4. yes of course it's possible, it was only installed on a DC in this example because this is a test lab
  5. have you tried refreshing, and have you followed all the steps in the guides properly ? yes WDS takes some work but once it\s setup its straightforward to manage
  6. no worries ! if you do find out if the ip helper works then please update this post
  7. Problem: Solution: Insert the Windows XP CD, reboot computer with it in, choose option R for recovery console then copy d:\I386\Driver.cab c:\system32\ntoskrnl.exe /v where d: is the drive letter of your cdrom drive if using a Swedish OS (or non-english) try leaving the /v out once copied, type Exit to exit and remove the cd.
  8. perhaps you have to configure IP Helpers on the cisco switch to point to the DHCP server
  9. hi, you just need to sysprep the image, download the XP SP3 deploy.cab file and extract its' contents to a folder called sysprep. Then follow these instructions http://support.microsoft.com/kb/302577 Note: if you are trying to deploy XP SP2 then use this one instead.
  10. enable F8 command prompt support in your boot.wim (check the troubleshooting section here for details on that) and read you smsts.log file
  11. ok there are some issues with capturing Windows Vista sp2, (sorry that i missed that point in your original post) have you read this thread on Technet yet ?
  12. when do you get the unknown operating system, is it after you have imaged the client ? what WIM file did you use in the task sequence ?
  13. please look at the site status component logs in configmgr instead, what are the logs saying in there
  14. Beginning next month Microsoft will start an upgrade to the Windows Update and Microsoft Update services. Microsoft plans to start the infrastructure update in late August, claiming "it will take a couple of months to complete the rollout." The update is required to "maintain and improve service quality, reliability, and... more > http://www.neowin.net/news/main/09/07/16/m...-windows-update
  15. is it the only problem listed in your site status
  16. right click on the client in the collection and choose 'approve'
  17. ok you'll have to tell me exactly how you've setup your wds server
  18. hi Peter, to be honest all you have to do is start a build and capture task sequence (exactly like the one for Deploy Vista), then once you've made the task sequence, simply disable the entire build section (or delete it) like this screenshot of a capture TS for XP and advertise the TS to a capture collection then add a computer or computers to that collection and the capture task sequence will be advertised to them easy
  19. well you could remove that machine from the collection the advertisement is advertised to, then run a machine policy retrieval and evaluation cycle in the Config Manager client (in control panel) on the client or just remove the advertisement and refresh machine policies on the client.
  20. ok first things first, did you read the README that comes with sp2 beta ?
  21. did you install mdt 2010 beta as well ? are you testing this with real hardware or in virtual machines
  22. ah well we use SCCM here, hence the SMS in the filename, but glad it's working now
  23. can you remove the advertisement of that program for that machine ?
  24. ok you must have missed that in the guide then http://www.windows-noob.com/forums/index.php?showtopic=491 glad to hear it's working now though
  25. ok then try pushing a new advertisement to it, eg: firefox make sure the firewall is disabled on the client for the test
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.