Jump to content


pss53

Established Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About pss53

  • Rank
    Newbie
  • Birthday 03/19/1983

Profile Information

  • Gender
    Male
  • Location
    Leeds, UK
  1. Kicked it off again without booting into Windows PE and it appears to be working, just hope that I can deploy this now with drivers that didn't work in the build and capture process... Do you know what Registry hack I need to put in my deploy to stop it auto logging in ?
  2. Niall, I've tried running this on the machine that I couldn't get to build and capture It runs the first part fine, but then it restarts into windows PE and tries running the registry hack again which isn't supported in windows PE... I kicked this off from RAP ? Not sure what I'm doing wrong do I need to cancel the boot into windows PE ?
  3. Hi Wondered if anyone could help me... I setup a KMS server on a 2003 box for office 2010 which works fine. I've read through a few guides on windows 7 activations also... So I went ahead and did a slmgr -ipk [PRODUCTKEY] but when I do a slmgr -dlv It's showing me unlicensed? Could it be the wrong product key ? All the updates are installed and I'm running 1.2 KMS? Any idea? Would an idea to have a 2nd KMS server running on a 2008 box for windows 7 ?
  4. Looking into SMSTS.log I can see Content location request for SP100014:1 failed. (Code 0x80040102) But looking through all my packages, os & task sequences I cannot find a reference for SP100014 ???? Any ideas? I'm thinking it must be something to do with my scan state package...does it need a program ??? I've just dropped the batch file into a folder and pointed the source files to that folder in the package?
  5. I seem to be getting a weird error... The task sequence execution engine failed executing the action (xcopy X86 USMT to USMTbits\X86) in the group (xcopy) with the error code 4 Action output: es\sp10002b\x86\replacementmanifests\microsoft-windows-terminalservices-licenseserver is a directory. Setting directory security c:\_smstasksequence\packages\sp10002b\x86\replacementmanifests\usb is a directory. Setting directory security c:\_smstasksequence\packages\sp10002b\x86\replacementmanifests\windowssearchengine is a directory. Setting directory security Content successfully downloaded at C:\_SMSTaskSequence\Packages\SP10002B Resolved source to 'C:\_SMSTaskSequence\Packages\SP10002B' Set command line: Run command line Working dir 'C:\_SMSTaskSequence\Packages\SP10002B' Executing command line: Run command line ‰????????Process completed with exit code 4 Command line returned 4 Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\SP10002B reference count 1 for the source C:\_SMSTaskSequence\Packages\SP10002B before releasing Delete source directory C:\_SMSTaskSequence\Packages\SP10002B Invalid drive specification Released the resolved source C:\_SMSTaskSequence\Packages\SP10002B. The operating system reported error 4: The system cannot open the file. It creates the two folders for USMTbits & Offline? sp10002b is my USMT package??? I've tried updating the DP? Any ideas? It only seemed to stop working since I put the workaround path into XCOPY.... This is the path I'm using... xcopy %_SMSTSSP10002B%* %USMTDrive%\USMTbits /herciy
  6. I had this problem, when using the .wim file it automatically puts it onto D:\ but when using the original source CD it installs happily on C:\ What I did was edit "APPLY OS" part in the task sequence and chose the destination as "specific logical drive letter" That worked for me...
  7. I followed the guide on this site to get my deployment of Windows 7 working. Now I have my image, I'm looking to incorporate USMT, what's the simplest way of doing this? I have looked at the following... http://www.windows-noob.com/forums/index.php?/topic/918-how-can-i-use-usmt-3-0-1-in-sccm-2007-sp1/ But cannot get my source machine to pick up the advertisement ? Is it an option to use the "CAPTURE USER STATE" in my deployment task sequence? Any tips or help would be appreciated... Thanks, Paul.
×
×
  • Create New...