anyweb

to be clear, the defuser process explained here is to apply a registry change to All Users (using a task sequence) while the video above, is to apply registry changes to the current logged on user only and does not involve any task sequence and does not use the defuser process at all. ok ?

ok i've done a very quick test in CM12 and created a simple package and program to deploy registry settings to a user, it worked fine and i did a little video which hopefully helps you resolve this once and for all, in the video you can see that the registry keys do not exist prior to running the package in Software Center, the package is deployed to a Device Collection as available. I can run/test this over and over by deleting the registry keys on the client and then re-running the package from software center. the key takeaway here is that I use the defuser process in a task sequence to apply the change to ALL Users, but in this example I apply a change only to the current logged on user so the Defuser process is not used at all.

ok i'll test it out here and post something as soon as i can

ok is your goal to apply the reg key via a package instead of via a task sequence ?

i'm not following you exactly, the registry settings that you export are whatever keys you'd normally export (for HKCU) except that you must modify any HKCU paths to instead point to HKLM\Defuser if using the process I explained above

in applications you have 'detection method' which can be used to detect for installed apps in many many ways (registry, msi, path, file)

hey Garth why do the reports not give powermanagement info on vms ? are they excluded due to being virtual ?

check your firewall, test by disabling it and see does it work, if so you need to open the appropriate ports (udp)

which report are you running ?

drive letter being D: before the reboot is totally fine, what i was looking for is logs relating to your apply operating system step, you may have to search on c: or D: for more logs or increase the logging capability or add a pause before and after that step.

your client is in a workgroup so being in an AD SITE boundary will not work ! try the boundary trick, it takes only a few minutes to do, i had the Execution status received: 24 (Application download failed ) InstallApplication 5/7/2014 2:02:01 PM 2988 (0x0BAC) problem and it solved it for me.

start by learning how USMT works, and to do so i'd recommend you read this old post i wrote. Create two custom task sequences as it describes and start testing capture user state (get that working first) and once it's working 100% everytime, then test restoring that data in a separate task sequence, once you have mastered that, you can start looking at the complexity that there is in refresh scenarios. You obviously wobn't be using USMT 3 listed in the guide, however you can use USMT as provided in your ADK (assesment and deployment kit), here are the usmt requirements http://technet.microsoft.com/en-us/library/hh824913.aspx and here's the version of ADK used in your version of Configuration Manager - http://www.microsoft.com/en-us/download/details.aspx?id=30652

no errrors in that log are you sure it was the right one ? check in x:\windows\temp\smstslog

if you use the mdt integrated task sequences they have multiple steps for dealing with partitions, are you ?

SCEP should be able to automaticallyt uninstall Microsoft Security Essentials, however i'd test it first on a test system and see what happens.

please attach your latest smsts.log files and i'llt ake a look

it's pretty easy, here's how, follow Justins guide below. http://setupconfigmgr.com/installing-a-secondary-site-configuration-manager-configmgr-2012-sp1/ cheers niall

is your device in a boundary ? I usually create a boundary that is a one-ip iprange for my build and capture virtual machine,

well you are doing something wrong, please re-read the guide and follow the steps from start to finish and be precise, if you don't you'll probably get unexpected results,

set it to apply to osdisk (the variable used in the format step)

this should give you some ideas (it's for USMT 3.x and CM2007 but you'll see past that) http://www.windows-noob.com/forums/index.php?/topic/918-how-can-i-use-usmt-3-0-1-in-sccm-2007-sp1/

well what is the target set to, scroll up in the log

ok well you could try to add a step immeditaly after the udi wizard step which is a Set Task Sequence Variable and set the variable OSDStateStorePath = NULL try that

search for the mac address of the computer you are booting in Configuration Manager, if it's found, then the device is not unknown, it's known.

that is not the entire log, are there no more logs in the C:\Windows\Ccmsetup folder or subfolders ?