anyweb

hi there first of all look at this error which means it cant find the distribution point, so did you distribute the package and then update the distribution point for the package ? and for testing, disable the firewall on the clients for now and lastly, do an nslookup test from the client if it's not reporting the domain controller properly then things wont work oh and one more thing, make sure the client is listed as Client = Yes in the All Systems collection

does this post give you some ideas ?

good question and i'm in the process of investigating this as we speak, so watch this space..it's still beta remember ;-) but in the meantime have you had a look at your scanstate.log and scanstateprogress log files to see what errors they report ?, feel free to post them here. also checkout this brief intro to USMT 4, i'll post more info soon can you tell me what components you have installed so far ? sp2 beta ? r2 ? mdt 2010 beta 2 ?

Important: Windows XP is supported only as an operating system on the source computer. USMT 4 is a tool set from the WAIK for Windows 7 and Windows Server 2008 R2. Once you have installed WAIK you can find USMT 4 in the C:\Program Files\Windows AIK\Tools\USMT folder. There are two versions, one for 32bit (X86) and one for 64bit (amd64). There is a USMT 4 help guide (CHM format) located at C:\Program Files\Windows AIK\Docs\CHMs\USMT.chm For those that don't know here's an overview of where USMT was (USMT 3) and where USMT is today (USMT 4) In a computer Refresh scenario where users get to keep their existing hardware, in USMT 3, you would move files into protected locations on the disk (your USMT store), wipe the Operating System and then move the files back into their final locations. With USMT 4 we now have hardlinks, and with hardlinks we don't move anything, USMT indexes the user files and registry settings, then wipe the Operating system files around them (yes, in effect keeping the original files where they were in the first place) and then map the unmoved files into the operating system. I'd recommend watching this USMT 4 video walkthrough followed by this video of Migrating XP to Windows 7. The main advantage of hardlinking is speed, it's way faster than the old method. USMT 4.0 supports the ability to archive files that are in use by using the shadow copy feature in Windows 7 and Windows Server 2008 R2. for a full list of whats new in USMT 4 see the following Word Doc from Microsoft. The below info is taken from the CHM PC Refresh (keep your computer) The following diagram shows a PC refresh migration, also known as a computer refresh migration. First, the administrator migrates the user state from a source computer to an intermediate store. After installing the operating system, the administrator migrates the user state back to the source computer. Scenario One: PC refresh using a compressed migration store For example, a company has just received funds to update all of its computers to Windows® 7. Each employee will keep the same computer, but the operating system on each computer will be updated. An administrator runs the ScanState command-line tool on each computer. ScanState saves each user state to a server. On each computer, an administrator installs the company's standard operating environment, which includes Windows 7, Microsoft® Office, and other company applications. An administrator runs the LoadState command-line tool on each computer. LoadState restores each user state back to the source computer. Scenario Two: PC refresh using hard-link migration store For example, a company has just received funds to update the operating system on all of its computers to Windows® 7. Each employee will keep the same computer, but the operating system on each computer will be updated. An administrator runs the ScanState command-line tool on each computer, specifying the /hardlink command-line option. ScanState saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic as well as minimizing migration failures on computers with very limited space available on the hard drive. After quarantine of the hard-link migration store, an administrator uninstalls the older operating system. On each computer, an administrator installs the company's standard operating environment (SOE), which includes Windows 7, Microsoft® Office, and other company applications. An administrator runs the LoadState command-line tool on each computer. LoadState restores each user state back on each computer. Scenario Three: PC refresh using Windows.old and the hard-link migration store For example, a company has just received funds to update all of their computers to Windows 7. Each employee will keep the same computer, but the operating system on each computer will be updated. An administrator clean installs Windows 7 on each computer, making sure that the Windows.old directory is created by installing Windows 7 without formatting or repartitioning and by selecting a partition that contains Windows XP or Windows Vista. On each computer, an administrator installs the company’s standard operating environment (SOE), which included Windows 7 and other company applications. An administrator runs the ScanState and LoadState command-line tools successively while specifying the /hardlink command-line option. PC Replacement (get a NEW computer) The following diagram shows a PC replacement migration. First, the administrator migrates the user state from the source computer to an intermediate store. After installing the operating system on the destination computer, the administrator migrates the user state from the store to the destination computer. Scenario One: Manual network migration A company receives 50 new laptops for their managers, and needs to reallocate the 50 older laptops to new employees. An administrator runs the ScanState tool on each of the old laptops, and saves each user state to a server. On the new laptops, an administrator installs the company's standard operating environment which includes Windows 7, Microsoft Office, and other company applications. An administrator runs the LoadState tool on the new laptops to migrate the user states to the appropriate computer. On the old computers, an administrator installs the company's standard operating environment which includes Windows 7, Microsoft Office, and other company applications. The old computers are now ready for the new employees to use. Scenario Two: Managed network migration A company is allocating 20 new computers to users in the accounting department. The users all have one computer with their files and settings: the source computer. On each source computer, an administrator runs the ScanState tool using Microsoft System Center Configuration Manager (SCCM, a logon script, a batch file, or a non-Microsoft management technology. ScanState collects the user state from each source computer and then saves it to a server. On each new computer, an administrator installs the company's standard operating environment which includes Windows 7, Microsoft Office, and other company applications. On each of the new computers, an administrator runs the LoadState tool using Microsoft System Center Configuration Manager (SCCM), a logon script, a batch file, or a non-Microsoft management technology. LoadState migrates the user states from the migration store to a new computer. Scenario Three: Offline migration using Windows PE A company is allocating 20 new computers to users in the accounting department. The users all have one computer with their files and settings. In this scenario, each user's one computer will serve as both the source and destination computer. On each source computer, an administrator boots the machine into Windows PE and runs ScanState to collect the user state to either a server or external hard disk. On each new computer, an administrator installs the company's standard operating environment which includes Windows 7, Microsoft® Office, and other company applications. On each of the new computers, an administrator runs the LoadState tool, restoring the user state from the migration store to the new computer. Related Reading:- Migrating Data using USMT how can I use USMT 3.0.1 in SCCM migrate today restore tomorrow how can I view the USMT recovery key user state recovery information How can I use Offline Mode in Windows PE using USMT 4 Using a scanstate (using offlinewindir in winpe ) Task Sequence in SCCM 2007 SP2 Some Sample XP to Windows 7 task sequences showing Hardlinking hardlinking and SMP Migrate XP to Windows 7 using Offline mode in Windows PE screenshots describing the process and here are some helpful USMT 4 troubleshooting links:- * How USMT works * Step-by-Step: Basic Windows Migration using USMT for IT Professionals * Common Issues * Frequently Asked Questions - FAQ * Log Files - you'll need them, trust me * USMT 4 Return codes * Scanstate Syntax * How to Use Hard Links for User State Migration * How to Rename a file using USMT feel free to add yours to the list here... cheers niall

here's the problem <![LOG[Failed to download pxe variable file. Code(0x00000001) if you can verify that DNS is working perfectly via nslookup then.....I've seen this happening on Dell's and from google the recommended action i s to load the manufacturer's network drivers in the boot.wim and/or update the bios version to the latest so can you try that ?

as i said on the technet forums i'll need to see the SMSTS.log file to see whats going on can you attach it here ?

sadly for you i think the only option is to uninstall and reinstall WSUS pointing to the bigger storage unless someone has another idea...

have you applied any network drivers to the boot.wim image ? the drivers must be Vista network drivers and you must update the distribution points after updating the wim file

try changing the addresses used by WDS from the default 239.X.X.X to 224.1.X.X to be compatible with the default cisco configuration. Restart the WDS service after making the change. cheers anyweb

you can add a password to the pxe boot, that would be a help however as regards locking collections, you need to use Security Class and Instance permissions to allow or deny users access to that part of the configmanager gui

right here ! but first i'd need to know what you have setup and what you want to achieve (keep it simple)

i meant to use SCCM to do the deploying/managing of software applications and updates on the client computers, you can 'let' the users install or update their own software by letting them use the RAP (Run Advertised Programs) feature in ConfigMgr client have you considered this approach, it would simply and standardise your current approach especially if you have sccm in the network already

if you move to part 2 of deploy XP you will see that you do the following: it is only after XP is installed using the build and capture task sequence, that you can CAPTURE the image to a WIM file, that file can be called somexpcapture.wim or whatever.wim and you use THAT captured wim file to do your installs of XP in the future, it will be your install.wim file... i hope that makes it a bit clearer

the scripts can be copied over via a login script or whatever, that part is easy what is not easy is defining what the script needs to do and what user account should run the script but i have to ask, why are you doing things this way, why not use SCCM or similar to manage these computers ?

Note: Screenshots below taken from a Windows 2008 server Step 1. Set the Share Permissions To set the permissions correctly on the Driver Packages share make sure the following are selected Everyone = Reader SMSadmin = Owner SYSTEM = Co-Owner where SMSadmin is the user you are using to Administer the SCCM server (this account has local administrative permissions on the sccm server and is a member of the local administrators on that server) Step 2. Set the NTFS Security Permissions verify that the SYSTEM account has Full Control verify that the SMSadmin account has Full Control verify that the Everyone account has Read & Execute, List Folder contents, Read,

all that step 3 and step 4 are far is to create the ConfigMgr client package from definition and then to distribute it to a DP. After they are done you simply return to the guide, which is part 2 of Deploy XP

are they domain joined, if so the domain admin will have local admin permissions on these machines making it easy to place files and folders in the public desktop hiddent folder if not, then please explain

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

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 >

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

yes of course it's possible, it was only installed on a DC in this example because this is a test lab

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

no worries ! if you do find out if the ip helper works then please update this post

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.

perhaps you have to configure IP Helpers on the cisco switch to point to the DHCP server