wdge

Read the first reply I posted, it explains how you create a package containing the files you want to copy. Then just use that package inside your Task Sequence.

But why not just place those files inside of the package-folder and use %~dp0?

I recently injected a driver named "Realtek PCIe GBE family" into our boot-image to make some Lenovo models work. I used the driver from: http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/g3r104ww.exe You can find it if you search for L430 at their pages. Remember not to inject the whole blob while you import the drivers. You'd want to import them first, then browse through the drivers to find the correct one "RealTek PCI GBE Family Controller". There should be 2 (one for x86, one for x64), you'd probably want to use the x86 one (since your boot-image is likely x86).

http://lmgtfy.com/?q=can+I+upgrade+from+sccm+2007+to+sccm+2012 In other words: Upgrading is not possible, but you can migrate over your packages etc. from the old server to the new one.

I don't understand why you would need the severname, care to explain? To be clear: the UNC path (with servername) that you define when you make a package is only the source location. SCCM wil make a package out of the files in the folder and distribute that package to other DPs, so the source location won't really be used in deployments.

I usually troubleshoot installations as follows: Advertise the program to a collection with the machine, make it available (not required) Open the software center (Start > all prog > MS System Center 2012 > Software Center) Start the installation of your program Look at the status while it's installing Monitor the log-file "C:\windows\CCM\Logs\execmgr.log" on the client (with the tool cmtrace.exe) while it's installing the package. (it should give you a hint as to what's going wrong) I would also try to have the program say only "setup.exe", if it seems to be a problem with the installer you could also add /L*v! C:\Verboselog.txt to the program to get a log file out of the installer itself (haven't tried it myself though).

Something like this might do the trick: select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like "%SQL Server%" or SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "%SQL Server%"

It's the same as making a user in the GUI (local user & groups), meaning the user would be a member of the default "users" group. It would not be a member of the administrator group though which I'm guessing is what you are asking about.

Might be a stupid question, but why do you want to use a UNC path for this? The file is located on the DP, correct? So why not just place the file in a folder, referance that folder when you create a package and use %~dp0 when you are going to copy the file? Example: Make a folder on your main sccm-server (i.e: E:\Sources\Applications\MyApp\<Version>) Inside of that folder you you create a new folder contaning the files you want copied make a bat-file in the root-folder that says something like: xcopy "%~dp0FolderWithFilesIwantToCopy" "C:\Temp\Example\MyDestination" /C /R /H /K /Y /I /S :: %~dp0 contains the running dir path, so you can use it no matter what distribution point the client got the package from :: Other stuff you might want to do... Make a new package in SCCM, and referance the above folder in "this pacakge contains sources files" in the first window of the wizard. But use UNC (\\myserver\Sources\Applications\MyApp\<Version>), remember to share your "sources" folder first In the program window choose the bat file Basic example if incase you are new, otherwise pardon me for boring you

I use the following in a bat-file: :: Creates the local user net user myUsername /ADD /expires:never /PASSWORDCHG:NO :: Set the password net user myUsername myPassword :: Set the password to never expire WMIC USERACCOUNT WHERE "Name='myuserName'" SET PasswordExpires=FALSE

Strange, I was under the impression you couldn't have DHCP installed on a server with WDS

When you network-boot your VM, how far does it actually get? Do you recieve an IP, can you see it downloading the WDSNBP-file and trying to contact the SCCM-server? If not, how is the WDS-service looking on your PXE-server (is it running?). Also, check the SMSPXE.log under "<installDrive>:\Program FIles\SMS_CCM\Logs" If WDS is looking fine, have you deployed your TS to a collection were you know the VM is a member (like all uknown computers), and is the "make avaialbe to boot media and PXE" checkbox active under "deployment settings" for the advertisement/deployment of the TS?

I finally solved it! The problem: The local administrator password on the Image did not match the password specified in the task sequence under "Apply Windows Settings". The solution: Since I had no clue what the local password was on the image. I deployed the image to a computer, changed the local admin password to match the TS and re-captured via a capture ISO.

I don't understand why you are using collection variables (Vres & Hres) in my example? What does that accomplish compared to typing the values in directly?

How does the "Setup Windows and ConfigMgr" step look like in your TS? Did you change the default package? (see step5 in http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/) You say you only got a few actions in the client, so I actually assume the installation went through. Did you check to see if the site code is detected correctly? Also, you might try to update the collections memebership as I've seen that help in some cases where you only got a couple of actions in the client, although it souldn't really be needed since you installed the client during OS-deployment..

http://technet.micro...y/gg682077.aspx Only XP/2003 and above are listed under "Operating System Requirements for Configuration Manager Client Installation"

AFAIK that trick only work post-winPE. So for the first half of your TS you can't use that method. What I'd do is: 1)get setres.exe (http://www.iansharpe.com/setres.php) 2) make a package out of it, with no program 3) creat a run commandline step running "setres.exe H1024 V768 b16" with your package selected at the "package" checkbox

Did you solve it? I got the exact same problem. x86-image working fine, but no progress bar in x64-image (used the same images in CM07 without problems). SMSTS.log: Executing command line "C:\Windows\System32\sysprep\sysprep.exe" /quiet /generalize /oobe /quit Failed to show task sequence progress dialog. Error code 0x8001010e