anyweb

did you update your sccm configmgr client to the sp2 version ?

no don't do that, the boot image that it didn't update, what is it called and what version is it currently, is it an mdt or custom boot image ?

i'd suggest you read this topic while you are at it, it'll show you how to find the right logs good that its working now cheers niall

create a reg file with the value required (simply export that key and save as a reg file) then make a package of that file and run it using the same method i use in this post (look at where i use a reg file for autologin) does that help ?

hmm that log looks fine, are you sure there are no other smsts.log file present, with a name like smsts-20100113-110024.log ?

please just upload it here....

can you post the entire smsts.log file i'd like to see it

is sccm in mixed or native mode ? what are you seeing happening on the client when it pxe boots now ?

did you see this then ? Install multiple applications Select this option to configure the Install Software task sequence step to install multiple applications in sequence. This step specifies the base variable name for a series of task sequence variables that each contain a <packageID: program name> pair separated by a colon. The series of variable names is formed by appending a numeric suffix between 001 and 999 to the specified base name. The variable names and associated values form a dynamic package list. The list of packages ends when no variable name exists with the next sequential numeric suffix. The associated packages will be installed in the order specified in the list. Each package installation will be completed before the installation for the next package begins. When you specify the Package ID always specify the Package ID using uppercase. The program name is case-sensitive and must exactly match the name assigned to the program when it was created. Virtual application packages distributed via the Configuration Manager 2007 R2 application virtualization feature cannot be distributed as part of a list of multiple applications. If the value of a variable is not created in the correct format or does not specify a valid package ID and program name, the installation of the package will fail. If no variables with the specified base name and "001" suffix are found, no packages are installed and the action succeeds. The program you select must meet the following criteria: * It must run under the local system account and not the user account. * It should not interact with the desktop. The program must run silently or in an unattended mode. It must not initiate a reboot on its own. The program must request a reboot using a 3010 return code. This ensures that the Install Software task sequence step will properly handle the reboot. For example, to install a single application by using a task sequence variable called AA001, you specify the following: Variable name: AA001 Variable value: CEN00054:Install To install three applications, you would specify the following additional variables: Task Sequence variable: AA002 Value: Package CEN00107:Install Silent Task Sequence variable: AA003 Value: Package ID: CEN0031:Install ImportantImportant The program specified must have the Allow this program to be installed from a list of software packages in the “Install Software” task sequence step without being advertised option selected or the installation will fail. This option can be selected when adding a program to an existing package in the New Program Wizard. Alternatively, you can specify this option by right-clicking an existing program, selecting clicking Properties, and then clicking the Advanced tab. If an application installation fails, continue installing other applications in the list Check this box to have the Install Software task sequence continue in the event that an application installation in the list fails. If this box is not checked and the installation fails, the task sequence step will end immediately. If the box is checked, the next package or program in the variable list is installed regardless of errors. http://technet.microsoft.com/en-us/library/bb680842.aspx

was the computer domain joined before you did OSD on it ? or did you join the domain during the task sequence...

if you restart the Windows Deployment Services service, does it make any difference to the error message ?

well your problem sounds like this one exactly does that help ?

hi Rik have you seen this post yet ?

check the firewall on the client and try again

cost wise, mdt and wds are your best bet, but if money is no object, then try SCCM wich can utilise wds, mdt and a whole lot more, however back to deploying, with wds you can deploy the os's or capture them but don't expect any thing fancy, with MDT you can deploy the images with custom applications and settings and many many options, and with SCCM you can do it all and then some, including managing everything after deployment (think about Seucify patches...) hth cheers niall

I came across this today, the USMT error codes in USMT 4 are different to the USMT error codes in USMT 3. For example: in USMT 3 error 38 means USMT_ERROR_USE_LACand in USMT 4 error 38 means USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE. So to avoid any confusion here are both: USMT 4 error codes here's the USMT 4 error codes - http://technet.microsoft.com/en-us/library/dd823291 (they are too long and detailed to paste here) USMT 3 error codes and here's the USMT 3 error codes - http://blogs.technet.com/deploymentguys/archive/2009/01/14/usmt-error-codes.aspx Error code Error text 0 USMT_SUCCESS 1 USMT_DISPLAY_HELP 2 USMT_MEMORY_FAIL 3 USMT_INVALID_PARAMETERS (Bad command line) 4 USMT_INVALID_STORE_LOCATION 5 USMT_NO_MORE_TOKEN 6 USMT_UNABLE_SET_SCRIPTFILES 7 USMT_UNABLE_GET_SCRIPTFILES (Can’t find XML file(s) specified in the command-line) 8 USMT_UNABLE_SET_STOREPATH 9 USMT_UNABLE_SET_USERS 10 USMT_UNABLE_FINDMIGUNITS 11 USMT_UNABLE_DOMIGRATION (A file is in use) 12 USMT_FAILED_MIGSTARTUP (Error in XML file ‘Bad XML’) 13 USMT_FAILED_SETMIGRATIONTYPE 14 USMT_FAILED_LOCALONLY 15 USMT_UNABLE_GET_WORKINGDIR 16 USMT_UNABLE_SETKEY 17 USMT_UNABLE_READKEY 18 USMT_TOO_LONG_KEYSTRING 19 USMT_UNABLE_SETCOMPRESSION 20 USMT_ERROR_INSUFFICIENT_RIGHTS 21 USMT_UNABLE_DELETE_STORE 22 USMT_UNABLE_SET_BENONADMIN 23 USMT_ERROR_INSUFFICIENT_STRINGBUFFER 24 USMT_ERROR_UNSUPPORTED_PLATFORM 25 USMT_ERROR_UNABLE_TOVERIFY_PLATFORM 26 USMT_UNABLE_SET_EFSMODE 27 USMT_INIT_ERROR 28 USMT_UNABLE_SET_LAC_LAE 29 USMT_ERROR_CORRUPTED_ENCRYPTED_STORE (Store is encrypted and no or invalid key has been specified) 30 USMT_ERROR_NO_INVALID_KEY (Store is only compressed but a key has been specified) 31 USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE 32 USMT_ERROR_LOGFILES_INSIDESTORE 33 USMT_INVALID_PLATFORM_FOR_TARGETXP 34 USMT_STORE_VALID_ONLY_FOR_XP 35 USMT_UNABLE_TO_READ_CONFIG_FILE 36 USMT_INVALID_CONFIG_FILE_FORMAT 37 USMT_ERROR_UNABLE_CREATE_LOGS 38 USMT_ERROR_USE_LAC 39 USMT_FAILED_TO_EXCLUDE_FOLDERS 40 USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG 41 USMT_STATUS_CANCELLED

now that is working you can add your photo to the members photos section if you want to of course

yup, you have the right idea

odd that it happened in the first place, glad you solved it

is the autopcc.exe file coming from you or from the maker of the software ? perhaps it is your problem, when creating packages (ie: packaging an application) I always try to use the original source software from the vendor, and install it as natively as possible, usually as an MSI with accompanying mst or a vbs scripted install

Today we are announcing the opening of the Technology Adoption Program nominations for the next release of System Center Configuration Manager. The Technology Adoption Program is designed to provide a consistent experience for Microsoft customers to obtain real-world customer feedback on Microsoft pre-release products. There are many benefits for our TAP customers, to name a few: * Lead the market by adopting critical enabling technologies early * Influence and shape the final product by providing early and deep feedback * Connect with expertise to obtain a deep understanding of strategic emerging technologies Building on over 14 years of systems management industry experience, Configuration Manager (formerly SMS) is the world leader in software distribution, OS deployment, HW/SW inventory and more. Moving forward, there are both new capabilities as well as enhancements to existing product functionality that form the investments for engineering. Over the coming year the next release of Configuration Manager will move into a public beta. Even at this early stage, we want to ensure that it is the highest quality release possible; the TAP program helps significantly in this effort. I would like to highlight for you briefly what the investment pillars for this next release are, and over the coming months we will continue to go deeper on these areas with different product folks through interviews, online chats and other forms of content. The next release of Configuration Manager will focus on a few main areas: * Improving client management experiences through enhanced, integrated software distribution models. The next release of Configuration Manager will provide a framework for the right application format to be delivered to the user based on who they are, the device they are using, and their connection. * Infrastructure improvements are also a main focus. Optimizing site hierarchy, replication and content distribution on the backend. For the managed client, improving client health and remediation capabilities will ensure that when a system is managed, it remains healthy and secure. Part of this is also improving the Admin experience. In the past we did this by reducing mouse clicks to get through an activity. This is only part of the process. Adding security models to enable role based administration, as well as improving the Admin console experience will ensure that Admins are more efficient everywhere. * In addition, other areas of focus include expanding device management scenarios, model based configuration management and improving patch management services; just a few of the places we are focused on development. We hope to see a strong interest in this TAP program, and we want to ensure as many organizations are engaged as possible. The team is limited in resource, and as a result, not every TAP nomination can be accepted. Completion/Submission of the TAP nomination form is not a guarantee of acceptance. All completed nominations are evaluated to ensure the right fit, priorities and alignment of goals are present. The TAP is not your only avenue to access the next release of ConfigMgr. There are other ways you be able to experience the product before release, such as the public beta programs. Stay tuned to this blog for further announcements. Link to Nomination Survey is here. More information about the Microsoft TAP program can be found here. System Center product information can be found here. Thanks for your time Jeff Wettlaufer Sr. Technical Product Manager System Center http://blogs.technet.com/systemcenter/archive/2010/01/08/the-next-wave-of-client-management-begins-now.aspx

how have you created the package ? is there a script ? or an msi ? is this program available for download so that I can take a look ?

it should work now cheers niall

the error means exactly as it says, sit back and wait and try again reading the logs on the server will help you know when it's ready

just use the one you get from Microsoft's volume license site, (technet or msdn) the VLK cd is always the best one to use in conjunction with the volume license key itself cheers niall